CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

test

Choose and run the smallest relevant local PsychSift test, reproduce failures deterministically, and widen verification only when needed. Use for test requests, behavioral proofs, or focused regression coverage.

Quality

84%

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

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.

An exemplary concise, policy-dense skill body: lean steps, explicit concurrency rules, a fix-rerun feedback loop, and honest reporting requirements. The only gap is that the preferred single-test invocation is described but never shown as a concrete command.

DimensionReasoningScore

Conciseness

Six lean numbered steps with zero padding and no explanation of concepts Claude already knows — every line adds policy or a command, matching the "every token earns its place" anchor.

5 / 5

Actionability

One fully concrete command is given ("npm run test:focused -- --files <paths>") plus specific tool names (Vitest, Playwright, typecheck), but the preferred single-target command is never shown and "Add the smallest deterministic regression proof" has no example, leaving minor execution gaps.

4 / 5

Workflow Clarity

A clear 1–6 sequence with an explicit feedback loop ("rerun the smallest failing check after each fix") and exit-code reporting, though step 4 ("Let the repository coordinator admit up to two focused Vitest/read-only typecheck leases") reads as concurrency policy rather than an executable step, and the primary single-target test invocation is left implicit.

4 / 5

Progressive Disclosure

The skill is well under 50 lines, single-purpose, needs no external references (none exist in the bundle), and is organized as a clean numbered list — meeting the simple-skill exception for a top structure score.

5 / 5

Total

18

/

20

Passed

Description

76%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 description with a concrete, multi-action "what" and an explicit "Use for..." trigger clause. Its main weakness is trigger phrasing that leans on project-internal jargon ("behavioral proofs") instead of the natural terms a user would actually say.

Suggestions

Replace or supplement jargon triggers with natural user phrasings, e.g. "Use when the user asks to run tests, write or verify a regression test, or prove a behavior works".

Add a common synonym or two for discoverability, such as "regression test" or "test suite", so the skill triggers on the phrasings users actually type.

DimensionReasoningScore

Specificity

The description names the domain (local PsychSift tests) and lists several specific actions — "Choose and run the smallest relevant local PsychSift test, reproduce failures deterministically, and widen verification only when needed" — with only minor coverage gaps (e.g., reporting and regression-test authoring are only implied via "focused regression coverage").

4 / 5

Completeness

It clearly answers both questions: the "what" is concrete (choose/run the smallest relevant test, reproduce failures deterministically, widen verification) and the "when" is an explicit trigger clause — "Use for test requests, behavioral proofs, or focused regression coverage" — so it is not the level 4 case where the "when" is only weakly specified.

5 / 5

Trigger Term Quality

"Use for test requests" is a natural user phrase, but "behavioral proofs" and "focused regression coverage" are internal jargon rather than phrases users would naturally say, and common variations like "run the tests", "write a test", or "regression test" are missing.

3 / 5

Distinctiveness Conflict Risk

The PsychSift-specific scope gives it a clear niche with minimal conflict risk, but the broad trigger "test requests" could still overlap with a generic run-the-tests request in another skill, keeping it just below the fully distinct anchor.

4 / 5

Total

16

/

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

BigSimmo/PsychSift

Path

.agents/skills/test/SKILL.md

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.