CtrlK
BlogDocsLog inGet started
Tessl Logo

decision-capture

Detect decisions in conversation and record them with rationale, alternatives, and outcome tracking.

68

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a tight, highly actionable instruction skill: concrete paths, a mandatory sequenced workflow with validation gates, and a complete template, all well-organized into navigable sections with no unnecessary concept explanation.

DimensionReasoningScore

Conciseness

The body is lean, avoids explaining concepts Claude already knows, and every section (detection criteria, mandatory execution order, template, follow-through) earns its place without padding.

3 / 3

Actionability

It gives concrete, executable guidance: exact memory_write target paths, a numbered mandatory execution order, and a complete copy-ready decision template with named frontmatter fields.

3 / 3

Workflow Clarity

The Recording section provides an explicit numbered sequence with a validation checkpoint ('Only then confirm'; 'Never say captured... unless memory_write succeeded'), satisfying the feedback-loop requirement for the persist operation.

3 / 3

Progressive Disclosure

This single-purpose skill has no bundle files and no nested references, and is organized into clearly signaled sections (Detection, Recording, Follow-through, Outcome tracking, Confirmation), matching the simple-skill allowance for a top score.

3 / 3

Total

12

/

12

Passed

Description

67%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific and clearly distinguishes the skill's niche, but it omits an explicit 'Use when...' trigger clause and only lightly surfaces natural trigger terms, leaving completeness and trigger coverage mid-range.

Suggestions

Add a 'Use when the user states a decision, e.g. "we decided", "going with", "settled on", or asks to record/log a decision.' clause to satisfy the 'when should Claude use it' requirement.

Surface a few natural trigger variations ('decided', 'going with', 'settled on') directly in the description to improve trigger-term coverage beyond the single word 'decisions'.

DimensionReasoningScore

Specificity

The description names several concrete actions — 'Detect decisions in conversation and record them with rationale, alternatives, and outcome tracking' — matching the anchor for multiple specific concrete actions.

3 / 3

Completeness

It clearly states what the skill does (detect and record decisions with rationale/alternatives/outcome tracking) but lacks a 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 2 per the judging guidelines.

2 / 3

Trigger Term Quality

It mentions 'decisions' which users would naturally say, but the description itself omits common natural variations like 'decided', 'going with', or 'settled on' that the activation block captures, so coverage is partial.

2 / 3

Distinctiveness Conflict Risk

The decision-capture niche with rationale, alternatives, and outcome tracking is distinct and unlikely to trigger for unrelated skills; voice is correctly third person.

3 / 3

Total

10

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
nearai/ironclaw
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.