pr-workflows

Turn issues into PRs, handle commits, and run prek checks consistently.

Quality

48%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/pr-workflows/SKILL.md

Quality

Content

37%Weight 40%Scale 1-3

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

The skill body is admirably concise and well-structured as an overview, but it provides no executable guidance or sequenced workflow itself, and its reference links point to files that do not exist. It functions as a table of contents without the underlying content.

Suggestions

Add concrete, executable guidance in the body or ensure the referenced reference/*.md files actually exist and contain the detailed steps.

Provide a numbered sequence for the issue-to-PR flow with validation checkpoints (e.g., verify prek passes before committing, confirm CI green before requesting review).

Include at least one concrete command or example (e.g., the prek invocation or a commit-message template) so the skill is actionable without external files.

Dimension	Reasoning	Score
Conciseness	The body is a lean ~15 lines with no padding or explanation of concepts Claude already knows; every line earns its place, matching the 'lean and efficient' anchor.	3 / 3
Actionability	It offers only high-level bullets like "Turning an issue into a PR" and "Running prek checks" with no concrete commands, code, or specifics, and the referenced files do not exist, matching 'describes rather than instructs'.	1 / 3
Workflow Clarity	The "When to use" list is a set of scenarios, not a sequenced workflow, and there are no validation checkpoints for the multi-step issue-to-PR flow, matching 'no sequence for multi-step tasks; no validation mentioned'.	1 / 3
Progressive Disclosure	The References section is well-signaled and one level deep, but the referenced bundle files (reference/*.md) are absent, so the structure promises detail it does not deliver, fitting 'some structure but could be better organized'.	2 / 3
	Total	7 / 12 Passed

Description

60%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description names concrete, relevant actions and natural domain terms, but omits an explicit 'Use when...' trigger, which caps completeness and distinctiveness at 2. It is clear and specific yet incomplete as activation guidance.

Suggestions

Add a 'Use when...' clause naming the situations that should trigger this skill (e.g., 'Use when turning issues into PRs, preparing commit messages and PR summaries, or running prek/pre-commit checks').

Include natural term variations such as 'pull requests', 'commit messages', and 'staged changes' to improve trigger coverage.

Add an explicit trigger phrase so the description answers 'when should Claude use it', not just 'what does it do'.

Dimension	Reasoning	Score
Specificity	"Turn issues into PRs, handle commits, and run prek checks" lists multiple concrete actions, matching the anchor that enumerates several specific capabilities rather than vague language.	3 / 3
Completeness	It clearly states what the skill does but provides no "Use when..." clause or equivalent explicit trigger, so per the guideline completeness is capped at 2 ('has what, when only implied').	2 / 3
Trigger Term Quality	Terms like "issues", "PRs", and "commits" are natural, but common variations ("pull request", "commit messages", "staged changes") are missing, fitting the 'some relevant keywords but missing common variations' anchor.	2 / 3
Distinctiveness Conflict Risk	The issue-to-PR/prek niche is fairly specific, but it could overlap with generic git or commit skills and lacks an explicit trigger to disambiguate, matching 'somewhat specific but could still overlap'.	2 / 3
	Total	9 / 12 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
relative_links	Relative link issues: 3 missing	Warning

	Total	15 / 16 Passed

Repository: pymc-labs/CausalPy
Path: .agents/skills/pr-workflows/SKILL.md
Commit: 7e23946

Reviewed: 13 days ago

Table of Contents

Discovery Implementation Validation

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.