project-setup

What the source does

• FilesystemNone observedNo reads or writes in the source
• NetworkNone observedNo outbound calls in the source
• ShellNone observedNo commands run in the source
• DependenciesPinnedNothing floats
• SecretsNone foundNo keys in source

Five audit layers

Gates applied: no behavioural pass.

Audit 0.4.1 · source sha 91a3e8e990b9 · 26 Oct 2026Report an issue or request a re-scan

• Publisherhaowjy GitHub userOwner of the repository this skill is read from
• Source folderhaowjy/creative-writing-skills/cw/skills/project-setupThe exact folder we audited
• LicenceApache-2.0As the repository states it
• Commit pinned for this verdict91a3e8e990b9A new audit runs when the source changes
• Repository statusNot archivedLast push 1 day ago
• Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

Its description: One-time project setup for creative writing. Interviews you about your project, collects writing samples, proposes kb structure, and creates AGENTS.md with project conventions.

---
name: project-setup
description: >
  One-time project setup for creative writing. Interviews you about your project, collects writing samples, proposes kb structure, and creates AGENTS.md with project conventions.
---

# Project Setup

Guide the author through setting up their creative writing project. The goal
is a working `AGENTS.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
AGENTS.md so style files can be created from early drafts.

## Propose and Iterate

Based on what you learn, draft a `AGENTS.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 `AGENTS.md` with the agreed content
2. Create the `kb/` directories referenced in AGENTS.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
4. Create `work/` with standard subdirectories (outline/, drafts/,
   critique-reports/, brainstorm/)
5. Save any writing samples to `kb/samples/`
6. If samples were provided and the author wants style analysis, produce
   initial style files in `kb/styles/`

## Existing Projects

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

Excerpt, first 3,451 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

git clone https://github.com/haowjy/creative-writing-skills
git -C creative-writing-skills checkout 91a3e8e990b9

Works in

1. 2026-10-26
   ✓SAFE B 89 / 100

   first audit · source 91a3e8e990b9

Questions about project-setup

• github.com/haowjy/creative-writing-skills/tree/main/cw/skills/pr — the audited source at commit 91a3e8e990b9 and every finding aboveObserved · 26 Oct 2026

Spotted something wrong? Report a correction · Methodology