CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

minutes-mcp-recall

Route meeting-recall questions to the right Minutes MCP tool.

Quality

76%

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 ./tooling/skills/goldens/claude/minutes-mcp-recall/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

92%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 an exemplary lean routing skill: a decision table with concrete tool names, host-specific prefix rules, and justified anti-patterns, with no wasted tokens. Its single defect is that the referenced references/tool-map.md is missing from the bundle, leaving the escalation path for uncovered requests broken.

Suggestions

Create references/tool-map.md with the complete Minutes MCP tool map, or remove the reference if the decision table is meant to be exhaustive — currently the link points to a file that does not exist.

If the tool map is added, keep it one level deep and organized by question type so the body's conditional reference ("only when the decision table does not cover the request") stays useful.

Optionally state in the body what to do when no table row matches and the tool map is unavailable, so the routing skill degrades gracefully.

DimensionReasoningScore

Conciseness

The body is lean and efficient: a decision table, two prefix rules, and three anti-patterns, with every line earning its place ("Do not call `get_meeting` speculatively to browse. It returns a full transcript."). There is no padding and no explanation of concepts Claude already knows, matching the anchor for assuming Claude's competence. The brief justifications in the anti-patterns (token waste, context budget) are operationally relevant, not verbosity.

5 / 5

Actionability

For an instruction-only skill the guidance is fully actionable: the decision table maps concrete user questions to specific tool names (`search_meetings`, `track_commitments`, `consistency_report`), the host section gives an exact transformation (`search_meetings` becomes `mcp_minutes_search_meetings`), and the `get_meeting` row embeds the specific find-then-fetch steps. The common cases are covered with copy-paste-ready tool names, so the absence of code is not penalized per the scoring notes.

5 / 5

Workflow Clarity

This is a simple single-purpose routing skill and the single action (pick the right tool) is unambiguous via the decision table, which per the rubric's simple-skill guidance merits a 5. The one multi-step path ("`get_meeting` after finding its id or date with `list_meetings` or `search_meetings`") is explicitly sequenced, and no validation checkpoints are needed since every operation is a read-only recall query, so the destructive/batch cap does not apply.

5 / 5

Progressive Disclosure

The body is well-sectioned and signals its one reference cleanly with an explicit condition ("Read [the complete tool map](references/tool-map.md) only when the decision table does not cover the request"), but the referenced file does not exist — there is no references/ directory in the bundle, making the link dangling. Scored against the actual bundle structure, a broken reference is more than the minor organization gap of anchor 4, landing at anchor 3.

3 / 5

Total

18

/

20

Passed

Description

53%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 and names a specific niche, but it tells Claude what the skill does without saying when to use it. It lacks the natural trigger phrases and capability list that would make routing to this skill reliable.

Suggestions

Add an explicit 'Use when...' clause with concrete trigger phrases, e.g. "Use when the user asks what was said in a meeting, wants to find a past meeting, check who owes what, or review their history with a person."

List 2-3 concrete capabilities to raise specificity, e.g. "Route meeting-recall questions (search transcripts, fetch full meetings, track commitments, check consistency) to the right Minutes MCP tool."

Include the natural user phrasings already present in the body's decision table ("What did we say about X?", "Who owes me?") as trigger terms in the description itself.

DimensionReasoningScore

Specificity

The description names the domain ("meeting-recall questions", "Minutes MCP tool") and one action ("Route ... to the right tool"), matching the anchor for 1-2 concrete actions without comprehensive coverage. It does not list the specific capabilities (search transcripts, fetch full meetings, track commitments), which keeps it below anchor 4.

3 / 5

Completeness

It has a clear 'what' ("Route meeting-recall questions to the right Minutes MCP tool") but no 'Use when...' clause or equivalent explicit trigger guidance; the 'when' is only weakly implied by the domain mention. Per the judging guideline, a missing explicit trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

"meeting-recall" and "Minutes MCP tool" are relevant domain keywords, analogous to "Works with PDF files", but natural phrases users actually say ("what did we say about", "find that meeting", "who owes me") and their synonyms are missing. This places it above anchor 2 (purely generic keywords) but below anchor 4's good keyword coverage.

3 / 5

Distinctiveness Conflict Risk

"Minutes MCP tool" carves out a clear, specific niche that is mostly distinct with only minor overlap risk against closely related meeting-transcript or memory skills. It falls short of anchor 5 because no distinct trigger phrases are given to fully disambiguate it from those neighbors.

4 / 5

Total

13

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 1 missing

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

13

/

16

Passed

Repository

silverstein/minutes

Path

tooling/skills/goldens/claude/minutes-mcp-recall/SKILL.md

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.