Focus on a specific task with context loading
56
38%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/product-design/skills/task-focus/SKILL.mdQuality
Discovery
0%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is critically weak across all dimensions. It provides no concrete actions, no natural trigger terms, no explicit usage guidance, and is so generic it could describe any skill. The description fails to help Claude distinguish when to select this skill from others.
Suggestions
Define specific concrete actions the skill performs (e.g., 'Loads project files, reads documentation, analyzes codebase structure').
Add a 'Use when...' clause with explicit trigger terms users would naturally say (e.g., 'Use when the user asks to focus on a feature, load context, or understand a specific part of the codebase').
Include domain-specific keywords and file types to make the skill distinctive (e.g., 'deep dive', 'investigate', 'analyze module', specific file extensions).
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague, abstract language ('specific task', 'context loading') without naming any concrete actions or domain. It does not describe what the skill actually does. | 1 / 3 |
Completeness | Fails to answer both 'what does this do' and 'when should Claude use it'. There is no 'Use when...' clause and the capabilities are completely undefined. | 1 / 3 |
Trigger Term Quality | Contains no natural keywords users would say. 'Focus', 'specific task', and 'context loading' are generic terms that don't match how users would phrase requests. | 1 / 3 |
Distinctiveness Conflict Risk | Extremely generic phrasing could apply to virtually any skill. 'Focus on a specific task' describes what all skills do, providing no distinguishing characteristics. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill with strong actionability and clear workflow sequencing. The execution instructions provide a clear step-by-step process with validation checkpoints, and the code examples are concrete and executable. Minor improvements could be made in conciseness by reducing redundancy and potentially splitting detailed format specifications into referenced files.
Suggestions
Remove the redundant example section or consolidate it with the execution instructions to reduce repetition
Consider moving the TodoTools format mapping and detailed output format to separate reference files for better progressive disclosure
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but includes some redundancy - the example section repeats information already covered, and some explanations could be tighter. The output format section is detailed but justified for clarity. | 2 / 3 |
Actionability | Provides concrete, executable guidance with specific code examples for status mapping, clear file format conversions, exact output format, and specific bash commands. The implementation tips add practical value. | 3 / 3 |
Workflow Clarity | Clear 8-step sequence in 'Execution Instructions' with explicit validation (check focus directory, parse task file, update header). Error handling section provides feedback loops for common failure cases. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but everything is inline in one file. For a skill of this length (~100 lines), some content like the TodoTools format mapping or detailed output format could be referenced externally. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
0ebe7ae
Table of Contents
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.