CtrlK
BlogDocsLog inGet started
Tessl Logo

project-planner

Detects stale project plans and suggests session commands. Triggers on: sync plan, update plan, check status, plan is stale, track progress, project planning.

83

1.54x
Quality

77%

Does it follow best practices?

Impact

94%

1.54x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./data/skills-md/0xdarkmatter/claude-mods/project-planner/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

76%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 concise, well-structured awareness skill that gives concrete command suggestions and avoids concept padding. Its main weakness is workflow clarity: it functions as a detection map rather than a sequenced process with checkpoints, and the heuristics are not fully tied to executable next steps.

Suggestions

Add a short ordered workflow that sequences detection -> diagnosis -> suggested command, so the response path is explicit rather than implied by the table.

Map each staleness heuristic (>3 days, commits since modification, topic relevance) to the specific /save or /sync command that resolves it, closing the actionability gap.

Consider consolidating the four Detection Logic code blocks into the Quick Reference table to reduce repetition and tighten the structure.

DimensionReasoningScore

Conciseness

The body is lean and efficient, using terse code-block examples and a compact quick-reference table with no concept explanations Claude would already know; every token earns its place.

5 / 5

Actionability

Concrete commands are given throughout (/save, /sync --git, /sync --status, /save --archive) with example detection conditions, but the staleness heuristics stop short of mapping each heuristic to a specific executable command, leaving a minor gap.

4 / 5

Workflow Clarity

The skill presents detection situations and a quick-reference table rather than a sequenced multi-step process, and there are no validation checkpoints; the sequence of how to evaluate and respond is implicit rather than enumerated.

3 / 5

Progressive Disclosure

Content is well-organized into clearly labeled sections (Purpose, Detection Logic, Quick Reference, Staleness Heuristics, Notes) with no nested references, but the detection-logic section inlines several code blocks that could be consolidated, leaving minor organization gaps.

4 / 5

Total

16

/

20

Passed

Description

78%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 is well-formed: it states a clear purpose, uses third person, and includes an explicit trigger list with natural phrases. It is slightly weak on specificity and distinctiveness, where the action vocabulary is generic and a few trigger terms could overlap with other status-tracking skills.

DimensionReasoningScore

Specificity

"Detects stale project plans and suggests session commands" names the domain plus two concrete actions (detect, suggest), but does not enumerate the detection heuristics or specific commands, matching the anchor for 1-2 concrete actions without comprehensive coverage.

3 / 5

Completeness

It explicitly states what the skill does ("Detects stale project plans and suggests session commands") and provides explicit "when" guidance with concrete trigger phrases ("Triggers on: ..."), satisfying both requirements.

5 / 5

Trigger Term Quality

"Triggers on: sync plan, update plan, check status, plan is stale, track progress, project planning" provides good coverage of natural phrases users would say, though a few common synonyms are missing.

4 / 5

Distinctiveness Conflict Risk

The plan-awareness niche with /save and /sync commands is mostly distinct with clear triggers, though terms like "check status" and "track progress" carry minor overlap risk with general status/progress skills.

4 / 5

Total

16

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
NeverSight/skills_feed
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.