CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

create-pr

Alias for sentry-skills:pr-writer. Use when users explicitly ask for "create-pr" or reference the legacy skill name. Redirects to the canonical PR writing workflow.

Quality

77%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/create-pr/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 short, well-organized alias document whose single redirect action is clear and appropriately free of nested references. It is weakened by triple restatement of the same redirect and generic disclaimer boilerplate, plus the absence of any concrete invocation mechanism for the canonical skill.

Suggestions

Collapse the three restatements of the redirect into a single instruction (e.g., 'This skill is an alias; invoke `sentry-skills:pr-writer` and follow its documented workflow').

Remove the generic 'Limitations' boilerplate about validation, testing, and expert review, which is not specific to this skill and adds token cost without guidance.

State how to reach the canonical skill (exact skill name/path or invocation command) so the redirect is mechanically executable.

DimensionReasoningScore

Conciseness

The redirect is stated three times (the 'When to Use' bullets, the standalone 'Use `sentry-skills:pr-writer` as the canonical skill' sentence, and 'If invoked via `create-pr`, run the same workflow...'), and the generic 'Limitations' boilerplate ('Do not treat the output as a substitute for environment-specific validation, testing, or expert review') adds no skill-specific value — the body could be tightened to a couple of sentences.

3 / 5

Actionability

Gives a concrete, executable instruction by naming the exact canonical skill (`sentry-skills:pr-writer`) and directing the reader to run its documented workflow; the minor gap keeping it from 5 is that no invocation mechanism (path or command) for the canonical skill is provided.

4 / 5

Workflow Clarity

As a single-action redirect skill the action is clearly and consistently stated, but there is residual ambiguity between invoking the other skill versus merely following its conventions, and no mechanism is specified — so it sits at 'clear sequence, minor gaps' rather than the unambiguous anchor-5 case.

4 / 5

Progressive Disclosure

At ~25 lines with no need for external reference files (none exist in the bundle) and well-organized 'When to Use' and 'Limitations' sections, this meets the simple-skill standard: well-organized sections with the single cross-skill pointer clearly signaled.

5 / 5

Total

16

/

20

Passed

Description

73%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 well-scoped alias description that cleanly answers both what (redirect to the canonical PR-writing skill) and when (explicit 'create-pr' or legacy-name mentions), with low conflict risk. Its main weakness is thin specificity: it never states what the canonical pr-writer workflow actually does.

Suggestions

Add one clause stating what the canonical skill does (e.g., 'creates and edits pull requests from staged changes') so the 'what' is concrete rather than purely referential.

Include the spelled-out phrase 'pull request' alongside 'PR' to capture the most common natural trigger variation users would say.

DimensionReasoningScore

Specificity

Names the domain (PR creation) and a single concrete action ('Redirects to the canonical PR writing workflow'), matching the '1-2 concrete actions but not comprehensive' anchor; it does not enumerate what the canonical workflow actually does, so it is not a 4.

3 / 5

Completeness

Both halves are explicit: what ('Alias for sentry-skills:pr-writer... Redirects to the canonical PR writing workflow') and when ('Use when users explicitly ask for "create-pr" or reference the legacy skill name'); it falls short of 5 because the 'what' never states what the canonical skill actually does (creating/editing PRs).

4 / 5

Trigger Term Quality

Includes the literal skill name 'create-pr' plus 'PR writing' as natural triggers, but omits the spelled-out 'pull request' and common variations like 'open a PR', fitting 'good keyword coverage; a few natural terms missing' rather than comprehensive anchor-5 coverage.

4 / 5

Distinctiveness Conflict Risk

The trigger is deliberately narrow — only explicit 'create-pr' or legacy-name mentions — giving a clear niche with distinct triggers and minimal risk of firing for unrelated skills, matching the anchor-5 example's profile.

5 / 5

Total

16

/

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.

Validation — 15 / 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

BigSimmo/Communication

Path

.agents/skills/create-pr/SKILL.md

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.