CtrlK
BlogDocsLog inGet started
Tessl Logo

best-practices

Transforms vague prompts into optimized Claude Code prompts. Adds verification, specific context, constraints, and proper phasing. Invoke with /best-practices.

60

Quality

72%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/best-practices/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%

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

Highly actionable and clearly sequenced with strong validation checkpoints and a properly organized reference layer. Its main weakness is conciseness — substantial repetition across the principles, examples, and eval sections inflates the token budget without adding new guidance.

Suggestions

Deduplicate the repeated before/after pairs: keep one canonical example per principle and remove the re-treads in Quick Examples and the Success Criteria section.

Move the full Quick Transformation Examples block and the Prompt Quality Eval rubric into a reference file, keeping only a pointer in SKILL.md.

Consolidate the Transformation Checklist and Quick Prompt Quality Check into a single checklist to avoid redundant scoring guidance.

DimensionReasoningScore

Conciseness

The ~494-line body repeats the same before/after pairs ("fix the login bug", "the API error") in the principles, Quick Examples, and Success Criteria sections, and the Quick Prompt Quality Check duplicates the checklist — accurate but padded with redundancy.

2 / 3

Actionability

Provides concrete, copy-paste-ready before/after examples, explicit "what to add" tables, and a step-by-step transform workflow — fully executable guidance rather than abstract direction.

3 / 3

Workflow Clarity

Sequences the flow clearly (mode selection → apply 5 principles → output → checklist) with validation checkpoints, and the context-first path spells out parallel agents plus post-synthesis steps.

3 / 3

Progressive Disclosure

References are well-signaled and one-level-deep with all five referenced files present, but the body keeps large inline content (10 Quick Transformation Examples, a second eval rubric) that duplicates references/before-after-examples.md and should live in a separate file.

2 / 3

Total

10

/

12

Passed

Description

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.

A specific, distinctive description that names concrete actions and a clear niche. It is held back by a missing explicit "Use when..." trigger clause and only partial coverage of natural user phrasings.

Suggestions

Add an explicit "Use when..." clause, e.g. "Use when a user asks to improve, fix, or optimize a prompt for Claude Code."

Broaden trigger terms to include natural phrasings like "improve my prompt", "rewrite this prompt", or "make this prompt better".

Keep third-person voice (already correct) but replace the invocation-only "when" signal with a usage-condition sentence.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Adds verification, specific context, constraints, and proper phasing" — naming exactly what the transformer does rather than vague fluff.

3 / 3

Completeness

Clearly states what the skill does, but the "when" is only conveyed via "Invoke with /best-practices" rather than an explicit "Use when..." trigger clause, which caps completeness at 2 per the guidelines.

2 / 3

Trigger Term Quality

Contains relevant terms ("prompts", "Claude Code prompts", "vague prompts") but misses common user phrasings like "improve my prompt" or "fix this prompt"; coverage is present but incomplete.

2 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (prompt transformation/optimization) with distinct triggers, making it unlikely to fire for unrelated skills.

3 / 3

Total

10

/

12

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (502 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository
MoizIbnYousaf/Ai-Agent-Skills
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.