CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pr-style

PR formatting reference — title, body template, label mapping, assignment, and draft policy. Invoked by pr/create and pr/update-desc commands to ensure consistent PR formatting.

Quality

73%

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/harness/adapters/antigravity/skills/pr-style/SKILL.md

The canonical home for this skill is pr-style in phatblat/dotfiles

SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is a deliberately minimal redirect stub: perfectly token-efficient and unambiguous about what to load, but it provides no substantive PR-formatting guidance itself and depends entirely on an external file that is not part of the skill bundle. As a result it is maximally concise yet weak on actionability.

Suggestions

Inline a brief summary of the core rules (title format, label mapping table, draft policy) so the skill remains actionable if the shared path is unavailable, with the shared file kept for full detail.

Reference a file within the skill bundle (e.g. references/pr-style.md) instead of a machine-specific home-directory path, so the skill is portable and the referenced content ships with it.

DimensionReasoningScore

Conciseness

The body is two functional lines — a generation provenance comment and a single load-and-follow instruction — with zero padding or explanation of things Claude already knows, matching the lean-and-efficient anchor exactly.

5 / 5

Actionability

"Load and follow the shared skill at `~/.agents/skills/pr-style/SKILL.md`" is a concrete pointer, but the body contains none of the actual guidance it claims to cover (title format, body template, label mapping, assignment, draft policy) — minimal concrete guidance with the specific steps entirely delegated, which is below the mostly-executable anchor at 4.

2 / 5

Workflow Clarity

The single action is unambiguous (load the named file and follow it), which per the simple-skill guidance supports a high score, but there is no fallback or guidance for when the shared path is unavailable and the real multi-step formatting workflow lives entirely outside this file, keeping it below 5.

4 / 5

Progressive Disclosure

The reference is one level deep and clearly signaled with an exact path, but SKILL.md contains no overview content of its own and the target file sits outside the skill bundle at a machine-specific home-directory path, a minor organization/portability gap versus the well-split clear-overview anchor at 5.

4 / 5

Total

15

/

20

Passed

Description

67%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 solid, third-person description with a well-enumerated scope and an explicit command-based trigger. Its main weaknesses are the absence of natural-language trigger phrasing and synonyms (notably "pull request" spelled out), which leave the when-clause less useful for natural invocation.

Suggestions

Add natural trigger phrases alongside the command names, e.g. "Use when creating or updating pull requests" so the skill triggers from user language, not only slash commands.

Include the spelled-out term "pull request" (and common variants like "PR description" or "open a PR") so the keyword coverage includes synonyms users actually say.

DimensionReasoningScore

Specificity

Enumerates five concrete coverage areas — "title, body template, label mapping, assignment, and draft policy" — giving specific scope, but they are nouns rather than concrete actions, so it falls short of the comprehensive multi-action anchor at 5.

4 / 5

Completeness

Both parts are present: a clear what ("PR formatting reference — title, body template, label mapping, assignment, and draft policy") and an explicit when ("Invoked by pr/create and pr/update-desc commands"). It is not a 5 because the trigger guidance cites command names rather than concrete natural-language trigger phrases.

4 / 5

Trigger Term Quality

"PR", "formatting", "label", and "draft" are natural keywords, but the description only ever uses the abbreviation "PR" and misses common variations like "pull request", matching the anchor for relevant keywords missing common synonyms rather than the good-coverage anchor at 4.

3 / 5

Distinctiveness Conflict Risk

The command-specific triggers ("pr/create and pr/update-desc") and the formatting-only scope create a mostly distinct niche, but "PR formatting" still has minor overlap risk with other pull-request-related skills, keeping it below the clear-niche anchor at 5.

4 / 5

Total

15

/

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

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Repository

phatblat/dotfiles

Path

.agents/harness/adapters/antigravity/skills/pr-style/SKILL.md

Revision

4d65cab

Reviewed

Table of Contents

DiscoveryImplementationValidation

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.

Claim skill