status-report-generator
Status Report Generator - Auto-activating skill for Enterprise Workflows. Triggers on: status report generator, status report generator Part of the Enterprise Workflows skill category.
35
3%
Does it follow best practices?
Impact
95%
1.00xAverage 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/status-report-generator/SKILL.mdQuality
Discovery
7%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 title repeated with boilerplate metadata. It provides no concrete actions, no meaningful trigger terms beyond the skill name itself, and no guidance on when Claude should select it. It fails on nearly every dimension of the rubric.
Suggestions
Add concrete actions describing what the skill does, e.g., 'Generates project status reports summarizing task progress, blockers, milestones, and team updates from provided data.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks for a status update, progress report, weekly summary, project recap, or team status.'
Remove the redundant duplicate trigger term ('status report generator' listed twice) and replace with varied natural language terms users would actually say.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names no concrete actions. It says 'Status Report Generator' but never describes what it actually does—no mention of what data it processes, what format it outputs, or what steps it performs. | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is meaningfully answered. There is no 'Use when...' clause and no description of capabilities beyond the skill's name. | 1 / 3 |
Trigger Term Quality | The only trigger term listed is 'status report generator' repeated twice. It misses natural variations users would say like 'status update', 'weekly report', 'progress report', 'project status', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'status report' is somewhat specific and unlikely to conflict with many other skills, but the lack of detail about what kind of status reports or in what context means it could overlap with general reporting or document generation skills. | 2 / 3 |
Total | 5 / 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 a hollow placeholder that contains no actual instructional content. It repeatedly describes itself in abstract terms ('provides automated assistance,' 'follows industry best practices') without ever defining what a status report looks like, how to generate one, what format to use, or any concrete steps. It fails on every dimension of the rubric.
Suggestions
Add a concrete status report template or format specification with example output (e.g., markdown template with sections for accomplishments, blockers, next steps, metrics).
Include a step-by-step workflow for gathering project data and assembling a status report, with specific instructions for each step.
Provide at least one complete, executable example showing input data and the resulting generated status report.
Remove all meta-description sections ('When to Use,' 'Capabilities,' 'Example Triggers') that describe the skill rather than teaching how to perform the task.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual instructions, code, or actionable content. Every section restates the same vague information. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no specific steps, no examples of actual status report generation. The 'Example Triggers' section just lists ways to invoke the skill, not how to accomplish anything. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. The skill claims to provide 'step-by-step guidance' but contains no steps, no sequence, and no validation checkpoints for any process. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no references to detailed materials, no links to supporting files, and no structured navigation to deeper 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
4dee593
- 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.