Provides a high-level statistical overview of the codebase using the Codescope knowledge graph.
Install
mkdir -p .claude/skills/cs-stats && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/11479" && unzip -o skill.zip -d .claude/skills/cs-stats && rm skill.zipInstalls to .claude/skills/cs-stats
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Show codebase statistics from the Codescope knowledge graph. Use when user asks how many functions, classes, files, or wants a project overview.Key capabilities
- →Display codebase statistics from the Codescope knowledge graph.
- →Provide counts of files, functions, classes, and modules.
- →Summarize imports and variables.
- →Show the number of relations within the codebase.
How it works
The skill queries the Codescope knowledge graph using the `graph_stats` MCP tool to retrieve various codebase metrics. It then formats these statistics into a readable summary.
Inputs & outputs
When to use cs-stats
- →View code project overview
- →Get counts of functions and classes
- →Analyze project module distribution
About this skill
Codebase Statistics
Show the knowledge graph statistics using the graph_stats MCP tool.
Display a clean summary:
Project: <repo-name>
========================
Files: XXX
Functions: XXX
Classes: XXX
Modules: XXX
Imports: XXX
Variables: XXX
Relations: XXX
========================
If the stats look empty (all zeros), suggest running /cs-index first.
When not to use it
- →When the Codescope knowledge graph is empty or not yet indexed.
Limitations
- →The skill relies on the Codescope knowledge graph for data.
- →If the stats look empty (all zeros), it suggests running `/cs-index` first.
How it compares
This skill provides a direct, summarized view of codebase statistics from a knowledge graph, offering a quick overview compared to manually inspecting code or running custom scripts.
Compared to similar skills
cs-stats side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| cs-stats (this skill) | 0 | 4mo | No flags | Beginner |
| jupyter-notebook | 30 | 6mo | Review | Intermediate |
| juicebox-core-workflow-b | 1 | 27d | Review | Advanced |
| obspy-data-api | 1 | 6mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
jupyter-notebook
davila7
Use when the user asks to create, scaffold, or edit Jupyter notebooks (`.ipynb`) for experiments, explorations, or tutorials; prefer the bundled templates and run the helper script `new_notebook.py` to generate a clean starting notebook.
juicebox-core-workflow-b
jeremylongshore
Implement Juicebox candidate enrichment workflow. Use when enriching profile data, gathering additional candidate details, or building comprehensive candidate profiles. Trigger with phrases like "juicebox enrich profile", "juicebox candidate details", "enrich candidate data", "juicebox profile enrichment".
obspy-data-api
benchflow-ai
An overview of the core data API of ObsPy, a Python framework for processing seismological data. It is useful for parsing common seismological file formats, or manipulating custom data into standard objects for downstream use cases such as ObsPy's signal processing routines or SeisBench's modeling API.
perplexity-core-workflow-b
jeremylongshore
Execute Perplexity secondary workflow: Core Workflow B. Use when implementing secondary use case, or complementing primary workflow. Trigger with phrases like "perplexity secondary workflow", "secondary task with perplexity".
source-coding
parcadei
Problem-solving strategies for source coding in information theory
biopython
davila7
Primary Python toolkit for molecular biology. Preferred for Python-based PubMed/NCBI queries (Bio.Entrez), sequence manipulation, file parsing (FASTA, GenBank, FASTQ, PDB), advanced BLAST workflows, structures, phylogenetics. For quick BLAST, use gget. For direct REST API, use pubmed-database.