CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/ci-test-job-conventions

Pure-reference for cross-CI test workflow conventions - when to shard (and how many shards), retry policy (which failures are safe to retry), flake-quarantine integration, artifact retention, per-trigger cadence (per-PR vs per-merge vs nightly), concurrency-cancel patterns, per-job timeouts, secret management, and cross-CI portability. Use as the team's reference for CI test-workflow design across GitHub Actions / GitLab CI / Jenkins / CircleCI; per-CI reporting and per-language reporter / cache-key lookups live in references/, as do the CircleCI test-config patterns (.circleci/config.yml workflows, test splitting, orbs, contexts - references/circleci.md).

67

Quality

84%

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

Overview
Quality
Evals
Security
Files

Quality

Content

78%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 well-structured reference skill with lean decision matrices, concrete per-CI config snippets, a clear sequenced how-to with a verification loop, and clean one-level-deep progressive disclosure into two real reference files. Minor trimming of explanatory one-liners and more explicit validation gates would lift the mid-tier dimensions.

DimensionReasoningScore

Conciseness

Largely lean decision-matrices and tables that assume Claude's competence, with only minor explanatory one-liners ('Hard timeouts prevent runaway jobs from consuming runners.', 'Don't retain forever - storage cost.') that could be trimmed; not a 5 due to those small padding instances.

4 / 5

Actionability

Provides concrete, executable guidance - specific shard counts, retry limits, retention bands, timeout values, and real config snippets like 'concurrency: group: ${{ github.workflow }}-${{ github.head_ref }}' + 'cancel-in-progress: true' - but much is decision-table form rather than fully copy-paste code, leaving minor gaps.

4 / 5

Workflow Clarity

The 'How to use this reference' is a clear 6-step numbered sequence with section references and a 're-check the workflow against the conventions below' verification loop, plus a worked example; not a 5 because validation checkpoints are implicit rather than explicit per-step gates.

4 / 5

Progressive Disclosure

SKILL.md is a decision surface that clearly signals one-level-deep references - the 'Deep references' section links to the real files references/circleci.md and references/junit-and-cache-lookups.md, both verified to exist - with content appropriately split and easy navigation.

5 / 5

Total

17

/

20

Passed

Description

83%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, specific description that clearly defines its cross-CI test-workflow niche and enumerates concrete conventions with good trigger keywords. The main gap is the 'when' framing, which reads as a reference-role statement rather than explicit user-scenario triggers.

DimensionReasoningScore

Specificity

Enumerates many concrete conventions - 'when to shard (and how many shards), retry policy... flake-quarantine integration, artifact retention, per-trigger cadence..., concurrency-cancel patterns, per-job timeouts, secret management, and cross-CI portability' - giving comprehensive coverage of specific actions.

5 / 5

Completeness

Has a clear 'what' (the enumerated conventions) and an explicit use clause ('Use as the team's reference for CI test-workflow design across...'), but the 'when' is framed as a reference role rather than concrete user trigger scenarios, leaving it slightly short of a 5.

4 / 5

Trigger Term Quality

Strong natural keywords ('GitHub Actions / GitLab CI / Jenkins / CircleCI', 'shard', 'retry', 'flake-quarantine', 'concurrency-cancel') that users would say, but lacks synonym/variation or file-extension coverage that would push it to a 5.

4 / 5

Distinctiveness Conflict Risk

Carves a clear niche as the cross-CI conventions reference, explicitly distinguishing itself from per-CI implementation skills ('per-CI reporting... live in references/'), minimizing conflict risk.

5 / 5

Total

18

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 3 missing

Warning

Total

15

/

16

Passed

Reviewed

Table of Contents