CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

run-pr

Run the automated open-PR maintenance sweep on bigsimmo/psychsift — fix failing CI on every open PR, address and resolve review threads, merge origin/main into branches with a real conflict, and push fixes. Use when the user types "Run PR" as the task message, or asks to sweep/fix/maintain all open PRs. "Run PR" is standing authorization for GitHub reads, pushes to PR feature branches, thread replies/resolutions, and CI re-runs; it never authorizes merging into main, closing PRs, force-pushes, branch deletion, auto-merge, or provider-backed gates.

Quality

91%

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

SKILL.md
Quality
Evals
Security

Quality

Content

88%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 operational skill: highly actionable commands, a rigorously sequenced sweep algorithm with validation and guardrails, and disciplined delegation of policy to an external rulebook. The main trim opportunities are the repeated policy-doc links, partial restatement of guardrails, and one embedded version number.

Suggestions

Consolidate the ~8 repeated links to docs/agents/pull-request-workflow.md into one 'Policy source' section with a list of section anchors, trimming the Authorization section's restatement to the single most common failure.

Replace the time-sensitive 'Node 24' mention with a version-agnostic requirement (e.g. 'the pinned Node version from .nvmrc') or move it to a maintenance-notes section.

Consider moving the CI job-to-local-reproduction table to a references/ file if the workflow matrix grows, keeping the per-PR algorithm lean in SKILL.md.

DimensionReasoningScore

Conciseness

Nearly every token carries repo-specific operational detail Claude could not know (skip labels, flake ledger, reading the 'needs:' array, the job-to-command map), but the same policy-doc link is repeated ~8 times, the Authorization section partially restates the external rulebook it says it does not restate, and 'Node 24' is time-sensitive version info. Not 5: these are minor instances of over-explanation and repetition that could be trimmed; not 3: there is no padding or explanation of concepts Claude already knows.

4 / 5

Actionability

Fully executable throughout: exact MCP tool calls (mcp__github__get_me, mcp__github__get_job_logs with failed_only), concrete git commands (git merge-tree --write-tree origin/main <tip>), a complete CI job-to-local-reproduction table with named npm scripts, and a copy-paste review-record template. Not 4: commands are specific and cover the common cases, including decision rules for flakes and unavailable environments.

5 / 5

Workflow Clarity

Setup steps 1-5 and per-PR steps 0-6 are clearly sequenced with explicit validation: trigger-legitimacy confirmation, clean git status requirement, before/after snapshots, skip gates recorded with reasons, a 3-cycle iteration cap, and 'heed a block, never override it' on guard:push. Not 4: this batch operation has feedback loops (fix-verify cycles, re-run vs. fix decision for transients) and explicit checkpoints, so the destructive/batch cap does not apply — validation is thoroughly present.

5 / 5

Progressive Disclosure

Well-organized single-file skill with policy correctly externalized one level deep to the shared rulebook (docs/agents/pull-request-workflow.md) rather than inlined, and no bundle files exist to misorganize. Not 5: the identical policy-doc link is repeated many times with different anchors, and the ~160-line body with the full CI table inline leaves minor navigation/organization gaps; not 3: structure and signaling are clearly good.

4 / 5

Total

18

/

20

Passed

Description

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

An excellent description: concrete actions, an explicit and unambiguous trigger, tight scoping to one repo, and clear authorization boundaries. The only weaknesses are mild verbosity in the authorization sentence and slightly incomplete synonym coverage for trigger terms.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'fix failing CI on every open PR, address and resolve review threads, merge origin/main into branches with a real conflict, and push fixes' — with comprehensive coverage and consistent third-person voice. Not 4: coverage is complete rather than having minor gaps.

5 / 5

Completeness

Explicitly answers both: what ('fix failing CI... resolve review threads... merge origin/main... push fixes') and when ('Use when the user types "Run PR" as the task message, or asks to sweep/fix/maintain all open PRs'). Not 4: the when-clause is concrete and fully explicit, not merely present.

5 / 5

Trigger Term Quality

Natural triggers are present ('Run PR' as the task message, 'asks to sweep/fix/maintain all open PRs'), but a few natural variations are missing (e.g. 'pull request' is never spelled out). Not 5: the anchor requires comprehensive synonym coverage, which is close but not fully met.

4 / 5

Distinctiveness Conflict Risk

Scoped to a specific repo (bigsimmo/psychsift) with an exact, distinctive trigger phrase ('Run PR'), giving it a clear niche with minimal conflict risk against other skills. Not 4: overlap risk is essentially nil, not 'minor'.

5 / 5

Total

19

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 6 suspicious

Warning

referenced_paths_exist

Referenced path issues: 1 possibly missing (scripts/setup-codex-worktree.mjs)

Warning

Total

14

/

16

Passed

Repository

BigSimmo/PsychSift

Path

.claude/skills/run-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.