skills/commitment-digest/SKILL.md
Compose and deliver summaries of open commitments, deadlines, pending signals, and resolution suggestions.
npx skillsauth add nearai/ironclaw commitment-digestInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Compose a summary of the user's current commitments. Used both in-conversation (user asks "show commitments") and by the commitment-digest mission for scheduled delivery.
memory_tree("projects/commitments/open/", depth=1) — list all open commitment files (skip README.md)memory_read each file to extract frontmatter: status, urgency, due, delegated_to, resolution_path, stale_after, tagsmemory_tree("projects/commitments/signals/pending/", depth=1) — count pending signals (skip README.md)memory_tree("projects/commitments/resolved/", depth=1) — count recently resolvedUse memory_tree and memory_read for digest assembly. Do not use CodeAct,
shell commands, or creative-generation tools to count or summarize
commitments.
Group commitments and present in this order:
## Commitments — <today's date>
### Overdue / Critical
- **<title>** (due <date>) — owner: <owner>
→ <resolution suggestion based on resolution_path>
### Due This Week
- **<title>** (due <date>) — owner: <owner>, delegated to: <person>
### Waiting / Delegated
- **<title>** — waiting on <person> since <date>
→ (follow-up suggested) if not updated in 3+ days
### Open (no deadline)
- **<title>** — owner: <owner>
### Agent Can Handle
- **<title>** — I can <suggested approach>. Want me to proceed?
### Pending Signals (<count>)
<count> unprocessed signals. Say "review signals" to triage them.
### Recently Resolved
- <title> (resolved <date>)
---
Did I miss anything? Tell me if I overlooked an obligation.
Rules:
stale_after as "(stale — still relevant?)"resolution_path: agent_can_handle, describe what the agent would do and ask for approvalresolution_path: needs_reply, offer to draft a response if possiblemessage tool to the user's preferred channeldevelopment
Linear issue tracker API integration. Covers first-use identity bootstrap (viewer + teams cached), raw GraphQL for list/search/create/update, and the rules for handling "my issues" / "assigned to me" requests.
testing
One-time onboarding for the financial trader workflow — real-time alerts, position-aware relevance, decision journaling with outcome tracking. After successful setup this skill is excluded from selection until the marker file is deleted.
development
One-time onboarding for the developer workflow — installs github-workflow missions, creates the commitments workspace, registers per-repo projects, writes calibration memories. After successful setup this skill is excluded from selection until the marker file is deleted.
devops
One-time onboarding for the content creator workflow — content pipeline stages, trend expiration, cross-platform cascades, heavy idea parking. After successful setup this skill is excluded from selection until the marker file is deleted.