tool-discovery
Recommend the right agents and skills for any task. Covers both heavyweight agents (Task tool) and lightweight skills (Skill tool). Triggers on: which agent, which skill, what tool should I use, help me choose, recommend agent, find the right tool.
Install with Tessl CLI
npx tessl i github:NeverSight/skills_feed --skill tool-discovery95
Does it follow best practices?
Validation for skill structure
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted description with strong trigger term coverage and clear completeness. The explicit 'Triggers on:' clause with natural user phrases is excellent for skill selection. The main weakness is moderate specificity - it could benefit from listing more concrete actions beyond 'recommend'.
Suggestions
Add 1-2 more specific actions to improve specificity, e.g., 'Recommend the right agents and skills for any task, compare capabilities, and explain when to use Task tool vs Skill tool.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (agents and skills recommendation) and describes the general action (recommend, covers agents and skills), but lacks specific concrete actions like 'compare capabilities', 'analyze task requirements', or 'explain tradeoffs'. | 2 / 3 |
Completeness | Clearly answers both what ('Recommend the right agents and skills for any task. Covers both heavyweight agents and lightweight skills') and when ('Triggers on:' followed by explicit trigger phrases). The 'Triggers on:' clause serves as an explicit 'Use when' equivalent. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'which agent', 'which skill', 'what tool should I use', 'help me choose', 'recommend agent', 'find the right tool'. These are realistic phrases users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on meta-level tool/agent selection rather than performing tasks directly. The trigger terms are distinct and unlikely to conflict with skills that actually perform work rather than recommend tools. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an exemplary skill file that maximizes information density while maintaining clarity. The decision flowchart, reference tables, and task-matching matrix provide immediately actionable guidance. The structure perfectly balances quick reference with pointers to deeper resources.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. Uses tables, flowcharts, and minimal prose. No unnecessary explanations of what agents or skills are—assumes Claude understands the concepts. | 3 / 3 |
Actionability | Provides concrete trigger keywords, exact tool invocation syntax, and a decision matrix mapping tasks to specific tools. Copy-paste ready examples for both Skill and Task tool usage. | 3 / 3 |
Workflow Clarity | Clear decision flowchart at the top provides unambiguous sequencing. The 'Match by Task Type' table gives explicit guidance on when to escalate from skill to agent. Simple skill with clear single-purpose workflow. | 3 / 3 |
Progressive Disclosure | Perfect structure: quick reference tables inline for immediate use, with clear one-level-deep references to detailed catalogs at the bottom. Navigation is explicit and well-signaled. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- 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.