CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

github-pipeline-audit

Sweeps every surface of the MockServer GitHub repository and the build pipeline to confirm nothing is outstanding and everything is clean and up to date. Covers issues, pull requests, all three GitHub security-alert types, the Dependabot updater's own health, GitHub Actions, Buildkite, branches and worktrees, discussions, releases, and published-artifact parity. Use when the user says "check GitHub", "anything outstanding", "is everything clean", "audit the repo", "check the build pipeline", "housekeeping", or before cutting a release.

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

85%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 operationally excellent skill body: executable commands, explicit sequencing, hard validation gates, and a high density of hard-won, non-obvious diagnostic knowledge. Its main weaknesses are a monolithic structure with no progressive disclosure despite its length, and a scattering of time-sensitive version/date references that are not quarantined in a clearly-marked historical section.

Suggestions

Split stable-but-bulky reference material into one-level-deep bundle files (e.g. references/dependabot-failures.md for the updater symptom/cause/fix table and references/release-parity.md for the channel-check table), keeping SKILL.md as the checklist-and-navigation overview.

Move time-sensitive observations (the 5.15.0-vs-9.2.0 solrsearch staleness, the twenty stale Spring alerts, the 186-commits-behind checkout) into a clearly labeled 'Known failure patterns (historical)' section so stale version numbers are not mistaken for current state.

Add the missing natural trigger terms — 'security alerts', 'CI', 'dependabot', 'dependencies' — to the description's 'Use when' clause to improve discovery.

DimensionReasoningScore

Conciseness

The body is dense with non-obvious, repo-specific operational knowledge (token-scope limitations, EC2 spot reclamation signatures, the stale solrsearch index, the 280-char dismissal cap) and wastes few tokens teaching known concepts. Minor deductions: time-sensitive version specifics ("reports 5.15.0 while the repo is on 9.2.0", "Twenty Spring alerts", "186 commits behind") sit in inline asides rather than a clearly-marked historical/evidence section, and a few editorial flourishes ("the check nobody thinks to run") could be trimmed.

4 / 5

Actionability

Nearly every section supplies copy-paste-ready commands — gh CLI calls with complete --jq filters, bk api invocations with log-cleaning pipelines, git freshness checks, curl endpoints for each release channel — plus a concrete report template. Placeholders (<N>, <slug>) are conventional and the specific examples cover the common cases.

5 / 5

Workflow Clarity

The workflow is explicitly sequenced (Section 0 "do this FIRST" with the dependency rationale, a four-step diagnosis order where each step rules out the next) and includes real validation checkpoints: the checkout-staleness count that "MUST be 0", "prove non-applicability before dismissing", git cherry before suggesting branch deletion, and the lsof/gitignored-plans check before worktree removal. The destructive/batch operations (bulk alert dismissal, branch/worktree removal) all carry evidence and safety gates, and feedback loops exist (retry on spot reclamation, reversible dismissals).

5 / 5

Progressive Disclosure

The ~340-line body is well-sectioned with headers, but it is entirely monolithic: no references/, scripts/, or assets/ files exist, and content that would naturally live in one-level-deep reference files — the Dependabot updater failure-cause table, the release-parity channel table, the alert-triage matrix — is fully inlined, so everything loads into context on every invocation.

3 / 5

Total

17

/

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.

A strong description: third-person, concrete, and comprehensive about the surfaces covered, with an explicit and well-phrased 'Use when' clause containing natural trigger terms and synonyms. The only gap is that a few plausible trigger phrasings (security alerts, CI, dependabot) are not included among the trigger terms.

DimensionReasoningScore

Specificity

The description enumerates ten concrete audited surfaces — "issues, pull requests, all three GitHub security-alert types, the Dependabot updater's own health, GitHub Actions, Buildkite, branches and worktrees, discussions, releases, and published-artifact parity" — giving comprehensive, specific coverage of what the skill does.

5 / 5

Completeness

It explicitly answers both questions: what ("Sweeps every surface... to confirm nothing is outstanding and everything is clean and up to date") and when ("Use when the user says..." with seven concrete trigger phrases plus a timing trigger, "before cutting a release").

5 / 5

Trigger Term Quality

Trigger phrases are natural user utterances with useful synonyms ("check GitHub", "anything outstanding", "is everything clean", "audit the repo", "check the build pipeline", "housekeeping", "before cutting a release"), but common variations users would plausibly say — "security alerts", "CI", "dependabot", "dependencies" — are missing from the trigger list.

4 / 5

Distinctiveness Conflict Risk

It carves out a clear niche — a repo-and-pipeline cleanliness audit pinned to a specific repository — with distinct triggers ("audit the repo", "housekeeping", "is everything clean") that are unlikely to fire for adjacent skills like issue triage or release management.

5 / 5

Total

19

/

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

mock-server/mockserver-monorepo

Path

.opencode/skills/github-pipeline-audit/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.