AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified Apache-2.0 Self-run

Project Setup

skill-haowjy-creative-writing-skills-project-setup · by haowjy

>

No reviews yet
0 installs
3 views
0.0% view→install

Install

$ agentstack add skill-haowjy-creative-writing-skills-project-setup

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-haowjy-creative-writing-skills-project-setup)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
1mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Project Setup? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Project Setup

Guide the author through setting up their creative writing project. The goal is a working CLAUDE.md and directory structure that all agents read for project-specific conventions, plus initial style files if writing samples are available.

Learn About the Project

Ask about:

  • What kind of project: novel, short story collection, serial?
  • How far along: starting fresh, or existing chapters and worldbuilding?
  • Single POV or multiple? Linear or non-linear timeline? How much worldbuilding?
  • Where do they keep their writing? What's the existing layout?

Writing Samples and Style

Ask about writing samples: these are the foundation for style analysis:

  • Do they have sample chapters or scenes already written?
  • Do they have writing from other projects that captures the voice they want?
  • Are there published works they want to draw style inspiration from?
  • Voice goals: close third, omniscient, first person? Formal, colloquial?

Collect whatever they have. Save samples to kb/samples/ so they're available for future style analysis. If they have enough material, offer to analyze their style using the /creative-writing-craft methodology: read the samples, identify the voice dimensions, and produce initial style files in kb/styles/.

If they're starting fresh with no samples, capture their voice goals in CLAUDE.md so style files can be created from early drafts.

Propose and Iterate

Based on what you learn, draft a CLAUDE.md section and show it to the author. Cover:

  • Project overview: what the project is, one paragraph
  • Author's space: where the author keeps their writing and how it's

organized

  • KB structure: what subdirectories exist under kb/ and what they're

for. Suggest based on project complexity:

  • Simple (short story, single POV): characters/, canon/, styles/, root vocab.md
  • Medium (novel, few POVs): add timeline/
  • Complex (series, large world): add world/, issues/, and domain vocab files such as world/vocab.md
  • Voice and style: what style files exist, what samples they're derived

from, voice goals not yet captured

  • Conventions: anything project-specific: naming patterns, chapter

numbering, POV tagging, spoiler handling

  • Shared vocabulary: early canonical terms, aliases, invented words,

genre terms with project-specific meanings, and terms the author wants agents to avoid or distinguish

Present the draft and let the author adjust. Iterate until they're satisfied.

Create the Files

Once approved:

  1. Write or update CLAUDE.md with the agreed content
  2. Create the kb/ directories referenced in CLAUDE.md
  3. Create kb/vocab.md when the project has named concepts agents must use

consistently; create domain vocab files when a domain already has enough distinct terms

  1. Create work/ with standard subdirectories (outline/, drafts/,

critique-reports/, brainstorm/)

  1. Save any writing samples to kb/samples/
  2. If samples were provided and the author wants style analysis, produce

initial style files in kb/styles/

Existing Projects

If CLAUDE.md already has creative writing conventions, read it first and suggest updates rather than overwriting.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.