CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

optimize-pipeline

Optimize Harness CI/CD pipeline performance via MCP. Configure parallel test execution with Test Intelligence, design multi-layer caching strategies, analyze pipeline bottlenecks with stage-level timing breakdowns, optimize cache hit rates, and design monorepo CI pipelines with selective builds. Use when asked to speed up pipelines, improve cache hit rates, set up parallel testing, optimize build times, or configure monorepo builds. Do NOT use for creating new pipelines (use create-pipeline instead) or debugging failures (use debug-pipeline instead). Trigger phrases: pipeline speed, slow pipeline, cache hit rate, parallel tests, test intelligence, build optimization, caching strategy, monorepo pipeline, pipeline bottleneck, build speed.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

75%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 an efficient, well-sequenced design playbook with genuinely non-obvious domain notes and good error-recovery guidance, but it stops at design: no tool call, command, or config example shows how to actually apply any optimization, and there is no step to verify improvements after changes are made. Single-file organization is solid with minor room to split per-topic detail into references.

Suggestions

Add concrete apply-path guidance: for each optimization step, show the MCP tool call (e.g., a harness pipeline-update call with resource_type and YAML payload parameters) or an example Harness pipeline YAML snippet for enabling Test Intelligence, parallelism, and a cache step — the read-only call blocks already model the format.

Close the workflow with a validation checkpoint: after applying changes, re-run the pipeline, pull execution timings with the harness_get call from Step 5, and compare against the Step 1 baseline to confirm the time savings before reporting done.

Consider moving per-build-tool caching details and the monorepo dependency-graph guidance into one-level-deep reference files so SKILL.md stays a shorter overview that branches by optimization type.

DimensionReasoningScore

Conciseness

Lean, imperative, bullet-driven content with zero padding or explanation of concepts Claude already knows; the explanatory asides that exist are genuinely non-obvious domain knowledge ('Test Intelligence needs 2-3 full test runs to build its initial model', 'Cache keys should be based on lockfiles, not timestamps', 'Set cache TTL (recommended 7-14 days)'). Every section adds information an agent would not already have. The Examples section slightly restates step content, but each line pairs a user phrasing with the matching response path, which earns its place.

5 / 5

Actionability

Data-gathering steps are executable — two harness_list call blocks and a harness_get block with concrete parameters — but the configuration core of the skill (Steps 3, 4, 6) provides only design parameters ('Enable Test Intelligence in the pipeline stage', 'Configure test splitting method: by class, by file, or by timing data', 'Use path-based triggers: only build services with changed files') with no tool call, command, or YAML example for actually applying any of it. This matches 'some concrete guidance but incomplete; missing key details' better than anchor 4, where gaps would be minor — here the apply-the-change path is entirely absent. Anchor 5 is clearly out of reach: only read-only calls are templated, nothing for configuration.

3 / 5

Workflow Clarity

Clear six-step sequence: scope and baseline timing data first (Step 1), task identification branching into five paths (Step 2), then per-task design steps, with a Troubleshooting section providing error-recovery loops for failure modes (TI not skipping tests, cache misses, monorepo building everything). Not 5: no post-change validation step — nothing instructs re-running the pipeline and comparing stage timings to confirm the optimization actually helped, which is the natural closing checkpoint for an optimization skill. Not 3: checkpoints are mostly present (baseline gathering up front, troubleshooting recovery at the back) and the gap is a single missing verify step.

4 / 5

Progressive Disclosure

Well-organized single-file skill with clear step, example, performance-note, and troubleshooting sections; the roughly 150-line body stays navigable with no nested or buried references. Not 5: the five optimization types are each self-contained playbooks that could live in one-level-deep reference files to keep SKILL.md as a shorter overview (e.g., per-build-tool caching details), which is a minor organization gap rather than 'content appropriately split'.

4 / 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.

An exemplary description: concrete third-person capabilities, comprehensive natural trigger phrases, explicit use-when guidance, and explicit do-not-use boundaries against sibling skills. It reads as a model instance of the top anchors on every dimension.

DimensionReasoningScore

Specificity

Lists five concrete capabilities ('Configure parallel test execution with Test Intelligence, design multi-layer caching strategies, analyze pipeline bottlenecks with stage-level timing breakdowns, optimize cache hit rates, and design monorepo CI pipelines with selective builds') with comprehensive coverage of the pipeline-optimization domain. Not 4: no coverage gaps — each named action is a distinct, concrete capability rather than a generic summary.

5 / 5

Completeness

Explicitly answers both 'what' (five concrete capabilities) and 'when' ('Use when asked to speed up pipelines, improve cache hit rates, set up parallel testing, optimize build times, or configure monorepo builds'), reinforced by a concrete trigger-phrase list. Not 4: the 'when' is fully explicit with concrete triggers, exactly the top-anchor pattern.

5 / 5

Trigger Term Quality

Beyond the natural phrasings in the 'Use when asked to' clause ('speed up pipelines', 'improve cache hit rates', 'set up parallel testing'), it supplies ten explicit trigger phrases ('pipeline speed, slow pipeline, cache hit rate, parallel tests, test intelligence, build optimization, caching strategy, monorepo pipeline, pipeline bottleneck, build speed') covering the common ways users phrase this need, including synonyms. Not 4: keyword coverage is comprehensive with synonyms, matching the top anchor.

5 / 5

Distinctiveness Conflict Risk

Clear niche (Harness CI/CD pipeline performance optimization via MCP) with distinct triggers, plus explicit boundary disambiguation ('Do NOT use for creating new pipelines (use create-pipeline instead) or debugging failures (use debug-pipeline instead)') that actively prevents wrong-skill triggering. Not 4: the explicit sibling-skill boundaries push conflict risk below 'minor'.

5 / 5

Total

20

/

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

harness/harness-ai

Path

plugins/claude/skills/optimize-pipeline/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.