CtrlK
BlogDocsLog inGet started
Tessl Logo

agent-prompt-quality-bar

Universal quality bar and final audit rubric for any agent system prompt. Activate this whenever you are unsure which archetype skill applies, or as a final review pass before writing the system prompt. It defines the required run contract, completion criteria, fallback paths, response format, and anti-patterns every produced agent prompt must satisfy.

62

Quality

72%

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

Fix and improve this skill with Tessl

tessl review fix ./packages/editor/src/ee/workspace/skills/agent-prompt-quality-bar/SKILL.md
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 body is highly actionable with a clear sequenced workflow and an explicit audit-checklist feedback loop, but it is somewhat long for a single-file meta-skill and offers no progressive disclosure beyond well-organized inline sections.

Suggestions

Dedupe the completion-criteria, response-format, capability, and refusal guidance that appears in both the required-sections list and the final audit rubric to tighten conciseness.

Consider moving the worked example or the full audit rubric into a one-level-deep reference file so the SKILL.md overview stays lean and gives progressive disclosure a clear win.

DimensionReasoningScore

Conciseness

The ~130-line body is mostly efficient with no concept-explaining fluff, but the nine bad/good example pairs plus the final audit rubric repeat criteria already covered in the required-sections list, so it could be tightened.

2 / 3

Actionability

Concrete and copy-paste-ready throughout: a six-item run contract, nine required sections each with explicit bad/good templates, an audit checklist, and anti-patterns with fixes — all specific actionable guidance for an instruction-only skill.

3 / 3

Workflow Clarity

The 'How to use this skill' section gives a clear four-step sequence (draft contract, write sections, apply audit rubric, reject anti-patterns), and the mandatory audit rubric is an explicit checklist with a feedback loop ('If any item fails, revise the system prompt before writing it').

3 / 3

Progressive Disclosure

It is a single self-contained file with well-organized section headers and no nested references, but at ~130 lines with all content inline and no bundle files or one-level-deep references, there is no progressive-disclosure structure to push it to 3.

2 / 3

Total

10

/

12

Passed

Description

67%

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 answers both what and when with an explicit trigger and lists concrete capabilities, but its second-person voice incurs a specificity penalty and its internal jargon plus universal framing weaken trigger-term quality and distinctiveness.

Suggestions

Rewrite in third person (e.g. 'Activates whenever no archetype skill fits, or as a final audit pass before writing an agent system prompt.') to remove the second-person voice penalty.

Replace internal jargon like 'archetype skill' and 'produced agent prompt' with plain user-facing terms so trigger keywords match what a user would naturally say.

Narrow the universal framing or sharpen the trigger so the skill is less likely to overlap with the domain archetype skills it references.

DimensionReasoningScore

Specificity

It lists multiple concrete actions ('defines the required run contract, completion criteria, fallback paths, response format, and anti-patterns'), which would anchor at 3, but the second-person voice ('you are unsure', 'before writing the system prompt') triggers the rubric's -1 specificity penalty.

2 / 3

Completeness

It clearly answers what ('defines the required run contract, completion criteria, fallback paths, response format, and anti-patterns') and when via the explicit 'Activate this whenever...' trigger, satisfying the anchor for both what and when.

3 / 3

Trigger Term Quality

The trigger clause 'Activate this whenever you are unsure which archetype skill applies, or as a final review pass before writing the system prompt' gives two relevant scenarios, but leans on internal jargon ('archetype skill', 'produced agent prompt') rather than the plainest user phrasings, so it is not a full 3.

2 / 3

Distinctiveness Conflict Risk

The 'Universal quality bar ... for any agent system prompt' framing is broad and intentionally overlaps with the archetype skills it cross-references, though the fallback trigger ('when you are unsure which archetype skill applies') carves a somewhat distinct niche.

2 / 3

Total

9

/

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
mastra-ai/mastra
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.