Agent Skills
› nearai/ironclaw
› commitment-digest
commitment-digest
GitHub用于整理和交付用户待办承诺、截止日期及待处理信号的摘要报告。通过读取记忆文件提取元数据,按优先级分组展示,并提供解决建议或代理处理选项,支持对话内即时展示或定时发送。
Trigger Scenarios
用户询问当前承诺状态
执行 commitment-digest 定时任务
Install
npx skills add nearai/ironclaw --skill commitment-digest -g -y
SKILL.md
Frontmatter
{
"name": "commitment-digest",
"version": "0.2.0",
"activation": {
"tags": [
"commitments",
"digest",
"reporting"
],
"keywords": [
"show commitments",
"commitment digest",
"commitment summary",
"commitment report",
"open commitments",
"my obligations",
"what do I owe",
"pending tasks",
"what's overdue",
"what's due",
"commitment status"
],
"patterns": [
"(?i)(show|list|summarize|review) (my )?(commitments|obligations|deadlines|tasks)",
"(?i)what('s| is| are) (pending|overdue|due|open)",
"(?i)commitment (digest|report|status|summary)"
],
"max_context_tokens": 1500
},
"description": "Compose and deliver summaries of open commitments, deadlines, pending signals, and resolution suggestions."
}
Commitment Digest
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.
Gathering data
memory_tree("projects/commitments/open/", depth=1)— list all open commitment files (skip README.md)memory_readeach 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 resolved
Use memory_tree and memory_read for digest assembly. Do not use CodeAct,
shell commands, or creative-generation tools to count or summarize
commitments.
Composing the digest
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:
- Omit empty sections entirely
- Keep each item to one line plus optional resolution suggestion
- If zero open commitments and zero pending signals: "No open commitments. You're clear."
- Flag commitments past
stale_afteras "(stale — still relevant?)" - For
resolution_path: agent_can_handle, describe what the agent would do and ask for approval - For
resolution_path: needs_reply, offer to draft a response if possible - For delegated items past 3 days without update: "(follow-up suggested)"
- Always end with "Did I miss anything?" to catch false negatives
Delivery
- In conversation: Display the digest inline
- From mission: Send via
messagetool to the user's preferred channel - Tone: Concise and scannable — a dashboard, not a narrative
Version History
- 5380a32 Current 2026-08-20 07:09


