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.
Install with Tessl CLI
npx tessl i github:f/awesome-chatgpt-prompts --skill prompt-lookupOverall
score
72%
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
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.
This description has strong completeness with explicit 'when' triggers and good trigger term coverage including the specific domain 'prompts.chat'. However, the specificity of capabilities could be improved with more concrete actions, and the generic nature of 'prompts' creates some conflict risk with other potential prompt-related skills.
Suggestions
Add more specific concrete actions like 'browse prompt categories', 'adapt prompts for specific use cases', or 'format prompts for different AI models' to improve specificity.
Include distinguishing details about what makes this skill unique compared to general prompt assistance, such as 'access the prompts.chat library' or 'retrieve community-curated prompt templates'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (AI prompts) and some actions ('discovering, retrieving, and improving prompts'), but lacks comprehensive concrete actions like 'search prompt libraries', 'generate prompt variations', or 'analyze prompt effectiveness'. | 2 / 3 |
Completeness | Clearly 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') with explicit trigger conditions. | 3 / 3 |
Trigger Term Quality | Good coverage of natural terms users would say: 'AI prompts', 'prompt templates', 'search for prompts', and the specific site 'prompts.chat'. These are terms users would naturally use when seeking prompt assistance. | 3 / 3 |
Distinctiveness Conflict Risk | The term 'prompts' is somewhat generic and could overlap with other prompt-related skills. However, the specific mention of 'prompts.chat' and focus on prompt templates provides some distinctiveness. | 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 skill provides adequate guidance for using prompts.chat MCP tools but lacks concrete examples of tool calls and expected responses. The structure is good and appropriately sized, but actionability suffers from describing parameters rather than showing executable examples. Adding sample tool invocations would significantly improve usefulness.
Suggestions
Add concrete tool call examples with sample inputs and expected outputs (e.g., show an actual search_prompts call and what the response looks like)
Remove or condense the 'When to Use This Skill' section since activation triggers belong in frontmatter, not body content
Add error handling guidance for common scenarios like no search results found or invalid prompt IDs
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some unnecessary sections like 'When to Use This Skill' which largely repeats what would be in the skill's activation triggers. The tool parameter lists could be more compact. | 2 / 3 |
Actionability | Provides concrete tool names and parameters, but lacks executable examples showing actual tool calls with sample inputs/outputs. The guidance is specific but not copy-paste ready. | 2 / 3 |
Workflow Clarity | Steps are listed for each operation but lack validation checkpoints. The 'Guidelines' section mentions searching before writing but doesn't provide a clear decision workflow or error handling for failed searches. | 2 / 3 |
Progressive Disclosure | For a skill of this size (~60 lines), the content is well-organized with clear section headers. No external references are needed, and the structure allows easy navigation between different tool operations. | 3 / 3 |
Total | 9 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 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 |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 12 / 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.