build-monitor

Continuously monitors Buildkite pipeline builds, detects failures, investigates root causes, fixes issues, and pushes fixes. Runs a polling loop that checks build status at configurable intervals for a configurable duration. Use when the user says "monitor builds", "watch pipeline", "watch CI", "continuous monitoring", "keep checking builds", or wants automated build-fix cycles.

Quality

88%

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

Quality

Content

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

The body is highly actionable with an excellent, well-validated workflow, but it is moderately verbose and misses the opportunity to push reference material (failure patterns, commit workflow) into separate bundle files for cleaner progressive disclosure.

Suggestions

Trim inferable prose — collapse the 'Do NOT re-derive' rationale and auth-check narrative into terse imperative steps to lift conciseness.

Move the Failure Patterns Reference table and the commit-workflow detail into a references/ file (e.g. references/failure-patterns.md) and link to it one level deep to improve progressive disclosure.

Verify scripts/ci/bk-pipeline-status.sh and the referenced docs path actually exist in the bundle, or mark them as external repo paths so navigation expectations are clear.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands and tables, but several prose blocks pad context Claude can infer — e.g., the 'Do NOT re-derive' tooling rationale, the auth-check narrative, and verbose section intros — that could be tightened without losing clarity.	3 / 5
Actionability	Fully executable guidance throughout: copy-paste-ready shell invocations of scripts/ci/bk-pipeline-status.sh, exact mvnw test commands, explicit subagent Task() calls, and concrete git commit/push steps covering the common cases.	5 / 5
Workflow Clarity	A clearly sequenced multi-step loop (auth check → fetch → classify → investigate → fix → adversarial review → commit/push → wait) with explicit validation checkpoints and fail-closed gates (auth stop, review PASS/BLOCK, gate failure ⇒ no commit), satisfying the destructive/batch feedback-loop requirement.	5 / 5
Progressive Disclosure	Reasonable section structure, but no bundle files exist in references/scripts/assets to offload detail, so the failure-patterns table and commit-workflow detail are inlined rather than split into one-level-deep reference files; references to an external docs path and a script are not part of a present bundle.	3 / 5
	Total	16 / 20 Passed

Description

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

The description is exemplary: it states concrete capabilities, provides a rich set of natural trigger phrases, and explicitly covers both what and when. Third-person voice is used throughout with no over-claims.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'monitors Buildkite pipeline builds, detects failures, investigates root causes, fixes issues, and pushes fixes' plus 'Runs a polling loop that checks build status at configurable intervals' — matching the comprehensive-coverage anchor.	5 / 5
Completeness	Explicitly answers both what (monitors/detects/investigates/fixes/pushes via a polling loop) and when via a clear 'Use when the user says...' clause with concrete trigger phrases.	5 / 5
Trigger Term Quality	Comprehensive natural trigger phrases with synonyms — 'monitor builds', 'watch pipeline', 'watch CI', 'continuous monitoring', 'keep checking builds', 'automated build-fix cycles' — the kind of language a user would actually say.	5 / 5
Distinctiveness Conflict Risk	Occupies a clear niche — Buildkite pipeline build monitoring and automated build-fix cycles — with distinct triggers and minimal overlap risk against other skills.	5 / 5
	Total	20 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 1 suspicious	Warning
referenced_paths_exist	Referenced path issues: 14 missing, 14 deeper-than-1-level	Warning

	Total	14 / 16 Passed

Repository: mock-server/mockserver-monorepo
Path: .opencode/skills/build-monitor/SKILL.md
Commit: 817ee95

Reviewed: 1 day 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.