CtrlK
BlogDocsLog inGet started
Tessl Logo

recover-no-show

Use when drafting one bounded follow-up after a supplied meeting record is marked no-show.

62

Quality

72%

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/recover-no-show/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.

A well-structured, lean instruction skill with explicit validation gates and a quality checklist. The main gap is the absence of a concrete worked example showing the actual draft output and gate decision together.

Suggestions

Add one short worked example pairing a gate decision (e.g., READY TO DRAFT) with the resulting labeled draft copy to make the output fully concrete.

Consider trimming redundant phrasing between the Required inputs list and the Guardrails (e.g., 'never invent ... date, time, timezone, duration' repeats input requirements).

DimensionReasoningScore

Conciseness

Lean, dense instruction prose that assumes Claude's competence with no padding about what meetings or no-shows are; only minor tightening possible in the inputs/guardrails lists, so just above the efficient midpoint.

4 / 5

Actionability

Concrete, executable guidance via labeled decision rules (STOP, NEEDS VERIFICATION, DRAFT FOR HUMAN REVIEW) and a defined output format, but no worked example of actual draft copy keeps it just below fully copy-paste ready.

4 / 5

Workflow Clarity

Seven clearly sequenced steps with explicit validation gates (contact gates, option validation, send-readiness checks) and a quality-check checklist; the terminal-by-design error path is not a fix-retry loop, so just below the 5 anchor.

4 / 5

Progressive Disclosure

A short (~45 line) single-purpose skill with no need for external references, organized into well-labeled sections (Purpose, Required inputs, Workflow, Output format, Guardrails, Quality check, Example invocation).

5 / 5

Total

17

/

20

Passed

Description

66%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 concise, third-person, and clearly answers both what and when with a distinctive trigger. It is slightly limited on action coverage and trigger synonym breadth, which keep specificity and trigger_term_quality at mid-range.

Suggestions

Add 1-2 more concrete actions or outcome states (e.g., 'returns a READY/STOP/NEEDS-VERIFICATION gate') to raise specificity.

Include common synonyms a user might say (e.g., 'missed meeting', 'reschedule a no-show') to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain ('meeting record marked no-show') and one concrete action ('drafting one bounded follow-up'), but coverage is a single action rather than several, matching the 1-2 concrete actions anchor.

3 / 5

Completeness

Explicitly answers both what ('drafting one bounded follow-up') and when ('Use when ... after a supplied meeting record is marked no-show'), with the when reasonably specific though a single condition rather than multiple trigger phrases.

4 / 5

Trigger Term Quality

Contains natural terms a user might say ('no-show', 'follow-up', 'meeting record'), but offers no synonyms or variations beyond this narrow phrasing.

3 / 5

Distinctiveness Conflict Risk

Carves a clear niche (bounded no-show recovery) with distinctive triggers ('no-show', 'bounded follow-up') that are unlikely to fire for unrelated skills.

5 / 5

Total

15

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
llaskin/AI-SDR-Skill-Pack
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.