console-tests
Write tests for the akash-network/console monorepo following established team patterns and reviewer expectations. Use this skill whenever you need to write, fix, review, or refactor tests in the console project — including unit tests, functional tests, integration tests, or E2E tests for both frontend (deploy-web) and backend (api, notifications, indexer, provider-proxy). Also trigger when the user mentions 'write tests', 'add tests', 'fix tests', 'test this', 'spec file', or asks about testing patterns in the console codebase. When in doubt about whether to use this skill for a testing task in this repo, USE IT.
90
86%
Does it follow best practices?
Impact
98%
1.81xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
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.
This is a strong skill description that clearly defines its scope (testing in the akash-network/console monorepo), lists concrete actions and test types, and provides explicit trigger guidance with natural user phrases. It covers both frontend and backend packages by name, making it highly distinctive and easy for Claude to select appropriately. The description is thorough without being padded with fluff.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: write, fix, review, refactor tests. Specifies test types (unit, functional, integration, E2E) and names specific packages (deploy-web, api, notifications, indexer, provider-proxy). | 3 / 3 |
Completeness | Clearly answers both 'what' (write tests following team patterns for the console monorepo across multiple packages and test types) and 'when' (explicit 'Use this skill whenever...' clause with detailed trigger scenarios and quoted trigger phrases). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'write tests', 'add tests', 'fix tests', 'test this', 'spec file', 'testing patterns'. Also includes domain-specific terms like package names and test type categories. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — scoped to a specific repository (akash-network/console), specific task domain (testing), and names concrete sub-projects. Very unlikely to conflict with other skills due to the narrow repo + testing combination. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, well-structured testing guide that provides highly actionable, concrete patterns with real code examples specific to the console monorepo. Its main weakness is some verbosity in explanatory sections that Claude doesn't need (e.g., explaining what unit vs integration tests are) and the lack of explicit validation/verification steps in the workflow. The progressive disclosure to reference files is well-executed.
Suggestions
Trim the 'Deciding What Type of Test to Write' section to remove explanations of what each test type is (Claude knows) and focus only on the project-specific decision criteria and constraints.
Add a brief validation checklist or feedback loop — e.g., 'Run vitest on your new spec, verify all tests pass, check coverage for the file under test' — to strengthen workflow clarity.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient and avoids explaining basic concepts, but some sections are verbose — e.g., the preamble about reading source files, the explanation of what each test level is for (Claude knows what unit/integration/E2E tests are), and some of the 'Bad' examples could be trimmed. The mocking section with the 'Good vs Bad' comparison is useful but slightly wordy. | 2 / 3 |
Actionability | The skill provides fully executable, copy-paste-ready code examples throughout — the setup function pattern, mocking patterns, assertion patterns, AAA structure, and test description conventions are all concrete and specific. Every rule is illustrated with real TypeScript code. | 3 / 3 |
Workflow Clarity | The skill clearly sequences the decision of which test type to write and provides good structural patterns, but lacks explicit validation checkpoints or feedback loops. For example, there's no 'run tests and verify' step, no guidance on what to do when tests fail, and no checklist for reviewing test quality before committing. | 2 / 3 |
Progressive Disclosure | The skill uses clear one-level-deep references to separate files (@references/frontend-patterns.md, @references/api-patterns.md) with well-signaled key points summarized inline. The main file serves as an effective overview without becoming monolithic, and the references are clearly labeled by topic. | 3 / 3 |
Total | 10 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- akash-network/console
- Commit
609b56d
- 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.