CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

experimental-code-coverage-build-inspector

Inspects LUCI build details using the inspect_coverage_build.py script to validate code coverage configurations, test execution, and target file coverage.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

—

The risk profile of this skill

Fix and improve this skill with Tessl

tessl review fix ./agents/skills/experimental-code-coverage-build-inspector/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%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 strongly actionable, well-sequenced inspection workflow with explicit validation gates and condition-driven deep-dive branches — workflow clarity is excellent. The main weaknesses are a dangling reference to a nonexistent references/language_coverage_map.json and some redundancy (duplicate buildbucket callouts, summary section) that costs tokens.

Suggestions

Create the missing references/language_coverage_map.json (or remove the two citations of it in Inputs and the Phase 1 summary) so every referenced path resolves within the bundle.

Move the five-entry recipe skip/error triage table into a one-level-deep reference file (e.g. references/recipe_error_triage.md) and link it from the workflow, keeping SKILL.md as a lean overview.

Trim redundancy: consolidate the two separate buildbucket IMPORTANT callouts into one and remove the decorative horizontal rules and overlapping phase details in 'Summary of Automated Script Checks'.

DimensionReasoningScore

Conciseness

The body is dense with domain-specific information Claude does not already know (recipe skip messages, GN args, profraw failure modes) and avoids padding, matching 'efficient; minor instances of over-explanation'. Not 5 because the buildbucket directive is stated twice in two IMPORTANT callouts, the 'Summary of Automated Script Checks' section partially repeats phase details, and decorative horizontal rules add tokens without value.

4 / 5

Actionability

Mostly executable guidance: a concrete copy-paste bash invocation with flags and artifact path, a concrete cron configuration, and a specific three-part artifact template. Not 5 because the cron Prompt template is garbled across backtick-fragmented lines and there is no sample of the script's output format to anchor Phase 1/2/3 interpretation.

4 / 5

Workflow Clarity

The workflow has a clear numbered sequence with an explicit validation checkpoint (the terminal-status gate with 'do NOT exit or return a final report prematurely'), a feedback loop for error recovery (the 10-minute async re-poll with cancel-on-terminal, plus four conditional deep-dive branches keyed to script findings), and a checklist-style artifact structure. This matches the anchor for clear sequence with explicit validation steps and feedback loops.

5 / 5

Progressive Disclosure

Sections are well-organized, but the body twice directs the reader to 'references/language_coverage_map.json' which does not exist in the bundle (no references/ directory is present), a dangling reference, and the detailed five-entry recipe error/skip triage table is inlined where a one-level-deep reference file would fit. This lands on 'some structure but could be better organized' rather than 4, whose 'references mostly clear' anchor assumes referenced files actually resolve.

3 / 5

Total

16

/

20

Passed

Description

66%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 specific, niche-scoped description that clearly states what the skill does and names its tooling, but it lacks any 'when to use' trigger guidance, capping completeness at 3. Keyword coverage is solid for the domain though missing common synonyms like tryjob, CQ, or Clang coverage.

Suggestions

Append a 'Use when...' clause with concrete triggers, e.g. 'Use when triaging CQ tryjobs, investigating 0% or low code coverage on target files, or debugging Clang coverage recipe skips/errors.'

Add natural trigger synonyms such as 'tryjob', 'CQ', 'Clang coverage', 'llvm-cov', and 'uncovered lines' so users phrasing the need differently still match.

Mention the recipe skip/error message triage and exact coverage percentage extraction capabilities to round out the action list toward comprehensive.

DimensionReasoningScore

Specificity

The description names the domain ("LUCI build details", "code coverage") and lists several concrete validation targets ("code coverage configurations, test execution, and target file coverage") plus the exact script name, matching the 'several specific actions; minor gaps' anchor. It falls short of 5 because it omits capabilities the body covers (recipe skip/error triage, uncovered line extraction, async polling) and below-5 phrasing like 'validate ... test execution' is somewhat generic.

4 / 5

Completeness

The 'what' is clear and concrete (inspect LUCI builds to validate coverage configuration, test execution, and target file coverage), but there is no 'Use when...' clause or any equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. It is not 2 because the 'what' half is specific and unambiguous.

3 / 5

Trigger Term Quality

Natural phrases a Chromium developer would say are present: "code coverage", "LUCI build", "target file coverage", "test execution", which is good keyword coverage with only a few natural terms missing. Not 5 because common variations and synonyms like "tryjob", "CQ", "Clang coverage", "llvm-cov", or "uncovered lines" are absent.

4 / 5

Distinctiveness Conflict Risk

The niche (Chromium/LUCI code coverage inspection, with a named script) is mostly distinct with only minor overlap risk against closely related build-inspection or buildbucket skills triggered by the generic opening "Inspects LUCI build details". Not 5 because that opening phrase could collide with a general LUCI build-inspection skill before the coverage-specific qualifier disambiguates.

4 / 5

Total

15

/

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

Warning

Total

15

/

16

Passed

Repository

chromium/chromium

Path

agents/skills/experimental-code-coverage-build-inspector/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.