sprint-planning-helper
Sprint Planning Helper - Auto-activating skill for Enterprise Workflows. Triggers on: sprint planning helper, sprint planning helper Part of the Enterprise Workflows skill category.
33
0%
Does it follow best practices?
Impact
97%
1.01xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/20-enterprise-workflows/sprint-planning-helper/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 essentially a placeholder with no substantive content. It repeats the skill name as its only trigger term, provides no concrete actions or capabilities, and lacks any explicit guidance on when Claude should select it. It would be indistinguishable from any other enterprise or project management skill.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates sprint backlogs, estimates story points, distributes work across team members, and generates sprint capacity plans.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user mentions sprint planning, backlog grooming, story point estimation, velocity tracking, scrum ceremonies, or iteration planning.'
Include diverse natural keywords users would actually say, such as 'sprint', 'backlog', 'scrum', 'story points', 'velocity', 'capacity planning', and 'iteration' to improve trigger term coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. It only names itself ('Sprint Planning Helper') and mentions a category ('Enterprise Workflows') without describing what it actually does—no verbs like 'creates sprint plans', 'estimates story points', 'assigns tasks', etc. | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is meaningfully answered. There is no 'Use when...' clause, and the 'what' is entirely absent beyond the skill name. The description fails both halves of the completeness requirement. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are the skill's own name repeated twice ('sprint planning helper'). There are no natural user keywords like 'sprint', 'backlog', 'story points', 'velocity', 'scrum', 'iteration planning', or other terms a user would naturally say. | 1 / 3 |
Distinctiveness Conflict Risk | The description is so vague that it could overlap with any project management, agile, or workflow-related skill. 'Enterprise Workflows' is extremely generic and provides no clear niche or distinct triggers to differentiate it. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty placeholder that provides absolutely no actionable content. It consists entirely of generic boilerplate text that repeats the skill name without ever defining what sprint planning help actually entails, what steps to follow, what tools to use, or what outputs to produce. It fails on every dimension of the rubric.
Suggestions
Define what sprint planning actually involves in this context—add concrete steps like backlog grooming, capacity calculation, story point estimation, and sprint goal definition with specific examples or templates.
Add executable examples such as a sprint planning template, a capacity calculation formula, or a sample sprint board configuration that Claude can directly use.
Include a clear multi-step workflow (e.g., 1. Review backlog → 2. Estimate capacity → 3. Select stories → 4. Validate sprint scope → 5. Document sprint goal) with validation checkpoints.
Remove all generic filler text ('This skill provides automated assistance for...') and replace with actual domain-specific instructions and constraints.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It repeats 'sprint planning helper' over a dozen times without providing any actual information Claude doesn't already know. Every section restates the same vague concept with no substance. | 1 / 3 |
Actionability | There are zero concrete steps, commands, code examples, or specific guidance. The skill describes what it claims to do ('provides step-by-step guidance') without actually providing any guidance whatsoever. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints—just abstract claims about capabilities like 'validates outputs against common standards' with no actual implementation. | 1 / 3 |
Progressive Disclosure | The content is a flat, repetitive structure with no references to detailed materials, no links to supporting files, and no meaningful organization beyond generic section headers that contain no real content. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
c8a915c
- 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.