CtrlK
BlogDocsLog inGet started
Tessl Logo

open-pr

Open a pull request on the Kiln repo with a semantic-commit title and a structured description (one-line TLDR, summary, implementation bullets, warnings, optional Mermaid diagram, collapsible examples and screenshots). Also covers the short watch window for review-bot comments and CI. Use when the user asks to open, create, or raise a PR, to write or rewrite a PR description, or to update a PR after a push.

73

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

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 well-structured, highly actionable instruction skill with a clear sequenced workflow, explicit validation and feedback loops, and concrete commands and examples. Its main weakness is a few verbose or large inline sections that could be tightened or moved to reference files.

Suggestions

Move the full worked PR description example and the ASD-STE100 rules list into separate reference files and link to them from the body, to keep the main SKILL.md lean and improve progressive disclosure.

Trim motivational prose such as 'The goal is a description that a new team member reads one time and understands' to keep the content token-efficient.

Consider condensing Step 6's exhaustive list of meaningful-vs-small change examples into a short rule plus one example on each side.

DimensionReasoningScore

Conciseness

Mostly efficient and assumes Claude's competence, but contains a few blocks that could be trimmed (the prose goal statements, the full STE rules list, and the long worked example), giving minor over-explanation.

4 / 5

Actionability

Fully executable guidance: exact commands, MCP tool names, a semantic-commit type table, a pre-open checklist, and a complete copy-paste-ready example description covering the common cases.

5 / 5

Workflow Clarity

A clearly sequenced Step 1-8 workflow with explicit validation checkpoints (checks.sh before push, pre-open checklist, reproduce->fix->re-run->push CI feedback loop) and checklists for the complex process.

5 / 5

Progressive Disclosure

Well-organized into clearly signaled Rules and Steps with a self-contained structure and no nested references, but several large inline blocks (the STE rules and the full worked example) could be split into separate reference files.

4 / 5

Total

18

/

20

Passed

Description

92%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, specific description that explicitly pairs concrete capabilities with natural 'Use when...' triggers and stays in third-person voice. Trigger term coverage is the only slightly weaker area, missing a few synonyms.

DimensionReasoningScore

Specificity

Lists multiple concrete actions (semantic-commit title, one-line TLDR, summary, implementation bullets, warnings, Mermaid diagram, collapsible examples and screenshots) plus the watch window, giving comprehensive coverage of what the skill does.

5 / 5

Completeness

Clearly answers both 'what' (open a PR with a structured title and description, plus watch for review-bot comments and CI) and 'when' with an explicit 'Use when...' clause and concrete trigger phrases.

5 / 5

Trigger Term Quality

Strong natural phrases users would say ('open, create, or raise a PR', 'write or rewrite a PR description', 'update a PR after a push'), but lacks some synonyms or extensions beyond the core PR verbs.

4 / 5

Distinctiveness Conflict Risk

A clear niche (opening PRs on the Kiln repo) with distinct, PR-specific triggers and minimal overlap risk with other skills.

5 / 5

Total

19

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Kiln-AI/Kiln
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.