specstory-project-stats
Fetch project statistics from SpecStory Cloud. Run when user says "get project stats", "show SpecStory stats", "project statistics", "how many sessions", or "SpecStory metrics".
Install with Tessl CLI
npx tessl i github:specstoryai/agent-skills --skill specstory-project-stats89
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
89%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 is a well-structured skill description with excellent trigger term coverage and clear 'when to use' guidance. The main weakness is the limited specificity about what statistics are actually fetched - users don't know if this covers session counts, usage metrics, performance data, etc. The description is functional but could be more informative about capabilities.
Suggestions
Expand the 'what' portion to list specific statistics available (e.g., 'Fetch session counts, usage metrics, and activity data from SpecStory Cloud')
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (SpecStory Cloud) and one action (fetch project statistics), but doesn't elaborate on what specific statistics are available or what the output includes. | 2 / 3 |
Completeness | Clearly answers both what (fetch project statistics from SpecStory Cloud) and when (explicit 'Run when user says...' clause with multiple trigger phrases). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including 'get project stats', 'show SpecStory stats', 'project statistics', 'how many sessions', and 'SpecStory metrics' - these are phrases users would naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with the specific 'SpecStory Cloud' product name and related trigger terms; unlikely to conflict with other skills due to the unique product context. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill with excellent actionability - concrete commands, complete output examples, and clear error handling. The main weakness is minor verbosity: the 'How It Works' section explains obvious steps, and the slash command table has a redundant duplicate row. Overall, it effectively teaches Claude how to fetch and present SpecStory project statistics.
Suggestions
Remove the duplicate row in the slash command table and condense the 'How It Works' section since Claude can infer these steps from the actual usage examples
Consider removing the explanatory sentence 'Your project has been actively using AI-assisted coding!' from the example response as it's filler text
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but includes some redundancy (duplicate slash command rows in table, explanatory text that could be trimmed). The 'How It Works' section explains obvious steps Claude could infer. | 2 / 3 |
Actionability | Provides fully executable bash commands, complete JSON output examples, and specific error handling guidance. The script path and environment variable usage are copy-paste ready. | 3 / 3 |
Workflow Clarity | For this simple single-task skill, the workflow is unambiguous: run script, get JSON, present results. Error handling table provides clear recovery actions for each error type. | 3 / 3 |
Progressive Disclosure | Well-organized sections with clear headers. Content is appropriately sized for a single file (~80 lines). Tables and code blocks make navigation easy without needing external references. | 3 / 3 |
Total | 11 / 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 |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
Total | 10 / 11 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.