Name: app-docs
Rating: 73.6 (1 reviews)
Author: jezweb

app-docs

Generate complete user documentation for a web app with screenshots. Browses the app via browser automation, screenshots every screen, and produces a structured user guide with step-by-step instructions, annotated screenshots, workflow diagrams, and reference tables. Supports quick (key screens), standard (all pages), thorough (every state and flow), and exhaustive (publishable documentation suite). Triggers: 'document the app', 'user guide', 'app documentation', 'screenshot docs', 'generate user docs', 'help docs', 'how-to guide', 'write the docs'.

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

82%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a highly actionable, well-sequenced documentation workflow with concrete templates and validation-aware autonomy rules. It is lean for its scope but large enough that splitting per-page templates into a reference file would improve progressive disclosure.

Suggestions

Add an explicit final verification step (e.g., spot-check rendered images, confirm every screenshot reference resolves, verify the guide opens in the target format) before declaring the doc complete.

Move the reusable per-page and supporting-section markdown templates into a references/ file (e.g. TEMPLATES.md) and link from SKILL.md to reduce inline bulk and improve progressive disclosure.

Tighten the 'Quality Bar' section, which restates guidance already embedded in the Screenshot Quality and workflow sections.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and well-structured with tables and templates assuming Claude's competence; minor padding in the 'Quality Bar' list and template blocks that reiterate earlier guidance keep it just below a 5.	4 / 5
Actionability	Provides copy-paste-ready markdown scaffolding, exact screenshot naming conventions, resolution specs (1280x720 desktop / 375x812 mobile), output file paths, and depth-specific tables covering common cases.	5 / 5
Workflow Clarity	A clear 6-step workflow with validation checkpoints (wait for data load, no spinners; autonomy rules gating destructive actions like real form submissions and deletes); missing an explicit final verify-output step prevents a 5.	4 / 5
Progressive Disclosure	No bundle files exist; the skill is a single well-organized self-contained file with clear section headers and no nested references. A large monolithic body with reusable templates that could be split into reference files keeps it just below 5.	4 / 5
	Total	17 / 20 Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is exemplary: concrete capabilities, a full set of natural trigger phrases, and explicit what/when guidance in third person. It distinguishes itself clearly from generic document skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Browses the app via browser automation, screenshots every screen' and 'produces a structured user guide with step-by-step instructions, annotated screenshots, workflow diagrams, and reference tables' — giving comprehensive coverage of capabilities.	5 / 5
Completeness	Explicitly answers both 'what' (browses, screenshots, produces a structured guide with annotated screenshots, diagrams, tables) and 'when' via a dedicated Triggers clause with concrete phrases.	5 / 5
Trigger Term Quality	Eight natural trigger phrases ('document the app', 'user guide', 'app documentation', 'screenshot docs', 'generate user docs', 'help docs', 'how-to guide', 'write the docs') cover synonyms and phrasings a user would naturally say.	5 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (web-app documentation via browser automation with screenshots) with distinct triggers and minimal overlap risk against other skills.	5 / 5
	Total	20 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 6 missing	Warning

	Total	15 / 16 Passed

Repository: jezweb/claude-skills
Path: plugins/dev-tools/skills/app-docs/SKILL.md
Commit: e875a6b

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.