prompt-enhancer

Enhance user prompts by analyzing project context (code structure, dependencies, conventions, existing patterns). Use when users provide brief development requests that would benefit from project-specific context to generate more accurate, contextually-aware prompts.

Quality

64%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/prompt-enhancer/SKILL.md

Quality

Discovery

67%

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 good structural completeness with explicit 'what' and 'when' clauses, which is its strongest aspect. However, it lacks specific concrete actions and natural trigger terms that users would actually say. The description is somewhat abstract and could benefit from more specific capability examples and user-facing keywords.

Suggestions

Add more specific concrete actions like 'scans codebase structure, reads package.json/requirements.txt, identifies coding patterns and conventions'

Include natural trigger terms users would say: 'improve my prompt', 'add context to this', 'flesh out this request', 'make this more detailed'

Dimension	Reasoning	Score
Specificity	Names the domain (prompt enhancement) and some actions ('analyzing project context'), but the specific actions are somewhat abstract. Lists context types (code structure, dependencies, conventions, patterns) but doesn't specify concrete operations like 'parse package.json', 'scan directory structure', etc.	2 / 3
Completeness	Clearly answers both what ('Enhance user prompts by analyzing project context') and when ('Use when users provide brief development requests that would benefit from project-specific context'). Has explicit 'Use when...' clause with trigger guidance.	3 / 3
Trigger Term Quality	Includes some relevant terms like 'prompts', 'project context', 'development requests', but misses natural user phrases like 'improve my prompt', 'add context', 'make this more specific', 'flesh out this request', or 'expand this prompt'.	2 / 3
Distinctiveness Conflict Risk	The focus on 'prompt enhancement' and 'project context' provides some distinction, but could overlap with general code analysis skills or documentation skills. The phrase 'development requests' is broad and could conflict with many coding-related skills.	2 / 3
	Total	9 / 12 Passed

Implementation

62%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill provides highly actionable and well-structured guidance for enhancing user prompts with clear workflow steps and validation checkpoints. However, it suffers from severe verbosity - the extensive templates, full example outputs, and framework-specific sections bloat the content significantly. The core concept could be conveyed in under 100 lines while referencing detailed templates externally.

Suggestions

Move the 100+ line example enhancement to a separate EXAMPLES.md file and reference it briefly

Consolidate the framework-specific sections (Flutter, Next.js, Python) into a separate FRAMEWORK-PATTERNS.md reference file

Reduce the main template to essential structure with placeholders rather than fully expanded examples

Remove explanatory text like 'Transform brief development requests into clear, detailed requirements' - Claude understands the purpose from context

Dimension	Reasoning	Score
Conciseness	Extremely verbose with extensive template content that Claude doesn't need spelled out. The 300+ line example enhancement and repeated framework-specific templates add significant token overhead. Much of this could be condensed to patterns and principles rather than full examples.	1 / 3
Actionability	Provides concrete, executable guidance with specific bash commands, clear markdown templates, and detailed examples for multiple frameworks. The workflow steps are specific and copy-paste ready.	3 / 3
Workflow Clarity	Clear 4-step workflow with explicit checkpoints. Step 4 explicitly states 'Do NOT implement until the user confirms' which is a critical validation gate. The sequence is unambiguous and includes feedback loops for clarification.	3 / 3
Progressive Disclosure	References external files (references/enhancement-patterns.md, references/framework-guides.md) appropriately, but the main file contains excessive inline content that should be split out. The framework-specific sections could be separate reference files.	2 / 3
	Total	9 / 12 Passed

Validation

100%

Warnings & errors only

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: bear2u/my-skills
Commit: 1be5394

Reviewed: 18 days ago

Table of Contents

Discovery Implementation Validation

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.