Skip to content
Back to skills

Writer

ASecurity

The Writer role — drafting sections, revising, polishing, or writing discussion for any project; also finding sources and checking quotes. Triggers on "draft this", "revise this section", "polish", "help me write", "find sources on X", "verify these quotes". Drafts through a six-phase pipeline (independent draft → evidence → integrate → blind critique → revision → audit); notes orient, they never cite; the Writer takes every verbatim quote itself at the source page (shared/evidence-handbook.m...

  • 5 stars
  • 0 votes
  • 0 copies
  • 4 views
  • Added September 29, 2026
researchgo

Security analysis

A100/100

Scanned September 29, 2026

npx -y skills add kengo006/alexandria --skill writer --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Writer?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Writer
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/kengo006-writer/badge)](https://www.skillsdirectory.com/skills/kengo006-writer)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: writer
description: The Writer role — drafting sections, revising, polishing, or writing discussion for any project; also finding sources and checking quotes. Triggers on "draft this", "revise this section", "polish", "help me write", "find sources on X", "verify these quotes". Drafts through a six-phase pipeline (independent draft → evidence → integrate → blind critique → revision → audit); notes orient, they never cite; the Writer takes every verbatim quote itself at the source page (shared/evidence-handbook.md) and dispatches the Searcher only for a large topic's complete sweep or the final audit, with the author's approval; delivery requires the audit's support-status list.
---

# Writer (wrapper)

Authority lives in the master file — this wrapper only loads it.

1. Read `governance/role-division.md` (constitution).
2. Read `roles/writer.md` — six phases, modes A/B/C/council, all disciplines.
3. Read `shared/evidence-handbook.md` — the evidence rules you take quotes by.
4. Read your project's style module (`style-modules/`).
5. Orient: `notes/vault-map.md`; ongoing projects: the project front door (`_entry.md`), criteria card, asset files.

**Digest of red lines** (master wins over this list):
- **You take the evidence**: search the vault, then take every quote and page number from the source page, with the printed page number you saw. Notes/MOCs orient, they never cite; note quotes never enter drafts. Whatever a dispatched Searcher returns, re-check at the page before it ships — criterion is destination, not phase.
- **Dispatch the Searcher only for two jobs** — a large topic's complete corpus sweep, and the final audit — and only after the author approves the scope and purpose.
- Judge the mode first (discuss / write / report / council); unsure → discuss, and ask.
- Council mode = **independent read-only advisory seats** (≤2, blind — the lead's position is withheld from seats); the lead takes the evidence.
- Write only inside the project folder; never the vault.
- Delivery gate: no audit, no delivery — support-status list attached, every cited claim anchored, quotes as complete passages.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…