CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

task

Manage PsychSift task lifecycle transitions safely, including start, status, handoff, landed proof, and cleanup planning. Use when beginning work, checking task state, preparing handoff, proving integration, or closing a session.

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Medium

Suggest reviewing before use

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 exceptionally lean, imperative body whose central command is executable as written, with clear sequencing and safety gates for risky git operations. The main weakness is the unnamed "required task-start script" in step 1, which is not directly executable.

DimensionReasoningScore

Conciseness

The 6-step body is lean with zero padding — no concept explanations, no filler, every line directs behavior. It assumes Claude's competence (e.g., "Inspect branch, upstream, worktrees, status" without re-explaining git), matching the level 5 anchor exactly.

5 / 5

Actionability

Step 2 is a fully copy-paste-ready command ("npm run workflow:lifecycle -- --phase <status|start|handoff|landed|cleanup> --write-evidence") and steps 4–6 are concrete directives. It falls short of 5 because step 1's "required task-start script" is never named or given a path, and step 3 lists what to inspect without the commands to do so — minor but real executable gaps.

4 / 5

Workflow Clarity

A clearly sequenced 6-step process with most checkpoints present: inspection of branch/upstream/worktrees/markers (step 3), approval gates on risky operations (step 5), and an explicit report of the proved transition (step 6). It is not a 5 because there is no error-recovery feedback loop (what to do when inspection reveals a problem), only implicit checkpoints.

4 / 5

Progressive Disclosure

The skill is under 50 lines with no bundle files (references/, scripts/, assets/ are absent) and no content that warrants external files, so per the simple-skill guideline a well-organized single body scores 5. The single header with a flat numbered list is clean and fully navigable.

5 / 5

Total

18

/

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 in third-person voice that clearly states what the skill does and gives an explicit, multi-trigger "Use when" clause. Minor room for improvement in concrete action verbs and synonym coverage in the trigger terms.

DimensionReasoningScore

Specificity

"Manage PsychSift task lifecycle transitions safely, including start, status, handoff, landed proof, and cleanup planning" names the domain and enumerates several specific lifecycle phases, giving mostly concrete coverage. It stops short of a 5 because the actions are phase names rather than multiple concrete operations (the only verb is the generic "manage").

4 / 5

Completeness

It explicitly answers both parts: the "what" is managing task lifecycle transitions across the enumerated phases, and the "when" is a full "Use when..." clause with concrete trigger phrases (beginning work, checking task state, preparing handoff, proving integration, closing a session). This matches the level 5 anchor clearly.

5 / 5

Trigger Term Quality

"Use when beginning work, checking task state, preparing handoff, proving integration, or closing a session" covers natural phrases a user would plausibly say. It misses common synonyms and variations of these triggers, keeping it below the comprehensive level 5 anchor.

4 / 5

Distinctiveness Conflict Risk

"PsychSift task lifecycle" carves out a clear project-specific niche with distinct triggers (handoff, landed proof, cleanup), so the risk of triggering for an unrelated skill is minimal. It clearly fits the level 5 anchor and not the level 4 anchor, which requires minor overlap risk.

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