CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

search

Search across all connected sources in one query. Trigger with "find that doc about...", "what did we decide on...", "where was the conversation about...", or when looking for a decision, document, or discussion that could live in chat, email, cloud storage, or a project tracker.

Quality

80%

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 ./enterprise-search/skills/search/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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, actionable workflow with concrete filter syntax, per-source mappings, and ready-to-use response templates for the common cases. Its weaknesses are redundancy — the Notes section and query-parsing guidance repeat or re-teach what the numbered steps and Claude's own competence already cover — and a missing explicit verification checkpoint between ranking and presenting results.

Suggestions

Cut the 'Notes' section or reduce it to only the two points not already stated in steps 1-7 (e.g., the single-source and person-mention handling), removing the restated parallel-search, synthesis, attribution, and filter bullets.

Trim the step 2 query-parsing bullets ('Intent', 'Entities', 'Time constraints') to just the filter syntax definitions, trusting Claude to parse a query without the taxonomy.

Add an explicit checkpoint between steps 5 and 6: verify the top-ranked results actually answer the parsed intent (and that dedupe merged true duplicates) before formatting the unified response.

DimensionReasoningScore

Conciseness

The body is mostly efficient but includes unnecessary explanation and repetition: query parsing guidance ('Intent', 'Entities', 'Time constraints') teaches Claude what it already knows, the 'Notes' section restates instructions from earlier sections ('Always search multiple sources in parallel — never sequentially' duplicates step 4; 'Synthesize results...' duplicates step 6), and 'Use natural language queries for semantic search when appropriate' is inferable filler. Not 4 because these redundant/padded sections are more than minor; not 2 because most sections carry real, skill-specific guidance.

3 / 5

Actionability

For an instruction-only skill the guidance is fully concrete: explicit filter syntax (from:, in:, after:, before:, type:) with per-source translation mappings, and copy-paste-ready response templates covering factual, exploratory, find, no-results, partial-results, and ambiguous-query cases. The absence of literal tool names is justified flexibility since MCP tools vary; not 4 because the templates and filter grammar are specific enough to execute directly across the common cases.

5 / 5

Workflow Clarity

A clear 7-step sequence (check sources → parse query → decompose → parallel execute → rank/dedupe → present → edge cases) with failure handling ('do not let one failure block others', partial-results template with retry suggestions). Not 5 because there is no explicit checkpoint verifying results actually answer the query intent before presenting, and the dedupe/rank step lacks a concrete validation loop; not 3 because failure recovery and error-tolerant execution are explicitly addressed throughout.

4 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ absent), and the single well-sectioned SKILL.md with a clearly signaled one-level-deep pointer to CONNECTORS.md is good structure with minor organization gaps. Not 5 because at ~170 lines the response templates and per-source translation guides are borderline inline content that could be split into reference files; not 3 because what is present is clearly sectioned, navigable, and references are not buried.

4 / 5

Total

16

/

20

Passed

Description

78%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.

A strong description: it explicitly states what the skill does and when to use it, with naturally spoken trigger phrases and third-person voice. The main gap is that it names only the top-level action (search across sources) without hinting at the decompose/parallelize/synthesize behavior that differentiates it.

DimensionReasoningScore

Specificity

The description names the domain ('Search across all connected sources in one query') but offers only that single action — it does not enumerate the concrete sub-capabilities (decompose, parallel search, synthesize, rank) that the body actually performs. Matches 'names domain and 1-2 concrete actions, but not comprehensive'; not 4 because several specific actions are not listed, not 2 because the action given is concrete rather than generic.

3 / 5

Completeness

Explicitly answers 'what' ('Search across all connected sources in one query') and 'when' ('Trigger with ... or when looking for a decision, document, or discussion that could live in chat, email, cloud storage, or a project tracker') with concrete trigger phrases, matching the top anchor exactly. Not 4 because the 'when' clause is already fully explicit with quoted trigger phrasings.

5 / 5

Trigger Term Quality

Natural spoken trigger phrases are directly quoted ('find that doc about...', 'what did we decide on...', 'where was the conversation about...') plus concrete nouns (decision, document, discussion, chat, email, cloud storage, project tracker) with synonyms covered. Not 5 because a few common variations are absent (e.g., 'search for', 'locate', 'that file/message', 'where is...').

4 / 5

Distinctiveness Conflict Risk

The federated cross-source search niche ('all connected sources in one query') is distinct with memorable trigger phrases, so it is 'mostly distinct; minor overlap risk'. Not 5 because generic phrasing like 'looking for a document' could also plausibly fire single-source file/search skills; not 3 because the cross-source framing and quoted triggers keep it clearly distinguishable.

4 / 5

Total

16

/

20

Passed

Validation

87%

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

Validation — 14 / 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 suspicious

Warning

Total

14

/

16

Passed

Repository

anthropics/knowledge-work-plugins

Path

enterprise-search/skills/search/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.