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.

77

Quality

96%

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

92%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 a well-structured, instruction-only skill with clear sequencing, explicit validation/read-back checkpoints, and concrete templates and verdict rules. It assumes Claude's competence and avoids padding, with only minor tightening possible in the precondition rationale.

Suggestions

Section 4 restates the enabling-work-vs-prerequisite distinction several times; consolidate the decision rule into one canonical statement to trim tokens.

The security and untrusted-content guidance could be condensed into a single short callout rather than woven through section 1 and section 2.

DimensionReasoningScore

Conciseness

The body is dense with domain-specific guidance and avoids teaching concepts Claude already knows, but the extended precondition/ownership discussion (sections 4 and 5) could be tightened in places where it restates the same enabling-work distinction.

4 / 5

Actionability

Provides concrete, executable artifacts: a copy-paste issue body template, a verdict taxonomy (READY/NEEDS_CONTRACT_WORK/BLOCKED/NO_ACTION) with explicit decision rules, and an exact reporting format with field-by-field guidance.

5 / 5

Workflow Clarity

A clearly sequenced six-step process (Choose mode → Read context → Establish contract → Check preconditions → Judge readiness → Create/propose/update) with explicit validation checkpoints (read-back, stop-if-changed, reconciliation-comment reuse) and feedback loops for destructive-ish GitHub mutations.

5 / 5

Progressive Disclosure

A single self-contained SKILL.md with no nested reference chains and no bundle files to navigate; content is organized into well-signaled numbered sections, which for a file of this size is appropriate one-level structure.

5 / 5

Total

19

/

20

Passed

Description

100%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 is exemplary: it states concrete capabilities and supplies numerous natural-language trigger phrases covering create, audit, and update intents. It clearly answers both 'what' and 'when' with minimal conflict risk.

DimensionReasoningScore

Specificity

Lists several concrete actions — 'Creates GitHub issues', 'runs the precondition check' — across distinct input sources (conversations, findings, ideas), with comprehensive coverage of the skill's behavior.

5 / 5

Completeness

Explicitly answers what it does ('Creates GitHub issues... and runs the precondition check') and when to use it via a concrete 'Use when...' clause listing real trigger phrases.

5 / 5

Trigger Term Quality

Provides a wide set of natural verbatim phrases users would actually say ('create an issue from this', 'turn this into an issue', 'check whether issue #42 is agent-ready', 'audit this issue contract') plus an explicit invocation token.

5 / 5

Distinctiveness Conflict Risk

Targets a clear niche (issue contract readiness for agent automation) with distinct trigger phrasing unlikely to overlap with general issue or planning skills.

5 / 5

Total

20

/

20

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