CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

project-management

Load to plan a cycle, audit issues, build a roadmap, or decompose research into issues.

Quality

68%

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 ./.agents/skills/project-management/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%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 dense, information-rich entry point with a genuinely well-designed 'Read when' navigation layer and concrete command grammar, but it is undermined by broken references (all 8 workflow files and templates absent from the bundle), duplicated project-map data inlined alongside its own reference file, and Intake prose so convoluted it reads more like policy data than executable guidance.

Suggestions

Include the workflows/*.md and templates/*.md files in the bundle (or remove/repair the links) — every command in the Commands table currently dead-ends, which caps actionability, workflow clarity, and navigation.

Move the inlined project-map and label-taxonomy JSON into references/project-map.md and references/labels.md (which already exist for exactly this content) and keep only the routing summary in SKILL.md.

Rewrite the Intake section as a short checklist of filing conditions instead of nested cross-referencing prose (e.g., the paragraph spanning § 6 and § 7.2 of audit-issues), so the rule can be applied without re-reading.

DimensionReasoningScore

Conciseness

The body never explains concepts Claude already knows and every line carries project-specific policy, but it could be tightened: the Intake section is tangled, convoluted prose, and the ~20-line project-map JSON duplicates content that already lives in references/project-map.md ("the project-management skill's references/project-map.md states what each kind holds"). Not 2 because there is no padded over-explanation, only density and duplication.

3 / 5

Actionability

The Commands table gives concrete invocations with argument grammars, and Execution Rules are specific ("Fill each [PLACEHOLDER]", "Remove the lines whose placeholders are empty", "A failed Linear read halts the workflow"), but the actual operating instructions for all 8 commands live in workflows/*.md files that are absent from the bundle, leaving key execution details unreachable. Not 4 because those missing workflow files are the core of executing this skill, not a minor gap.

3 / 5

Workflow Clarity

Sequencing rules are stated ("Run the sections of a workflow in order", "Skip a section only on its explicit Skip if condition") and one checkpoint exists ("A failed Linear read halts the workflow with its diagnostic, never a partial result"), but the actual step sequences and validation checkpoints are delegated to workflow files not present in the bundle, so they cannot be verified and are effectively implicit. The audit-issues workflow performs batch tracker writes, where the rubric expects explicit feedback loops in reach.

3 / 5

Progressive Disclosure

The 'Read when' section signals each reference file with clear conditions and the Commands table maps commands to workflow files — good navigation design — but all 8 workflows/*.md links and the templates/ links point to files missing from the bundle, and the taxonomy and project-map JSON blocks are inlined when they belong in the existing reference files. The broken references and inline duplication match the 'could be better organized' anchor rather than 'minor organization gaps'.

3 / 5

Total

12

/

20

Passed

Description

75%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 concise, third-person description that names four concrete, distinct capabilities and includes an explicit 'Load to...' trigger clause. It sits solidly at the 'good' level: specific and distinguishable, with minor gaps in command coverage and natural-term synonyms keeping it from the top anchor.

DimensionReasoningScore

Specificity

Names the domain (tracker/project planning) and four concrete actions — "plan a cycle, audit issues, build a roadmap, or decompose research into issues" — matching the 'several specific actions' anchor. Not 5 because coverage has minor gaps: commands like proposal-sweep, roadmap create, and research-spike/complete are absent; not 3 because it goes well beyond 1-2 actions.

4 / 5

Completeness

The 'what' is clear (the four actions) and "Load to..." acts as an explicit trigger clause equivalent to 'Use when', so it clears the cap at 3. Not 5 because the 'when' is merged into the purpose clause rather than stated as concrete trigger phrases (e.g., 'Use when the user asks to plan a cycle or audit a project').

4 / 5

Trigger Term Quality

Good natural keyword coverage — "plan", "audit issues", "build a roadmap", "research" are phrases a user would plausibly say. Not 5 because synonyms like "project", "tracker", "backlog", or "sprint" are missing and "decompose research" is less natural than "break down research"; not 3 since the terms present go beyond 'some relevant keywords'.

4 / 5

Distinctiveness Conflict Risk

The combination of cycle planning, issue auditing, roadmap building, and research decomposition carves a mostly distinct tracker-operations niche with minor overlap risk against generic project-management or issue-filing skills. Not 5 because 'plan a cycle' is tool-specific jargon that a generic planning skill could also claim.

4 / 5

Total

16

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

relative_links

Relative link issues: 8 possibly missing (workflows/audit-issues.md, workflows/cycle-plan.md, workflows/proposal-sweep.md, workflows/research-complete.md, workflows/research-issue.md, +3 more)

Warning

Total

14

/

16

Passed

Repository

vanillagreencom/kendex

Path

.agents/skills/project-management/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.