commitments
When to Use
Use this skill when you need triage acc's open promises and close them with honest real-world verdicts via acc_act(runtime="outcome").
Routing sugar over the two MCP verbs — no logic lives here.
- List open promises:
acc commitments(CLI, read-only observation). - For each closeable one:
acc_act(runtime="outcome", input={"ref": "<id>", "good": true|false, "note": "..."}). - Provenance discipline: the default
self_gradedis a WEAK prior (credits at 0.25×). Passowneronly when the owner validated,external/runtimeonly when reality did (a real reply, a passing test, a world result). Never tag your own grade as reality. - Leave genuinely-waiting commitments open —
waitingis a first-class clean state.
Limitations
- Use this skill only when the task clearly matches its upstream source and local project context.
- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.
- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.