CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

health

Assess local PsychSift repository health quickly with offline checks and clear separation of code failures from environment or tooling blockers. Use for routine health checks, stale-state diagnosis, or a fast confidence snapshot.

Quality

82%

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

92%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 lean, fully sequenced six-step workflow with exact npm commands, an explicit failure-classification scheme, and a defined output contract. Minor gaps in executable detail ('relevant logs', 'active repo-owned processes') keep actionability just short of perfect, but token efficiency and structure are excellent for a skill of this size.

Suggestions

Name the specific log files or locations to inspect in step 1 and how to identify 'active repo-owned processes' (e.g. a ps/pgrep pattern) to close the actionability gap.

DimensionReasoningScore

Conciseness

Six lean steps with no concept explanations or padding; every line instructs and assumes Claude's competence ('Inspect branch, status, worktrees, runtime versions...').

5 / 5

Actionability

Exact commands ('npm run check:runtime', 'npm run check:skills', 'npm run verify:cheap'), an enumerated six-way failure taxonomy, and a defined output format make most steps executable; minor gaps remain in 'relevant logs' and 'active repo-owned processes', which specify neither locations nor identification method.

4 / 5

Workflow Clarity

A clear 1-6 sequence in which the named checks are explicit checkpoints, step 4 is the failure-handling path (classify into product code, test, tooling, resources, environment, or provider-gated), and step 6 defines the output contract with a guardrail in step 5.

5 / 5

Progressive Disclosure

At 13 lines with no external references needed, the flat numbered list under a single header is appropriately organized; per the simple-skill guidance, under-50-line skills with no reference needs can score 5 with well-organized sections.

5 / 5

Total

19

/

20

Passed

Description

62%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 clearly states what the skill does and includes an explicit 'Use for' trigger clause, but its trigger phrases lean on internal jargon ('stale-state diagnosis', 'fast confidence snapshot') rather than natural user language. Capability coverage is adequate but not comprehensive, while the PsychSift-specific framing keeps conflict risk low.

Suggestions

Add natural trigger synonyms users would actually say — e.g. 'repository status', 'sanity check', 'is the repo healthy' — alongside 'routine health checks'.

Enumerate one or two more concrete capabilities in the description (e.g. 'inspects runtime versions, worktrees, and repo-owned processes') to lift specificity beyond the current two.

DimensionReasoningScore

Specificity

Names the domain ('local PsychSift repository health') with two concrete capabilities ('offline checks', 'clear separation of code failures from environment or tooling blockers'), but coverage is not comprehensive — the checks themselves are not enumerated.

3 / 5

Completeness

Both 'what' ('Assess local PsychSift repository health quickly with offline checks and clear separation...') and 'when' ('Use for routine health checks, stale-state diagnosis, or a fast confidence snapshot') are explicitly present, but the when-clause could use more concrete natural trigger phrases.

4 / 5

Trigger Term Quality

'routine health checks' is a natural phrase, but 'stale-state diagnosis' and 'a fast confidence snapshot' are internal jargon users would rarely say; common variations like 'repo status' or 'sanity check' are missing.

3 / 5

Distinctiveness Conflict Risk

The repo-specific framing ('local PsychSift repository health') and offline-check focus carve a mostly distinct niche, with only minor overlap risk against a generic diagnostics or CI-status skill.

4 / 5

Total

14

/

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/health/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.