CtrlK
BlogDocsLog inGet started
Tessl Logo

delegation-tracker

Track delegated commitments, set follow-up timers, and generate nudge reminders when updates are overdue.

61

Quality

73%

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/delegation-tracker/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 skill body is actionable, well-sequenced, and token-efficient, with a mandatory execution order and a write-success validation gate before confirmation. It is solid across all dimensions with only minor gaps.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — no padding about what delegation is — with only minor redundancy between the "Execution order is mandatory" block and the later Action steps.

4 / 5

Actionability

Provides concrete paths, tool calls (memory_search, memory_tree), a full commitment frontmatter template, and a confirmation message template; minor gaps remain in placeholders like "<infer from context>" and "<today>".

4 / 5

Workflow Clarity

A clearly mandated execution order with an explicit validation gate ("Only then confirm"; "Never say tracked... unless the corresponding memory_write succeeded") is present, though no error-recovery branch is defined if the write fails.

4 / 5

Progressive Disclosure

Content is organized into clear, well-signaled sections ("When delegation is detected", "When an update is received", "Follow-up generation") and is self-contained with no need for external references; the inlined full template is the only borderline-inline material.

4 / 5

Total

16

/

20

Passed

Description

71%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 action-oriented with a clear niche, but it lacks an explicit "Use when..." trigger clause, leaving the activation context implied rather than stated.

Suggestions

Append an explicit trigger clause, e.g. "Use when the user mentions delegating, handing off, waiting on, or needing to follow up with someone."

Add natural synonyms users actually say ("waiting on", "handed off", "chase up") to broaden trigger-term coverage.

Tie the nudge/timer behavior to a concrete activation signal so the "when" is as explicit as the "what".

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Track delegated commitments, set follow-up timers, and generate nudge reminders" — covering the domain comprehensively with specific verbs rather than vague language.

5 / 5

Completeness

The "what" is clear and concrete, but there is no explicit "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

Includes natural terms like "delegated commitments", "follow-up", "nudge reminders", and "overdue", but omits common synonyms a user might say (e.g. "waiting on", "handed off", "chase up").

4 / 5

Distinctiveness Conflict Risk

The delegation-tracking niche is mostly distinct with clear triggers, though "commitments" and "follow-up" carry minor overlap risk with general task/todo skills.

4 / 5

Total

16

/

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.