Write Review Artifact
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.
Install
/plugin marketplace add lyndonkl/claudeThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add lyndonkl/claude --skill write-review-artifactgit clone --depth 1 https://github.com/lyndonkl/claude.git /tmp/claude
mkdir -p ~/.claude/skills
cp -r /tmp/claude/skills/write-review-artifact ~/.claude/skills/write-review-artifactPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Write Review Artifact
## Output schema
```yaml
---
agent: technical-reviewer
version: 1.0
draft_path: corpus/drafts/{slug}.md
draft_sha256: {hash}
reviewed_at: ISO8601
topic_hint: {string or null}
total_claims: N
counts:
simplified-correct: N
simplified-boundary: N
wrong: N
contested: N
overclaim: N
blockers: N # count of wrong claims
glossary_alignment_notes: N
go_no_go: GO | GO-WITH-HEDGES | NO-GO
timebox_used_hours: N.N
---
```
## Body sections (exact order, no exceptions)
1. `## Summary` — one paragraph, plain English, counts + verdict.
2. `## Blockers` — every `wrong` claim, numbered, excerpt + why-wrong + primary source + suggested fix. Empty section if zero.
3. `## Claims` — full per-claim table: #, excerpt, location, classification, confidence, primary_source, action, note.
4. `## Boundary-Break Suggestions` — for every `simplified-boundary`.
5. `## Glossary Alignment` — terms where writer's glossary diverges from field. Empty if zero.
6. `## Could-Not-Verify` — claims where primary source was paywalled / unreachable / not findable.
7. `## Research Log` — queries run, sources fetched, time spent. Audit trail.
## Go/no-go rule (mechanical)
- `blockers = count(wrong)`
- If `blockers > 0` → `NO-GO`.
- Else if `contested + overclaim > 0` → `GO-WITH-HEDGES`.
- Else → `GO`.
## Guardrails
1. Never emit GO if blockers > 0.
2. Never omit Could-Not-Verify section, even empty — an empty section is the positive signal.Details
- Skill name
write-review-artifact- Repository
- lyndonkl/claude
- Path
skills/write-review-artifact/SKILL.md- Repo updated
- 1 September 2026
FAQ
What does the Write Review Artifact skill do?
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.
How do I install the Write Review Artifact 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 Review Artifact popular?
It lives in lyndonkl/claude, which has 200 GitHub stars and 25 forks.
Related skills
Abstraction Concrete Examples
200lyndonkl/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.
Academic Letter Architect
200lyndonkl/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.
Adr Architecture
200lyndonkl/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.
Write Section Promise
200lyndonkl/claude
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.
Wc Captain Ladder
200lyndonkl/claude
Computes the optimal rolling-captaincy LADDER across a matchday's staggered kickoff sequence — the ordered captain candidates, the explicit bank-or-switch rules at each kickoff, and the captaincy_uplift that wc-fitness-eval folds into raw_xEV. Because the armband doubles the round's points AND can be MOVED during the round to a player who has not yet kicked off, captaincy EV is the expected value of the best outcome reachable by switching across the sequence — not a naive 2x of the top xEV player. Call from wc-matchday-tactician (to write MB2 of the matchday plan), from the strategists (to val
Write Weekly Digest
200lyndonkl/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.
Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.