Write Section Promise

Crafts the one-sentence promise a substacker section makes to its reader — specific, testable, non-overlapping with other sections, written in the writer's voice (not marketing). Use when propose-section stages a new section or when an existing promise is being revised. Trigger keywords — section promise, one-sentence promise, section statement, reader promise.

200 stars 25 forksWriting & Content Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add lyndonkl/claude

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add lyndonkl/claude --skill write-section-promise
Manual install
git clone --depth 1 https://github.com/lyndonkl/claude.git /tmp/claude
mkdir -p ~/.claude/skills
cp -r /tmp/claude/skills/write-section-promise ~/.claude/skills/write-section-promise

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Write Section Promise

## Four tests

A promise passes if ALL of:

1. **Specific** — reader can predict what a post in this section will do for them.
2. **Testable** — point at a candidate post and say yes/no.
3. **Non-overlapping** — distinguishable from every other section's promise by at least one axis.
4. **Voiced** — reads as the writer's voice per `audience-notes.md` + `voice-profile.md`, not marketing copy.

## Workflow

```
For a candidate section:
- [ ] Step 1: Draft 3 candidate promises
- [ ] Step 2: Score each on the 4 tests
- [ ] Step 3: Pick highest-scoring
- [ ] Step 4: If none pass all 4, flag and return best-with-caveat
```

## Worked example

**Section**: Intuition-first ML (candidate).

- Draft A: "Essays about machine learning." — FAILS specific, FAILS non-overlap (too broad).
- Draft B: "We break down ML concepts." — FAILS voiced (marketing tone), FAILS testable.
- Draft C: "Essays that build geometric or mechanical intuition for how ML systems actually work, before the math." — PASSES all 4. Winner.

## Guardrails

1. ≤25 words. Longer promises become paragraphs and no one reads.
2. No buzzwords. No "we dive deep into X" or "unlock insights."
3. One sentence, not two.
4. Second person or declarative — never "I argue…"
5. Must fit the writer's voice per `audience-notes.md` + `voice-profile.md`.
Read the full skill on GitHub

Details

Skill name
write-section-promise
Path
skills/write-section-promise/SKILL.md
Repo updated
1 September 2026

FAQ

What does the Write Section Promise skill do?

Crafts the one-sentence promise a substacker section makes to its reader — specific, testable, non-overlapping with other sections, written in the writer's voice (not marketing). Use when propose-section stages a new section or when an existing promise is being revised. Trigger keywords — section promise, one-sentence promise, section statement, reader promise.

How do I install the Write Section Promise skill?

Claude Code plugin: /plugin marketplace add lyndonkl/claude. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Write Section Promise popular?

It lives in lyndonkl/claude, which has 200 GitHub stars and 25 forks.

Related skills

Abstraction Concrete Examples

200

lyndonkl/claude

Builds structured abstraction ladders that translate high-level principles into concrete, actionable examples across 3-5 levels. Bridges communication gaps, reveals hidden assumptions, and tests whether abstract ideas work in practice. Use when explaining concepts at different expertise levels, moving between abstract principles and concrete implementation, identifying edge cases by testing ideas against scenarios, designing layered documentation, decomposing complex problems into actionable steps, or bridging strategy-execution gaps.

Testing & QA25

Academic Letter Architect

200

lyndonkl/claude

Guides the creation of evidence-based academic recommendation letters, reference letters, and award nominations that combine concrete examples, meaningful comparisons, and genuine enthusiasm. Use when writing recommendation letters for students, postdocs, or colleagues, or when user mentions recommendation letter, reference, nomination, letter of support, endorsement, or needs help with strong advocacy and comparative statements.

Research & Science25

Adr Architecture

200

lyndonkl/claude

Documents significant architectural and technical decisions with full context, alternatives considered, trade-offs analyzed, and consequences understood. Creates a decision trail that helps teams understand why decisions were made. Use when choosing between technology options, making infrastructure decisions, establishing standards, migrating systems, or when user mentions ADR, architecture decision, technical decision record, or decision documentation.

Software Development25

Write Weekly Digest

200

lyndonkl/claude

Renders the Trend Scout ranked keep-and-drop lists into ops/trend-scout/YYYY-WW-digest.md using the agent voice profile and including an appendix of all sources surveyed. Use once per weekly run as the terminal skill. Trigger keywords — weekly digest, write digest, Trend Scout digest, Saturday morning digest.

Writing & Content25

Write Review Artifact

200

lyndonkl/claude

Composes the final Technical Reviewer artifact at ops/technical-reviewer/YYYY-MM-DD-{slug}-review.md. Enforces frontmatter schema, section order (Summary → Blockers → Claims → Boundary-Break Suggestions → Glossary Alignment → Could-Not-Verify → Research Log), go/no-go decision rule, and never-modify-draft principle. Use exactly once per Technical Reviewer run as the last step. Trigger keywords — write review, technical review artifact, compose review, claim review output.

Writing & Content25

Write Weekly Report

200

lyndonkl/claude

Composes the substacker final ops/growth-analyst/YYYY-WW-report.md from ingest + baseline + attribute + per-section + public-page outputs. Enforces 400-800 word budget, YAML frontmatter schema, seven-section body structure. Truncates weakest sections first when over budget. Injects data-caveats from any degraded-mode flags upstream. Use as the final compose step of the weekly pipeline. Trigger keywords — weekly report, compose report, growth report, Monday report.

Writing & Content25

Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.