Skip to content
Back to skills

In Author Essentials

ASecurity

Authoring essentials: the outline -> draft -> detrope -> revise -> structural-check pipeline for prose and courseware, backed by the author rule pack and critic-prose

  • 26 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added September 5, 2026
ai-agentsrust

Security analysis

A100/100

Scanned September 5, 2026

npx -y skills add matthewsinclair/intent --skill in-author-essentials --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of In Author Essentials?

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

Security grade badge for In Author Essentials
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/matthewsinclair-in-author-essentials/badge)](https://www.skillsdirectory.com/skills/matthewsinclair-in-author-essentials)

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
---
description: "Authoring essentials: the outline -> draft -> detrope -> revise -> structural-check pipeline for prose and courseware, backed by the author rule pack and critic-prose"
chains_to: ["in-detrope"]
---

# Authoring Essentials

Load the authoring discipline for a project that writes prose or courseware -- books, courses, long-form articles. Chained from `/in-session` when `author` is a declared language. The rules live in the `author` rule pack (`intent claude rules list --lang author`); this skill is the pipeline that applies them, and `critic-prose` is the reviewer.

## When to invoke

- Chained from `/in-session` when `author` is in the project's `languages`.
- At the start of an authoring session, before drafting.
- When the user asks to write, edit, or review a chapter, module, or article.

## The two tiers

The `author` pack splits by how a rule is checked -- mirrored by `critic-prose`'s two modes:

- **style (mechanical, default)** -- greppable checks, cheap, run on every draft (`critic-prose review`).
- **craft (judgment, on instruction)** -- a read: voice, continuity, citation, and the full `/in-detrope` diagnosis (`critic-prose craft-check`, or `/in-detrope`).

## The authoring pipeline

Detrope at every step -- do not save it for the end:

1. **Outline** -- the spine first: parts, then chapters (book) or modules (course), in order. Each unit gets front-matter (`title` + an ordering key); courseware modules get learning objectives.
2. **Draft** -- write the unit in one voice and register throughout.
3. **Mechanical detrope** -- `Task(subagent_type="critic-prose", prompt="review <unit>.md")`: the mechanical trope pass + house-style checks. Fix the greppable tells before a human read.
4. **Revise** -- read for craft: voice, continuity against earlier units, citations. On instruction, `Task(subagent_type="critic-prose", prompt="craft-check <work>/")` and the full `/in-detrope <unit>.md`.
5. **Structural check** -- one H1, no skipped heading levels; front-matter and objectives present; a clean heading tree.

## Detrope: two forms, one home

detrope has one home -- `intent/plugins/claude/skills/in-detrope/data/trope-catalog.md` -- and two forms:

- **Mechanical (default)** -- `IN-PR-STYLE-004` greps the catalogue's `detection: automated` regexes. critic-prose runs it on every `review`.
- **Full LLM (on instruction)** -- `/in-detrope` does the contextual and stylometric diagnosis (`IN-AU-CRAFT-003`). Run it under direct instruction before publication; critic-prose only recommends it, never runs it.

Never fork the trope catalogue; both forms read the one home.

## Rules

The author discipline is the shared `IN-PR-*` prose base plus its own `IN-AU-*` rules -- read one with `intent claude rules show <id>` (`intent claude rules list --lang prose` / `--lang author`):

Prose base -- style (mechanical), shared with every prose discipline:

- `IN-PR-STYLE-001` -- banned filler and house style (`eg` not `e.g.`)
- `IN-PR-STYLE-002` -- no vanity metrics
- `IN-PR-STYLE-003` -- one H1, no skipped heading levels
- `IN-PR-STYLE-004` -- mechanical trope pass

Author-specific -- style (mechanical):

- `IN-AU-STYLE-003` -- front-matter and learning objectives present

Author-specific -- craft (judgment):

- `IN-AU-CRAFT-001` -- voice and register consistency
- `IN-AU-CRAFT-002` -- cross-chapter continuity
- `IN-AU-CRAFT-003` -- full `/in-detrope` diagnosis (on-instruction handoff)
- `IN-AU-CRAFT-004` -- citation and attribution

Declare the language with `intent lang init author`; its rules are then served by the installed Intent tool -- `intent claude rules list --lang author`, `intent claude rules show <id>`.

## Red Flags

| Rationalisation                                     | Reality                                                                         |
| --------------------------------------------------- | ------------------------------------------------------------------------------- |
| "I'll detrope at the very end."                     | Detrope every step -- tells compound and get baked in.                          |
| "The mechanical pass was clean, so it reads human." | The grep misses the contextual tells. Run `/in-detrope` before publishing.      |
| "It's just prose, no need to review."               | Voice drift, broken continuity, and fabricated citations are real defects.      |
| "One quote is fine without a source."               | A single fabricated citation poisons trust in the whole work (IN-AU-CRAFT-004). |

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…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.