prompt-lookup
Activates when the user asks about AI prompts, needs prompt templates, wants to search for prompts, or mentions prompts.chat. Use for discovering, retrieving, and improving prompts.
79
69%
Does it follow best practices?
Impact
93%
1.55xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/claude/prompts.chat/skills/prompt-lookup/SKILL.mdQuality
Discovery
82%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 does a good job of explicitly stating both when to activate and what it does, with decent trigger term coverage including the specific site 'prompts.chat'. However, the capabilities listed (discovering, retrieving, improving) are somewhat generic and could be more concrete. The broad use of 'prompts' as a trigger term creates some conflict risk with other AI-related skills.
Suggestions
Add more specific concrete actions, e.g., 'Browse the prompts.chat catalog, retrieve prompt templates by category, and suggest improvements to existing prompts' instead of the generic 'discovering, retrieving, and improving'.
Narrow the distinctiveness by clarifying the specific source or method, e.g., 'Searches the prompts.chat database of curated prompt templates' to reduce overlap with general prompt engineering skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (AI prompts) and some actions ('discovering, retrieving, and improving prompts'), but these are somewhat generic and not highly concrete. It doesn't list specific capabilities like 'search prompt databases', 'generate prompt templates', or 'optimize existing prompts with techniques like chain-of-thought'. | 2 / 3 |
Completeness | Explicitly answers both 'what' (discovering, retrieving, and improving prompts) and 'when' ('Activates when the user asks about AI prompts, needs prompt templates, wants to search for prompts, or mentions prompts.chat'). The trigger conditions are clearly stated. | 3 / 3 |
Trigger Term Quality | Includes good natural trigger terms: 'AI prompts', 'prompt templates', 'search for prompts', 'prompts.chat'. These cover multiple natural ways a user might phrase requests related to this skill, including the specific site name. | 3 / 3 |
Distinctiveness Conflict Risk | The mention of 'prompts.chat' adds distinctiveness, but 'AI prompts' and 'improving prompts' could overlap with general prompt engineering skills or other AI-related skills. The term 'prompts' is quite broad and could trigger conflicts with other prompt-related tools. | 2 / 3 |
Total | 10 / 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 is a reasonably well-structured skill for MCP tool usage that clearly identifies available tools and their parameters. Its main weaknesses are the lack of concrete call examples (showing actual input/output), missing error handling guidance, and some redundancy in the activation criteria. The content would benefit from being tightened and augmented with executable examples.
Suggestions
Add concrete tool call examples with sample inputs and expected outputs (e.g., a `search_prompts` call with query='code review' and what the response looks like)
Add error handling guidance: what to do when search returns no results, when a prompt ID is not found, or when improvement fails
Remove the redundant opening sentence and trim the 'When to Use This Skill' section, which largely duplicates the skill description
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but includes some unnecessary framing (e.g., the 'When to Use This Skill' section largely restates what the description already covers, and the opening sentence is redundant). The tool parameter descriptions are useful but could be tighter. | 2 / 3 |
Actionability | Provides concrete tool names and parameter specifications, which is helpful. However, there are no executable examples showing actual tool calls with sample inputs/outputs. The guidance is specific enough to act on but lacks copy-paste-ready examples. | 2 / 3 |
Workflow Clarity | The three workflows (search, get, improve) are clearly separated and sequenced. However, there are no validation checkpoints or error handling guidance—e.g., what to do if search returns no results, if a prompt ID is invalid, or if improvement fails. | 2 / 3 |
Progressive Disclosure | For a simple skill with no bundle files and under 50 lines of substantive content, the organization is clean with well-labeled sections that are easy to navigate. No external references are needed given the scope. | 3 / 3 |
Total | 9 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- f/awesome-chatgpt-prompts
- Commit
b5a3e42
- 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.