CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

prompt-enhancer

Prompt engineering and optimization for AI/LLMs. Capabilities: transform unclear prompts, reduce token usage, improve structure, add constraints, optimize for specific models, backward-compatible rewrites. Actions: improve, enhance, optimize, refactor, compress prompts. Keywords: prompt engineering, prompt optimization, token efficiency, LLM prompt, AI prompt, clarity, structure, system prompt, user prompt, few-shot, chain-of-thought, instruction tuning, prompt compression, token reduction, prompt rewrite, semantic preservation. Use when: improving unclear prompts, reducing token consumption, optimizing LLM outputs, restructuring verbose requests, creating system prompts, enhancing prompt clarity.

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

63%Weight 40%Scale 1-5

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

The body is highly actionable — the token-optimization section in particular provides novel, concrete, end-to-end guidance with worked examples — but it is noticeably verbose, explaining prompting techniques Claude already knows, repeating output rules, and over-exemplifying. Splitting the specialized deep-dives into reference files would address both conciseness and progressive disclosure.

Suggestions

Move the ~120-line LLM Output Token Optimization deep-dive (key mappings, tradeoffs analysis, worked real-world example) into a references/ file, keeping only a short when-to-apply decision summary in SKILL.md — this improves both conciseness and progressive disclosure.

Compress the nine-technique catalog (CoT, Few-Shot, ReAct, etc.) into a compact one-line-per-technique table or move it to a reference file; Claude already knows these techniques, so only the when-to-apply-within-enhancement guidance adds value.

State the output-only rule once (in the Output Format section), and merge 'Enhancement Process' and 'Implementation Notes' into a single numbered workflow that ends with the quality checklist wired to an explicit revise-if-checklist-fails step.

DimensionReasoningScore

Conciseness

The ~380-line body catalogs nine prompting techniques Claude already knows (CoT, Few-Shot, ReAct, Self-Consistency, Tree-of-Thoughts, Role-Based, Least-to-Most at ~4 lines each), states the output-only rule three times ('Clean Output: Return ONLY the enhanced prompt', 'Return ONLY the enhanced prompt with: No conversational lead-in', 'Output ONLY the enhanced version'), and includes four full before/after examples where two would establish the pattern — noticeably verbose with several padded sections (anchor 2).

2 / 5

Actionability

Guidance is fully concrete and copy-paste ready: exact key mappings ('queries → q, keyword → kw, filter → f, sort_by → s'), a complete implementation pattern for both the system prompt and application remapping layer, a worked real-world token-optimization example with <categories> mapping and <examples>, and four complete before/after transformations covering the common cases (anchor 5).

5 / 5

Workflow Clarity

A clear sequence is present (Input Analysis → technique selection → token optimization → structural improvements → language optimization, plus the 5-step Implementation Notes) with an explicit validation checkpoint ('Before returning the enhanced prompt, verify: ✓ Main objective is clear...'). Not 5 because there is no feedback loop from a failed checklist to a revision step and the flow is split across two sections; not 3 because checkpoints are explicit and the non-destructive task needs no more validation than the checklist provides.

4 / 5

Progressive Disclosure

No bundle files exist and everything is inlined in a single ~380-line SKILL.md; the ~120-line 'LLM Output Token Optimization' deep-dive (mapping tables, tradeoffs analysis, worked example) and the technique catalog are specialized content that should live in separate reference files (anchor 3: content that should be separate is inline). Not 2 because section headers are clear and well-organized, giving real structure.

3 / 5

Total

14

/

20

Passed

Description

96%Weight 40%Scale 1-5

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 is excellent: concrete capabilities, comprehensive natural trigger terms, and explicit what-and-when guidance in third-person voice. The only weakness is a handful of generically-scoped keywords ('clarity', 'structure') that create minor conflict risk with writing/editing skills.

DimensionReasoningScore

Specificity

Six concrete capabilities are enumerated in third-person noun phrases ('transform unclear prompts, reduce token usage, improve structure, add constraints, optimize for specific models, backward-compatible rewrites'), comprehensively covering transformation, token efficiency, structure, constraints, model tuning, and compatibility — a direct anchor-5 match with no notable gaps.

5 / 5

Completeness

It explicitly answers both questions: 'Capabilities:' states what the skill does, and an explicit 'Use when: improving unclear prompts, reducing token consumption, optimizing LLM outputs...' clause enumerates six concrete trigger scenarios — matching the anchor-5 example pattern.

5 / 5

Trigger Term Quality

Sixteen keywords with synonym clusters (LLM prompt/AI prompt; prompt optimization/prompt compression/token reduction) plus natural action verbs users would actually say ('improve, enhance, optimize, refactor, compress prompts') give comprehensive natural-term coverage; the rare jargon entries ('instruction tuning') are offset by dominant natural phrasing.

5 / 5

Distinctiveness Conflict Risk

The LLM prompt-engineering niche is clear with distinct triggers ('prompt engineering', 'few-shot', 'chain-of-thought'), but generic keyword entries like 'clarity', 'structure', and 'improve' could overlap general writing/editing skills, and 'reduce token usage' overlaps cost-optimization skills — mostly distinct with minor overlap risk (anchor 4).

4 / 5

Total

19

/

20

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

samhvw8/dot-claude

Path

skills/prompt-enhancer/SKILL.md

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.