Install any skill in seconds. Free to start, no credit card required.
Get Started Free →mkurman/process-docs
When the user needs to create SOPs, playbooks, runbooks, or other operational documentation that defines how a recurring process should be executed.
Passed 12 of 22 test cases with the skill, and 6 of 22 without it.
and 4 more in the full report
6 fixed6 passed either way10 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
Document the decision logic for granting production SSH access to requesting engineers based on whether they are contractors or full-time staff.
| Checked | Without skill | With skill |
|---|---|---|
| Uses explicit if/then conditional phrasing to define decision branches. | Missed | Passed |
The instructions your model reads when the skill loads.
-----|------------|-----| | [Trigger] | [Person/Role] | [Timeframe] |
How to verify the process was completed correctly.
| Date | Author | Change |
|---|
### Template 2: Incident Runbook
Severity: [P0-P3] On-Call Owner: [Role] Last Tested: [Date]
How this incident is identified (alerts, customer reports, monitoring).
Decision tree for identifying root cause.
Step-by-step fix for each known root cause.
Checklist for after the incident is resolved.
### Template 3: Onboarding Playbook
Duration: [e.g., 2 weeks] Buddy/Owner: [Role]
test cases passed, vs 6 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.