CtrlK
BlogDocsLog inGet started
Tessl Logo

meeting-prep

Pull together briefing materials before a scheduled meeting

63

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./surfsense_backend/app/agents/chat/multi_agent_chat/main_agent/skills/builtin/meeting-prep/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a tight, well-structured instruction-only skill: concrete output sections, an explicit source-ordering workflow with a fabrication guardrail, and no token waste. It fully satisfies the conciseness, actionability, workflow, and disclosure dimensions for a sub-50-line single-purpose skill.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — no definition of what a meeting or KB is, no library tutorials, and each line ("omit any with no signal — don't pad", "within the last 30 days", "3-5 questions") earns its place, matching the 'lean and efficient' anchor 3.

3 / 3

Actionability

For an instruction-only skill the guidance is concrete and executable: named output sections with specific content directives, a concrete tool invocation `task(google_search, ...)`, and precise parameters (last 30 days, 3-5 questions), meeting the 'specific, copy-paste ready' anchor 3 without needing code.

3 / 3

Workflow Clarity

Source ordering gives an explicit sequence ("Always check the user's KB first", "Only fall back to...") with a fabrication guardrail, and as a single-purpose skill under 50 lines that is clearly organized, the simple-skills carve-out permits a 3; it is above 2 because the sequence and ordering rule are explicit rather than implicit.

3 / 3

Progressive Disclosure

The skill is under 50 lines, needs no external references, and is organized into well-signaled sections (When to use, Output structure, Source ordering), which the guidelines say lets progressive disclosure score 3 on well-organized sections alone.

3 / 3

Total

12

/

12

Passed

Description

50%

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 clean and third-person but middling: it conveys a single action and a timing cue without explicit trigger guidance or a list of concrete capabilities. Adding a 'Use when...' clause with the skill's natural trigger phrases would lift completeness and trigger-term quality together.

Suggestions

Add an explicit 'Use when...' clause listing natural triggers (prep, brief me, pull background, what do I need to know, call, interview) to raise completeness and trigger_term_quality.

Enumerate concrete capabilities (gather attendee context, surface open threads, compile recent moves, draft suggested questions) to move specificity from one action to multiple concrete actions.

Include trigger variations like 'call' and 'interview' alongside 'meeting' to sharpen distinctiveness and reduce overlap with general research skills.

DimensionReasoningScore

Specificity

"Pull together briefing materials" names the meeting-prep domain and a single action, but does not enumerate multiple concrete actions (e.g. gather attendee context, surface open threads, draft questions), so it stops at the 'some actions, not comprehensive' anchor rather than reaching 3.

2 / 3

Completeness

It answers 'what' (pull together briefing materials) and gives a timing cue ("before a scheduled meeting"), but there is no explicit 'Use when...' clause with trigger guidance, which the guidelines say caps completeness at 2; it is above 1 because both what and a partial when are present.

2 / 3

Trigger Term Quality

"briefing materials" and "scheduled meeting" are natural terms a user might say, but coverage is thin and omits common variations the body itself lists ("prep", "brief me", "call", "interview", "pull background"), landing at 'some relevant keywords but missing common variations' rather than the full-coverage anchor 3.

2 / 3

Distinctiveness Conflict Risk

The meeting-prep niche is fairly specific and unlikely to trigger for unrelated skills, but the description's sparse trigger terms let it overlap with general research/briefing skills, so it sits at 'somewhat specific but could still overlap' rather than the distinct-trigger anchor 3.

2 / 3

Total

8

/

12

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

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

15

/

16

Passed

Repository
MODSetter/SurfSense
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.