Setup Matt Pocock Skills
ywwynm/EverythingDone
Sets up an Agent skills block in AGENTS.md/CLAUDE.md and docs/agents/ so the engineering skills know this repo's issue tracker (GitHub or local markdown), triage label vocabulary, and domain doc…
Analyzes Claude Code usage patterns and provides comprehensive recommendations.
Install Claude Code Analyzer
$ npx skills add Microck/ordinary-claude-skills --skill claude-code-analyzer -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Microck/ordinary-claude-skills claude-code-analyzer --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Microck/ordinary-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills_all/claude-code-analyzer .claude/skills/claude-code-analyzer && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "claude-code-analyzer" agent skill from https://github.com/Microck/ordinary-claude-skills/tree/main/skills_all/claude-code-analyzer into .claude/skills/claude-code-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "claude-code-analyzer", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Microck/ordinary-claude-skills/tree/main/skills_all/claude-code-analyzerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Microck/ordinary-claude-skills --skill claude-code-analyzer -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Microck/ordinary-claude-skills claude-code-analyzer --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Microck/ordinary-claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills_all/claude-code-analyzer .agents/skills/claude-code-analyzer && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "claude-code-analyzer" agent skill from https://github.com/Microck/ordinary-claude-skills/tree/main/skills_all/claude-code-analyzer into .agents/skills/claude-code-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "claude-code-analyzer", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Microck/ordinary-claude-skills --skill claude-code-analyzer -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Microck/ordinary-claude-skills claude-code-analyzer --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Microck/ordinary-claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills_all/claude-code-analyzer .cursor/skills/claude-code-analyzer && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "claude-code-analyzer" agent skill from https://github.com/Microck/ordinary-claude-skills/tree/main/skills_all/claude-code-analyzer into .cursor/skills/claude-code-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "claude-code-analyzer", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Microck/ordinary-claude-skills.git --path skills_all/claude-code-analyzer--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Microck/ordinary-claude-skills --skill claude-code-analyzer -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Microck/ordinary-claude-skills claude-code-analyzer --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Microck/ordinary-claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills_all/claude-code-analyzer .gemini/skills/claude-code-analyzer && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "claude-code-analyzer" agent skill from https://github.com/Microck/ordinary-claude-skills/tree/main/skills_all/claude-code-analyzer into .gemini/skills/claude-code-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "claude-code-analyzer", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Microck/ordinary-claude-skills claude-code-analyzerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Microck/ordinary-claude-skills --skill claude-code-analyzer -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Microck/ordinary-claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills_all/claude-code-analyzer .github/skills/claude-code-analyzer && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "claude-code-analyzer" agent skill from https://github.com/Microck/ordinary-claude-skills/tree/main/skills_all/claude-code-analyzer into .github/skills/claude-code-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "claude-code-analyzer", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Microck/ordinary-claude-skills --skill claude-code-analyzer -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Microck/ordinary-claude-skills claude-code-analyzer --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Microck/ordinary-claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills_all/claude-code-analyzer .opencode/skills/claude-code-analyzer && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "claude-code-analyzer" agent skill from https://github.com/Microck/ordinary-claude-skills/tree/main/skills_all/claude-code-analyzer into .opencode/skills/claude-code-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "claude-code-analyzer", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
claude-code-analyzer- GitHub stars
- 403
- Token cost
- ~2.3k tokens
- SKILL.md length
- 785 words
- Files
- 2
- Skills in repo
- 91
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Analyzes Claude Code usage patterns and provides comprehensive recommendations.
- Works in 4 steps: Run Usage Analysis → Run Project Analysis → Interpret Combined Results → …
- User wants to optimize their Claude Code workflow
- SKILL.md covers Core Capabilities, Complete Analysis Workflow, Example: Complete Optimization… and When to Use Each Tool, plus 5 more sections
- Calls bash, brew and apt; reaches docs.claude.com and anthropic.com
What it does
Claude Code Analyzer is an agent skill from Microck/ordinary-claude-skills. Analyzes Claude Code usage patterns and provides comprehensive recommendations. Runs usage analysis, discovers GitHub community resources, suggests CLAUDE.md improvements, and fetches latest docs on-demand. Use when user wants to optimize their Claude Code workflow, create configurations (agents/skills/commands), or set up project documentation.
Its SKILL.md is about 2.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `metadata.json`).
It sits in Agent Workflows, covering Agent instruction files. It works with GitHub. The repository describes itself as: An unappealing collection of Claude Skills and resources.
When your agent uses it
- User wants to optimize their Claude Code workflow
- Create configurations (agents/skills/commands)
- Set up project documentation
Example prompts
- “Use the claude-code-analyzer skill to analyz Claude Code usage patterns and provides comprehensive recommendations”
- “/claude-code-analyzer”
Requirements
- Docker
Workflow steps
4 steps, taken from the step headings in SKILL.md.
- Run Usage Analysis
- Run Project Analysis
- Interpret Combined Results
- Fetch Docs and Create Configurations
What it can do on your machine
Read from SKILL.md and the folder at commit 1056d29. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
bashbrewapt
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
docs.claude.comanthropic.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Claude Code Analyzer loads about 2.3k tokens when it runs. Until then it costs about 92 tokens; SKILL.md has 785 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 785 words (~2,333 tokens).
“Complete workflow optimization for Claude Code through usage analysis, community discovery, and intelligent configuration generation.”
- name
- claude-code-analyzer
Files
SKILL.md and 1 other file in skills_all/claude-code-analyzer of Microck/ordinary-claude-skills.
- SKILL.md
- metadata.json
Open the folder on GitHubat commit 1056d29
Compare with similar skills
Claude Code Analyzer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Claude Code Analyzer this skillMicrock/ordinary-claude-skills | 403 | — | ~2.3k | Automated safety check: Pass | Custom licence | |
| Setup Matt Pocock Skillsywwynm/EverythingDone | 144 | 9 repos | ~1.7k | Automated safety check: Pass | GPL-3.0 | |
| AI Self ImprovementJocysCom/FocusLogger | 213 | — | ~1.1k | Automated safety check: Pass | GPL-3.0 | |
| AI Readyjohnpapa/ai-ready | 223 | — | ~5.4k | Automated safety check: Pass | MIT | |
| Attmcojp Claude Mdnatsukium/dotfiles | 106 | — | ~1.3k | Automated safety check: Notes | CC0-1.0 | |
| Workflow Creatornicepkg/ai-workflow | 285 | — | ~2.6k | Automated safety check: Pass | MIT |
Similar skills
AI Self Improvement
JocysCom/FocusLogger
Update, create, improve, and synchronise this repository's AI agent instructions and related assets (including skills).
AI Ready
johnpapa/ai-ready
ANALYSIS SKILL — Analyze any repository and generate AI-ready configuration — a canonical AGENTS.md, thin per-tool pointer files, skills, CI workflows, issue templates.
Attmcojp Claude Md
natsukium/dotfiles
Change the org-level CLAUDE.md that governs every attmcojp repository.
Workflow Creator
nicepkg/ai-workflow
Create complete Claude Code workflow directories with curated skills.
- Official
Learn From PR
dotnet/maui
Analyzes a finished pull request that involved an agent to find what slowed or helped it, and recommends specific changes to instruction files, skills and docs.
More from Microck/ordinary-claude-skills
All 91 skills in this repoEvery Style Editor
Microck/ordinary-claude-skills
This skill should be used when reviewing or editing copy to ensure adherence to Every's style guide.
Gemini Imagegen
Microck/ordinary-claude-skills
Generate and edit images using the Gemini API (Nano Banana Pro).
Andrew Kane Gem Writer
Microck/ordinary-claude-skills
Write Ruby gems following Andrew Kane's proven patterns and philosophy.
Codex
Microck/ordinary-claude-skills
Execute Codex CLI for code analysis, refactoring, and automated code changes.
Docs Review
Microck/ordinary-claude-skills
Review documentation changes for compliance with the Metabase writing style guide.
File Todos
Microck/ordinary-claude-skills
This skill should be used when managing the file-based todo tracking system in the todos/ directory.
Related
Works with
Categories
Questions about Claude Code Analyzer
What does Claude Code Analyzer do?
Analyzes Claude Code usage patterns and provides comprehensive recommendations. Claude Code Analyzer is an agent skill from Microck/ordinary-claude-skills. Analyzes Claude Code usage patterns and provides comprehensive recommendations.
When should I use Claude Code Analyzer?
Claude Code Analyzer fits situations like: user wants to optimize their Claude Code workflow; create configurations (agents/skills/commands); set up project documentation.
How do I install Claude Code Analyzer in Claude Code?
Run `npx skills add Microck/ordinary-claude-skills --skill claude-code-analyzer -a claude-code`. Or copy the skill folder (skills_all/claude-code-analyzer in Microck/ordinary-claude-skills) into .claude/skills/claude-code-analyzer in your project. Claude Code loads it when a task matches its description.
How do I install Claude Code Analyzer in Codex?
Run `npx skills add Microck/ordinary-claude-skills --skill claude-code-analyzer -a codex`. Or copy the skill folder (skills_all/claude-code-analyzer in Microck/ordinary-claude-skills) into .agents/skills/claude-code-analyzer in your project. Codex loads it when a task matches its description.
Can I use Claude Code Analyzer in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Microck/ordinary-claude-skills --skill claude-code-analyzer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/claude-code-analyzer, .gemini/skills/claude-code-analyzer, .github/skills/claude-code-analyzer and .opencode/skills/claude-code-analyzer in your project.
What does Claude Code Analyzer need to run?
Going by SKILL.md and its folder, Claude Code Analyzer needs the command-line tools its instructions call (bash, brew and apt). Our summary lists: Docker.
Does Claude Code Analyzer access the network?
SKILL.md names 2 domains. In commands or code: docs.claude.com and anthropic.com; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.
Is Claude Code Analyzer safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Claude Code Analyzer use?
Claude Code Analyzer has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Claude Code Analyzer use?
About 2.3k tokens (SKILL.md is roughly 9.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Claude Code Analyzer?
Skills that share tags, products or a category with Claude Code Analyzer: Setup Matt Pocock Skills (ywwynm/EverythingDone, 144 stars), AI Self Improvement (JocysCom/FocusLogger, 213 stars), AI Ready (johnpapa/ai-ready, 223 stars) and Attmcojp Claude Md (natsukium/dotfiles, 106 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Claude Code Analyzer?
Microck (a GitHub user) maintains it in Microck/ordinary-claude-skills, which has 403 GitHub stars. The repository holds 91 skills in this directory. The repository was last updated on September 6, 2026.
Source: Microck/ordinary-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.