testing

Governs how to examine, write, fix, and run tests in the rc-unified-crm-extension monorepo. Use when writing new tests, debugging failing tests, examining test coverage, adding tests for new features or connectors, or asking about test conventions, test structure, mocking strategies, or running tests.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

77%

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

The content is highly actionable with executable templates, specific commands, and clear debugging workflows with validation checkpoints. Its main weakness is progressive disclosure — everything lives in one ~200-line file with no bundle files to offload detail — and minor verbosity from duplicated guidance.

Suggestions

Split the inline unit/integration/MCP test templates into reference files (e.g. references/unit-template.js, references/integration-template.js) and link to them from SKILL.md to improve progressive disclosure.

De-duplicate the nock/jest.clearAllMocks() guidance, which appears in both the template blocks and the "Key conventions" bullets, to tighten conciseness.

Move the lengthy "Is It the Test or the Code?" decision tables into a reference file, keeping only the core decision rules inline in SKILL.md.

Dimension	Reasoning	Score
Conciseness	The body is largely efficient and avoids teaching Claude basic Jest/testing concepts, but it runs ~200 lines with substantial inline templates and tables that could be tightened; the duplicated nock/clearAllMocks guidance and lengthy template blocks push it toward the "mostly efficient but could be tightened" anchor.	2 / 3
Actionability	Provides fully executable, copy-paste-ready unit and integration test templates, specific commands (`npm test --workspace=@app-connect/core`, `npx jest ... --verbose --no-coverage`), and concrete helper signatures like createMockUser(overrides) and the in-memory SQLite pattern.	3 / 3
Workflow Clarity	"Examining Failing Tests" and "Is It the Test or the Code?" give a clear numbered sequence with validation checkpoints (run isolated, read failure message, --verbose, check env) plus explicit feedback loops and decision rules for error recovery.	3 / 3
Progressive Disclosure	The body is a single monolithic file with all detail inline and no bundle references to offload material; the closing "Additional Reference" section lists real repo files but these are external source paths rather than skill-bundle references, so structure is present but not split into one-level-deep bundle files.	2 / 3
	Total	10 / 12 Passed

Description

100%

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 is specific, trigger-rich, and clearly distinguishes the skill's scope to a particular monorepo. It fully answers both what it does and when to use it without verbosity.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "examine, write, fix, and run tests" and "writing new tests, debugging failing tests, examining test coverage, adding tests for new features or connectors" — naming the specific scope (the rc-unified-crm-extension monorepo).	3 / 3
Completeness	Explicitly answers what (governs examine/write/fix/run of tests) and when via the "Use when writing new tests, debugging failing tests, examining test coverage..." clause, satisfying both halves with explicit triggers.	3 / 3
Trigger Term Quality	Covers natural user phrasings such as "writing new tests", "debugging failing tests", "test coverage", "test conventions", "test structure", "mocking strategies", and "running tests" — the terms a developer would actually say.	3 / 3
Distinctiveness Conflict Risk	Scoped to a specific monorepo (rc-unified-crm-extension) and concrete test activities, giving it a clear niche unlikely to conflict with more general testing skills.	3 / 3
	Total	12 / 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
relative_links	Relative link issues: 5 suspicious	Warning

	Total	15 / 16 Passed

Repository: ringcentral/rc-unified-crm-extension
Commit: 25fc4c6

Reviewed: 1 day 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.