Install any skill in seconds. Free to start, no credit card required.
Get Started Free →brycewang-stanford/doc-coauthoring
Coordinate writing, revision, and submission workflows for collaborative academic and policy documents.
Passed 19 of 24 test cases with the skill, and 7 of 24 without it.
and 17 more in the full report
13 fixed6 passed either way4 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 13 test cases the skill fixed. Same model, same prompt, with and without the skill.
We have made 3 consecutive minor text adjustments to the 'Deployment Strategy' section of our spec without introducing any major structural changes. What quality check should be performed now?
| Checked | Without skill | With skill |
|---|---|---|
| Asks whether any content can be removed without losing critical information after 3 minor iterations. | Missed | Passed |
The instructions your model reads when the skill loads.
This skill provides a structured workflow for guiding users through collaborative document creation. Act as an active guide, walking users through three stages: Context Gathering, Refinement & Structure, and Reader Testing.
Use references/RUNTIME-MATRIX.md to decide what is available in the current environment before offering connectors, artifacts, or reader-test subagents.
If no artifact-like surface is available, default to a normal markdown file in a user-specified path or an explicitly named working file. Do not assume artifacts are available.
Trigger conditions:
Initial offer: Offer the user a structured workflow for co-authoring the document. Explain the three stages:
Explain that this approach helps ensure the doc works well when others read it (including when they paste it into Claude). Ask if they want to try this workflow or prefer to work freeform.
If user declines, work freeform. If user accepts, proceed to Stage 1.
Goal: Close the gap between what the user knows and what Claude knows, enabling smart guidance later.
Start by asking the user for meta-context about the document:
test cases passed, vs 7 / 24 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.