CtrlK
BlogDocsLog inGet started
Tessl Logo

prompt-engineering

Use this skill when you writing commands, hooks, skills for Agent, or prompts for sub agents or any other LLM interaction, including optimizing prompts, improving LLM outputs, or designing production prompt templates.

36

Quality

33%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./plugins/customaize-agent/skills/prompt-engineering/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

27%

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

This skill attempts to cover three large topics (prompt engineering, agent prompting, persuasion principles) in a single monolithic file, resulting in excessive verbosity and poor organization. It explains many concepts Claude already knows (context windows, few-shot learning, persuasion psychology) and reads more like an educational document than an actionable skill reference. The strongest sections are the concrete good/bad examples in the persuasion principles, but overall the skill would benefit dramatically from aggressive trimming and splitting into focused sub-files.

Suggestions

Split into 3-4 separate files (e.g., PROMPT_PATTERNS.md, AGENT_PROMPTING.md, PERSUASION.md) with SKILL.md serving as a concise overview with links to each

Remove explanations of concepts Claude already knows: what context windows are, what few-shot learning is, what chain-of-thought prompting is, basic persuasion psychology definitions

Add a concrete workflow with validation steps for prompt development: draft → test on edge cases → measure metrics → iterate, with specific checkpoints

Reduce the persuasion principles section to just the table, examples, and quick reference - cut the psychology explanations and research citations

DimensionReasoningScore

Conciseness

This skill is extremely verbose at ~400+ lines. It explains concepts Claude already knows well (what a context window is, what few-shot learning is, what chain-of-thought prompting is, basic persuasion psychology). The entire 'Context Window' section explains what a context window is to an LLM. The persuasion principles section includes extensive psychological explanations that don't add actionable value. Much of this content restates common knowledge.

1 / 3

Actionability

The skill provides some concrete examples (Python templates, prompt structures, markdown examples) but much of the content is descriptive rather than instructive. Sections like 'Best Practices' and 'Common Pitfalls' are generic lists without executable guidance. The persuasion principles provide good/bad example comparisons which are actionable, but the prompt engineering section is more educational than operational.

2 / 3

Workflow Clarity

The 'Progressive Disclosure' pattern shows a clear 4-level sequence, and the 'Prompt Optimization' section shows an iterative versioning approach. However, there are no explicit validation checkpoints or feedback loops for the prompt engineering workflow itself. The 'degrees of freedom' section provides useful categorization but lacks a clear decision workflow. No verification steps for when prompts are deployed to production.

2 / 3

Progressive Disclosure

This is a monolithic wall of text combining three distinct topics (prompt engineering patterns, agent prompting best practices, persuasion principles) all in a single file with no references to supporting files. The content would benefit enormously from being split into separate files with a concise overview in SKILL.md pointing to detailed references. No bundle files are provided despite the content length warranting them.

1 / 3

Total

6

/

12

Passed

Description

40%

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 functions primarily as a trigger clause without explaining what the skill actually does — it tells Claude when to use it but not what concrete actions or outputs it provides. The language is vague and overly broad, covering a wide range of LLM-related activities without specificity. Additionally, it uses second person voice ('you writing') which violates the style guidelines.

Suggestions

Add a clear 'what it does' section listing specific concrete actions, e.g., 'Generates system prompts, refactors prompt templates, adds few-shot examples, structures chain-of-thought reasoning, and optimizes token usage in LLM interactions.'

Rewrite in third person voice — change 'Use this skill when you writing' to something like 'Assists with crafting and optimizing prompts... Use when...'

Narrow the scope or add more distinct trigger terms to reduce overlap, e.g., specify 'prompt engineering', 'system prompt design', 'few-shot prompting', '.skill.md files' to create a clearer niche.

DimensionReasoningScore

Specificity

The description mentions broad categories like 'commands, hooks, skills for Agent' and 'prompts for sub agents' but does not list concrete actions (e.g., 'generate prompt templates', 'refactor system prompts', 'add few-shot examples'). The actions are vague: 'writing', 'optimizing', 'improving', 'designing' are generic verbs without specifics.

1 / 3

Completeness

It has a 'Use when' clause that addresses the 'when' question, but the 'what does this do' part is essentially absent — it only describes when to use it, not what concrete capabilities or outputs the skill provides. The description is entirely trigger-focused without explaining what the skill actually does.

2 / 3

Trigger Term Quality

It includes some relevant keywords like 'prompts', 'LLM', 'hooks', 'skills', 'sub agents', 'prompt templates' that users might naturally use. However, it misses common variations like 'system prompt', 'few-shot', 'prompt engineering', 'chain of thought', and the phrasing is somewhat jargon-heavy with terms like 'hooks' and 'commands' that could be ambiguous.

2 / 3

Distinctiveness Conflict Risk

The mention of 'commands, hooks, skills for Agent' could overlap with general coding or agent-building skills. 'Prompts for sub agents or any other LLM interaction' is broad enough to potentially conflict with many AI-related skills. The scope is somewhat defined but not sharply bounded.

2 / 3

Total

7

/

12

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

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

Warning

Total

10

/

11

Passed

Repository
NeoLabHQ/context-engineering-kit
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.