Claude Plugins — Gerenciamento de Tickets e Automação
SashaMarchuk/claude-plugins
Plugins para ticket management, calendário, multi-agent rigor e análise de dados
Ver no GitHubConjunto de cinco plugins opinionados para Claude Code: ClickUp (criar e gerenciar tickets), Google Calendar (agendamento com Meet), Ultra (multi-agent swarm com validação adversarial), Ultra Analyzer (pipeline de análise de dados com rigor) e Claude Migrate (migração de chats entre contas). Todos livres, MIT-licensed e focados em workflows de engenharia com qualidade garantida.
Instalação
npx convez-ai SashaMarchuk/claude-plugins1 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
Casos de uso
- Criar e gerenciar tickets ClickUp com histórias de usuário estruturadas
- Agendar eventos Google Calendar com validação de conflitos
- Executar análises rigorosas com multi-agent swarm e debate adversarial
- Validar e analisar corpus de dados (MongoDB, PDF, web, JSON/CSV, SQLite)
- Migrar chats e projetos entre contas Claude.ai com verificação byte-exact
Veredito

Suite madura e bem arquitetada para automação de workflows técnicos. Destaca-se pelo foco em qualidade (validação adversarial, gates estruturados) e integração profunda com ferramentas reais (ClickUp, Google Calendar); exige familiaridade com Claude Code e setup inicial cuidadoso.
README
A tradução para o português deste README ainda está na fila.
claude-plugins
Opinionated Claude Code plugins by Sasha Marchuk — tooling for ticket management, automation, multi-agent rigor, data analysis, and account migration. Free, MIT-licensed, and open to contributions.
Quick install — get all five plugins
In Claude Code:
/plugin marketplace add SashaMarchuk/claude-plugins
/plugin install clickup@sashamarchuk-plugins
/plugin install gevent@sashamarchuk-plugins
/plugin install ultra@sashamarchuk-plugins
/plugin install ultra-analyzer@sashamarchuk-plugins
/plugin install claude-migrate@sashamarchuk-plugins
/reload-plugins
Marketplace name vs. GitHub source:
SashaMarchuk/claude-plugins(GitHubowner/repo) is what you pass tomarketplace addto fetch the manifest.sashamarchuk-pluginsis the marketplace's declared name insidemarketplace.json— that's the suffix you use onplugin install. Anthropic's plugin-manifest validator rejects marketplace names that start withclaude-oranthropic-(reserved for official), hence the rename.
ultra-analyzer and claude-migrate both declare ultra as a dependency, so they pull ultra in automatically on Claude Code v2.1.110+; on older versions the explicit install lines above fetch it. claude-migrate (beta) additionally uses a local Node + Playwright runtime, but only for its byte-exact copy-page verification step. clickup and gevent are independent but share ~/.claude/shared/identity.json for user + teammate data — onboard either one first and the other inherits the roster.
Plugins
| Plugin | What it does |
|---|---|
| clickup | /clickup:create / :onboard / :status / :workspace / :memory — create and manage ClickUp tickets with enforced Connextra user stories, fuzzy list aliases, teammate auto-resolution, duplicate detection, and a two-step onboarding wizard (identity + workspace). |
| gevent | /gevent:schedule / :onboard / :status / :calendar — create/update/cancel Google Calendar events with Google Meet. Always attaches a configurable notes bot, conflict + past-time guards, two-step onboarding (identity + calendar defaults). Shares the teammate roster with clickup. |
| ultra | /ultra:run / :resume — multi-agent swarm with adversarial validation, structured debates, devil's advocate, and anti-AI-slop checks. Tiers --small / --medium / --large / --xl; wraps other skills for maximum-rigor runs. |
| ultra-analyzer (beta) | /ultra-analyzer skill set — rigorous data/corpus pipeline (discover → analyze → validate → synthesize) with resume-able state and /ultra gates at critical boundaries. Source-agnostic: MongoDB, filesystem, PDF, web scrapes, JSON/CSV, SQLite. Requires the ultra plugin. |
| claude-migrate (beta) | /claude-migrate:init / :run / :resume / :progress / :verify — move your chats and projects from one Claude.ai account to another. Parse a data export (or extract live in a browser) → cheap-model value scan → you confirm what migrates → distill each kept chat into one paste-ready first message → re-create projects and seed chats. Always builds a byte-exact, self-contained copy page (the zero-tooling floor); when a pre-authenticated browser is reachable it also runs confirmation-gated automation (seed → await OK → rename → strip). Resume-able state machine with /ultra gates. Requires the ultra plugin + local Node/Playwright. |
Install a single plugin
Assuming /plugin marketplace add SashaMarchuk/claude-plugins was already run:
/plugin install clickup@sashamarchuk-plugins
/plugin install gevent@sashamarchuk-plugins
/plugin install ultra@sashamarchuk-plugins
/plugin install ultra-analyzer@sashamarchuk-plugins # requires ultra
/plugin install claude-migrate@sashamarchuk-plugins # requires ultra + Node/Playwright
/reload-plugins
Your data is preserved across updates
All user state lives outside the plugin directory by design, so /plugin update never wipes what you've collected:
| Location | Contents | Used by |
|---|---|---|
~/.claude/shared/identity.json | User profile + teammate roster (name, email, external_ids, active, last_validated_at) — single source of truth for "who is on the team" | clickup, gevent |
~/.claude/clickup/{config.json, memory.md, drafts/} | Workspace + lists + aliases + learned memory rules + idempotency drafts | clickup |
~/.claude/gevent/config.json | Calendar defaults + always-include attendees (notes bot) + behavior flags | gevent |
~/.claude/skills/ultra/global-lessons.md | Per-run lessons log | ultra |
<your-project>/.planning/ultra-analyzer/<run-name>/ | Config, seeds, findings, state per analyzer run | ultra-analyzer |
<your-project>/.planning/claude-migrate/<run-name>/ | Per-run migration state, parsed chat units, value scores, distilled briefs, and the generated copy page | claude-migrate |
All JSON writes are atomic (tmp + fsync + os.replace) under fcntl.flock on a sentinel file, and readers preserve unknown keys — so clickup and gevent can evolve independently without stepping on each other's fields in identity.json.
This preservation guarantee was verified empirically — a sandboxed rm -rf + recopy of the plugin dir (simulating a worst-case update) left every pre-seeded user file intact.
Migrating from the legacy user-level create-call skill (now published as gevent)
Important: the calendar plugin was renamed from create-call to gevent in this marketplace. If you previously installed create-call as a user-level skill at ~/.claude/skills/create-call/, that legacy skill still wins over the plugin by Claude Code precedence. The rename to gevent doesn't change that — the legacy user-level skill is keyed on the directory name on disk, not the plugin name.
Migration steps:
- Back up your legacy contacts (optional):
cp ~/.claude/skills/create-call/contacts.json /tmp/create-call-contacts.bak.json - Remove the legacy user-level skill:
rm -rf ~/.claude/skills/create-call - Install the plugin under its new name:
/plugin install gevent@sashamarchuk-plugins(aftermarketplace add SashaMarchuk/claude-plugins) - Run onboarding:
/gevent:onboard - The identity wizard offers (as a one-time prompt on first run if it detects a leftover legacy contacts file anywhere in common backup locations) to import your
contacts.jsonentries as a thin seed into~/.claude/shared/identity.json.
The plugin will emit a loud banner on every invocation as long as ~/.claude/skills/create-call/ still exists, so it's hard to miss. (The banner path still points at the legacy directory — that's the shadow source, not the new plugin name.)
Platform support
All plugins are tested on macOS and Linux. Windows is not currently supported — the shared-identity helper uses fcntl.flock for cross-process locking, which is POSIX-only, and the ultra-analyzer / claude-migrate runners use POSIX shell. claude-migrate additionally needs Node 18+ and Playwright (Chromium) for its verify step (the migration itself runs without them; only byte-exact copy-page verification requires them). A Windows fallback (msvcrt.locking) would be a welcome PR.
Troubleshooting install
"Plugin <name> not found in any marketplace" — the marketplace was added but you're using the wrong identifier after @. Inside marketplace.json the declared name is sashamarchuk-plugins. Use that:
/plugin install gevent@sashamarchuk-plugins
Not @SashaMarchuk/claude-plugins (that's the GitHub source, which marketplace add takes).
"Failed to parse marketplace file... impersonates an official Anthropic/Claude marketplace" — you're on an older clone from before 2026-04-23. Pull latest: the marketplace name field has been renamed from claude-plugins to sashamarchuk-plugins. Re-add: /plugin marketplace remove SashaMarchuk-claude-plugins then /plugin marketplace add SashaMarchuk/claude-plugins.
After install, plugins don't show up — run /reload-plugins. Claude Code caches the skill list until reload.
Contributing / feedback
Contributions are welcome — see CONTRIBUTING.md for how to file an issue, propose a plugin, or open a PR. The quickest way to help: open an issue with a concrete example of what broke or what's missing.
License
MIT — see LICENSE. Use it, fork it, ship your own marketplace from it.