CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

newtask

Prepare an isolated current task checkout using the current host's supported workflow. Check ownership and the base, restore dependencies only when needed, and start the app only for a task that needs it.

Quality

66%

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

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/newtask/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

60%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 content is a well-structured, safety-conscious workflow with concrete commands for dependency restoration, base-freshness checks, and app startup, and it appropriately quarantines dated historical measurements in a labeled section. Its main weaknesses are prose-only guidance for the core branch/worktree/ownership steps and hedging that could be tightened for token efficiency.

Suggestions

Add the concrete commands for the core steps: the git branch/worktree creation sequence, the ownership check, and the disk-capacity check, so the central workflow is executable rather than directional.

Tighten the repeated authority-boundary caveats (the PR-read, fetch, and cleanup authority rules each appear multiple times) into a single consolidated statement.

Move the 'Historical Windows example' section into a references/ file (e.g. references/historical-environments.md) and keep only the one-line lesson in SKILL.md.

DimensionReasoningScore

Conciseness

The body is dense and mostly earns its tokens, but hedging-heavy sentences ('A same-task continuation keeps its established checkout and checkpoint; it does not start over merely because owned changes exist') and authority caveats restated multiple ways could be tightened, matching the mostly-efficient-but-could-be-tightened anchor rather than the efficient 4.

3 / 5

Actionability

Concrete commands exist (BASE_FRESHNESS_NO_FETCH=1 node scripts/check-base-freshness.mjs, node scripts/setup-codex-worktree.mjs, npm run ensure), but the central steps — creating the task branch/worktree, checking ownership, and checking disk capacity — get directional prose with no executable command, matching the some-concrete-guidance-but-incomplete anchor.

3 / 5

Workflow Clarity

The numbered 1-6 sequence is clear with most checkpoints present: base-freshness validation with a drift-handling branch, 'verify project identity before browser work', a no-app guard for documentation-only tasks, and destructive operations gated on verified ownership. It falls short of 5 because there is no explicit validate-fix-retry feedback loop.

4 / 5

Progressive Disclosure

Sections are well-organized with clearly signaled, one-level-deep references to host docs and scripts (docs/agents/codex-cloud-environment.md, docs/agents/codex-desktop-worktree-setup.md), but the Historical Windows example is inline content that would fit better in a separate reference file, and the body runs past the ~50-line threshold where structure alone earns a 5.

4 / 5

Total

14

/

20

Passed

Description

58%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 communicates a clear set of concrete, conditionally-scoped capabilities in third person, but it entirely lacks a 'when to use this' trigger clause and the natural keyword coverage users would employ. It reads as a policy summary for an insider rather than a discoverability-oriented skill description.

Suggestions

Add an explicit 'Use when...' clause (e.g. 'Use when starting a new task, setting up a worktree, or resuming an owned task checkout') to lift completeness above the cap of 3.

Include natural user phrasings and synonyms such as 'new task', 'worktree', 'branch setup', and 'resume task' so trigger_term_quality covers the vocabulary users actually say.

Mention the branch/worktree creation step in the description to close the coverage gap that keeps specificity at 4.

DimensionReasoningScore

Specificity

Lists several concrete, conditionally-scoped actions ('Prepare an isolated current task checkout', 'Check ownership and the base', 'restore dependencies only when needed', 'start the app only for a task that needs it'), matching the several-specific-actions anchor with minor gaps rather than the comprehensive coverage of a 5.

4 / 5

Completeness

The 'what' is clear (prepare checkout, check ownership/base, restore deps, start app), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines; 'only for a task that needs it' is a constraint, not a trigger.

3 / 5

Trigger Term Quality

Relevant keywords like 'task checkout', 'restore dependencies', and 'start the app' are present, but the natural phrases a user would say ('new task', 'set up a worktree', 'create a branch') are missing, matching the some-keywords-but-missing-variations anchor rather than the good-coverage anchor.

3 / 5

Distinctiveness Conflict Risk

The task-checkout-preparation niche with ownership and base checks is mostly distinct with only minor overlap risk against closely related worktree/branch-setup skills, fitting the 'mostly distinct' anchor rather than the minimal-conflict 5 because the trigger vocabulary is thin.

4 / 5

Total

14

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 2 possibly missing (scripts/check-base-freshness.mjs, scripts/setup-codex-worktree.mjs)

Warning

Total

15

/

16

Passed

Repository

BigSimmo/PsychSift

Path

.claude/skills/newtask/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.