CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

prompt-engineering

Provides workflows to write, debug, and optimize prompts for LLMs, including few-shot example selection, chain-of-thought structuring, system prompt design, and template composition. Use when the user asks to write or improve a prompt, wants help with few-shot examples, chain-of-thought, system prompts, prompt templates, or asks how to get better results from an LLM.

69

Quality

87%

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

The canonical home for this skill is giuseppe-trisciuoglio/developer-kit

SKILL.md
Quality
Evals
Security

Quality

Content

71%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.

Well-structured, actionable content with good progressive disclosure and a feedback loop in the optimization workflow. The main weakness is conciseness: repeated metrics, duplicate Constraints sections, and a filler integration section inflate the body.

Suggestions

Merge the two "Constraints" sections and remove the duplicated metrics list (currently stated in section 3 and again right after) to tighten the body.

Drop or condense the "Integration with Other Skills" section — it asserts integration without explaining how to use it, adding tokens without guidance.

Add an explicit validation/checkpoint step to Workflow 3 (Scale Prompt Systems) so all three workflows share the same feedback-loop discipline.

DimensionReasoningScore

Conciseness

Mostly efficient but includes repetition that could be tightened: optimization metrics are listed twice (section 3 and the trailing line), there are two separately titled "Constraints" sections, and the "Integration with Other Skills" section is largely filler.

3 / 5

Actionability

Provides concrete, copy-paste-ready prompt templates (few-shot example, CoT structure, template system, system-prompt framework) and a pitfalls table with fixes; the workflows themselves are higher-level guidance rather than exact commands, leaving minor gaps.

4 / 5

Workflow Clarity

Three numbered workflows with clear sequences and a feedback loop in Workflow 2 ("If accuracy < baseline, revert... return to step 2") plus a Quality Gates checklist; Workflow 3 is more abstract and lacks validation checkpoints, so it stops short of a 5.

4 / 5

Progressive Disclosure

Keeps the overview in SKILL.md and points to five one-level-deep reference files that all exist; each section clearly signals which reference to load, and a Resources and References section consolidates navigation.

5 / 5

Total

16

/

20

Passed

Description

100%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.

A strong description: third-person voice, concrete actions, explicit "Use when..." triggers, and natural keywords. It clearly distinguishes the skill and answers both what and when.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "write, debug, and optimize prompts" plus four named sub-areas (few-shot example selection, chain-of-thought structuring, system prompt design, template composition) — giving comprehensive coverage of the domain.

5 / 5

Completeness

Explicitly answers both what ("Provides workflows to write, debug, and optimize prompts...") and when ("Use when the user asks to write or improve a prompt...") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural phrases users actually say — "write or improve a prompt", "few-shot examples", "chain-of-thought", "system prompts", "prompt templates", "better results from an LLM" — with synonyms across the prompt-engineering vocabulary.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (LLM prompt engineering) with distinct, specific triggers (few-shot, CoT, system prompts, templates) that minimize overlap with other skills.

5 / 5

Total

20

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

15

/

16

Passed

Repository

giuseppe-trisciuoglio/developer-kit

Path

plugins/developer-kit-ai/skills/prompt-engineering/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.