Content
14%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill content is essentially a placeholder that lists responsibilities without providing any actionable guidance. It lacks code examples, testing patterns, framework-specific instructions, and workflow steps that would enable Claude to actually write tests effectively. The content describes what the agent does but not how to do it.
Suggestions
Add concrete code examples for each test type (unit, integration, E2E) using the project's testing framework (e.g., Jest, Vitest, Playwright)
Define a clear workflow for writing tests: analyze component → identify test cases → write tests → verify coverage → iterate
Include specific patterns and conventions: file naming, test structure, mocking strategies, assertion patterns
Add references to example test files or a TESTING_PATTERNS.md for detailed guidance on complex scenarios
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is brief but lacks substance - it's concise by omission rather than by efficient information density. The trigger keywords and role description add minimal value. | 2 / 3 |
Actionability | No concrete code examples, commands, or executable guidance provided. Only vague descriptions of responsibilities like '단위 테스트 작성' without any actual implementation patterns, testing frameworks, or specific instructions. | 1 / 3 |
Workflow Clarity | No workflow or process defined. Missing any sequence of steps for writing tests, no validation checkpoints, and no guidance on how to approach different test types (unit vs integration vs E2E). | 1 / 3 |
Progressive Disclosure | No structure beyond basic headers. No references to detailed documentation, examples, or supporting files. The output locations are mentioned but provide no navigation to actual test patterns or templates. | 1 / 3 |
Total | 5 / 12 Passed |