CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

testland/github-actions-test-jobs

Use whenever the task is to run tests in GitHub Actions: a test workflow on pull requests, matrix builds across OS and runtime versions, splitting a suite across parallel runners, service containers such as Postgres or Redis, uploading JUnit reports, and trigger filters.

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 highly actionable, well-structured skill: copy-paste YAML for every common GitHub Actions testing pattern, a verification section with error-recovery guidance, and clean one-level-deep references to real bundle files. The main deductions are partial redundancy between the worked example and earlier sections, and a broken step-numbering sequence (Steps 4–5 silently relocated to a reference).

Suggestions

Renumber the step headers continuously (the sequence currently skips from Step 3 to Step 6 because Steps 4–5 moved into references/services-and-reporting.md) or drop numbers in favor of descriptive headings so the sequence reads coherently.

Trim the verbatim documentation quotes to the single operative fact (e.g., keep the fail-fast default and the 256-job limit, cut the surrounding quoted sentences) to tighten token efficiency.

Cut or compress the Worked example, which restates patterns already shown in Steps 1–9, down to the one new thing it demonstrates (combining them in a single realistic workflow).

DimensionReasoningScore

Conciseness

The body is code-first and assumes competence — no "what is GitHub Actions" filler — but the long verbatim documentation quotes and the Worked example and References sections, which partially restate content already covered, keep it a notch below the lean 5 anchor. It sits above the 3 anchor because the padding is limited and the facts cited are ones Claude could easily get wrong.

4 / 5

Actionability

Every section ships copy-paste-ready YAML: the minimal workflow, the fail-fast matrix, the Jest shard matrix, the retry action with its actual inputs, path filters with a workflow_dispatch block, the concurrency group, and the full fork-safe two-job split — fully executable and covering the common cases.

5 / 5

Workflow Clarity

The "How to use" list gives a clear sequence and the "Verify before merge" section provides a real feedback loop (missing secret → check repo settings → add → re-run), with the anti-patterns table as a checklist. However the step headers jump from Step 3 to Step 6 — Steps 4–5 were moved into a reference file without renumbering — which breaks the numbered sequence enough to fall below the 5 anchor's fully coherent progression.

4 / 5

Progressive Disclosure

The SKILL.md is a well-organized overview whose deep material (OS/runtime matrix depth, service containers, JUnit reporting) is split into two real, one-level-deep reference files that are clearly signaled in context and re-listed with descriptions in the References section — matching the 5 anchor.

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 description: it pairs an explicit "Use whenever..." trigger with a comprehensive list of concrete capabilities, and its GitHub-Actions-test-specific vocabulary keeps it distinct from neighboring CI skills. The only gap is missing common synonyms such as "CI" or "continuous integration" that users would naturally say.

DimensionReasoningScore

Specificity

The description lists six concrete actions — "a test workflow on pull requests", "matrix builds across OS and runtime versions", "splitting a suite across parallel runners", "service containers such as Postgres or Redis", "uploading JUnit reports", and "trigger filters" — giving comprehensive, specific coverage rather than the minor-gaps profile of the 4 anchor.

5 / 5

Completeness

It explicitly answers both questions: the opening "Use whenever the task is to run tests in GitHub Actions" is a concrete trigger clause, and the colon-introduced list clearly states what the skill does — matching the 5 anchor rather than the 4 anchor where the 'when' could be more explicit.

5 / 5

Trigger Term Quality

Natural phrases like "run tests", "GitHub Actions", "test workflow", "pull requests", "JUnit reports", and "Postgres or Redis" give good keyword coverage, but common synonyms users actually say — "CI", "continuous integration", ".github/workflows" — are absent, so it falls short of the 5 anchor's synonym-and-extension comprehensiveness.

4 / 5

Distinctiveness Conflict Risk

The description is pinned to a clear niche — test jobs in GitHub Actions specifically — with triggers (matrix builds, service containers, JUnit, trigger filters) that sibling CI skills (GitLab CI, Jenkinsfile) would not match, so conflict risk is minimal.

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 possibly missing (references/circleci.md)

Warning

Total

15

/

16

Passed

Reviewed

On this page