testing-and-ci

Testing conventions, CI pipeline rules, and smoke test coverage for SkillHub. Ensures agents write tests correctly and understand the CI gate requirements.

Quality

75%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/testing-and-ci/SKILL.md

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a tight, highly actionable reference: concrete commands, paths, naming conventions, CI workflow tables, and a validation checklist, with project-specific gotchas rather than generic padding. It exemplifies token-efficient, executable skill content.

Dimension	Reasoning	Score
Conciseness	The body is dense and lean — tables for smoke tests and CI workflows, exact Make targets and paths, and no padding explaining what JUnit/Vitest/Mockito are; the only prose block (the stale-artifact Maven warning) is project-specific gotcha knowledge Claude would not know, so every token earns its place.	3 / 3
Actionability	It provides fully concrete, copy-paste-ready guidance: exact `make` targets, module test paths, naming templates like `{ControllerName}Test.java`, workflow filenames, and staging commands, matching the 'fully executable code/commands' anchor.	3 / 3
Workflow Clarity	The Pre-PR Testing Checklist is an explicit sequenced validation gate, and the 'Never run ... directly' warning with the `-am`/Makefile remediation acts as a feedback-loop guard for a fragile build, satisfying 'clear sequence with explicit validation steps; checklists for complex processes.'	3 / 3
Progressive Disclosure	No bundle files exist (references/scripts/assets are absent), and the body is well-organized into clear one-level sections (Backend, Frontend, Smoke, CI, Staging, Checklist) with no nested references; per the simple-skill guideline, well-organized sections with no external references needed score 3.	3 / 3
	Total	12 / 12 Passed

Description

50%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description clearly scopes the skill to SkillHub testing/CI/smoke coverage but remains abstract and lacks an explicit 'Use when' trigger clause. It is serviceable yet sits at the middle of the rubric for every dimension.

Suggestions

Add an explicit 'Use when...' clause listing natural triggers such as 'Use when adding or modifying backend/frontend tests, changing GitHub Actions workflows, or adding smoke/E2E tests.'

Replace abstract phrasing with concrete actions, e.g. 'Run backend/frontend tests via Make targets, follow test naming conventions, and satisfy the CI gate before opening a PR.'

Broaden trigger terms with common variations users actually say (e.g. 'unit tests', 'integration tests', 'PR checks', 'GitHub Actions').

Dimension	Reasoning	Score
Specificity	"Testing conventions, CI pipeline rules, and smoke test coverage" names the domain and several actions but stays abstract rather than listing concrete actions, matching the 'names domain and some actions' anchor; it is not a list of multiple specific concrete actions (3) nor vague (1).	2 / 3
Completeness	It states what the skill covers but only implies when to use it via "Ensures agents write tests correctly"; with no explicit 'Use when...' clause, the judging guideline caps completeness at 2.	2 / 3
Trigger Term Quality	Keywords like "tests", "CI pipeline", "smoke test", and "CI gate" are relevant but lean technical and miss common user variations, fitting 'some relevant keywords but missing common variations'; not the broad natural-term coverage of 3 nor purely generic jargon of 1.	2 / 3
Distinctiveness Conflict Risk	Scoping to SkillHub and the testing/CI niche makes it somewhat specific and unlikely to broadly conflict, yet 'testing' is a common domain that could still overlap with similar skills, matching the 2 anchor rather than a sharply distinct 3 or generic 1.	2 / 3
	Total	8 / 12 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: 4 missing	Warning

	Total	15 / 16 Passed

Repository: iflytek/skillhub
Path: .agents/skills/testing-and-ci/SKILL.md
Commit: ac46ad5

Reviewed: 3 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.