CtrlK
BlogDocsLog inGet started
Tessl Logo

prompt-engineer

Skill para desenhar prompts reutilizaveis de texto, imagem e video com foco em clareza, controle, custo e reprodutibilidade. Use quando a qualidade do prompt for parte central da feature ou do fluxo. Trigger em: "prompt engineer", "prompt engineering", "melhorar prompt", "otimizar prompt", "template de prompt", "system prompt", "few-shot", "chain of thought", "reduzir custo de prompt", "iterar prompt", "prompt reutilizavel".

64

Quality

76%

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 ./skills/26-prompt-engineer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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 a solid conceptual framework for incremental prompt construction with the 3-layer approach and clear validation checkpoints. However, it lacks concrete examples of actual prompts at each layer, which significantly reduces actionability. The content is moderately concise but carries some boilerplate overhead from governance references and generic input/output sections.

Suggestions

Add a concrete example showing a real prompt evolving through Camada A → B → C (e.g., a product description generator), with actual prompt text at each stage.

Remove or consolidate boilerplate sections like 'Quando Nao Usar' and 'Entradas Esperadas' which describe obvious information Claude can infer from context.

Include at least one copy-paste-ready prompt template inline (not just a reference to templates/agent-spec.md) to make the skill immediately actionable.

DimensionReasoningScore

Conciseness

The skill is moderately efficient but includes some sections that add little value (e.g., 'Quando Nao Usar' with vague items, 'Entradas Esperadas' listing obvious inputs). The governance references and boilerplate sections consume tokens without adding actionable content. The Layering section is well-structured but could be tighter.

2 / 3

Actionability

The Layering section provides a useful incremental framework with clear steps, but lacks concrete examples of actual prompts at each layer. There are no executable code snippets, no sample prompt templates, and no input→output examples showing what a good prompt looks like at each camada. The guidance remains at a process-description level rather than copy-paste ready.

2 / 3

Workflow Clarity

The 3-layer progressive construction workflow is clearly sequenced with explicit validation checkpoints ('Testar aqui antes de avançar') at each layer. The feedback loop is implicit but present — test before advancing, and there's a clear evidence-of-completion criterion. For a non-destructive prompt engineering task, this level of workflow clarity is appropriate.

3 / 3

Progressive Disclosure

The skill references multiple external files (patterns/ai-integration/prompt-patterns.md, templates/agent-spec.md, templates/prompt-spec.md, multiple policies) which suggests good intent for progressive disclosure, but no bundle files are provided to verify these exist. The references are one-level deep and clearly signaled, but the main content could benefit from better separation — the Layering section is appropriately inline, but governance references are numerous without clear navigation structure.

2 / 3

Total

9

/

12

Passed

Description

89%

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 is a well-structured skill description that excels in trigger term coverage and completeness, with explicit 'Use quando' and 'Trigger em' clauses. The main weakness is that the capability description could be more specific about concrete actions beyond 'desenhar prompts'. The description uses appropriate third-person voice and avoids vague language.

Suggestions

Expand the capability description with more concrete actions, e.g., 'Cria templates de prompt, otimiza uso de tokens, estrutura few-shot examples, implementa chain-of-thought, avalia e itera prompts para reduzir custo'.

DimensionReasoningScore

Specificity

Names the domain (prompt engineering) and some actions ('desenhar prompts reutilizaveis de texto, imagem e video') with quality attributes ('clareza, controle, custo e reprodutibilidade'), but doesn't list multiple concrete discrete actions like 'create templates, optimize token usage, add few-shot examples, structure chain-of-thought reasoning'.

2 / 3

Completeness

Clearly answers both 'what' (designing reusable text, image, and video prompts with focus on clarity, control, cost, and reproducibility) and 'when' (explicit 'Use quando' clause plus a detailed 'Trigger em' list with specific keywords).

3 / 3

Trigger Term Quality

Excellent coverage of natural trigger terms including both Portuguese and English variations: 'prompt engineer', 'prompt engineering', 'melhorar prompt', 'otimizar prompt', 'template de prompt', 'system prompt', 'few-shot', 'chain of thought', 'reduzir custo de prompt', 'iterar prompt', 'prompt reutilizavel'. These are terms users would naturally use.

3 / 3

Distinctiveness Conflict Risk

The skill occupies a clear niche around prompt engineering and design, with highly specific trigger terms like 'prompt engineer', 'few-shot', 'chain of thought', 'system prompt' that are unlikely to conflict with other skills. The domain is well-defined and distinct.

3 / 3

Total

11

/

12

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
felvieira/claude-skills-fv
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.