CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

drift

Detect PsychSift schema, migration, type, environment, and generated-artifact drift offline, while keeping live Supabase comparison approval-gated. Use when schema sources disagree or deployment drift is suspected.

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 lean, well-sequenced procedure with a good approval gate, but the executable core is thin: the static drift checks that define the skill are named without any command or method, and no validation/feedback loop closes the workflow. Adding the concrete check commands and a verify-after-manifest step would lift the two weaker dimensions.

Suggestions

In step 2, name the concrete static checks or commands to run (e.g., specific CLI invocations, file-diff commands, or scripts) so the skill's core detection is executable rather than directional.

Add an explicit verification step after step 4 (e.g., re-run the drift check to confirm the new manifest/test catches the mismatch) to close the feedback loop for this database-adjacent workflow.

Include a short example of the expected report format for step 6 so the final output (sources of truth, mismatch, remediation order, remaining live comparison) is unambiguous.

DimensionReasoningScore

Conciseness

Eight lean lines with zero concept explanations or padding; each step adds distinct instruction (e.g., 'Run static drift and consistency checks that do not contact a provider'). This matches anchor 5 — every token earns its place and the skill assumes Claude's competence.

5 / 5

Actionability

Specific artifacts are named (`supabase/schema.sql`, `npm run check:supabase-project`), but the core detection step 'Run static drift and consistency checks' names no command, script, or method, and steps 1, 3, and 6 are direction rather than executable specifics. This matches anchor 3 ('some concrete guidance but incomplete'), not 4, since the only literal command appears in the ask-before gate rather than the workflow itself.

3 / 5

Workflow Clarity

A clear 6-step sequence with an explicit approval checkpoint ('Ask before `npm run check:supabase-project`, live schema inspection, CLI linking, pulling, or diffing') and a closing report step — anchor 4 ('clear sequence with most checkpoints present; minor validation gaps'). Not 5 because there is no feedback loop: nothing instructs re-running checks or verifying after step 4 adds a manifest or test, which matters for database-operation skills.

4 / 5

Progressive Disclosure

The skill is under 50 lines, single-purpose, has no bundle files, and inlines nothing that belongs in a separate file; the single well-organized numbered list qualifies for 5 under the rubric's simple-skill guidance.

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: third-person, concise, explicit 'Use when' triggers, and a highly specific niche that minimizes conflict risk. The only gap is that action coverage centers on a single detect verb and omits what happens after drift is found.

DimensionReasoningScore

Specificity

The description enumerates precise drift categories ('schema, migration, type, environment, and generated-artifact drift'), the offline constraint, and the approval-gated live comparison, giving concrete targets. It falls between anchor 3 (1-2 concrete actions) and anchor 4 (several specific actions) — the enumerated targets are precise, but 'detect' is the only main verb and post-detection behavior is unstated.

4 / 5

Completeness

It explicitly answers both what ('Detect ... drift offline, while keeping live Supabase comparison approval-gated') and when ('Use when schema sources disagree or deployment drift is suspected') with concrete trigger phrases, matching anchor 5. The 'when' clause is already specific, so anchor 4's 'could be more explicit' does not apply.

5 / 5

Trigger Term Quality

Natural trigger phrases are present ('schema sources disagree', 'deployment drift is suspected', 'Supabase', 'migration'), matching anchor 4's 'good keyword coverage; a few natural terms missing'. Not 5 because common synonyms like 'out of sync' or 'stale types' are absent.

4 / 5

Distinctiveness Conflict Risk

Anchored to a named project (PsychSift) and a specific backend (Supabase) with niche-specific triggers, giving a clear niche with minimal conflict risk — anchor 5. It would not plausibly fire for unrelated 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/drift/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.