smoke-tests

Use when running VS Code smoke tests or working on smoke-test CI steps. Covers npm run smoketest / smoketest-no-compile, grep filtering tests, and a temporary repeat-loop technique for tracking down flaky smoke tests in CI.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

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 well-structured, highly actionable operational guide with copy-paste commands, an explicit fail-fast validation loop, and clear cross-references to sibling skills. Slightly verbose in places, which is the only thing holding conciseness below the top anchor.

Dimension	Reasoning	Score
Conciseness	Mostly lean and assumes Claude's competence (no preamble on what smoke tests or mocha are), but a few explanatory asides in the 'Inside the artifact' bullets and the fail-fast rationale could be trimmed.	4 / 5
Actionability	Fully executable, copy-paste-ready guidance throughout: concrete npm commands, a complete YAML loop snippet, `gh run download`, and `az pipelines runs artifact download` invocations covering the common cases.	5 / 5
Workflow Clarity	Both workflows (flaky-loop probe and CI-failure log debugging) are clearly sequenced with explicit fail-fast validation and a prioritized 'check these first' checklist; minor checkpoint gaps keep it off the top anchor.	4 / 5
Progressive Disclosure	Well-organized into clearly headed sections with one-level-deep, clearly signaled cross-skill references ('see the azure-pipelines / code-oss-logs / unit-tests / integration-tests skill'); no bundle files exist to split further, and navigation is easy.	4 / 5
	Total	17 / 20 Passed

Description

87%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 clearly states both what the skill covers and when to use it, with concrete command names and natural trigger terms. Only minor gaps in action coverage and synonym breadth keep specificity and trigger_term_quality off the top anchor.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions and named commands ('npm run smoketest / smoketest-no-compile', 'grep filtering tests', 'temporary repeat-loop technique for tracking down flaky smoke tests'), but omits the CI-failure log debugging that the body covers, leaving minor gaps.	4 / 5
Completeness	Explicitly answers both: 'what' ('Covers npm run smoketest / smoketest-no-compile, grep filtering tests, and a temporary repeat-loop technique...') and 'when' ('Use when running VS Code smoke tests or working on smoke-test CI steps') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural terms users would say ('VS Code smoke tests', 'smoke-test CI steps', 'flaky smoke tests') plus the literal npm command, though a few common synonyms are missing.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (VS Code smoke tests) with distinct triggers; minimal conflict risk with unit/integration-test skills, which the body explicitly distinguishes from.	5 / 5
	Total	18 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 2 missing	Warning

	Total	15 / 16 Passed

Repository: posit-dev/positron
Path: .github/skills/smoke-tests/SKILL.md
Commit: b0258bc

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.