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
Quality
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 placeholder that provides almost no useful information for skill selection. It repeats the skill name as trigger terms, describes no concrete capabilities, and offers no guidance on when Claude should select this skill. The 'Enterprise Workflows' category mention adds minimal value without explaining what that means.
Suggestions
Add specific actions the skill performs, e.g., 'Generates formatted status reports by aggregating project progress, blockers, and next steps from team updates'
Replace the duplicate trigger term with natural variations users would say: 'status update', 'weekly report', 'progress summary', 'team status', 'standup notes'
Add an explicit 'Use when...' clause describing scenarios: 'Use when the user needs to create status reports, summarize project progress, or prepare updates for stakeholders'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Status Report Generator') without describing any concrete actions. There are no specific capabilities listed like 'generates weekly summaries', 'aggregates metrics', or 'formats reports'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and provides no meaningful 'when to use' guidance. The 'Triggers on' line just repeats the skill name rather than describing use cases. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('status report generator, status report generator' - duplicated) and overly narrow. Missing natural variations users would say like 'status update', 'weekly report', 'progress report', 'team status', etc. | 1 / 3 |
Distinctiveness Conflict Risk | While 'status report' is somewhat specific, the lack of detail about what kind of status reports (project, team, system, etc.) or what format/context could cause overlap with other reporting or documentation 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 essentially a placeholder template with no actual content. It describes capabilities without providing any concrete implementation, code examples, or actionable guidance for generating status reports. The entire body consists of generic marketing-style language that adds no value to Claude's ability to perform the task.
Suggestions
Add concrete examples of status report formats with actual templates (e.g., markdown or JSON structure for weekly/monthly reports)
Include executable code or commands for gathering project data and generating reports automatically
Define a clear workflow: data collection → aggregation → formatting → output, with specific steps for each phase
Provide sample inputs and expected outputs showing what a completed status report looks like
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual value. Phrases like 'provides automated assistance' and 'follows industry best practices' are vague filler that Claude doesn't need. | 1 / 3 |
Actionability | There is zero concrete guidance, no code, no commands, no specific steps. The entire skill describes what it claims to do without actually providing any executable instructions for generating status reports. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. The skill mentions 'step-by-step guidance' but provides none. There are no steps, no sequence, and no validation checkpoints. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no references to detailed materials, no examples, and no structured navigation to additional resources. | 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
0c08951
- 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.