CtrlK
BlogDocsLog inGet started
Tessl Logo

testing-core-processors

Use when writing or debugging integration tests for error processors in packages/core/src/processors/. Covers the MockLanguageModelV2 pattern for simulating API errors and verifying retry behavior, plus the build prerequisites for focused vitest runs.

70

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is testing-core-processors in mastra-ai/mastra

SKILL.md
Quality
Evals
Security

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 concise, highly actionable body built around complete executable code and concrete commands, with a clear test-writing workflow and well-organized sections. Minor gains available from trimming redundant comments and making the validation/retry feedback loop explicit.

DimensionReasoningScore

Conciseness

Lean and assumes Claude's competence (no preamble on what vitest or a processor is), with complete code; minor trims possible such as the redundant 'Same error logic as doGenerate' comment and the 'Devin Secrets Needed: None' filler.

4 / 5

Actionability

Provides copy-paste-ready, executable code for the mock model, concrete build/run commands ('pnpm build:core', 'npx vitest run ...'), and explicit assertion checkpoints per test type covering the common cases.

5 / 5

Workflow Clarity

Clear sequence (build prerequisites → mock model → three test types with assertions → run commands) with a troubleshooting checkpoint for the build step, though validation feedback loops are implicit rather than spelled out as a retry loop.

4 / 5

Progressive Disclosure

Well-organized into clear single-level sections with one signaled external reference ('See prefill-error-recovery.test.ts'); the large inline mock block is central enough to belong here, so organization is good with only minor gaps.

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, concrete description that clearly states both purpose and trigger, scoped tightly to a specific codebase path and mock pattern. Minor room to broaden trigger-term synonyms, but distinctiveness and completeness are excellent.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions — 'writing or debugging integration tests', 'simulating API errors', 'verifying retry behavior', 'build prerequisites for focused vitest runs' — but stops short of the comprehensive multi-action coverage of a 5.

4 / 5

Completeness

Explicitly answers both 'what' (MockLanguageModelV2 pattern, API error simulation, retry verification, build prerequisites) and 'when' ('Use when writing or debugging integration tests for error processors in packages/core/src/processors/').

5 / 5

Trigger Term Quality

Includes natural phrases a user would say ('writing or debugging integration tests', 'error processors', 'retry behavior') with good coverage, but lacks synonyms or file-extension variants like '.test.ts' that would push it to 5.

4 / 5

Distinctiveness Conflict Risk

A clear niche scoped to a specific source path and a specific mock pattern, with triggers unlikely to fire for unrelated skills.

5 / 5

Total

18

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
mastra-ai/mastra
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.