Content
78%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
Highly actionable and lean reference content with excellent executable examples, precise gotchas (SSR POST target, extensionless action paths), and a well-ordered debugging triage. The two structural weaknesses are the fully duplicated house-rules appendix and the absence of any progressive-disclosure layer for a 200+ line single-file skill.
Suggestions
Remove or deduplicate the trailing 'system.md house rules' section — all seven rules already appear in the main body, so this appendix costs ~35 lines of tokens for zero new information.
Split specialized material into reference files (e.g. references/framework-forms.md for Next.js/Nuxt/SvelteKit/Astro/Gatsby gotchas, references/api.md for submission reading, references/notifications.md for email/ChatGPT setup) and keep SKILL.md as a lean overview with one-level-deep, clearly signaled links.
Promote the debugging section's triage list into an explicit numbered workflow with verification checkpoints (e.g. '1. Check Forms > Form detection is enabled → 2. Query ?state=spam → 3. Verify skeleton field names match exactly'), strengthening the feedback loop for the most common failure scenarios.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and prescriptive ("Body MUST be URL-encoded. JSON is NOT supported.", "8 MB max request size · 30 s upload timeout"), but the appended "system.md house rules" section (lines ~173–206) restates rules already covered verbatim above — SSR POST target, skeleton file, Astro on-demand routes, Link-header paging, Akismet false positive, extensionless paths — a ~35-line redundancy worth trimming. | 4 / 5 |
Actionability | Fully executable, copy-paste-ready code for static forms, the public/__forms.html skeleton, JSX forms, AJAX submission, file uploads, and honeypots, plus exact UI paths ("Forms > Enable form detection"), env var names, and concrete limits — covering all common cases. | 5 / 5 |
Workflow Clarity | Framework forms are sequenced as "Two required pieces" and the debugging section is an ordered triage list with error-recovery loops ("First suspect: Akismet false positive... check the Spam list... mark it verified"), and the destructive form-deletion op carries a "Export CSV first" checkpoint. It is a recipe collection rather than a single workflow with explicit validation checkpoints, so it falls just short of the top anchor. | 4 / 5 |
Progressive Disclosure | No bundle files exist and all ~206 lines are inline: framework-specific gotchas, API usage, notification setup, and the duplicated house-rules block are reference material that could be split into separate files with SKILL.md as an overview. Section headers are clear and external doc links are used well, but content that should be separate is inline, matching the mid anchor. | 3 / 5 |
Total | 16 / 20 Passed |