CtrlK
BlogDocsLog inGet started
Tessl Logo

pr-post

Post-push CI verification and fix workflow. Use when: (1) user says "pr-post", "check ci", "check actions", "fix ci", or "are checks passing", (2) after pushing code to a PR branch, (3) when the user wants to verify GitHub Actions status and fix any failures.

76

Quality

96%

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

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

An excellent, lean skill body: executable commands, an explicit validation and feedback loop, and repo-specific diagnostic knowledge, all well-organized into clear sections with no padding. No bundle files are needed or referenced.

DimensionReasoningScore

Conciseness

Lean and efficient with no concept explanation: every line is an executable command, a repo-specific fact (ESLint zero-warnings, React Compiler), or a guardrail; the single intro line frames the body without padding.

5 / 5

Actionability

Fully executable `gh` commands cover the common path, placeholders like <run-id> are explicitly derived (HEAD commit / failing check URL), and the diagnosis step lists concrete repo-specific failure causes with a concrete commit format.

5 / 5

Workflow Clarity

A clear 7-step sequence with an explicit validation checkpoint (`--watch --fail-fast`) and a validate-fix-retry feedback loop ('Re-check CI status. Repeat until all checks pass'), plus a Rules checklist guarding force-push and hooks.

5 / 5

Progressive Disclosure

Under 50 lines, single-purpose, with no need for external references; the body is well-organized into ## Workflow and ## Rules sections, satisfying the simple-skill exception for a top score.

5 / 5

Total

20

/

20

Passed

Description

91%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 strong, well-structured description that crisply states its purpose and gives an explicit, enumerated trigger list. Its only soft spot is a narrow action set and minor overlap risk with broader PR-review skills.

DimensionReasoningScore

Specificity

Names the CI domain and two concrete actions ('verify GitHub Actions status and fix any failures'), which is comprehensive for a focused skill but lists only ~2 actions, fitting just above the 3 anchor rather than the multi-action 5 anchor.

4 / 5

Completeness

Explicitly answers both 'what' ('Post-push CI verification and fix workflow') and 'when' via a numbered 'Use when:' clause with concrete trigger phrases, matching the 5 anchor exactly.

5 / 5

Trigger Term Quality

Enumerates five natural phrases a user would actually say ('pr-post', 'check ci', 'check actions', 'fix ci', 'are checks passing') plus contextual triggers, giving comprehensive coverage of natural terms and synonyms for this domain.

5 / 5

Distinctiveness Conflict Risk

The CI-fix niche and distinct 'pr-post' trigger give a clear scope, but 'check ci'/'are checks passing' could overlap slightly with general PR-review skills, so it sits at 4 rather than the minimal-conflict 5 anchor.

4 / 5

Total

18

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
mayank-arora/agent-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.