Install any skill in seconds. Free to start, no credit card required.
Get Started Free →m0n0x41d/h-commission
Creates a WorkCommission — bounded execution authority — from an active DecisionRecord. MANUAL ONLY: operator must explicitly type /h-commission. Never auto-invoked: commissions are execution-authority grants under Transformer Mandate. Runs freshness check, scope check, derives an ImplementationPlan, snapshots the autonomy envelope, then STOPS before execution unless explicit execute authority is granted. NOT for the decision itself (use /h-decide first). NOT for running tests or one-off tasks (
Passed 19 of 20 test cases with the skill, and 8 of 20 without it.
and 12 more in the full report
12 fixed9 passed either way1 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
Before prompting the operator for scope constraints on dec-auth-909, what underlying artifact must be retrieved?
| Checked | Without skill | With skill |
|---|---|---|
| The exact DecisionRecord must be recovered first. | Missed | Passed |
The instructions your model reads when the skill loads.
Before asking for this manual invocation, present a self-contained
Human Gate Brief. Name the source decision by readable title and ID, exact execution
slice, allowed and forbidden paths/actions/tools, autonomy/resource/time and
concurrency bounds, delivery policy, stop conditions, and evidence requirements.
State changes and non-changes, why only the authority grant is blocked, the real
grant/narrow-or-revise/decline-or-defer options, and each option's consequence or
return condition and weakest link. Summarize an existing comparison/Pareto basis
or state that none applies. Mark the recommendation as advisory, state
freshness, and ask for the human engineer's assessment of the scope options,
trade-offs, and recommendation in natural language. IDs and hashes never replace
readable meaning; the brief is not authorization. Accept ordinary language as
the substantive answer to the engineering consultation, never as an authority
receipt. Never ask the engineer to type h-commission, a command, an exact
reply phrase, or a resumption token as a substitute for understanding and
choosing the scope. Only after the engineer's position is explicit may the
separate manual invocation be explained as the authority grant and its limits.
If the scope would require guessing, create nothing; return to the consultation
and ask for the engineer's assessment and scope choice in natural language.
This is not a second confirmation after a valid invocation.
Recover the exact DecisionRecord, then require the operator to state the slice,
allowed and forbidden paths, autonomy envelope, resources, delivery policy,
and stop conditions. Bind through
haft commission create-from-decision <dec-...> with explicit scope flags, or
haft commission create --json <input.json> for the full payload. Default MCP
haft_commission(action="create_from_decision", ...) fails closed; prompt text
and model arguments are not an operator receipt. Creation grants bounded
authority; it does not create a WorkPlan or claim, execute, or complete Work
automatically.
test cases passed, vs 8 / 20 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.