Name: prompt-engineer
Rating: 45.6 (1 reviews)
Author: administrakt0r

prompt-engineer

Transforms user prompts into optimized prompts using frameworks (RTF, RISEN, Chain of Thought, RODES, Chain of Density, RACE, RISE, STAR, SOAP, CLEAR, GROW)

Quality

48%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/prompt-engineer/SKILL.md

The canonical home for this skill is prompt-engineer in administrakt0r/AI-Agents-Safe-Coding-Skills

Quality

Content

42%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 content is rich and conceptually actionable, but it is undermined by structural defects (a missing Step 2, broken/escaped code fences, orphaned 4.5/4.6 subsections, and misnumbered examples) and by verbose restatement of the workflow in the Critical Rules section. Cleaning up the numbering and trimming redundancy would materially improve the score.

Suggestions

Fix the workflow numbering: add the missing 'Step 2: Clarify' section and renumber so the orphaned 4.5 Language Adaptation and 4.6 Quality Checks fall under a real Step 4.

Repair the broken/escaped code fences and the nested ```` markdown wrapping so the example generated prompts render cleanly, and renumber examples (1/2/3) contiguously.

Trim the verbose 'Critical Rules' ALWAYS/NEVER lists that restate the workflow, and drop the framework table's rationale column to reduce padding.

Dimension	Reasoning	Score
Conciseness	The body is noticeably verbose: the ALWAYS/NEVER 'Critical Rules' sections restate the workflow, the framework table carries a rationale column, and the worked examples are padded, yielding several unnecessary sections.	2 / 5
Actionability	The framework-mapping table, blending strategy, and example generated prompts are concrete and actionable, but the missing Step 2 and structurally broken code fences leave key gaps.	3 / 5
Workflow Clarity	A sequence is present (Analyze, Select, Quality Checks) but Step 2 (Clarify) is referenced in the rules and examples yet absent from the Workflow section, and the 4.5/4.6 checkpoints are orphaned under a non-existent Step 4.	3 / 5
Progressive Disclosure	The skill is self-contained with section headers (appropriate given no bundle files), but organization is messy — broken step numbering, missing Step 2, and examples labeled only 2 and 4 — so it could be better organized.	3 / 5
	Total	11 / 20 Passed

Description

53%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 conveys a clear purpose and a distinctive framework-based niche, but it reads as a single action plus a jargon-heavy acronym list and omits any explicit trigger guidance. Adding a 'Use when...' clause with natural user phrasings would lift the weaker dimensions.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user provides a vague prompt, asks to improve or optimize a prompt, or wants help writing a prompt for a task.'

Reword the framework acronym dump into natural language so it reads as triggers users would actually say rather than technical jargon.

List a couple of distinct concrete actions (e.g. 'analyzes intent, selects a framework, and returns a ready-to-use prompt') instead of repeating 'transforms/optimized' as one action.

Dimension	Reasoning	Score
Specificity	The phrase 'Transforms user prompts into optimized prompts' names the domain and one concrete action, while the rest is an enumerated list of framework acronyms rather than several distinct concrete actions.	3 / 5
Completeness	It gives a clear 'what' (transforms prompts via named frameworks) but includes no 'when'/'Use when' trigger clause, capping completeness at 3 per the missing-trigger guidance.	3 / 5
Trigger Term Quality	It contains some relevant natural terms ('prompts', 'optimized prompts', 'frameworks') but misses common user phrasings like 'improve my prompt' or 'write a better prompt', and the acronym list leans technical.	3 / 5
Distinctiveness Conflict Risk	The prompt-optimization niche and enumerated framework set make it mostly distinct with only minor overlap risk against general writing helpers.	4 / 5
	Total	13 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/prompt-engineer/SKILL.md
Commit: 57c135b

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.