agentmods.dev

doc-critique

doc-critique is a skill for Claude Code from sananthanarayan/skilldrop. It costs 114 tokens per session (1,848 once invoked), scanned A, original, MIT.

A structured critique of an existing technical or business document against a quality checklist for its document type.

In plain words
What is it for?
Use it to review design documents, ADRs, runbooks, summaries, comparison tables, slide outlines, decision logs, or other documents.
Why use it?
It reveals missing information, unclear reasoning, and serious weaknesses before the document is used for decisions or implementation.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the skilldrop plugin — 51 skills, 4 agents shipped together

not rated 2 22d ago A scan 114 tokens original MIT
View the source file sananthanarayan/skilldrop sananthanarayan.github.io
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/sananthanarayan/skilldrop/doc-critique
Any agent
npx skills add sananthanarayan/skilldrop --skill doc-critique
Clone the repo
git clone --depth 1 https://github.com/sananthanarayan/skilldrop

Made for: Claude Code.

Or install skilldrop, the plugin that ships this one along with the rest of its 51 skills, 4 agents.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for doc-critique

README.md
[![agentmods](https://agentmods.dev/badge/skills/sananthanarayan/skilldrop/doc-critique.svg)](https://agentmods.dev/skills/sananthanarayan/skilldrop/doc-critique)
Your own site
<a href="https://agentmods.dev/skills/sananthanarayan/skilldrop/doc-critique"><img src="https://agentmods.dev/badge/skills/sananthanarayan/skilldrop/doc-critique.svg" alt="Measured on agentmods" height="20"></a>
Per session 114 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,848 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00114 $0.01848
Opus 5 $0.00057 $0.00924
Sonnet 5 $0.00023 $0.00370
Haiku 4.5 $0.00011 $0.00185

Measured 6d ago against content hash 87cdf0c67562, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

doc-critique scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/doc-critique/SKILL.md · 120 lines

How it starts

The opening of the file, as written. The whole thing — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.

doc-critique

You help the user review an existing document with the same opinionated rubric the skilldrop generators use to produce them. The collection is otherwise asymmetric — every other skill creates artifacts; this one reviews them.

How to respond

  1. Identify the doc type. Ask if the user hasn't said. Match it to the closest skilldrop archetype:

    Doc type Rubric file
    ADR (MADR or Nygard) rubrics/adr.md
    Engineering design doc / RFC / tech proposal rubrics/design-doc.md
    Runbook / operational doc rubrics/runbook.md
    Tech-comparison matrix / vendor selection rubrics/tech-comparison.md
    Exec summary / 1-pager rubrics/exec-summary.md
    Slide deck or outline rubrics/deck.md
    Decision log / meeting notes rubrics/decision-log.md
    Other / unsure Use rubrics/generic.md and call out the type-mismatch

    For mixed/ambiguous docs (e.g. "a design doc that's also being used as a runbook"), pick the primary purpose and note the dual-use in the critique header.

  2. Read the whole doc before commenting. A finding that looks like a blocker on page 1 sometimes gets resolved by page 4 — don't fire critique at sections in isolation.

  3. Apply the rubric, not your taste. Each rubric has a fixed set of checks. Walk through them in order. If a check passes, note it pass-by-default (don't flood the output with green checkmarks); if it fails, write a finding.

  4. Categorize every finding by severity:

    Severity Meaning
    🟥 Blocker The doc can't ship without fixing this. A reviewer/exec/on-caller will be unable to act on the doc as-is. Example: ADR with no alternatives considered; runbook with no rollback command; exec summary missing The Ask.
    🟧 Major The doc will ship and be used but a key decision is poorly supported / a section is missing or weak / a claim is unsupported. The doc loses credibility but doesn't fail outright.
    🟨 Minor Style, ordering, redundancy, missing nice-to-haves. The doc works; this is the difference between "passable" and "good".
    ⚪ Nit Typo, formatting, terminology preference. Optional.

Read the full file on GitHub · 120 lines

Files

What ships with it

13 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 6d ago First seen · 120 lines · 114 tokens per session scan A 87cdf0c67562

Subscribe to this mod's changes

doc-critique is a skill published in the GitHub repository sananthanarayan/skilldrop (2 stars, last pushed 22d ago), licensed MIT. It adds 114 tokens to every session and 1,848 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Writing and docsadragent-skillsai-agentsanthropicclaudeclaude-code
Related

Other skills, from other repositories

openlore-brainstorm

Transform a feature idea into an annotated story using a Domain Sketch or Constrained Option Tree. Use when asked to brainstorm, explore, or shape a feature before implementation.

clay-good/OpenLore · 40 tokens

openlore-execute-refactor

Apply a confirmed .openlore/refactor-plan.md with a test gate after each change. Use when asked to execute or continue an OpenLore refactoring plan.

clay-good/OpenLore · 41 tokens

openlore-plan-refactor

Identify a high-priority refactoring target, assess its blast radius, and write .openlore/refactor-plan.md without changing code. Use when asked to plan or prioritize a refactor.

clay-good/OpenLore · 46 tokens

openlore-debug

Debug with OpenLore structural context, an explicit root-cause hypothesis, and RED/GREEN verification. Use when a bug, failure, or regression needs diagnosis and repair.

clay-good/OpenLore · 39 tokens

openlore-analyze-codebase

Run a full static OpenLore analysis and summarize architecture, call graph, refactoring issues, and duplicate code. Use when asked to analyze, map, or assess a codebase without LLM inference.

clay-good/OpenLore · 48 tokens

mission-brief

Mission-driven SDD orchestrator: take a feature description, structure it into a Mission Brief (goal, constraints, success criteria), generate an ordered step list with prompts that trigger installed SDD skills via model invocation or command-file discovery, and walk those steps to converged implementation. Use when…

tikalk/adlc-team-skills · 99 tokens