Install any skill in seconds. Free to start, no credit card required.
Get Started Free →davekilleen/decision-log
Capture an important decision with its context, options, rationale, and review date, then find it again when it matters.
Passed 20 of 24 test cases with the skill, and 12 of 24 without it.
and 9 more in the full report
9 fixed12 passed either way3 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
We just finalized our choice to migrate our backend API from REST to GraphQL. Can you help me record this using `/decision-log`? I want to list who participated (Sarah and Alex), the alternatives we evaluated, the trade-offs we accepted regarding caching complexity, and the follow-up actions with assigned owners.
| Checked | Without skill | With skill |
|---|---|---|
| Response includes a header line specifying status as Decided | Missed | Passed |
| Follow-up action items follow the hyphenated checklist format with an owner designation suffix | Missed | Passed |
The instructions your model reads when the skill loads.
Maintain searchable log of major decisions with full context and rationale.
/decision-log [decision] - Document specific decision/decision-log list - View all logged decisionsPrompt for decision details:
Document context:
Capture rationale:
Save decision record in 06-Resources/Decisions/
# Decision: [Title]
**Date:** [Today]
test cases passed, vs 12 / 24 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.