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

77%

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

96%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.

The body is a concise, highly actionable reference with concrete commands, paths, and conventions, plus a clear validated pre-PR workflow. Progressive disclosure is good given the skill is self-contained with no bundle files.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — it lists tools, build commands, paths, and conventions with no padding or explanation of concepts Claude already knows, and every line earns its place.	5 / 5
Actionability	It provides copy-paste-ready commands (`make test-backend-app`, `make staging`, etc.), concrete file paths, naming conventions, and a pre-PR checklist that fully cover the common cases.	5 / 5
Workflow Clarity	The Pre-PR Testing Checklist gives a clear sequenced workflow with explicit validation checkpoints (each `make ...` must pass), and the staging section provides a feedback loop (build, smoke test, tear down) for the destructive/batch deployment path.	5 / 5
Progressive Disclosure	Content is well-organized into clear sections with no bundle files present (references/, scripts/, assets/ do not exist), and the smoke-test and workflow tables appropriately summarize what would otherwise be verbose lists; minor gaps only — no external deep-dive references are signaled, though none are strictly needed here.	4 / 5
	Total	19 / 20 Passed

Description

58%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.

The description clearly states what the skill covers and is domain-specific, but it lacks an explicit 'Use when...' trigger clause in the frontmatter and its keywords are internal categories rather than natural user phrases.

Suggestions

Add an explicit 'Use when...' trigger clause to the description, e.g. 'Use when adding or modifying backend/frontend tests, changing CI/CD workflows, or adding smoke/E2E tests.'

Include natural user-facing keywords and synonyms (e.g. 'unit tests', 'integration tests', 'GitHub Actions', 'test coverage', 'CI gate') so the skill triggers on phrases users actually say.

Lead with concrete actions (e.g. 'Write and run backend/frontend tests, configure CI pipelines, and maintain smoke test coverage') before the framing sentence.

Dimension	Reasoning	Score
Specificity	Names the domain (testing, CI pipeline, smoke tests) and several concrete capabilities ('write tests correctly', 'understand the CI gate requirements'), but the actions are framed as outcomes rather than explicit concrete operations, leaving minor coverage gaps.	4 / 5
Completeness	The 'what' is clearly stated, but there is no 'Use when...' clause in the description itself — the trigger guidance lives only in the body, so per the rubric this caps completeness at 3.	3 / 5
Trigger Term Quality	It contains relevant terms ('backend tests', 'frontend tests', 'CI/CD workflows', 'smoke tests', 'E2E tests') but these read as internal categories rather than natural phrases a user would utter, and it omits common synonyms users actually say.	3 / 5
Distinctiveness Conflict Risk	The SkillHub-specific framing ('CI gate requirements', smoke test coverage) gives it a fairly distinct niche with only minor overlap risk against generic testing skills.	4 / 5
	Total	14 / 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: 4 missing	Warning

	Total	15 / 16 Passed

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

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.