Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →okhp3/okhp3-process-capture
Capture a recurring task as either a backlog entry or a new skill skeleton.
Passed 18 of 20 test cases with the skill, and 5 of 20 without it.
and 22 more in the full report
16 fixed4 passed either way1 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 14 test cases the skill fixed. Same model, same prompt, with and without the skill.
When writing the frontmatter metadata for a newly captured skill skeleton, what specific constraint applies to the description property to ensure proper agent invocation?
| Checked | Without skill | With skill |
|---|---|---|
| specifies that the frontmatter description must be pushy | Missed | Passed |
The instructions your model reads when the skill loads.
OverKill Hill P³ · overkillhill.com · github.com/OKHP3
The intake mechanism. Turns "I just did this for the third time" into a structured artifact, not a lost observation.
Extract the pattern. From the current conversation (or a description the user gives), identify: what was the task, what tools/skills were used, what was the input, what was the output, were there corrections or judgment calls along the way that would need to be encoded as instructions.
Assess readiness. Has this pattern stabilized enough to write down, or is this still "developing taste" (per the original delegation-contract framing — genuinely novel judgment calls each time means it's not a skill yet)?
docs/BACKLOG.md entry (date, task, times observed, candidate family, status: captured). Stop here.Determine target family. Does this fit an existing family (mermaid/, social-posting/, or this repo's own process-capture/), or does it need a new top-level family? If new, note this explicitly — adding a new family directory is a bigger decision than adding a skill within one, and the user should confirm.
Produce the skeleton. Frontmatter (name, "pushy" description per skill-creator's triggering guidance) + section-header outline matching the body's intended structure, with 1-2 sentence descriptions per section and pointers to reference files that will need authoring. Match the structure of existing skills in this repo (core+domain pattern for multi-skill families, single-skill pattern for self-contained ones).
Update the index. Add the new skill's trigger row to root AGENTS.md, even though the skeleton isn't fully authored yet — mark it in the "Planned" section if the body is still mostly TOC, move to "Active" once authored.
A skeleton from this skill is a starting point for skill-creator (the Anthropic example skill, if available) for full authoring, testing, and description-optimization — this skill does intake and structure, not iteration and evals.
Built by Jamie Hill · OverKill Hill P³ Published at github.com/OKHP3 Part of the OKHP3/skillz Agent Skill library. MIT License -- free to use, fork, and adapt. A nod to the source is appreciated.
test cases passed, vs 5 / 20 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.