Help us improve
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Multi-agent algorithm intelligence system that analyzes codebases for optimization opportunities, researches cutting-edge algorithms via deep web research, identifies complexity bottlenecks, and applies superior data structures and algorithms with before/after benchmarking. 3 commands, 7 agents, 1 skill, 3 templates.
npx claudepluginhub trusted-american/marketplace --plugin algorithm-expertYou are orchestrating a comprehensive algorithmic analysis of a codebase. The goal is to find every place where a better algorithm or data structure would meaningfully improve performance, scalability, or correctness.
Apply a specific algorithm optimization to the codebase — replaces a suboptimal algorithm or data structure with a superior one, including before/after benchmarking and correctness verification
Research algorithms for a specific problem domain — searches academic papers, algorithm databases, competitive programming resources, and cutting-edge implementations to find the best approach for your problem
You are a world-class algorithm researcher. You find the best known algorithms for any computational problem by combining deep knowledge of classic algorithms with active research into cutting-edge developments.
You are a performance benchmarking specialist. You design, implement, and run benchmarks that produce statistically meaningful performance comparisons for algorithm optimizations.
You are a computational complexity analyst. You read source code and determine the precise time and space complexity of every significant function, accounting for hidden costs in library calls, nested iterations, and recursive structures.
You are a data structure specialist. You analyze how code USES its data structures and recommend the optimal structure for each access pattern. The right data structure can turn an O(n) operation into O(1) or reduce memory usage by orders of magnitude.
You are a software implementation researcher. You find the best existing implementations of algorithms and data structures — from standard libraries to battle-tested open-source packages — so developers can use proven code instead of reinventing it.
Uses power tools
Uses Bash, Write, or Edit tools
Has parse errors
Some configuration could not be fully parsed
Share bugs, ideas, or general feedback.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Analyze and optimize code performance
Analyze and optimize code performance
Deep analysis mode with extended reasoning for complex problems
Senior Algorithms Engineer with deep expertise in algorithm design and analysis, data structures, dynamic programming, graph algorithms, computational complexity, mathematical optimization, sorting and searching, and numerical methods.
Use this agent when you need to design scalable architecture and folder structures for new features or projects. Examples include: when starting a new feature module, refactoring existing code organization, planning microservice boundaries, designing component hierarchies, or establishing project structure conventions. For example: user: 'I need to add a user authentication system to my app' -> assistant: 'I'll use the code-architect agent to design the architecture and folder structure for your authentication system' -> <uses agent>. Another example: user: 'How should I organize my e-commerce product catalog feature?' -> assistant: 'Let me use the code-architect agent to design a scalable structure for your product catalog' -> <uses agent>.
Curated skills for Claude Code and Codex power users - tool selection, workflow optimization, and productivity
Fullstack development agent for the A3 platform — orchestrates Ember.js, Firebase/Firestore, and GCP Cloud Functions with deep codebase knowledge, round-robin review, and GitHub-authenticated access control
Multi-agent Playwright test generation system that creates thorough, production-ready test suites one page at a time
Multi-agent reverse engineering system with 10 specialized agents, 3 commands, and continuous fidelity assurance. Deeply researches any software via Firecrawl, Perplexity, and web intelligence; extracts architecture and features; analyzes competitors for UX, adoption, and feature parity; generates implementation blueprints; builds autonomous clones with orchestrated agent teams; and maintains fidelity through automated drift detection and self-healing loops. 3 commands, 10 agents, 1 skill, 4 templates.
Plugin registry for Claude Code, maintained by Trusted American Insurance Agency.
marketplace/
├── plugins/ # First-party plugins
├── community/ # Third-party forks and adaptations
├── .claude-plugin/
│ └── marketplace.json # Auto-generated plugin index (do not edit)
├── tools/
│ ├── lib/registry.js # Shared registry generation logic
│ ├── generate-marketplace-json.js # CLI script to regenerate marketplace.json
│ └── marketplace-mcp/ # MCP server for plugin management
├── .github/workflows/ci.yml # Validation + registry generation
└── .mcp.json # Auto-loads the MCP server in Claude Code
Every plugin in plugins/ or community/ must contain these files:
| File | Purpose |
|---|---|
README.md | Usage documentation |
LICENSE | License file |
.claude-plugin/plugin.json | Plugin manifest |
Components go in the plugin root, never inside .claude-plugin/:
plugin-name/
├── .claude-plugin/
│ └── plugin.json # Manifest — only file in this directory
├── skills/ # Each skill is a subdirectory with a SKILL.md
│ └── skill-name/
│ └── SKILL.md
├── agents/ # Agent definitions (.md files)
│ └── agent-name.md
├── commands/ # Slash command definitions (.md files)
│ └── command-name.md
├── hooks/ # Hook configurations (.json files)
│ └── hooks.json
├── templates/ # Output templates (.md files)
│ └── template-name.md
├── .mcp.json # MCP server config (optional)
├── README.md
└── LICENSE
The name field is required and must be kebab-case (^[a-z0-9-]+$). All other fields are optional but recommended.
{
"name": "my-plugin",
"version": "0.1.0",
"description": "What this plugin does",
"author": { "name": "Author Name" },
"license": "MIT",
"keywords": ["keyword1", "keyword2"],
"repository": "https://github.com/org/repo"
}
Names must be unique across the entire marketplace. If two plugins share a name, CI will warn and the second one overwrites the first in .claude-plugin/marketplace.json.
.claude-plugin/marketplace.json is a generated index of all plugins. It is not updated in PRs. The flow:
main.node tools/generate-marketplace-json.js, which scans plugins/ and community/, reads each plugin.json, collects component directories, and writes .claude-plugin/marketplace.json.main with [skip ci] to avoid a loop.The lastUpdated timestamp updates on every run. The generation logic lives in tools/lib/registry.js and is shared between the CLI script and the MCP server.
The MCP server at tools/marketplace-mcp/ auto-loads when you open this repo in Claude Code (configured in .mcp.json). It exposes 6 tools:
| Tool | What it does |
|---|---|
create_plugin | Scaffolds a new plugin with required files and correct directory structure |
validate_plugin | Checks a plugin for required files, valid manifest, and component structure |
validate_all | Validates every plugin in plugins/ and community/ |
list_plugins | Lists all plugins with version, description, and component breakdown |
add_component | Adds a skill, agent, command, hook, or template to an existing plugin |
get_conventions | Returns the full marketplace conventions document |
Validation checks: required files exist, plugin.json is valid JSON with a kebab-case name, and any component directories that exist contain correctly typed files (.md for skills/agents/commands/templates, .json for hooks).
Every push and PR runs two jobs:
plugins/ and community/ for README.md, LICENSE, and a valid .claude-plugin/plugin.json with a kebab-case name.npm test in tools/marketplace-mcp/ (vitest, 57 tests covering validation, registry generation, component handling, and security).On merge to main, a third job runs:
.claude-plugin/marketplace.json and commits it.Prerequisites: Claude Code and Node.js 18+ (22 recommended).
git clone https://github.com/trusted-american/marketplace.git
cd marketplace
npm ci --prefix tools/marketplace-mcp
Open the repo in Claude Code. The MCP server loads automatically. Run list plugins to verify.
If you use the jira-orchestrator plugin for Jira/Confluence integration: