recursive-decision-ledger

Use when the user asks for repeated rollouts, marked decision processes, high-dimensional search, stochastic optimization, local-optima exploration, ensemble comparison, or recursive reasoning with a visible evidence trail.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No known issues

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 well-structured, lean instruction skill: a concrete field contract, a gated multi-step loop with validation and feedback, and copy-paste output templates, all within a single appropriately sectioned file.

Dimension	Reasoning	Score
Conciseness	The body is lean: a ledger field contract, a 7-step loop, two compact text templates, promotion rules, and a summary shape, with no padding explaining what rollouts or recursion are; every section earns its tokens and assumes Claude's competence.	3 / 3
Actionability	It provides concrete, copy-paste-ready artifacts (the coherence-mark block and summary-shape block), an explicit field contract, and specific promotion conditions; as an instruction-only skill, the absence of executable code is not penalized because the guidance is actionable.	3 / 3
Workflow Clarity	The 'Rollout Loop' is a clearly sequenced 7-step process with explicit validation gates (promotion gate, replay and freshness gates) and a feedback path (downgrade on drift/tail risk/stale data/failed replay), satisfying the destructive-ops validation requirement rather than omitting it.	3 / 3
Progressive Disclosure	No bundle files exist (references/, scripts/, assets/ are absent) and none are needed; the skill is a self-contained single file split into clearly labeled sections (Ledger Contract, Rollout Loop, Coherence Mark, Promotion Rules, Summary Shape) with no nested references or monolithic wall of text.	3 / 3
	Total	12 / 12 Passed

Description

72%

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 strong on triggers and distinctiveness but weak on stating what the skill actually does, leaving the 'what' only implied. It reads as a pure trigger clause rather than a what-and-when statement.

Suggestions

Add an explicit capabilities clause before the 'Use when...' trigger, e.g. 'Records a recursive decision ledger of rollouts, marks candidates, and gates live promotion. Use when...' so the 'what' is stated, not just the 'when'.

Replace the jargon phrase 'marked decision processes' with a more natural user-facing term such as 'tagged decision tracking' to keep trigger_term_quality natural and consistent.

Lead with one concrete action verb (e.g., 'Maintains' / 'Records') in third person to lift specificity from naming the domain to naming concrete actions.

Dimension	Reasoning	Score
Specificity	The description enumerates trigger scenarios ("repeated rollouts, marked decision processes, high-dimensional search, stochastic optimization, local-optima exploration, ensemble comparison, or recursive reasoning with a visible evidence trail") but states no concrete actions the skill performs, so it lands at the 'names domain and some actions, but not comprehensive' anchor rather than the explicit multi-action anchor 3.	2 / 3
Completeness	It has an explicit 'Use when...' clause answering 'when', but never states what the skill does (e.g., record a ledger, mark decisions, gate promotions), so the 'what' is only implied and completeness is capped at 2 per the missing-what guidance.	2 / 3
Trigger Term Quality	It gives broad, natural phrasing a user would actually say in this domain ("repeated rollouts", "high-dimensional search", "stochastic optimization", "ensemble comparison", "local-optima exploration", "recursive reasoning"), matching the 'good coverage of natural terms' anchor.	3 / 3
Distinctiveness Conflict Risk	The trigger set is a narrow, distinctive niche (recursive decision ledgers / stochastic optimization / local-optima exploration) that is unlikely to fire for unrelated general skills, matching the 'clear niche with distinct triggers' anchor.	3 / 3
	Total	10 / 12 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: affaan-m/ECC
Commit: 754b8dd

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.