Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →q00/publish
Publish Seed specification as GitHub Issues for team-based project management
Passed 12 of 17 test cases with the skill, and 6 of 17 without it.
and 9 more in the full report
9 fixed6 passed either way5 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
In the Markdown body of each child Task issue created from a seed, how must the relationship to the parent Epic issue be referenced at the top of the body?
| Checked | Without skill | With skill |
|---|---|---|
| Includes 'Parent: #<epic_number>' at the start of the Task issue body. | Missed | Passed |
The instructions your model reads when the skill loads.
Convert a Seed specification into structured GitHub Issues for team workflows.
ooo publish [seed_path]
/ouroboros:publish [seed_path]
Trigger keywords: "publish to github", "create issues from seed", "seed to issues"
When the user invokes this skill:
1a. Verify gh CLI is installed:
command -v gh >/dev/null 2>&1 && echo "OK" || echo "MISSING"
If missing, tell the user:
GitHub CLI (gh) is not installed.
Install it: https://cli.github.com/
Stop.
1b. Verify gh is authenticated:
gh auth status
If not authenticated, tell the user:
test cases passed, vs 6 / 17 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.