nearai/decision-capture
skills/decision-capture/SKILL.md
Detect decisions in conversation and record them with rationale, alternatives, and outcome tracking.
$ install --global
skillsauthnpx skillsauth add nearai/ironclaw decision-captureInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 15, 2026, 10:09 AM4.4s1 file scanned
SKILL.md
- name:
- decision-capture
- version:
- 0.2.0
- description:
- Detect decisions in conversation and record them with rationale, alternatives, and outcome tracking.
- max_context_tokens:
- 1200
Decision Capture
When a decision is detected in conversation, record it in the commitments workspace. Decisions are durable knowledge — they explain why a path was chosen and enable outcome tracking over time.
Detection
Look for explicit decision language:
- "We decided to..." / "I'm going with..." / "Let's do X"
- "The call is..." / "We settled on..."
- "I chose X over Y because..."
Do NOT capture:
- Brainstorming or hypotheticals: "maybe we should...", "what if we..."
- Preferences without commitment: "I think X is better"
- Questions: "should we go with X?"
When uncertain, ask: "Was that a decision, or still thinking it through?"
Recording
This skill is only successful if the decision is actually persisted. Do not just summarize or acknowledge the decision.
Execution order is mandatory:
- Call
memory_writeforprojects/commitments/decisions/<date>-<slug>.md - If applicable, call
memory_writefor a follow-on commitment inprojects/commitments/open/ - If applicable, call
memory_writeforcontext/intel/<slug>.md - Only then confirm to the user what was recorded
Never say a decision was "captured", "recorded", or "saved" unless the
corresponding memory_write call succeeded.
Write to projects/commitments/decisions/<date>-<slug>.md via memory_write:
---
type: decision
decided_at: <today YYYY-MM-DD>
context: <topic-slug>
participants: [<who was involved>]
confidence: <high if explicit, medium if inferred>
reversible: <true|false>
outcome: null
outcome_positive: null
tags: [<relevant tags>]
---
# <What was decided>
## Context
<Why this decision was needed — 1-2 sentences.>
## Options considered
1. **<Option A>** — <brief pros/cons>
2. **<Option B>** — <brief pros/cons>
## Rationale
<Why this option was chosen.>
## Outcome
<To be filled in later when outcome is known.>
Follow-through
- If the decision creates an obligation (e.g., "we decided to migrate by Q2"), also create a commitment in
projects/commitments/open/following the commitment schema. - Write an intelligence MemoryDoc to
context/intel/<slug>.mdwith a brief summary: "Decided X on <date>. Rationale: <reason>." This makes the decision searchable as durable knowledge.
For explicit requests like "record this decision", "log this decision", or "note the decision", default to doing all required writes immediately rather than asking a follow-up question unless the content is genuinely ambiguous.
Outcome tracking
The triage mission checks for decisions older than 7 days without an outcome. It prompts: "You decided <X> <N> days ago. How did it turn out?" When the user provides an outcome, update the decision file's outcome and outcome_positive fields.
Confirmation
After the write(s) succeed, briefly confirm:
- where the decision was written
- whether any follow-on commitment was created
- one-line summary of the rationale
Related Skills
nearai/linear
development
VerifiedTrustedCommunity
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.
12,145SKILL.mdUpdated Apr 15, 2026
nearai/trader-setup
testing
VerifiedTrustedCommunity
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.
11,894SKILL.mdUpdated Apr 19, 2026
nearai/developer-setup
development
VerifiedTrustedCommunity
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.
11,894SKILL.mdUpdated Apr 19, 2026
nearai/content-creator-setup
devops
VerifiedTrustedCommunity
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.
11,894SKILL.mdUpdated Apr 19, 2026