recipe-task
Execute tasks following appropriate rules with rule-advisor metacognition
39
25%
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 ./skills/recipe-task/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 extremely vague and abstract, providing no concrete actions, no natural trigger terms, and no guidance on when to use the skill. The phrase 'rule-advisor metacognition' is opaque jargon that would not help Claude select this skill appropriately. It would be nearly impossible to distinguish this from any other skill in a collection.
Suggestions
Replace abstract language with concrete actions: specify exactly what tasks this skill executes and what 'rules' it follows (e.g., 'Validates code changes against project-specific linting rules and style guidelines').
Add an explicit 'Use when...' clause with natural trigger terms that describe scenarios where this skill should be selected (e.g., 'Use when the user asks about rule compliance, policy checking, or guideline enforcement').
Define the specific domain or niche this skill operates in to make it distinguishable from other skills (e.g., is it about code review rules, business process rules, data validation rules?).
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses entirely abstract language ('execute tasks', 'appropriate rules', 'rule-advisor metacognition') with no concrete actions specified. There is no indication of what domain or specific capabilities this skill provides. | 1 / 3 |
Completeness | Both 'what' and 'when' are extremely weak. The description does not explain what the skill concretely does, nor does it provide any explicit trigger guidance or 'Use when...' clause. | 1 / 3 |
Trigger Term Quality | The terms used ('rule-advisor metacognition', 'appropriate rules') are technical jargon that no user would naturally say. There are no natural keywords that would help Claude match this skill to a user request. | 1 / 3 |
Distinctiveness Conflict Risk | 'Execute tasks following appropriate rules' is maximally generic and could apply to virtually any skill. There is nothing distinctive that would help Claude differentiate this from other skills. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a reasonable meta-workflow for task execution with rule-advisor integration, with clear step sequencing and specific tool references. However, it lacks executable examples, validation/error-handling checkpoints, and has some redundancy between the steps and the 'Important Notes' section. The references to rule-advisor JSON fields (taskAnalysis.essence, metaCognitiveGuidance, etc.) assume familiarity without providing schema documentation or examples of actual responses.
Suggestions
Add a concrete example of a rule-advisor invocation and its expected JSON response to make the workflow actionable and copy-paste ready.
Include explicit validation checkpoints—e.g., what to do if rule-advisor returns no selectedRules, or if TaskCreate fails—to add error recovery feedback loops.
Remove the 'Important Notes' section or merge its content into the steps, as it largely repeats what's already stated in Steps 1-4.
Link to or inline a brief schema reference for the rule-advisor JSON response fields (taskAnalysis, metaCognitiveGuidance, warningPatterns) so the skill is self-contained.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is moderately efficient but includes some redundancy—Step 2 sub-points largely restate what rule-advisor already provides, and the 'Important Notes' section repeats instructions already given in the steps. Some tightening is possible. | 2 / 3 |
Actionability | It provides a structured process with specific tool invocations (Agent tool with subagent_type, TaskCreate, TaskUpdate) and references to JSON response fields, but lacks executable code examples or concrete command syntax. The guidance is specific enough to follow but not copy-paste ready. | 2 / 3 |
Workflow Clarity | Steps are clearly sequenced (1-4) with a logical flow, but there are no explicit validation checkpoints or feedback loops for error recovery. The 'Verify skill fidelity' task is mentioned but not elaborated on, and there's no guidance on what to do if rule-advisor fails or returns unexpected output. | 2 / 3 |
Progressive Disclosure | The content is reasonably structured with clear sections and steps, but everything is inline in a single file with no references to external documentation. The rule-advisor's JSON schema fields are referenced but never linked to documentation explaining them. | 2 / 3 |
Total | 8 / 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 | |
- Repository
- shinpr/claude-code-workflows
- Commit
2e719be
- 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.