Your habits
Store personal skills under ~/.claude/skills/. Optimize for your own workflow without promising compatibility to others.
Navigation Explore Code Guide
Claude Code third-party ecosystem
Community-built tools that extend Claude Code. Every tool verified against its public repository.
26 tools verified May 2026 · Skills guidance updated Sep 2026
Mistral Large 4: public-preview evidence
Checked October 6, 2026. Mistral Large 4 accepts text and images and produces text through Studio and the API. The guide treats it as a provider candidate; a native Claude Code integration was not tested.
Prices and benchmark conditions
The standard-tier sale rates were $0.68 input, $0.07 cached input, and $2.09 output per million tokens. No sale end date was found. The dossier separates Mistral's launch scores from independent evaluator results and their conditions.
Mistral Large 4 evidence dossier →Deployment questions
Weights were planned for later in October, with differing dates in the sources. European infrastructure does not establish every endpoint's residency terms. Total parameters imply 525 GB of raw weights at four bits, before runtime and cache.
Compare API prices and limits →By the numbers
0
Community Tools
0
Categories
0
Languages
0
Stable Tools
Skills: Distribution is not mutualized maintenance
A public catalog helps you discover procedures and patterns. An install count, leaderboard position, or marketplace rating does not prove that a skill fits your client, repository, risk level, or maintenance model.
A shared local contract
Commit project skills under .claude/skills/ with a named owner, review path, assumptions, and retirement signal.
Versioned support
Publish through a maintained repository or plugin when users need compatibility and release support for a specific tool.
Discovery first
Treat the catalog as a source of candidates. Consume, fork, specialize, extract a pattern, or reject after local evaluation.
Install only after inspection
Review the selected revision, SKILL.md, supporting files, scripts, dependencies, and tool grants. Claude Code-specific fields may behave differently in another client.
npx skills add <owner/repo> Keep both boundaries explicit
Security: treat a downloaded skill like executable code. Ownership: treat it like situated context whose assumptions and maintainer must be recorded.
Skill ownership guide →Tool browser
No tools match your filters.
Recommendations by persona
| Persona | Recommended Tools | Rationale |
|---|---|---|
| Solo developer | ccusage + claude-code-viewer | Cost awareness + session history review |
| Small team (2-5) | ccusage + Conductor or multiclaude | Cost tracking + parallel development |
| Enterprise | ccusage (MCP) + Entire CLI | Programmatic cost data + audit trails |
| Python-centric | ccburn + Claude Chic | Native Python ecosystem tools |
| Multi-agent user | Toad or Conductor | Unified agent management |
| Config-heavy setup | claude-code-config + AIBlueprint | TUI config management + scaffolding |
Related: MCP vs CLI decision guide
Not sure whether to use MCP servers or CLI tools for a given integration? The decision guide covers four key questions, a 15-row guidance table by situation, and token cost analysis.
MCP vs CLI: Which to use? →Known gaps
As of March 2026, community tooling has notable missing pieces:
Visual skills editor
No GUI for creating or editing .claude/skills/. Must edit YAML/Markdown manually.
Visual hooks editor
No GUI for managing hooks in settings.json. Requires JSON editing.
Unified admin panel
No single dashboard combining config, sessions, cost, and MCP management.
Per-MCP-server profiler
No way to measure token cost attributable to each MCP server individually.
Cross-platform config sync
No tool syncs Claude Code config across machines. Manual copy of ~/.claude/ required.
Session replay ✅ filled
Entire CLI (launched Feb 2026) provides rewindable checkpoints with full context replay.