commitment-setup

One-time setup for the commitments tracking system. Creates the workspace structure and schema docs, installs triage and digest missions, then excludes itself once `projects/commitments/README.md` exists.

Quality

69%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/commitment-setup/SKILL.md

Quality

Content

71%Weight 40%Scale 1-5

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

The body is highly actionable and well-sequenced with appropriate validation checkpoints, but the large embedded schema reference and some editorializing reduce conciseness and progressive-disclosure quality.

Suggestions

Move the schema README content into a references file (e.g. references/schema.md) and reference it from the body, since it is written to disk anyway as projects/commitments/README.md.

Trim editorializing such as 'This reframes decisions — when AI makes completeness cheap, there is no excuse for shortcuts.' to keep the body lean.

Break the long run-on mission goals into bulleted steps and add an explicit validate-or-retry note for mission creation failures.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete schema definitions, but includes editorializing ('when AI makes completeness cheap, there is no excuse for shortcuts') and long run-on mission-goal paragraphs that could be tightened, fitting the some-unnecessary-explanation anchor.	3 / 5
Actionability	Fully executable with exact memory_write/memory_read/mission_create calls, full file contents, specific paths, and cron cadences, matching the copy-paste-ready top anchor.	5 / 5
Workflow Clarity	Clear 8-step sequence with checkpoints (check existing setup, confirm before reinstall, check existing missions) for destructive/batch operations, but lacks explicit error-recovery feedback loops in the mission goals, fitting the clear-sequence-minor-gaps anchor.	4 / 5
Progressive Disclosure	Well-sectioned but the ~150-line schema README is inlined as a code block with no external reference files despite no bundle being provided, fitting the some-structure-but-content-should-be-separate anchor.	3 / 5
	Total	15 / 20 Passed

Description

67%Weight 40%Scale 1-5

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 distinct, clearly stating what the skill does, but it lacks an explicit 'Use when...' trigger clause, which caps completeness and limits trigger-term quality.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to set up, install, or initialize the commitments tracking system.'

Include natural user phrases like 'set up commitments' or 'install commitments' in the description to mirror the activation keywords.

Mention the default digest channel assumption or that re-setup requires deleting README.md, so the 'when' is more concrete.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('Creates the workspace structure and schema docs, installs triage and digest missions, then excludes itself'), matching the comprehensive-coverage anchor rather than the minor-gaps anchor at 4.	5 / 5
Completeness	Has a clear 'what' but only weakly implies 'when' via 'One-time setup' and the self-exclusion marker; with no explicit 'Use when...' trigger guidance the completeness cap of 3 applies.	3 / 5
Trigger Term Quality	Contains 'commitments tracking system' and 'setup' but lacks the natural user phrases (e.g. 'set up commitments') and variations found in the activation keywords, fitting the some-keywords-but-missing-variants anchor.	3 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (commitments tracking) with a distinct marker ('projects/commitments/README.md') and specific missions, giving minimal conflict risk per the top anchor.	5 / 5
	Total	16 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: nearai/ironclaw
Path: skills/commitment-setup/SKILL.md
Commit: 2831516

Reviewed: 12 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.