skill-lookup
Activates when the user asks about Agent Skills, wants to find reusable AI capabilities, needs to install skills, or mentions skills for Claude. Use for discovering, retrieving, and installing skills.
Install with Tessl CLI
npx tessl i github:f/awesome-chatgpt-prompts --skill skill-lookupOverall
score
75%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
90%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-structured description with strong trigger terms and clear 'when' guidance. The main weakness is that the 'what' portion could be more specific about the concrete actions performed (e.g., search skill registries, download skill files, configure skill settings). The description effectively uses third person voice and provides good disambiguation.
Suggestions
Expand the capabilities section with more specific actions like 'search skill registries, download skill packages, configure skill settings' to improve specificity
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Agent Skills) and some actions ('discovering, retrieving, and installing skills'), but lacks comprehensive detail about what specific operations are performed or what skills actually are. | 2 / 3 |
Completeness | Clearly answers both what ('discovering, retrieving, and installing skills') and when ('Activates when the user asks about Agent Skills, wants to find reusable AI capabilities, needs to install skills, or mentions skills for Claude') with explicit trigger conditions. | 3 / 3 |
Trigger Term Quality | Good coverage of natural terms users would say: 'Agent Skills', 'reusable AI capabilities', 'install skills', 'skills for Claude', 'discovering', 'retrieving'. These are terms users would naturally use when looking for this functionality. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on Agent Skills management with distinct triggers like 'Agent Skills', 'install skills', 'skills for Claude'. Unlikely to conflict with other skills due to the specific domain focus. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a functional guide for using prompts.chat MCP tools but could be more actionable with concrete examples of tool calls and responses. The workflow for installation lacks validation steps, and some sections explain concepts Claude already understands. The organization is good for the skill's scope.
Suggestions
Add concrete tool call examples showing actual JSON parameters and expected response formats for search_skills and get_skill
Add validation steps to the install workflow: check if directory exists, verify files were written, handle errors from get_skill
Remove or condense the 'When to Use This Skill' section - these triggers are obvious from context
Remove the 'Skill Structure' section - Claude understands file types and doesn't need this explained
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but includes some unnecessary explanation like the 'When to Use This Skill' section which lists obvious triggers Claude could infer, and the 'Skill Structure' section explains concepts Claude already knows. | 2 / 3 |
Actionability | Provides clear tool names and parameters but lacks concrete examples of actual tool calls or expected responses. The installation steps are described but not shown with executable commands or code. | 2 / 3 |
Workflow Clarity | The install workflow has numbered steps but lacks validation checkpoints - no verification that files were saved correctly, no error handling if get_skill fails, and no confirmation step before overwriting existing skills. | 2 / 3 |
Progressive Disclosure | For a skill of this size (~80 lines), the content is well-organized with clear section headers. No external references are needed, and the structure allows easy navigation between search, get, and install operations. | 3 / 3 |
Total | 9 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 13 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
body_examples | No examples detected (no code fences and no 'Example' wording) | Warning |
Total | 13 / 16 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.