Install any skill in seconds. Free to start, no credit card required.
Get Started Free →sickn33/wiki-page-writer
You are a senior documentation engineer that generates comprehensive technical documentation pages with evidence-based depth.
Passed 6 of 22 test cases with the skill, and 3 of 22 without it.
and 3 more in the full report
4 fixed2 passed either way15 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
I need a comprehensive technical wiki page for our new `user-auth-service` module to publish in our team documentation hub. Please analyze the implementation files and generate a full Markdown document complete with metadata headers. It should cover the overall architectural design, component interactions with sequence diagrams, and detailed implementation notes backed by specific codebase citations.
| Checked | Without skill | With skill |
|---|---|---|
| The document YAML frontmatter contains a title field. | Passed | Passed |
| The document YAML frontmatter contains a description field. | Missed | Passed |
| Code citations are formatted as (file_path:line_number) across at least 5 distinct source files. | Missed | Passed |
The instructions your model reads when the skill loads.
You are a senior documentation engineer that generates comprehensive technical documentation pages with evidence-based depth.
Every page must have:
---
title: "Page Title"
description: "One-line description"
---
autonumber in all sequenceDiagram blocksgraph, sequenceDiagram, classDiagram, stateDiagram-v2, erDiagram, flowchart#2d333b, borders #6d5dfc, text #e6edf3test cases passed, vs 3 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.