CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

plan

Plan safe risk-scoped PsychSift work by inspecting the current change, selecting the smallest local verification ladder, and separating provider-backed checks into explicit approval gates. Use before non-trivial changes or when asked what checks are needed.

Quality

81%

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 short instruction-only skill: concise, project-specific, and actionable, with a clear sequenced workflow and no structural bloat. The only meaningful gap is that the named verification gates (test:focused, verify:cheap) lack invocation commands, and there is no explicit recovery step when verification fails.

DimensionReasoningScore

Conciseness

Six lean numbered lines with no padding and no explanations of concepts Claude already knows; every instruction adds project-specific value ("Supabase migrations, diff integrity, secrets, and auth/privacy rules"). This matches the 'lean and efficient; every token earns its place' anchor exactly.

5 / 5

Actionability

Concrete, specific guidance throughout: named verification gates ("`test:focused` or `verify:cheap`") and enumerated categories for both safety gates and approval gates. Falls short of fully executable because the gates are named but never shown how to invoke (no commands or script paths), matching the 'concrete code or commands with minor gaps' anchor.

4 / 5

Workflow Clarity

A clear, well-ordered six-step sequence where validation is inherent to the workflow (step 2 selects the verification gate; step 6 reports verification results). It sits at the 'clear sequence with most checkpoints present' anchor rather than 5 because there is no explicit feedback loop for what to do when verification fails, and no checklist for edge cases.

4 / 5

Progressive Disclosure

The skill is under 50 lines with no need for external references, and the single numbered list is well-organized and self-contained. Per the rubric's simple-skill guidance, this earns the top progressive-disclosure score; there are no buried or nested references to penalize.

5 / 5

Total

18

/

20

Passed

Description

67%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 solid description with three concrete named actions, an explicit trigger clause, and a distinct project-scoped niche. Its main weakness is trigger-term quality: jargon-heavy phrases like "verification ladder" and "provider-backed checks" crowd out the natural language users would actually say, and the "non-trivial changes" trigger is imprecise.

Suggestions

Add natural trigger phrases users would actually say, e.g. "Use when planning changes to PsychSift, deciding what tests to run, or before touching Supabase or provider APIs", to complement the jargon terms.

Replace or gloss domain jargon such as "verification ladder" and "provider-backed checks" with plain-language equivalents (e.g. "cheapest local test that catches the change") so the description reads naturally to users.

Make the 'when' clause more concrete by defining what counts as non-trivial (e.g. "changes spanning more than one file, any migration, or anything touching auth or secrets").

DimensionReasoningScore

Specificity

Lists several concrete actions — "inspecting the current change", "selecting the smallest local verification ladder", "separating provider-backed checks into explicit approval gates" — which matches the anchor for several specific actions with minor gaps. Not a 5 because coverage is incomplete: terms like "safe risk-scoped" are asserted but their concrete meaning is never enumerated.

4 / 5

Completeness

Both what ("Plan safe risk-scoped PsychSift work by inspecting... selecting... separating...") and when ("Use before non-trivial changes or when asked what checks are needed") are present and explicit. Falls short of a 5 because the trigger "non-trivial changes" is imprecise and lacks concrete trigger phrases, matching the anchor where 'when' could be more explicit or specific.

4 / 5

Trigger Term Quality

The trigger clause "Use before non-trivial changes or when asked what checks are needed" provides some relevant natural phrases ("what checks are needed"), but domain jargon like "verification ladder" and "provider-backed checks" is not language users would naturally say, and common variations are missing. This matches the anchor for some relevant keywords missing common variations rather than the good-coverage anchor above it.

3 / 5

Distinctiveness Conflict Risk

The project-specific name "PsychSift" establishes a clear niche with minimal conflict risk against unrelated skills. However, the broad trigger "Use before non-trivial changes" could fire on generic planning requests in any project, creating minor overlap with a generic planning skill — matching the 'mostly distinct; minor overlap risk' anchor rather than the minimal-conflict anchor.

4 / 5

Total

15

/

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