organvm-iv-taxis/specstory-project-stats
.build/codex/skills/specstory-project-stats/SKILL.md
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 --global
skillsauthnpx skillsauth add organvm-iv-taxis/a-i--skills specstory-project-statsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 17, 2026, 2:27 AM33.9s1 file scanned
SKILL.md
- name:
- specstory-project-stats
- description:
- Fetch project statistics from SpecStory Cloud. Run when user says "get project stats", "show SpecStory stats", "project statistics", "how many sessions", or "SpecStory metrics".
- license:
- Apache-2.0
- author:
- SpecStory, Inc.
- version:
- 1.0.0
- allowed-tools:
- Bash(node *)
- governance_phases:
- [frame]
- organ_affinity:
- [organ-iv]
- triggers:
- [command:project-stats, user-asks-about-specstory-stats]
SpecStory Project Stats
Fetches project statistics from SpecStory's cloud platform, showing contributor counts, session activity, and other project metrics.
How It Works
- Identifies the project via
.specstory/.project.json, git remote, or folder name - Calls the SpecStory Cloud API
- Returns project statistics in JSON format
- Presents the data in a readable summary
Prerequisites
- Project must be synced to SpecStory Cloud
- Node.js must be available to run the script
Usage
Slash Command
| User says | Action |
|-----------|--------|
| /specstory-project-stats | Fetch stats for current project |
| /specstory-project-stats | Same as above (no arguments needed) |
Direct Script Usage
# Fetch stats for current project
node skills/specstory-project-stats/scripts/get-stats.js
# With custom API endpoint (for development)
SPECSTORY_API_URL=http://localhost:5173 node skills/specstory-project-stats/scripts/get-stats.js
Output
The script outputs JSON with project statistics:
{
"project_id": "specstoryai/agent-skills",
"sessions": {
"total": 156,
"last_30_days": 47,
"last_7_days": 12
},
"contributors": {
"total": 5,
"active_last_30_days": 3
},
"activity": {
"first_session": "2025-10-15",
"last_session": "2026-01-28",
"avg_sessions_per_week": 8.2
}
}
Project ID Resolution
The script determines project ID in this order:
.specstory/.project.json- Usesgit_idorworkspace_idfield- Git remote - Extracts repo name from
originremote URL - Folder name - Falls back to current directory name
Error Handling
| Error | Meaning | Action | |-------|---------|--------| | 404 | Project not found | Project needs to sync to SpecStory Cloud first | | 401 | Unauthorized | API endpoint may require authentication | | Network error | Can't reach API | Check internet connection |
Present Results to User
After fetching stats, present them in a friendly format:
Example Response (success)
Here are the stats for **specstoryai/agent-skills**:
**Sessions**
- Total: 156 sessions captured
- Last 30 days: 47 sessions
- Last 7 days: 12 sessions
**Contributors**
- Total: 5 contributors
- Active recently: 3
**Activity**
- First session: October 15, 2025
- Most recent: January 28, 2026
- Average: ~8 sessions per week
Your project has been actively using AI-assisted coding!
Example Response (404 error)
This project doesn't exist on SpecStory Cloud yet.
To get started:
1. Make sure you have SpecStory installed
2. Run `specstory sync` to push your local sessions to the cloud
3. Try this command again
Need help? Check the docs at https://docs.specstory.com
Environment Variables
| Variable | Default | Description |
|----------|---------|-------------|
| SPECSTORY_API_URL | https://cloud.specstory.com | API endpoint |
Notes
- Statistics are fetched from SpecStory Cloud, not local history
- Project must have synced sessions to show meaningful stats
- The API is public and doesn't require authentication for basic stats
Related Skills
organvm-iv-taxis/shell-history-hygiene
development
VerifiedTrustedCommunity
Dry-run audit + targeted cleanup for shell command history. Currently wraps atuin (stats today, prune, dedup with dated preview artifacts); extensible to zsh/bash/mcfly backends. Always previews before applying — apply commands are echoed for the human to run, never auto-executed. Triggers on "/shell-history-hygiene", "audit atuin", "audit shell history", "clean shell history", "atuin prune", "atuin dedup", "shell history hygiene", "history cleanup". Replaces ad-hoc one-liners (e.g. `... | tee cmd > file.txt` which wrote two files, swallowed dedup output, and left a junk `cmd` file).
12SKILL.mdUpdated Jul 20, 2026
organvm-iv-taxis/setup-cowork
tools
VerifiedTrustedCommunity
Guided Cowork setup — install role-matched plugins, connect your tools, try a skill.
12SKILL.mdUpdated Jul 20, 2026
organvm-iv-taxis/session-lifecycle-patterns
development
VerifiedTrustedCommunity
Manage AI agent session lifecycles with structured phases (FRAME, SHAPE, BUILD, PROVE), context preservation across sessions, handoff protocols, and session metadata tracking. Triggers on session management, agent lifecycle, or multi-session workflow requests.
12SKILL.mdUpdated Jul 20, 2026
organvm-iv-taxis/session-governance-audit
tools
VerifiedTrustedCommunity
Parse a session transcript into a structured Session Governance Index — an annotated bibliography of every file modified and commit made, internal-energy accounting (tool uses, estimated tokens), shipped-vs-tasked atom tally, and classification of missing items as Gaps or Vacuums. Triggers on "visibility-schema-substrate-sweep", "session cascade audit", "session governance audit", or any request to summarize what a session actually produced versus what it was asked to produce.
12SKILL.mdUpdated Jul 20, 2026