convez.ai
SkillProdutividadeAvançado
Emasoft

Emasoft Plugins Marketplace

Emasoft/emasoft-plugins

Plugins profissionais para workflows multi-agent, validação e otimização

Ver no GitHub
InicialPluginScore · de 0 a 100

Coleção de plugins e agents de alta qualidade para Claude, incluindo ferramentas de validação, orquestração multi-agent e otimização de custos. Engloba sugestores inteligentes de skills, gerenciadores de agentes especializados e reporters de tokens com análise detalhada.

Instalação

$npx convez-ai Emasoft/emasoft-plugins

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
2
Forks
0
Acompanhando
0
Saúde
42%
Último commit
há 1 dia
Versão
v1.2.0
Issues abertas
0
Contribuidores
2

Casos de uso

  • Orquestração de múltiplos agentes especializados (arquiteto, programador, integrador)
  • Validação abrangente de plugins, skills e servidores MCP
  • Análise de consumo de tokens e redução de custos com cache
  • Automação de ciclos de vida de agentes (spawn, monitor, hibernate, terminate)
  • Sugestão inteligente de skills com acurácia acima de 88%

Veredito

Ecossistema maduro e bem documentado para arquiteturas multi-agent em produção. Destaca-se pela instrumentação profissional (token-reporter, llm-externalizer) e agentes especializados com responsabilidades claras, ideal para equipes que precisam orquestrar fluxos complexos de IA.

README

A tradução para o português deste README ainda está na fila.

Emasoft Plugins Marketplace

A collection of high-quality Claude Code plugins for multi-agent development workflows, skill activation, and plugin validation.

Plugin Versions

PluginVersionCategoryDescription
perfect-skill-suggester1.6.1UtilityHigh-accuracy skill activation (88%+) with AI-analyzed keywords
claude-plugins-validation1.3.1UtilityComprehensive validation suite for plugins, skills, hooks, and MCP
emasoft-assistant-manager-agent1.1.2AgentUser interface and role routing for the Emasoft agent ecosystem
emasoft-chief-of-staff1.3.2AgentMulti-agent lifecycle management (spawn, monitor, hibernate, terminate)
emasoft-architect-agent1.1.2AgentArchitecture design, requirements analysis, and specification creation
emasoft-orchestrator-agent1.2.1AgentTask distribution, agent coordination, and progress monitoring
emasoft-integrator-agent1.1.2AgentQuality gates, code review, testing, and release management
emasoft-programmer-agent1.0.1AgentCode implementation, testing, and debugging (Python, JS/TS, Rust, Go, .NET, C/C++, Swift)
token-reporter1.2.2Developer ToolsPer-operation token usage reporter with cost estimates, cache efficiency, and tool attribution
llm-externalizer3.2.1Developer ToolsMCP server that offloads LLM tasks to cheaper local or remote models with ensemble mode

Last updated: 2026-03-15


Installation

Step 1: Add Marketplace

claude plugin marketplace add Emasoft/emasoft-plugins

Step 2: Update Marketplace Index

claude plugin marketplace update emasoft-plugins

This refreshes the local plugin index. Always run this before installing to ensure you get the latest available plugins and versions.

Step 3: Install Plugin

# Utility plugins
claude plugin install perfect-skill-suggester@emasoft-plugins
claude plugin install claude-plugins-validation@emasoft-plugins
claude plugin install token-reporter@emasoft-plugins
claude plugin install llm-externalizer@emasoft-plugins

# Emasoft agent ecosystem (install the roles you need)
claude plugin install emasoft-assistant-manager-agent@emasoft-plugins
claude plugin install emasoft-chief-of-staff@emasoft-plugins
claude plugin install emasoft-architect-agent@emasoft-plugins
claude plugin install emasoft-orchestrator-agent@emasoft-plugins
claude plugin install emasoft-integrator-agent@emasoft-plugins
claude plugin install emasoft-programmer-agent@emasoft-plugins

Step 4: Verify Installation

claude plugin list

Step 5: Restart Claude Code

Important: After installation, you must restart Claude Code for the plugin to take effect.

Troubleshooting: If claude plugin install says "Plugin not found", run claude plugin marketplace update emasoft-plugins first to refresh the local cache.


Update to Latest Version

When a new version is released, follow these steps:

Step 1: Update Marketplace Cache

claude plugin marketplace update emasoft-plugins

Step 2: Uninstall Current Version

claude plugin uninstall perfect-skill-suggester

Step 3: Install Latest Version

claude plugin install perfect-skill-suggester@emasoft-plugins

Step 4: Restart Claude Code

Restart Claude Code to load the updated plugin.


Reinstall (Fix Broken Installation)

If the plugin is not working correctly, perform a clean reinstall:

Step 1: Uninstall

claude plugin uninstall perfect-skill-suggester

Step 2: Update Marketplace Cache

claude plugin marketplace update emasoft-plugins

Step 3: Reinstall

claude plugin install perfect-skill-suggester@emasoft-plugins

Step 4: Restart Claude Code

Restart Claude Code to load the freshly installed plugin.


Uninstall

To completely remove the plugin:

Step 1: Uninstall Plugin

claude plugin uninstall perfect-skill-suggester

Step 2: (Optional) Remove Marketplace

If you no longer want plugins from this marketplace:

claude plugin marketplace remove emasoft-plugins

Step 3: Restart Claude Code

Restart Claude Code to complete the removal.


Troubleshooting

Commands not found after installation

Symptom: Plugin shows as installed and enabled, but /pss-reindex-skills or /pss-status commands are not found.

Solution: Restart Claude Code. Plugins only load their commands on startup.

Plugin install fails

Symptom: claude plugin install returns an error.

Solutions:

  1. Update the marketplace cache first:
    claude plugin marketplace update emasoft-plugins
    
  2. Try reinstalling the marketplace:
    claude plugin marketplace remove emasoft-plugins
    claude plugin marketplace add https://github.com/Emasoft/emasoft-plugins
    

Plugin shows as disabled

Symptom: Plugin is installed but status shows ✘ disabled.

Solution: Enable the plugin:

claude plugin enable perfect-skill-suggester

Hook not triggering

Symptom: Plugin is installed and enabled, but skill suggestions don't appear.

Solutions:

  1. Verify the plugin is enabled: claude plugin list
  2. Check hooks are registered: /hooks (inside Claude Code)
  3. Restart Claude Code

Hook path not found after version update

Symptom: After updating a plugin, you see an error like:

UserPromptSubmit operation blocked by hook:
can't open file '.../perfect-skill-suggester/1.2.1/scripts/pss_hook.py': No such file or directory

Cause: Claude Code is still referencing the OLD version path in memory. The cache now has the new version (e.g., 1.2.2/), but the running session has the old path (1.2.1/) cached.

Solution: Restart Claude Code after any plugin update. This is required for Claude Code to reload the new version paths.

If restarting doesn't fix it, perform a clean reinstall:

# 1. Clear the marketplace cache
rm -rf ~/.claude/plugins/cache/emasoft-plugins/

# 2. Uninstall the plugin
claude plugin uninstall perfect-skill-suggester@emasoft-plugins

# 3. Reinstall
claude plugin install perfect-skill-suggester@emasoft-plugins

# 4. Restart Claude Code

Old version still showing after update

Symptom: After running claude plugin marketplace update, the plugin still shows the old version.

Cause: The marketplace cache or installed plugin cache is stale.

Solution: Full reinstall cycle:

# 1. Clear marketplace cache
rm -rf ~/.claude/plugins/cache/emasoft-plugins/

# 2. Uninstall
claude plugin uninstall perfect-skill-suggester@emasoft-plugins

# 3. Reinstall
claude plugin install perfect-skill-suggester@emasoft-plugins

# 4. Verify version
claude plugin list | grep perfect-skill

# 5. IMPORTANT: Restart Claude Code

No skill suggestions appear (silent failure)

Symptom: Plugin is installed and working, but no skills are ever suggested, even for prompts that should match.

Cause: The skill index file doesn't exist at ~/.claude/cache/skill-index.json.

Solution: Run /pss-reindex-skills to generate the skill index. This must be done after installation.

"Failed to read skill index" error

Symptom: Error message mentioning "Failed to read skill index from ".

Causes:

  • File permissions issue
  • Disk full
  • File corrupted

Solutions:

  1. Check file exists: ls -la ~/.claude/cache/skill-index.json
  2. Check permissions: chmod 644 ~/.claude/cache/skill-index.json
  3. Regenerate index: /pss-reindex-skills

"Failed to parse skill index" error

Symptom: Error message mentioning "Failed to parse skill index".

Cause: The skill index JSON file is corrupted or malformed.

Solution: Regenerate the index (it will overwrite the corrupted file):

/pss-reindex-skills

Available Plugins

Perfect Skill Suggester (PSS)

Full Documentation | Architecture | Changelog

High-accuracy skill activation with AI-analyzed keywords and Rust-powered matching.

Features:

  • 88%+ accuracy on skill activation
  • AI-analyzed keywords via Haiku agents
  • Rust binary for ~10ms hook execution
  • 70+ synonym expansion patterns
  • Weighted scoring system
  • Three-tier confidence routing (HIGH/MEDIUM/LOW)
  • Co-usage boosting for related skills
  • Multi-project skill discovery from ~/.claude.json

Commands:

  • /pss-status - View PSS status and index statistics
  • /pss-reindex-skills - Regenerate skill index with AI analysis

Requirements:

  • Pre-built binaries included for all platforms (macOS, Linux, Windows)
  • Python 3.8+ for index generation

Supported Platforms:

PlatformBinary
macOS Apple Siliconpss-darwin-arm64
macOS Intelpss-darwin-x86_64
Linux x86_64pss-linux-x86_64
Linux ARM64pss-linux-arm64
Windows x86_64pss-windows-x86_64.exe

Claude Plugins Validation

Full Documentation | Skill Reference

Comprehensive validation suite for Claude Code plugins, marketplaces, hooks, skills, and MCP servers.

Features:

  • 5 specialized Python validators (plugin, skill, hook, MCP, marketplace)
  • Expert plugin-validator agent for thorough examination
  • Complete skill with 5 reference documents
  • GitHub marketplace deployment validation
  • Links to 45+ official Anthropic documentation URLs
  • Multi-language linter auto-installation (8 languages supported)
  • Multi-language dependency verification

Supported Languages:

LanguageLinters
Pythonruff, mypy
JavaScript/TypeScripteslint, typescript
Rustclippy, rustfmt
Gostaticcheck, golangci-lint
Shell/Bashshellcheck
PowerShellPSScriptAnalyzer
Rubyrubocop

Validators:

  • validate_plugin.py - Full plugin structure validation
  • validate_skill.py - Skill directory and frontmatter validation
  • validate_hook.py - Hook configuration and script validation
  • validate_mcp.py - MCP server configuration validation
  • validate_marketplace.py - Marketplace and GitHub deployment validation

Usage:

# Validate a plugin
cd OUTPUT_SKILLS/claude-plugins-validation
uv run python scripts/validate_plugin.py /path/to/your-plugin --verbose

# Validate a marketplace for GitHub deployment
uv run python scripts/validate_marketplace.py /path/to/marketplace --verbose

# From any other plugin directory (without pyproject.toml):
uv run --with pyyaml python scripts/validate_plugin.py . --verbose

Exit Codes:

CodeMeaning
0All checks passed
1Critical issues - plugin broken
2Major issues - some features may fail
3Minor issues - warnings only

Token Reporter

Per-operation token usage reporter for Claude Code. Shows token counts, cost estimates, tool attribution, cache efficiency, duration, bash commands, web fetches, and file activity when agents complete. Only outputs in debug mode (claude --debug).

Note: The plugin name is token-reporter (used for installation), while the GitHub repo is named token-reporter-plugin. Always use the plugin name when installing.

Install:

claude plugin install token-reporter@emasoft-plugins

Features:

  • Per-operation token counts (input, output, cache-write, cache-read)
  • Cache efficiency percentage
  • Per-tool token attribution (input, output, result-to-input)
  • MCP tools listed vertically with full names
  • Cost estimates based on Anthropic API pricing
  • Duration tracking
  • Bash commands and web fetches listed individually
  • All files (read, edited, written) listed individually
  • Lifetime cost for completed agents, current-operation cost for session
  • Debug-mode-only output (no overhead in normal mode)

Requirements: uv, Python 3.8+


LLM Externalizer

MCP server that offloads bounded LLM tasks from Claude Code to cheaper local or remote models. Supports LM Studio, Ollama, vLLM, llama.cpp (local) and OpenRouter (remote) with profile-based configuration and ensemble mode.

Note: The plugin name is llm-externalizer (used for installation), while the GitHub repo is named llm-externalizer-plugin. Always use the plugin name when installing.

Install:

claude plugin install llm-externalizer@emasoft-plugins

Features:

  • 7 read-only analysis tools (chat, code_task, batch_check, scan_folder, compare_files, check_references, check_imports)
  • Profile-based backend configuration with named profiles
  • Ensemble mode: two models in parallel on OpenRouter
  • Auto-batching for large file sets
  • Secret scanning and redaction
  • 2 auto-discovered skills for tool usage and configuration

Requirements: Node.js >= 18, npm. For remote: OPENROUTER_API_KEY env var.


Emasoft Agent Ecosystem

The six emasoft-* plugins form a complete multi-agent development team. Each plugin defines a role boundary and communicates with other roles via AI Maestro messaging.

USER
  │
  ▼
EAMA (Assistant Manager) ── User interface, role routing
  │
  ▼
ECOS (Chief of Staff) ── Agent lifecycle, coordination
  │
  ├── EAA (Architect) ── Design docs, planning
  ├── EOA (Orchestrator) ── Task distribution, delegation
  └── EIA (Integrator) ── Code review, quality gates
                │
                ▼
        EPA (Programmer) ── Code implementation
PluginRoleAgentsSkills
emasoft-assistant-manager-agentUser interface, role routing28
emasoft-chief-of-staffAgent lifecycle management1014
emasoft-architect-agentArchitecture design, planning613
emasoft-orchestrator-agentTask distribution, coordination615
emasoft-integrator-agentCode review, quality gates1119
emasoft-programmer-agentCode implementation, testing15

Key design principles:

  • One plugin per agent instance — each agent loads ONLY its own plugin
  • Inter-agent communication via AI Maestro messaging (not skill sharing)
  • Role boundaries enforced by plugin mutual exclusivity

For Developers

This section is for contributors who want to develop or modify the plugins.

Clone the Repository

Important: Use --recursive to also fetch plugin submodules:

git clone --recursive https://github.com/Emasoft/emasoft-plugins.git
cd emasoft-plugins

If you already cloned without --recursive, initialize submodules:

git submodule update --init --recursive

Setup Git Hooks

After cloning, set up git-cliff changelog generation and version sync hooks:

./scripts/setup-hooks.sh

This installs the following hooks:

RepositoryHookPurpose
Main marketplacepre-commitSyncs plugin versions from submodules to marketplace.json
Main marketplacepost-commitRegenerates CHANGELOG.md with git-cliff
Each submodulepost-commitRegenerates CHANGELOG.md with git-cliff

Requirements: Install git-cliff for changelog generation:

# macOS
brew install git-cliff

# Or via cargo
cargo install git-cliff

Version Sync

When you bump a plugin's version in its submodule, the pre-commit hook automatically updates marketplace.json. The version is read from (in order of priority):

  1. .claude-plugin/plugin.json
  2. pyproject.toml
  3. package.json

You can also run the sync manually:

# Check for version mismatches
python scripts/sync-versions.py --check --verbose

# Update marketplace.json with submodule versions
python scripts/sync-versions.py --verbose

Local Testing

# Validate the marketplace
claude plugin validate .

# Validate a specific plugin
claude plugin validate ./perfect-skill-suggester

# Load plugin locally without installing
claude --plugin-dir ./perfect-skill-suggester

Adding a Local Marketplace

For development, you can add the cloned repo as a local marketplace:

claude plugin marketplace add /path/to/emasoft-plugins

Releasing New Versions

Use the release script for proper version bumping and tagging:

python release.py patch perfect-skill-suggester "Bug fix description"
python release.py minor perfect-skill-suggester "New feature"
python release.py major perfect-skill-suggester "Breaking change"

License

MIT License - See individual plugin directories for specific licenses.

Author

Emasoft

Architecture

flowchart TB
    subgraph Marketplace["Marketplace Repository"]
        MJ[marketplace.json]
        UW[update-submodules.yml]
        SV[sync_marketplace_versions.py]
    end

    subgraph Plugins["Plugin Repositories"]
        P1[plugin-a]
        P2[plugin-b]
        P3[plugin-n]
    end

    subgraph Automation["GitHub Actions"]
        CRON[Scheduled Check<br/>every 6 hours]
        DISPATCH[Repository Dispatch<br/>plugin-updated event]
    end

    P1 -->|submodule| Marketplace
    P2 -->|submodule| Marketplace
    P3 -->|submodule| Marketplace

    P1 -->|notify-marketplace.yml| DISPATCH
    P2 -->|notify-marketplace.yml| DISPATCH
    P3 -->|notify-marketplace.yml| DISPATCH

    CRON -->|triggers| UW
    DISPATCH -->|triggers| UW
    UW -->|runs| SV
    SV -->|updates| MJ

How It Works

  1. Plugin Update: When a plugin repo pushes changes, its notify-marketplace.yml workflow sends a repository dispatch event
  2. Marketplace Update: The marketplace's update-submodules.yml workflow triggers (via dispatch or scheduled cron)
  3. Version Sync: The sync_marketplace_versions.py script reads each plugin's version and updates marketplace.json
  4. Auto Commit: Changes are committed and pushed automatically
Ver o original no GitHub

Bom para

Relacionados