CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/github-actions-test-jobs

Configures GitHub Actions test workflows - `.github/workflows/test.yml` with matrix builds (OS × runtime, with per-OS quirks - path separators, line endings, shells - and per-language runtime matrices in references/os-matrix.md), JUnit XML artifact upload, retry/sharding, services (PostgreSQL, Redis), per-trigger filtering (pull_request, push, schedule, workflow_dispatch). Use when the project hosts on GitHub and the team wants idiomatic GitHub Actions patterns for test workflows, or needs continuous cross-platform OS / runtime coverage.

72

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

Overview
Quality
Evals
Security
Files

Quality

Content

86%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 lean, actionable skill body with executable YAML patterns and proper reference offloading. The main weakness is a numbering gap between Step 3 and Step 6 that mildly disrupts the referenced workflow sequence.

Suggestions

Number the 'Service containers and reporting' section as Step 4 (and Step 5 if split) so the body's section numbers match the 'How to use' references to Steps 1–9.

Trim redundant gloss lines that restate the preceding code block verbatim (e.g. the 'The minimal pattern...' sentence under Step 1) to tighten conciseness.

Consider moving the full Step 6 retry snippet into references/services-and-reporting.md alongside the other deferred recipes so the main body stays a consistent overview.

DimensionReasoningScore

Conciseness

Efficient body of copy-paste YAML with minimal concept re-explanation, but a few trailing gloss lines (e.g. 'The minimal pattern: trigger on PR + push-to-main, install deps, run tests.') restate what the preceding code already shows.

4 / 5

Actionability

Fully executable, copy-paste-ready YAML blocks cover the common cases (basic workflow, matrix, sharding, retry, path filters, concurrency, secrets) with concrete action versions and commands.

5 / 5

Workflow Clarity

'How to use' gives a numbered sequence and 'Verify before merge' supplies a validation/feedback loop, but the body's section numbering has gaps — Steps 4 and 5 are merged into an unnumbered 'Service containers and reporting' section while Steps 6–9 resume, slightly breaking the referenced sequence.

4 / 5

Progressive Disclosure

SKILL.md is a well-signaled overview that offloads depth (os-matrix.md, services-and-reporting.md) to one-level-deep references that exist as real files, with bulk detail appropriately split out and clearly navigable.

5 / 5

Total

18

/

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, third-person description that concretely lists capabilities and provides an explicit 'Use when' trigger clause. Slightly heavy on technical event names, but highly specific and distinctive.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — matrix builds, JUnit XML artifact upload, retry/sharding, services (PostgreSQL, Redis), per-trigger filtering — giving comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

Explicitly answers both 'what' (configures test workflows with matrix builds, JUnit, retry, services, filtering) and 'when' via a concrete 'Use when the project hosts on GitHub...' trigger clause.

5 / 5

Trigger Term Quality

Strong natural keywords ('GitHub Actions test workflows', 'cross-platform OS / runtime coverage', 'matrix builds') with good coverage, though several terms are technical event names (pull_request, schedule, workflow_dispatch) rather than phrases a non-expert user would naturally say.

4 / 5

Distinctiveness Conflict Risk

Clear niche (GitHub Actions test workflows) with distinct triggers; the GitHub + test-workflow scoping minimizes overlap with sibling CI skills like gitlab-ci-test-jobs.

5 / 5

Total

19

/

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: 1 missing

Warning

Total

15

/

16

Passed

Reviewed

Table of Contents