Accint commitments
Skill sickn33/agentic-awesome-skills/plugins/agentic-awesome-skills/skills/accint-commitments
Triage acc's open promises and close them with honest real-world verdicts via acc_act(runtime="outcome").From its SKILL.md
npx -y skills add sickn33/agentic-awesome-skills --skill accint-commitmentsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
What its file declares
Copied from the file, not written here
The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
1.6 KB, 263 tokens by cl100k_base, as published. Nobody here has run it
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.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most debug triage skills give in 263 tokens
Counted across 839 of the 1,149 authors here whose files we hold, read 2026-08-07
- Investigate root cause before proposing any fixin 102 of 839, across 67 files
- Read error messages completelyin 89 of 839, across 49 files
- Create a failing test case before fixingin 84 of 839, across 46 files
- Reproduce the issue consistentlyin 82 of 839, across 41 files
- Change one variable at a timein 82 of 839, across 42 files
- Check recent changesin 74 of 839, across 36 files
- Write the regression test before fixingin 74 of 839, across 40 files
- Fix the root cause not the symptomin 60 of 839, across 45 files
- Implement a single fix at a timein 59 of 839, across 20 files
- Trace data flow backward to the sourcein 50 of 839, across 20 files
- Remove all debug instrumentationin 49 of 839, across 13 files
- Form a single hypothesisin 48 of 839, across 18 files
Said here and by no other author read
- List open promises
- Close each closeable promise
- Provide an honest real-world verdict
- Set provenance based on actual validator
- Leave genuinely-waiting commitments open
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.