CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pr-to-green

Bring a pull request to green by syncing with main, resolving conflicts safely, and fixing failing checks with CausalPy conventions.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

Quality

Content

81%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 strong, well-structured workflow skill: concrete commands, explicit validation checkpoints, and thoughtful escalation clauses for destructive git operations and scope drift. The only gaps are a few unspecified repo conventions and mild padding in the subagent sections.

DimensionReasoningScore

Conciseness

The body is written as lean imperative bullets with no explanation of concepts Claude already knows (git, CI, subagents), e.g. 'git fetch upstream' then 'git rebase upstream/<base-branch>'. Minor over-explanation could be trimmed, such as 'Each subagent runs in its own context window and returns a condensed result' and 'so local branch tracks the PR head'.

4 / 5

Actionability

Concrete, executable commands appear throughout ('gh pr view <number>', 'gh pr checks <number>', 'gh pr checkout <number>', 'git diff --name-only --diff-filter=U', 'uv run pytest', 'prek run --all-files'). A few directions remain high-level, e.g. 'follow docs placement and glossary/citation conventions' and 'maintainer-preferred merge strategy', which keeps it below fully copy-paste-ready.

4 / 5

Workflow Clarity

The six-step workflow is explicitly sequenced with validation checkpoints and a real feedback loop: 'Re-run targeted checks after conflict resolution', 'Always run prek run --all-files before final handoff', 'If fixes introduced new failures, loop back to step 3', and 'Do not push until a full local pass is achieved'. Error recovery and escalation paths are explicit, matching the top anchor rather than the 'minor validation gaps' anchor.

5 / 5

Progressive Disclosure

The single file is well-sectioned (When to use, Preconditions, Workflow, Subagent delegation, Guardrails) with two clearly signaled, one-level-deep references ('.agents/skills/python-environment/SKILL.md', AGENTS.md#testing), neither of which resolves in this bundle. The detailed escalation-report specifications are somewhat long for the main file, and the file exceeds 50 lines, so it falls just short of the top anchor.

4 / 5

Total

17

/

20

Passed

Description

66%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 specific, distinct, third-person description with good natural keywords and concrete actions. Its main weakness is the missing 'Use when...' trigger clause, which both caps completeness and leaves the activation conditions implicit.

Suggestions

Add an explicit trigger clause, e.g. 'Use when a PR is failing checks, has merge conflicts, is behind main, or the user asks to get a PR green/fix CI.'

Include common trigger synonyms such as 'CI', 'failing tests', and 'rebase' so natural user phrasings match the description.

Mention the maintainer status-update capability ('report what was fixed and what remains') to round out coverage of what the skill does.

DimensionReasoningScore

Specificity

It lists three concrete actions — 'syncing with main', 'resolving conflicts safely', and 'fixing failing checks with CausalPy conventions' — matching the 'several specific actions; minor gaps' anchor. It falls short of 5 because capabilities covered in the body (e.g. preparing a maintainer status update) are absent from the description.

4 / 5

Completeness

The 'what' is clear ('Bring a pull request to green by syncing with main, resolving conflicts...'), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric guideline. The 'when' is only weakly implied by 'to green', so it does not reach the 4 anchor.

3 / 5

Trigger Term Quality

Natural terms users would say are present: 'pull request', 'green', 'main', 'conflicts', 'failing checks'. It misses common variations such as 'CI', 'failing tests', 'rebase', or 'PR checks', so it fits 'good keyword coverage; a few natural terms missing' rather than comprehensive coverage.

4 / 5

Distinctiveness Conflict Risk

'Bring a pull request to green' plus the CausalPy qualifier carves a distinct niche with minor overlap risk against generic git-conflict or fix-CI skills. It is not a 5 because the trigger phrasing is not distinctive enough to fully separate it from a hypothetical generic CI-repair skill.

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

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

Repository

pymc-labs/CausalPy

Path

.agents/skills/pr-to-green/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.