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.
Overall
score
19%
Does it follow best practices?
Validation for skill structure
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill status-report-generatorActivation
7%This description is essentially a placeholder with minimal useful content. It provides no concrete actions, no meaningful trigger terms beyond the skill name, and no guidance on when to use it. The description relies entirely on the skill name to convey purpose, which is insufficient for Claude to make informed skill selection decisions.
Suggestions
Add specific capabilities describing what the skill does, e.g., 'Generates project status reports including progress summaries, blockers, milestones, and next steps from task data and updates.'
Include a 'Use when...' clause with natural trigger terms like 'weekly update', 'progress report', 'team status', 'standup summary', 'project update email'.
Specify the context or data sources the skill works with (e.g., 'from Jira tickets', 'from git commits', 'from meeting notes') to distinguish it from other reporting skills.
| 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 what kind of reports, what data sources, or what output formats. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and provides no 'when should Claude use it' guidance. The 'Triggers on' line just repeats the skill name rather than providing meaningful trigger scenarios. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('status report generator, status report generator'). Missing natural variations users would say like 'weekly update', 'progress report', 'team status', 'project summary', 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 context could cause overlap with other reporting or documentation skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is an empty template with no substantive content. It describes what a status report generator skill would do but provides absolutely no actionable guidance, code examples, report templates, or workflow steps. The content is entirely meta-description without any actual instructional value.
Suggestions
Add concrete examples of status report formats (e.g., weekly project status, sprint summary) with actual templates or code to generate them
Define a clear workflow: what inputs are needed, how to gather project data, how to structure the output, and validation steps
Include executable code or specific commands for generating reports (e.g., querying project management tools, formatting output)
Remove all generic boilerplate ('provides automated assistance', 'follows best practices') and replace with specific, actionable instructions
| 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, no examples of actual status report formats or generation logic. The content only describes what the skill claims to do without showing how. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. Despite claiming to provide 'step-by-step guidance,' there are no actual steps, sequences, or processes documented for generating status reports. | 1 / 3 |
Progressive Disclosure | The content is a shallow placeholder with no meaningful structure. There are no references to detailed documentation, no examples to link to, and no organized sections with actual content. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
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.