CtrlK
BlogDocsLog inGet started
Tessl Logo

prompt-architect

Create and enhance prompts, system instructions, and principle files. Capabilities: transform verbose prompts, add patterns/heuristics, optimize token usage, structure CLAUDE.md principles, improve agent/persona definitions, apply prompt engineering techniques (CoT, few-shot, ReAct). Actions: create, enhance, optimize, refactor, compress prompts. Keywords: prompt engineering, system prompt, CLAUDE.md, principle files, instruction optimization, agent prompt, persona prompt, token efficiency, prompt structure, workflow prompts, rules, constraints, few-shot, chain-of-thought, soul, tensions, dialectic. Use when: creating new prompts, enhancing principle files, improving system instructions, optimizing CLAUDE.md, restructuring verbose prompts, adding patterns to workflows, defining agent behaviors.

91

1.28x
Quality

Does it follow best practices?

Impact

95%

1.28x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

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.

The content is a well-organized, highly actionable prompt-engineering skill with concrete templates, transformations, a clear sequenced workflow, and explicit validation tests. Its main weaknesses are length/redundancy across the repeated soul and transformation sections and the absence of any file-based progressive disclosure for its substantial reference material.

Suggestions

Deduplicate the soul structure: it appears as an inline example, again as a <building_blocks> template, and again in the worked <example> — keep one canonical template and reference it to cut ~40-60 lines.

Split the large <building_blocks> templates and <key_transformations> reference material into a separate references/ file (e.g. BUILDING_BLOCKS.md) and point to it one level deep, improving progressive disclosure.

Tighten the overlap between <expertise_transfer> and <key_transformations>, which restates the same compression/taxonomy guidance; consolidate into a single section.

DimensionReasoningScore

Conciseness

The body is high-signal with no basic-concept filler, but it is long (~400 lines) with redundancy — the inline <soul> example, the <building_blocks> soul template, and the worked example each restate overlapping structure, and key_transformations repeats expertise_transfer concepts.

2 / 3

Actionability

Provides concrete, copy-paste-ready templates (soul, mental models, anti-patterns formats) plus concrete before/after transformations and a fully worked example, giving actionable guidance rather than vague direction.

3 / 3

Workflow Clarity

A clear sequenced workflow is present via detect_mode, diagnosis, technique_selection tables, and a numbered summary (Mode → Type → Complexity → Preserve → Compress → Taxonomy → Generate) with a validation section of explicit tests; no destructive/batch operations apply the cap.

3 / 3

Progressive Disclosure

No bundle files exist and the skill is a single ~400-line monolithic file with all content inline; the large building_blocks/templates/reference material could be split into separate one-level-deep reference files, so it falls short of the score-3 single-file exception (which targets skills under 50 lines).

2 / 3

Total

10

/

12

Passed

Description

100%

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 is well-crafted: it states concrete capabilities, includes an explicit 'Use when' trigger clause, and covers a broad set of natural keywords in third-person voice. It satisfies every dimension at the top anchor with only minor dilution from a few jargon terms.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'create, enhance, optimize, refactor, compress prompts' plus 'transform verbose prompts, add patterns/heuristics, optimize token usage, structure CLAUDE.md principles' — matching the score-3 anchor for multiple specific concrete actions.

3 / 3

Completeness

Explicitly answers 'what' via Capabilities/Actions and 'when' via an explicit 'Use when:' clause enumerating triggering situations, satisfying the score-3 anchor for both what and when.

3 / 3

Trigger Term Quality

A 'Keywords' list gives broad natural coverage — 'prompt engineering, system prompt, CLAUDE.md, few-shot, chain-of-thought' — that a user would plausibly say; a few esoteric terms (soul, tensions, dialectic) slightly dilute but overall coverage is strong.

3 / 3

Distinctiveness Conflict Risk

The niche (prompt architecture, CLAUDE.md principle files, dialectic/tensions) is clearly distinct from unrelated skills and unlikely to trigger for the wrong skill.

3 / 3

Total

12

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
majiayu000/claude-skill-registry-data
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.