CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

minutes-mcp-recall

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

Quality

77%

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 ./.claude/plugins/minutes/skills/minutes-mcp-recall/SKILL.md

The canonical home for this skill is minutes-mcp-recall in silverstein/minutes

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 content is a well-structured, lean routing overview with a concrete decision table, clear host-prefix rules, and a properly signaled one-level-deep reference to a real bundle file. It is highly actionable and well-organized, with only minor conciseness trimming possible in the anti-patterns.

DimensionReasoningScore

Conciseness

The body is lean with no over-explanation of concepts Claude already knows (no 'what is MCP' or 'what is a meeting'); it is not a 5 because the anti-patterns carry minor justificatory padding ('It returns a full transcript', 'Replaying the whole transcript wastes tokens ...') that could be trimmed.

4 / 5

Actionability

The decision table maps concrete user phrases to exact tool names and the prefix section gives a concrete rule ('mcp_minutes_' prefix); for an instruction-only skill this is copy-paste-ready, actionable guidance covering the common cases, so absence of code is not penalized.

5 / 5

Workflow Clarity

This is a simple single-purpose routing skill whose single action is unambiguous via the decision table; the operations are read-only recall (not destructive/batch), so the validation cap does not apply and the simple-skill exception permits a 5, with the noted multi-step get_meeting sequence explicitly described.

5 / 5

Progressive Disclosure

The body is a clear overview with well-signaled one-level-deep navigation to the verified-real references/tool-map.md ('Read ... only when the decision table does not cover the request'), and the bulk detail (34-tool map) is appropriately split into that reference file.

5 / 5

Total

19

/

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 names a distinct niche and a concrete routing action but is held back by the absence of an explicit 'Use when...' trigger clause and sparse natural trigger terms. It is clear but not comprehensive enough to score above the midpoint on most dimensions.

Suggestions

Add an explicit 'Use when...' clause naming concrete trigger phrases, e.g. 'Use when the user asks what was said in a meeting, asks to find a past meeting, or checks who owes a commitment.'

Include natural user-facing trigger terms and synonyms ('meeting notes', 'transcript', 'what was said', 'find that meeting') instead of relying on 'meeting-recall questions' and the technical 'MCP'.

List 1-2 more concrete actions (e.g. 'search, retrieve, and summarize meeting transcripts') to raise specificity beyond a single routing verb.

DimensionReasoningScore

Specificity

Names the domain ('meeting-recall questions', 'Minutes MCP tool') and one concrete action ('Route ... to the right ... tool'), matching the '1-2 concrete actions but not comprehensive' anchor; it is not a 2 because a concrete routing action is named, and not a 4 because no additional specific actions are listed.

3 / 5

Completeness

It gives a clear 'what' (route meeting-recall questions to the right tool) but 'when' is only weakly implied by the object phrase with no explicit 'Use when...' clause, so per the guideline completeness is capped at 3.

3 / 5

Trigger Term Quality

'meeting-recall questions' is a relevant trigger phrase, but 'MCP' is technical jargon and natural variations users would actually say ('meeting notes', 'what was said', 'transcript', 'find that meeting') are missing, fitting 'some relevant keywords but missing common variations'.

3 / 5

Distinctiveness Conflict Risk

It carves a clear niche (Minutes MCP meeting recall) with low conflict risk; it is not a 5 because it lacks the explicit 'use when ... mentions ...' trigger phrasing of the 5 anchor and could overlap with generic meeting-search skills.

4 / 5

Total

13

/

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.

Validation — 15 / 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

silverstein/minutes

Path

.claude/plugins/minutes/skills/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.