CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

source-management

Manages connected MCP sources for enterprise search. Detects available sources, guides users to connect new ones, handles source priority ordering, and manages rate limiting awareness.

Quality

69%

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

Quality

Content

67%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-organized, actionable instruction-only skill: ready-to-use message templates, concrete priority orderings per query type, and clear rate-limit handling. Its main costs are token duplication of the source list and a small amount of illustrative padding, plus a reliance on an external reference that is not part of the bundle.

Suggestions

Deduplicate the six-source capability list: keep the table under "Checking Available Sources" and have the connect-guidance template reference it ("You currently have [N] source(s) connected" can list them inline once) instead of repeating the full list.

Trim or repurpose the sample "Source Status" ASCII block in Source Health into a one-line instruction ("report per-source availability as a list"), since the block is illustrative rather than executable.

Make the vague prevention directive concrete, e.g. "skip a source when its tool prefix is absent or the query type's priority list places it last and earlier sources already answered".

DimensionReasoningScore

Conciseness

The six-source capability list is duplicated verbatim (the table under "Checking Available Sources" and again inside the connect-guidance template), and the sample "Source Status" ASCII block is illustrative padding — the body is mostly efficient but could be tightened. It avoids re-explaining concepts Claude already knows, keeping it above a 2.

3 / 5

Actionability

Copy-paste-ready user message templates ("[Tool name] isn't currently connected. To add it: 1. Open your MCP settings..."), concrete per-query-type priority orderings, and numbered connection steps give mostly executable guidance; a few directives like "check if the source is likely to have relevant results before querying" stay vague, preventing a 5.

4 / 5

Workflow Clarity

Sequences are clearly ordered (connect: 3 steps; rate limiting: detection → handling → prevention with recovery guidance like "Do not retry immediately"), but there are no explicit validation checkpoints (e.g. confirming a newly added source is detected). No destructive or batch operations apply, so the 3-cap is not triggered.

4 / 5

Progressive Disclosure

Good section structure in a single ~170-line file of appropriate size, with clearly signaled navigation. Not a 5 because the only reference points outside the skill bundle ("../../CONNECTORS.md", unverifiable from the skill directory) and there is no bundle to split the priority-table detail into.

4 / 5

Total

15

/

20

Passed

Description

58%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 solid, specific description of what the skill does, weakened by the complete absence of when-to-use trigger guidance and thin natural-language trigger terms. The domain framing (MCP sources for enterprise search) keeps conflict risk low.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to connect a source, check which sources are available, or asks why a source is missing or rate limited."

Broaden trigger terms with natural synonyms users would say: "connector", "data source", "add a tool", "which tools are connected".

Replace the abstract "manages rate limiting awareness" with a concrete action such as "detects rate-limited sources and continues searching the remaining ones".

DimensionReasoningScore

Specificity

The description lists several concrete actions — "Detects available sources", "guides users to connect new ones", "handles source priority ordering" — but "manages" and "rate limiting awareness" are slightly generic/abstract, leaving minor gaps in coverage.

4 / 5

Completeness

The "what" is clear and multi-part, but there is no "Use when..." clause or equivalent explicit trigger guidance, which the judging guidelines cap at 3.

3 / 5

Trigger Term Quality

Terms like "MCP sources", "enterprise search", "connect", and "priority" are relevant, but natural user phrasings such as "add a connector", "data source", or "which sources are connected" are missing, matching the anchor for relevant keywords without common variations.

3 / 5

Distinctiveness Conflict Risk

"Connected MCP sources for enterprise search" carves a mostly distinct niche with minor overlap risk against generic search-related skills, but not the fully distinct trigger phrasing of a 5.

4 / 5

Total

14

/

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

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

Repository

anthropics/knowledge-work-plugins

Path

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