CtrlK
BlogDocsLog inGet started
Tessl Logo

meeting-prep

Pull together briefing materials before a scheduled meeting

62

Quality

73%

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

93%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 a tight, actionable, well-structured instruction skill that assumes Claude's intelligence and gives concrete output and sourcing guidance. The only soft spot is the absence of explicit validation checkpoints in the research workflow.

DimensionReasoningScore

Conciseness

The body is lean, assumes Claude's competence, and never over-explains concepts Claude already knows; every line (sections, tool calls, source ordering) earns its place.

5 / 5

Actionability

Though instruction-only, the guidance is highly concrete and executable: four named output sections with sources, an explicit `task(google_search, ...)` invocation, "within the last 30 days", and "3-5 questions".

5 / 5

Workflow Clarity

There is a clear sequence (KB first → external fallback → four output sections) with guardrails ("never to fabricate…", "omit any with no signal"), but no explicit validation checkpoints for the multi-step gather-and-synthesize process.

4 / 5

Progressive Disclosure

At under 50 lines with no bundle files and no need for external references, the well-organized sections (When to use, Output structure, Source ordering) satisfy the simple-skill exception for progressive disclosure.

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 conveys a clear purpose and niche but is thin on natural trigger terms and lacks an explicit "Use when…" clause, leaving activation guidance implicit. It is solid but could be sharpened with user-facing trigger phrasing.

Suggestions

Append an explicit trigger clause, e.g. "Use when the user asks to prep, be briefed, or pull background before a meeting, call, or interview."

Add the natural trigger phrases users say ("prep", "brief me", "pull background", "what do I need to know") so activation matches real phrasing.

Tighten the action verb beyond the generic "pull together" to name concrete deliverables (e.g., "compile attendee context, open threads, and suggested questions").

DimensionReasoningScore

Specificity

"Pull together briefing materials before a scheduled meeting" names a concrete action and domain, but the single verb "pull together" is somewhat generic and coverage is not comprehensive, matching the anchor for one-to-two concrete actions.

3 / 5

Completeness

It states a clear "what" and a thin timing-based "when" ("before a scheduled meeting"), but lacks an explicit "Use when…"-style user-intent trigger clause, which the guidelines cap at 3.

3 / 5

Trigger Term Quality

"briefing materials" and "scheduled meeting" are relevant natural keywords, but common variations users actually say ("prep", "brief me", "pull background") are absent from the description.

3 / 5

Distinctiveness Conflict Risk

The meeting-prep framing is a clear niche with mostly distinct triggers, carrying only minor overlap risk with general research or summarization 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.

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.