CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

60

Quality

71%

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 ./skills/create-pr/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a minimal alias skill that correctly redirects to the canonical pr-writer skill. Its strength is extreme conciseness and clear intent. Its weakness is that it provides no actionable content itself—if the referenced skill cannot be loaded, Claude has no fallback guidance on how to create a PR.

Suggestions

Add a brief 2-3 line summary of the core PR workflow steps as a fallback in case the canonical skill cannot be resolved.

Specify the exact mechanism for invoking the canonical skill (e.g., whether it's a file path, a skill registry lookup, or another resolution method).

DimensionReasoningScore

Conciseness

Extremely lean—only states the alias relationship and redirect. No unnecessary explanation of what PRs are or how they work. Every token serves a purpose.

5 / 5

Actionability

It tells Claude to run the same workflow as sentry-skills:pr-writer, but provides no concrete steps, commands, or code itself. The actionability depends entirely on the referenced skill, and there's no inline fallback or summary of what to do.

3 / 5

Workflow Clarity

For a simple alias/redirect skill, the single action (redirect to canonical skill) is unambiguous. However, it doesn't specify exactly how to invoke or load the canonical skill, which is a minor gap.

4 / 5

Progressive Disclosure

Appropriately delegates to the canonical skill rather than duplicating content. The reference is clear and one level deep. Minor gap: no bundle files or linked file to verify the reference resolves correctly.

4 / 5

Total

16

/

20

Passed

Description

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

This description is functional as an alias/redirect skill, clearly stating when it should be triggered and what it does. However, it lacks specificity about the actual capabilities of the underlying PR writing workflow, and could benefit from additional natural trigger terms users might say when wanting to create a pull request.

Suggestions

Add natural trigger terms users might say, such as 'pull request', 'write a PR', or 'open PR' to improve discoverability beyond just the exact alias name.

Include a brief mention of what the canonical PR writing workflow actually does (e.g., 'generates PR titles, descriptions, and summaries from code changes') so Claude can better match user intent.

DimensionReasoningScore

Specificity

Names the domain (PR writing) but describes no concrete actions beyond 'redirects to the canonical PR writing workflow.' The actual capabilities are not listed here.

2 / 5

Completeness

Has a clear 'what' (alias/redirect to pr-writer) and an explicit 'when' ('when users explicitly ask for create-pr or reference the legacy skill name'). The 'when' is concrete but narrow.

4 / 5

Trigger Term Quality

Includes specific trigger terms like 'create-pr' and 'legacy skill name,' and mentions 'PR writing workflow.' However, it could include more natural user phrases like 'pull request,' 'write a PR,' or 'open a PR.'

4 / 5

Distinctiveness Conflict Risk

Very clearly scoped as an alias for a specific skill with explicit trigger conditions. Minimal risk of conflicting with other skills since it targets a very specific legacy name reference.

5 / 5

Total

15

/

20

Passed

Validation

90%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.