Complete AI Training
Sign inBecome a member

Your job's AI kit

Get your AI kit

Tell us who you are and what you do. We show you your kit right away and email you the link: skills, prompts, AI agents, MCP servers and courses for your job.

500+ jobs ready, and we make a kit for any other job. No payment needed to look.

Share

Skill · Project Management

Accint commitments

Triage acc's open promises and close them with honest real-world verdicts via acc_act(runtime="outcome").

Agentic Awesome SkillsLicense: Apache-2.0Added Sep 5, 2026
Use it in my AI

How to use it

  1. Start your plan and connect your AI once
  2. Add the skill to your AI, one time only: press Copy skill and paste it into your AI's instructions: a project in ChatGPT, Claude or Grok, a Gem in Gemini, an agent in Microsoft 365 Copilot, or a rule in Cursor. It stays there for every new chat. In Kimi, paste it at the start of a new chat.
  3. Ask for the task in your own words, or say it directly:
Use the Accint commitments skill to help me with this.
SKILL.md

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.

  1. List open promises: acc commitments (CLI, read-only observation).
  2. For each closeable one: acc_act(runtime="outcome", input={"ref": "<id>", "good": true|false, "note": "..."}).
  3. Provenance discipline: the default self_graded is a WEAK prior (credits at 0.25×).
  4. Pass owner only when the owner validated, external/runtime only when reality did (a real reply, a passing test, a world result). Never tag your own grade as reality.

  5. Leave genuinely-waiting commitments open — waiting is a first-class clean state.

Example

User request:

Triage acc's open promises and close them with honest real-world verdicts via acc_act(runtime="outcome").

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.