CtrlK
BlogDocsLog inGet started
Tessl Logo

commitment-digest

Compose and deliver summaries of open commitments, deadlines, pending signals, and resolution suggestions.

59

Quality

68%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/commitment-digest/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 content is well-structured, concise, and highly actionable, with a clear workflow and an appropriate single-file organization for a simple read-and-summarize skill.

DimensionReasoningScore

Conciseness

The body is lean — no concept explanations, direct memory_tree/memory_read calls, and a tight output template — with only minor restatement between the numbered gathering steps and the 'Use memory_tree and memory_read for digest assembly' line, fitting the efficient-but-trimmable anchor 4.

4 / 5

Actionability

Concrete commands with exact paths (e.g. memory_tree("projects/commitments/open/", depth=1)) and a copy-paste output template make it mostly executable, but counting steps ('count pending signals') and 'today's date' leave minor gaps versus the fully copy-paste anchor 5.

4 / 5

Workflow Clarity

A clear numbered gathering sequence plus ordered composing/delivery sections and an explicit false-negative feedback loop ('Did I miss anything?') provide most checkpoints; only a light read-validation gap keeps it below anchor 5.

4 / 5

Progressive Disclosure

This single-purpose skill has no external bundle files and is organized into well-signaled sections (Gathering data, Composing the digest, Delivery), so the simple-skill exception applies and structure is clear without nested references.

5 / 5

Total

17

/

20

Passed

Description

58%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 well-scoped to a clear niche, but it lacks an explicit 'when to use' trigger clause and the natural user phrases that would improve trigger-term quality and completeness.

Suggestions

Append a 'Use when...' clause naming concrete triggers, e.g. 'Use when the user asks to review open commitments, what's overdue or due, or wants a commitment digest/report.'

Add natural user phrases such as 'what do I owe' or 'what's overdue' directly into the description so trigger-term quality reaches the natural-language anchor.

Keep the existing specificity but ensure the 'when' guidance is as explicit as the 'what' to lift completeness above 3.

DimensionReasoningScore

Specificity

Quotes 'Compose and deliver summaries of open commitments, deadlines, pending signals, and resolution suggestions' — names the domain plus several concrete actions (compose, deliver, suggest resolutions), with only minor coverage gaps versus the comprehensive anchor 5.

4 / 5

Completeness

It gives a clear 'what' (compose/deliver summaries of commitments, deadlines, signals, resolutions) but provides no explicit 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

The description surfaces 'commitments', 'deadlines', and 'pending signals', which are relevant, but it omits the natural phrasings users actually say (e.g. 'what do I owe', 'what's overdue') that only appear in the activation block, not the description.

3 / 5

Distinctiveness Conflict Risk

'Commitment digest' is a clear, narrow niche with distinct triggers; only minor overlap risk exists with generic task-management skills, fitting the 'mostly distinct' anchor 4 rather than the fully distinct anchor 5.

4 / 5

Total

14

/

20

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.