CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

adding-tests-and-ci

Where a new test belongs, how to write a browser E2E test that fails when the feature breaks, and how to scope CI jobs, steps, and workflow triggers so they run only when a change can affect them. Use when adding, moving, or writing a test (including Design E2E specs), adding or changing a CI job, step, or workflow, or when a job is slow or runs on unrelated changes.

Quality

86%

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

82%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 strong, unusually dense internal policy skill: nearly every line carries repo-specific evidence (scripts, guards, historical failures) with concrete commands and a dedicated validation section for CI changes. The main improvements are trimming time-sensitive dated rationale and splitting one or two detail-heavy sections into references.

Suggestions

Move the dated runner-pool figures (2026-09-29 median wait, October 2026 Enterprise Cloud migration) and the 'Real failures this replaces' quotes into an 'old patterns' / history note so the live guidance does not stale.

Consider splitting the CI-job rules table into a references/ file (like design-e2e.md) so SKILL.md reads as an overview with the per-rule evidence one level deep.

In 'Proving a CI change', state the error-recovery loop explicitly (e.g. what to do when classifier output disagrees with the expected on/off/full result) to upgrade the bullets to a validate-fix-retry sequence.

DimensionReasoningScore

Conciseness

The body is dense with repo-specific facts Claude could not know (script names, guard names, runner-pool numbers) and never explains generic concepts, matching the 'efficient; minor instances that could be trimmed' anchor. The dated capacity figures ('on 2026-09-29 the Fast tests gate waited a median 445 s', 'moved to Enterprise Cloud in October 2026') and the quoted historical complaints in 'Real failures this replaces' are time-sensitive rationale that will stale and could be trimmed or moved to a deprecated/old-patterns note.

4 / 5

Actionability

Guidance is fully concrete and executable for an instruction-only skill: exact commands ('node --experimental-strip-types --test scripts/ci-change-scope.test.ts ...', 'pnpm mutation:changed'), exact file paths ('templates/calendar/server/lib/series-recurrence.oracle.spec.ts'), specific guard names ('guard:no-oracle-loosening', 'guard:mobile-build-paths'), and copy-ready YAML ('group: <name>-${{ github.event.pull_request.number || github.ref }}'). It is not a 5-with-gaps: the specific examples cover the common cases the skill itself names.

5 / 5

Workflow Clarity

Each task area has a clear sequence and real validation checkpoints — 'Proving a CI change' specifies classifier test cases, real main-range runs with before/after evidence, local run: snippet checks, and actionlint, and the E2E section is an explicit checklist. It falls short of the 5 anchor because the validation steps are parallel bullets rather than a sequenced validate→fix→retry loop, and error-recovery paths (e.g. what to do when the classifier output is wrong) are implicit.

4 / 5

Progressive Disclosure

The single bundle reference is well signaled, one level deep, and verified to exist and be self-contained ('Design's harness ... and its traps are in references/design-e2e.md'), and section headers make the body easy to navigate. Below the 5 anchor because the body carries substantial full-detail guidance inline (the CI rules table, test-worker tuning) that an ideal overview-plus-references split would move out, leaving SKILL.md as more of a full manual than an overview.

4 / 5

Total

17

/

20

Passed

Description

88%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 well-crafted description that concretely states what the skill does and gives an explicit, naturally phrased 'Use when' clause covering its three trigger scenarios. Only minor gaps: a few missing synonyms ('flaky', 'pipeline', 'GitHub Actions') and slight breadth on the generic 'writing a test' trigger.

DimensionReasoningScore

Specificity

It names three concrete capabilities in imperative third person — 'Where a new test belongs, how to write a browser E2E test that fails when the feature breaks, and how to scope CI jobs, steps, and workflow triggers' — comprehensive for its stated domain, matching the 'multiple specific concrete actions; comprehensive coverage' anchor. Not 4: no capability area of the skill is left uncovered by the description.

5 / 5

Completeness

Both halves are explicit: the 'what' lists the three capabilities, and an explicit 'Use when' clause gives concrete triggers covering test work, CI changes, and slow/mis-scoped jobs. This mirrors the 5-anchor example structure ('what ... Use when ...') exactly; the 4 anchor's 'when could be more explicit' does not apply.

5 / 5

Trigger Term Quality

Natural user phrasings are well covered: 'adding, moving, or writing a test', 'CI job, step, or workflow', 'a job is slow or runs on unrelated changes', plus 'Design E2E specs'. A few natural terms a user might say are missing (e.g. 'flaky', 'GitHub Actions', 'pipeline', 'skip a job'), which lands it on 'good keyword coverage; a few natural terms missing' rather than the comprehensive-synonyms anchor.

4 / 5

Distinctiveness Conflict Risk

The test-placement plus CI-scoping niche is distinct and the triggers are specific, but 'adding, moving, or writing a test' is broad enough to fire on any test task, and the body names closely related sibling gates (test-audit, design-editor-architecture) whose territory could overlap — 'mostly distinct; minor overlap risk with closely related skills'.

4 / 5

Total

18

/

20

Passed

Validation

75%

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

Validation — 12 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 10 missing

Warning

Total

12

/

16

Passed

Repository

BuilderIO/agent-native

Path

.agents/skills/adding-tests-and-ci/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.