Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →m0n0x41d/h-status
Project state dashboard for haft — read-only consolidation of active problems, pending decisions, refresh-due artifacts, open work commissions, recent notes, and module coverage. Make sure to use this skill whenever the user asks "where are we", "what's pending", "what's stale", "project status", "what needs attention", "show me the state", "what's in flight", "what did we decide on X recently", "haft status" — or whenever a session resumes after a break and situational awareness is needed befor
Passed 13 of 17 test cases with the skill, and 3 of 17 without it.
and 14 more in the full report
13 fixed4 passed either way5 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
We need to check memory neighborhood context for the 'user_session_v2' entity under the haft memory schema. What step must be performed prior to querying the neighborhood if alias names exist?
| Checked | Without skill | With skill |
|---|---|---|
| Resolves entity aliases prior to initiating the neighborhood lookup. | Missed | Passed |
The instructions your model reads when the skill loads.
Use the native Pi tool haft_query rather than shelling out manually.
Contract truth: typed neighborhood and recall are V9 CONTRACT capabilities. Source, schema, skill, or local-test presence is not installed-runtime proof and does not establish Pi host parity. A readiness claim requires current EXACT-CANDIDATE EVIDENCE from P14 tied to one exact candidate; RC or release status additionally requires release authority. Pi support is experimental, and contract inclusion or evidence alone does not establish CURRENT PRODUCT status.
If the operator's current question is not about project status, resumption, coverage, or reliance on recorded project state, return without calling this skill. Do not run status after completing unrelated work merely to backfill a governance-looking report.
Start with:
{
"action": "status",
"full": false
}
If status reports several canonical project scopes, retry the same read-only
call with one exact scope_id from the reported available values:
{
"action": "status",
"full": false,
"scope_id": "<exact emitted ScopeID>"
}
Choose the scope from the operator's current object or question.
test cases passed, vs 3 / 17 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.