CtrlK
BlogDocsLog inGet started
Tessl Logo

prp-issue-contract

Creates GitHub issues from conversations, findings, or ideas and runs the precondition check before a planning-capable agent starts work. Use when the user asks to "create an issue from this", "turn this into an issue", "check whether issue #42 is agent-ready", "check this issue before automation", "audit this issue contract", "update this issue to make it agent-ready", or invokes /prp-issue-contract.

73

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

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

A tightly written, highly actionable instruction-only skill with clear sequencing and validation checkpoints. The only real weakness is length in a single monolithic file with no progressive disclosure into references.

Suggestions

Consider moving the longer policy guidance (e.g., section 4 precondition heuristics) into a references/ file and keeping SKILL.md as an overview with a one-level-deep pointer, to improve progressive_disclosure.

Tighten a few elaborate policy sentences in sections 4 and 5 to lift conciseness toward a 5.

Add a brief one-line overview/TL;DR at the top mapping the six steps, so the structure is navigable at a glance.

DimensionReasoningScore

Conciseness

Dense, operational guidance that assumes Claude's competence and avoids explaining known concepts (no 'what is a GitHub issue' filler); a few policy sentences are elaborate and could be tightened, keeping it just below a 5.

4 / 5

Actionability

Provides concrete, executable guidance: the four contract elements (Problem/Why/Outcome/Acceptance), a copy-paste issue-body template, four precisely defined verdicts, and a compact reporting-format template — copy-paste ready and covering the common cases.

5 / 5

Workflow Clarity

Six clearly sequenced numbered steps with explicit validation checkpoints ('read it back before reporting success', 'stop if intervening changes alter the proposal', 'Stop before designing the solution') and a verdict decision tree, satisfying feedback-loop expectations for the issue-update/close operations.

5 / 5

Progressive Disclosure

Well-organized into clearly headed numbered sections with no nested references and easy navigation, but it is a longer single-file doc with no overview pointer to separated detail; the under-50-lines simple-skill exception does not strictly apply, so it sits at 4 rather than 5.

4 / 5

Total

18

/

20

Passed

Description

95%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, third-person description that clearly states capability and provides rich, natural trigger phrases. Minor specificity gap is the only thing keeping it from a perfect profile.

DimensionReasoningScore

Specificity

Names the domain (GitHub issues) and several concrete actions — 'Creates GitHub issues from conversations, findings, or ideas and runs the precondition check' — with audit/update/check modes implied via triggers; minor coverage gaps versus a comprehensive 5.

4 / 5

Completeness

Explicitly answers both 'what' (creates issues, runs precondition check) and 'when' with concrete trigger phrases, matching the score-5 anchor.

5 / 5

Trigger Term Quality

Includes comprehensive natural phrases a user would actually say — 'create an issue from this', 'turn this into an issue', 'check whether issue #42 is agent-ready', 'audit this issue contract', 'update this issue to make it agent-ready' — plus the /prp-issue-contract invocation.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (agentic issue-contract readiness) with distinctive triggers like 'agent-ready', 'issue contract', and the /prp-issue-contract slash command, minimizing overlap with other skills.

5 / 5

Total

19

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
Wirasm/prp
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.