CtrlK
BlogDocsLog inGet started
Tessl Logo

assess-patch-risk

Assess an immutable patch artifact's program impact, regression risk, and auto-merge eligibility. Use for generated patch files, provider pull-request diffs, or commit ranges when reviewers need evidence about affected runtime paths, contracts, tests, and recoverability. This skill is read-only and does not generate, edit, apply, push, or merge the patch.

72

Quality

90%

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.

A well-structured, lean analysis skill with a sequenced workflow, explicit validation and feedback loops, and clean progressive disclosure into verified bundle files. The only minor gap is limited copy-paste code beyond the validation command.

DimensionReasoningScore

Conciseness

The body is dense and information-rich with no padding or explanations of concepts Claude already knows (no 'what is a patch/PR/diff'); every step and rule earns its tokens.

5 / 5

Actionability

Provides a concrete executable validation command (with stdin variant), a referenced JSON schema, and concrete recommendation/workflow labels; stops short of copy-paste code covering common cases beyond validation, fitting the 'mostly executable; minor gaps' anchor.

4 / 5

Workflow Clarity

A clearly sequenced 10-step workflow with an explicit validation checkpoint (validate JSON before returning), a feedback loop for error recovery, a bounded hold_for_evidence plan, and a Hard Rules checklist.

5 / 5

Progressive Disclosure

The body is a clear overview with well-signaled one-level-deep references (references/risk-rubric.md and the validation script, both verified to exist), with detailed content appropriately split into those bundle files.

5 / 5

Total

19

/

20

Passed

Description

87%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 concretely states what the skill does and gives explicit, multi-scenario trigger guidance with a useful read-only boundary. Minor keyword synonym coverage is the only gap.

DimensionReasoningScore

Specificity

Names the patch-risk domain and lists several specific assessment actions (program impact, regression risk, auto-merge eligibility), matching the 'several specific actions; minor gaps' anchor rather than a comprehensive enumerated list.

4 / 5

Completeness

Explicitly answers both what ('Assess an immutable patch artifact's program impact, regression risk, and auto-merge eligibility') and when ('Use for generated patch files, provider pull-request diffs, or commit ranges when reviewers need evidence...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural trigger phrases users would say ('generated patch files', 'provider pull-request diffs', 'commit ranges') with good coverage, though it omits some synonyms/extensions like 'diff' or 'PR review'.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (immutable patch artifact risk assessment) with distinct triggers and a sharpening read-only boundary statement, giving minimal conflict risk with other skills.

5 / 5

Total

18

/

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

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

Repository
openai/plugins
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.