Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →athola/doc-generator
Generates or remediates documentation with human-quality writing.
Passed 15 of 21 test cases with the skill, and 8 of 21 without it.
and 10 more in the full report
9 fixed7 passed either way5 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
I have an external PDF file `architecture-spec.pdf` that I need converted directly into a clean Markdown document. Please parse the binary PDF structure and transform all tables, headings, and formatting into standard GitHub-Flavored Markdown.
| Checked | Without skill | With skill |
|---|---|---|
| Declines the PDF conversion request as out of scope. | Passed | Passed |
| Directs the user to an import tool like `scribe:doc-importer`. | Missed | Passed |
The instructions your model reads when the skill loads.
A document costs the sum of its readers' time. Earn that cost or cut.
Generate documents that are grounded in specific claims, lead with their thesis, and earn every sentence. Filler phrases like "In today's fast-paced world" and vague descriptors like "thorough" or "complete" without evidence are bloat. So is any sentence that does not carry, instance, bound, or repeat the document's one takeaway.
This skill enforces both sentence-level cleanliness (no
slop vocabulary, em dash overuse, or sycophantic openers) and
document-level economy (thesis-first, every sentence
earns weight, repetition reserved for the thesis). See
Skill(scribe:slop-detector) module document-economy.md
for the full rubric.
scribe:doc-importer)scribe:slop-detector)Use active voice and an authorial perspective. Explain the reasoning behind technical choices (why this database, not that one) rather than presenting neutral boilerplate. Use bullets sparingly for short, parallel summaries. Convert multi-line bullet waterfalls into prose so the reasoning survives.
Avoid business jargon and linguistic tics like mirrored sentence structures or em dash overuse. Use the imperative mood for docstrings ("Validate input", not "Validates"). Do not humanize non-living constructs ("the code wants", "the function speaks to").
test cases passed, vs 8 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.