CtrlK
BlogDocsLog inGet started
Tessl Logo

create-pr

Use when creating a PR for a non-trivial bug fix in this repo. Assembles a structured PR description following .github/PULL_REQUEST_TEMPLATE.md with expanded sections for root cause, risks, and test plan. Do NOT use for trivial one-liner fixes.

76

Quality

93%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

An exemplary short instruction skill: lean, concrete, and well-sequenced with an explicit approval checkpoint before the irreversible PR-creation step. No bundle files exist, so progressive disclosure is evaluated on the body structure alone.

DimensionReasoningScore

Conciseness

Lean and directive throughout with no over-explanation of concepts Claude already knows; every line including the closing 'Why:' earns its place.

5 / 5

Actionability

Provides exact ordered `##` headers, concrete commands (`git log --follow`, `git blame`, `make testacc TESTARGS='-run=...'`, `gh pr create`), and a precise `| File | Change |` table format — fully executable guidance for an instruction skill.

5 / 5

Workflow Clarity

Clear sequence from skeleton assembly through filling the template to an explicit approval gate before the visible-to-others `gh pr create`, with a feedback rationale for the checkpoint.

5 / 5

Progressive Disclosure

Under 50 lines, single-purpose, no external references needed, and well-organized with bolded directive sections — meeting the rubric's simple-skill exception for a top score.

5 / 5

Total

20

/

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, tightly scoped description that answers what and when with concrete specifics and an explicit negative boundary. Minor keyword synonym coverage keeps trigger_term_quality and specificity just short of full marks.

DimensionReasoningScore

Specificity

Names a concrete template file and specific expanded sections (root cause, risks, test plan), but does not enumerate the full set of assembly mechanics, leaving minor coverage gaps short of a 5.

4 / 5

Completeness

Explicitly states both what it does ('Assembles a structured PR description following .github/PULL_REQUEST_TEMPLATE.md with expanded sections...') and when to use it ('Use when creating a PR for a non-trivial bug fix'), with concrete trigger phrases and a negative boundary.

5 / 5

Trigger Term Quality

Natural phrasing like 'creating a PR' and 'non-trivial bug fix' map to what users say, but synonyms such as 'pull request' or 'merge request' are absent.

4 / 5

Distinctiveness Conflict Risk

Scoped to 'non-trivial bug fix in this repo' with an explicit 'Do NOT use for trivial one-liner fixes' boundary, giving it a clear niche with minimal conflict risk.

5 / 5

Total

18

/

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
coralogix/terraform-provider-coralogix
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.