CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

87

1.76x
Quality

93%

Does it follow best practices?

Impact

88%

1.76x

Average score across 2 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

86%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 strong, actionable testing guide with executable examples, a clear test-level decision table, and a verification section with checkpoints. It is well-structured with appropriate progressive disclosure into two real reference files; the only mild weakness is a few explanatory sentences that could be tighter.

DimensionReasoningScore

Conciseness

Largely lean and assumes Claude's competence with minimal over-explanation of basic concepts, though a few explanatory sentences (e.g. motivating why vi.mock causes OOM) could be trimmed further.

4 / 5

Actionability

Provides copy-paste-ready TypeScript examples with explicit good/bad contrasts and concrete verification commands (npm test, npx tsc --noEmit, npm run lint -- --quiet), covering the common cases.

5 / 5

Workflow Clarity

The 'After Writing Tests' section gives a clear 5-step sequence with explicit validation checkpoints, but the body is guidance across many test types rather than one fragile pipeline, so the explicit error-recovery feedback loop is present only at the end.

4 / 5

Progressive Disclosure

SKILL.md is a well-organized overview that signals one-level-deep references to real bundle files (frontend-patterns.md, api-patterns.md) via 'Read @references/...', splitting detail appropriately with easy navigation.

5 / 5

Total

18

/

20

Passed

Description

100%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 is exemplary: it states concrete capabilities, enumerates natural trigger terms, answers both what and when explicitly, and is tightly scoped to a single repo to avoid conflicts. Voice is imperative/infinitive rather than first/second person, so no specificity penalty applies.

DimensionReasoningScore

Specificity

Lists multiple concrete actions (write, fix, review, refactor) and enumerates test types (unit, functional, integration, E2E) across named frontend and backend targets, giving comprehensive coverage.

5 / 5

Completeness

Explicitly answers both 'what' (write tests for the console monorepo following team patterns) and 'when' (Use this skill whenever... Also trigger when...), with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural phrases users would actually say ('write tests', 'add tests', 'fix tests', 'test this', 'spec file') plus synonyms, with a 'when in doubt, USE IT' nudge.

5 / 5

Distinctiveness Conflict Risk

Scoped tightly to the akash-network/console monorepo with app-specific targets, giving a clear niche with minimal overlap risk against generic testing skills.

5 / 5

Total

20

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
akash-network/console
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.