Home / Reports / doc-coauthoring

doc-coauthoring

Validated 8 Jul 2026 · Repository

PRO

Poor

0 critical

6 warnings

16 suggestions

88 passed

Domain scores

Anti-Slop

Accessibility

100

Enterprise

100

Issues

Warnings (6)

5.1-no-style-sectionline 1

No writing style section found

Fix: Add a '## Writing Style' or '## Anti-Slop' section

15.1-no-budget-capline 6

Multi-agent skill has no budget or turn cap; runaway costs are possible

Fix: Add max_turns, cost_limit, or similar budget constraint for subagents

19.3-generator-no-output-specline 6

Generator pattern detected but no output format specified

Fix: Document the output format (template, schema, or example output)

7.7-task-ambiguityline 24

Ambiguous instruction detected (vague-success)

Fix: Replace with specific, measurable success criteria

7.7-task-ambiguityline 244

Ambiguous instruction detected (non-falsifiable)

Fix: Specify what 'good/right/correct' means with concrete checks

12.5-no-exit-criterialine 104

1 of 3 phases lack exit criteria; Claude may skip phases or run past completion

Fix: Add exit criteria to each phase: 'Exit when: [specific condition]'

Suggestions (16)

5.2-no-do-dontline 1

Missing DO/DON'T lists for style guidance

Fix: Add explicit DO and DON'T lists for writing patterns

16.4-no-idempotencyline 6

Skill does not document whether it is safe to re-run

Fix: Add idempotency guidance: state whether running the skill twice produces the same result or causes side effects

17.1-no-input-contractline 6

No input contract found; unclear what data the skill expects

Fix: Document what the skill expects as input (format, required fields, constraints)

17.2-no-output-contractline 6

No output contract found; unclear what the skill produces

Fix: Document what the skill produces (format, structure, side effects)

17.3-no-mode-awarenessline 6

Skill does not clarify standalone vs composed behavior

Fix: Clarify whether the skill works standalone, in pipelines, or both

3.4-gerund-namingline 2

Skill name could use gerund form for clarity

Fix: Consider gerund-style names like 'processing-pdfs' or 'analyzing-logs' (per best practices)

18.1-no-confidence-signalline 1

No confidence signal found for orchestrator decision-making

Fix: Add confidence indicators (e.g., confidence: high/medium/low) so orchestrators can route or retry

18.2-no-progress-signalline 1

Complex skill lacks progress reporting checkpoints

Fix: Add progress signals (e.g., 'Step 2 of 5: validating input') for long-running workflows

18.3-no-structured-outputline 1

No structured output format defined for machine consumption

Fix: Define a structured output format (JSON, YAML, or table) so downstream tools can parse results

4.2-ambiguous-termline 46

Ambiguous term 'appropriate' found