CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

fix

Diagnose and repair a local PsychSift verification failure using the smallest reproducer and safest scoped change. Use when lint, typecheck, tests, builds, browser checks, or offline evaluations fail or hang.

Quality

86%

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

78%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 extremely token-efficient, well-sequenced repair workflow with a genuine validate-and-widen feedback loop, appropriate in scale for a simple single-purpose skill. Its main weakness is actionability: beyond the single triage command, steps like classification and minimal reproduction are stated as goals rather than executable guidance.

Suggestions

Add a concrete example of a 'narrowest deterministic check' (e.g., a sample command re-running the single failing test or lint rule) so step 4 is executable rather than directional.

Specify what 'widen proportionally' means operationally, e.g., 'rerun the affected suite, then the full verification command from step 1, and stop when it passes'.

Give one-line decision criteria or an example for the six-way classification in step 3 (e.g., 'test: expectation stale vs code: behavior wrong') so the classification is actionable.

DimensionReasoningScore

Conciseness

Six lean lines with zero padding or explanation of concepts Claude already knows; every step earns its place. This matches the 5 anchor ("assumes Claude's competence") with no over-explanation to trim.

5 / 5

Actionability

Step 2 provides one executable command ("npm run workflow:triage -- --log <path> --write-evidence"), but the remaining steps are directional without specifics — "Classify the cause as code, test, tooling, resource, race, or provider/configuration" and "Reproduce with the narrowest deterministic check" give no commands, criteria, or examples for how to execute them. This fits the 3 anchor (some concrete guidance but incomplete, missing key details) rather than 4, where most guidance would be executable.

3 / 5

Workflow Clarity

A clear 6-step sequence with a real validation loop in step 5 ("Make the smallest safe fix, rerun that check, then widen proportionally") and pre-edit reproduction in step 4. Not 5 because there is no explicit final checkpoint that the originally failing command now passes, and "widen proportionally" leaves the terminal state implicit; not 3 because checkpoints are present rather than missing.

4 / 5

Progressive Disclosure

The skill is under 50 lines, single-purpose, with no bundle files and no content that warrants external references; the clean numbered list is well-organized. Per the rubric's simple-skill guideline, this merits 5.

5 / 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 description that clearly states both capability and explicit trigger conditions in third person, scoped tightly to PsychSift verification failures. Keyword coverage is good though not exhaustive of common synonyms.

DimensionReasoningScore

Specificity

"Diagnose and repair a local PsychSift verification failure using the smallest reproducer and safest scoped change" names several concrete actions (diagnose, repair, minimize reproducer, scope the change) with only minor gaps in coverage — it does not enumerate what repair covers (e.g., code vs config vs test fixes). It falls short of the 5 anchor's comprehensive multi-action list.

4 / 5

Completeness

Explicitly answers both: what ("Diagnose and repair a local PsychSift verification failure using the smallest reproducer and safest scoped change") and when ("Use when lint, typecheck, tests, builds, browser checks, or offline evaluations fail or hang") with concrete trigger phrases, matching the 5 anchor's structure.

5 / 5

Trigger Term Quality

"lint, typecheck, tests, builds, browser checks, or offline evaluations fail or hang" gives good natural keyword coverage of what users actually say, but misses common variations like "CI", "flaky tests", "debug", or "verification". Not at the 5 anchor's synonym-and-extension-level comprehensiveness.

4 / 5

Distinctiveness Conflict Risk

"local PsychSift verification failure" carves out a clear niche with distinct, failure-scoped triggers, so conflict risk with generic code-review or debugging skills is minimal. It clearly fits the 5 anchor rather than the 4 anchor's "minor overlap risk with closely related 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

BigSimmo/PsychSift

Path

.agents/skills/fix/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.