CtrlK
BlogDocsLog inGet started
Tessl Logo

task-analyzer

Selects the smallest set of task-execution skills and metacognitive safeguards for standalone task and diagnosis workflows.

56

Quality

64%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/task-analyzer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 well-organized, instruction-only workflow with a concrete decision table, priority order, output schema, and completion checklist, supported by a single clearly signaled one-level reference.

DimensionReasoningScore

Conciseness

The ~70-line body is efficient with tables, a priority list, and a YAML template, assuming Claude's competence; minor redundancy in the boundary-setting lines (e.g. 'Documentation routing and workflow Structural Scale belong to documentation-criteria, not this skill' restated in the Process section) keeps it just below the lean 5.

4 / 5

Actionability

Concrete guidance is provided via the task-evidence mapping table, a three-priority selection order, and a full output YAML schema; as an instruction-only skill this is actionable, with only minor gaps (e.g. how to extract 'task-evidence tags' is left implicit) versus the fully copy-paste-ready 5.

4 / 5

Workflow Clarity

A clear three-step sequence (Identify Essence → Match Skills → Generate Guidance) is followed by an Output template and a Completion Check that functions as a validation checklist; not a destructive/batch operation so no cap applies, but the checkpoints are confirmable rather than explicit feedback loops, sitting below 5.

4 / 5

Progressive Disclosure

The single reference [skills-index.yaml](references/skills-index.yaml) is one level deep and clearly signaled, with the catalog correctly externalized and the process kept inline; good structure and easy navigation, just shy of the multi-reference clarity of a 5.

4 / 5

Total

16

/

20

Passed

Description

53%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 clearly states the skill's purpose in third person but lacks an explicit 'Use when...' trigger clause and leans on jargon over natural user phrases, capping completeness and trigger quality at 3.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers, e.g. 'Use when starting a standalone task or diagnosing a problem before executing or selecting other skills.'

Soften jargon like 'metacognitive safeguards' with natural synonyms a user might say (e.g. 'self-checks', 'review safeguards') to improve trigger-term coverage.

Optionally add a second concrete action or artifact type to lift specificity toward 4.

DimensionReasoningScore

Specificity

Quotes 'Selects the smallest set of task-execution skills and metacognitive safeguards' — names the domain and a concrete action, but stays abstract with no concrete artifacts or file types, matching the 'names domain and 1-2 concrete actions' anchor rather than the multi-action coverage of 4.

3 / 5

Completeness

The 'what' is clear ('Selects the smallest set...') but 'when' is only weakly implied by 'for standalone task and diagnosis workflows' with no explicit 'Use when...' clause, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Terms like 'task-execution skills', 'metacognitive safeguards', and 'diagnosis workflows' are relevant but jargon-heavy; common natural variations a user would actually say are missing, fitting the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

Skill-selection/metacognitive niche for 'standalone task and diagnosis workflows' is mostly distinct with only minor overlap risk against other orchestration skills, matching the 'mostly distinct; minor overlap risk' anchor rather than the clear-niche 5.

4 / 5

Total

13

/

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
shinpr/claude-code-workflows
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.