Install any skill in seconds. Free to start, no credit card required.
Get Started Free →code-yeongyu/pi-goal
Persistent Codex-style goal tracking for pi.
Passed 4 of 10 test cases with the skill, and 4 of 10 without it.
3 fixed6 passed either way11 still failing3 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
We want to resume our paused goal tracking session. Which interface controls resume transitions?
| Checked | Without skill | With skill |
|---|---|---|
| Identifies user-facing slash commands as the control mechanism for resume transitions. | Missed | Passed |
The instructions your model reads when the skill loads.
Use goal tools only when the user explicitly wants persistent goal tracking or when an active goal already exists.
Create a goal:
create_goal({
objective: "Ship the pi-goal extension",
token_budget: 50000,
});
Inspect a goal:
get_goal({});
Update a goal:
update_goal({
status: "complete",
});
update_goal only accepts complete. User-facing /goal commands control pause, resume, budget-limited, and clear transitions.
Before marking a goal complete, audit the actual current state:
update_goal({ status: "complete" }) only when no required work remains.test cases passed, vs 4 / 10 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.