Automated summary
Connects a Bora Automatizar client's existing tools (spreadsheets, CRM, e-commerce, scheduling, payments) to automated flows, with pipeline orchestration and optional deployment.
Strengths
- Decision table mapping each briefing need to the right sub-integration (Sheets, RD Station, Pipedrive, ClickUp, Stripe, Shopify, Calendly, generic webhook).
- Ready-made assets: paste-ready mcp-config.json files, per-API Python clients, four reference orchestration YAMLs, a smoke_test.py validator and a Coolify deployment guide.
- Explicit security baseline: tokens kept outside git, HMAC-validated webhooks (401 otherwise), enforced HTTPS, and least-privilege keys such as Stripe restricted keys.
- Deliberately scoped: WhatsApp is excluded and redirected to Bora Automatizar's own system.
Limitations
- Assumes access to the Bora Automatizar internal repo and its subfolder layout plus the client's real credentials, so it is not usable standalone.
- Content is Portuguese-only and tied to the Brazilian SMB tool ecosystem (RD Station, Pipedrive, Coolify).
- Little guidance on data mapping between systems, per-provider rate limits, or error handling beyond the orchestrator's retry/condition steps.
Use it when a client already runs a CRM, spreadsheet, store or calendar and needs it wired into an automated flow or internal alerting.
Do not use it for WhatsApp messaging (handled by Bora Automatizar's own system) or for greenfield projects with no existing tool to connect.
Security analysis
CautionThis is a legitimate integration/deployment guide. It contains no destructive, obfuscated, or exfiltration instructions and includes security best practices, but its use of Bash, Docker, network APIs, webhooks, and client credentials makes it a caution-level skill that should be reviewed in its execution context.
- •Declares Bash and instructs running local Python smoke tests plus Docker/Coolify deployment; executing these scripts and deployments can affect external systems if untrusted or misconfigured.
- •Handles client API credentials/tokens for multiple third-party services; requires strict scoping and secure storage, though the skill advises ~/.credentials and least privilege.
- •Generic webhook and notification integrations can send client data to external endpoints; HMAC validation is recommended but must be enforced in implementation.
- •Skill directs the agent to run Python scripts (orquestrador/smoke_test.py) and to deploy services via Docker Compose/Coolify using the Bash tool; legitimate but powerful execution surface not verifiable from the manifest alone
- •Workflow touches live production credentials (Stripe, Shopify, RD Station, Pipedrive) and public webhooks; instructions rely on the agent correctly following the stated hygiene rules (tokens only in ~/.credentials/, HMAC validation, HTTPS, restricted keys)
- •References multiple subdirectories, config files and scripts (mcp-config.json, deploy/, orquestrador/fluxos/) that are not included in the provided content, so their actual behavior cannot be audited
Examples
O cliente já usa RD Station. Monta a integração pra todo lead novo cair numa planilha do Sheets e avisar o time comercial no Slack.Quando um pedido da Shopify passar de R$ 1.000, cria uma task no ClickUp e dispara alerta no Discord. Isso precisa rodar 24/7, sobe com o deploy.Consolida assinaturas do Stripe e agendamentos do Calendly num fluxo só usando o orquestrador, e roda o smoke_test.py antes de entregar.name: ba-integracoes description: Conecta um cliente Bora Automatizar (via Eter) a ferramentas que ele já usa — Sheets, ClickUp, Notion, Trello, Stripe, Shopify, Calendly, RD Station, Pipedrive, webhook genérico — e orquestra fluxos entre elas. Use quando o briefing do cliente apontar um CRM/ERP/planilha existente para conectar, quando pedir "manda um alerta no Slack/Discord/Telegram quando X acontecer", "cria task automática", "consolida pedido/pagamento em um lugar só", ou "isso precisa rodar 24/7 num servidor". Não cobre WhatsApp — isso é o sistema próprio do Bora Automatizar. allowed-tools: Read Write Bash user-invocable: true
/ba-integracoes — Conectar sistemas existentes do cliente
Você está agora em modo integração. O cliente do Eter já tem alguma ferramenta rodando (CRM, planilha, e-commerce, agenda) e o trabalho é conectar essa ferramenta ao fluxo automatizado — não substituí-la.
WhatsApp fica fora deste pacote. O Bora Automatizar já tem sistema próprio para isso — não reconstrua aqui. Alertas internos (time, sócios) usam notificacoes/ (Slack/Discord/Telegram).
Como decidir o que usar
| Cenário do briefing | Use |
|---|---|
| "Registra lead em algum lugar" e não tem CRM | google-sheets/ |
| "Já uso RD Station" (CRM mais comum em PME BR) | rd-station/ |
| "Já uso Pipedrive" | pipedrive/ |
| "Organizar tasks do time" | clickup/ (completo) ou trello/ (simples) |
| "Wiki / base de conhecimento" | notion/ |
| "Cobrança / assinatura mensal" | stripe/ |
| "Loja online" | shopify/ |
| "Agendamento de reunião pública" | calendly/ |
| "Ferramenta que não está na lista" | webhook-generico/ |
| "Notificar time/sócios de evento" (não é o cliente final) | notificacoes/ (Slack/Discord/Telegram) |
| "Precisa combinar 2+ integrações num pipeline" | orquestrador/ — YAML com etapas, retry, condição |
| "Isso precisa rodar sozinho, sempre" | deploy/ — Docker Compose + Coolify |
Como trabalhar
- Leia o briefing do cliente — qual ferramenta ele já usa hoje (se usa).
- Abra o
README.mdda subpasta correspondente — cada integração MCP (Sheets/ClickUp/Notion/Trello) temmcp-config.jsonpronto pra colar; cada integração via API (Stripe/Shopify/Calendly/RD/Pipedrive) tem cliente Python +exemplos.md/funcoes-prontas.md. - Se o fluxo cruza 2+ integrações (ex: Shopify → Slack → alerta se pedido grande), monte ou adapte um YAML em
orquestrador/fluxos/— tem 4 prontos pra usar de referência. - Antes de considerar pronto, rode
python orquestrador/smoke_test.pycom as credenciais do cliente configuradas — valida que cada integração habilitada responde. - Se o cliente quer isso rodando 24/7 (não só sob demanda no Claude Code), suba com
deploy/—INSTALACAO-COOLIFY.mdtem o passo a passo guiado.
Segurança
- Tokens só em
~/.credentials/(fora do git). Nunca hardcoded. - Webhook sempre com secret HMAC validado — sem assinatura válida, 401.
- HTTPS em qualquer endpoint público.
- Escopo mínimo por integração (ex: Stripe Restricted Key, não Secret Key).
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/bora-automatizar-integrations-mscreznf/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/bora-automatizar-integrations-mscreznf' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/bora-automatizar-integrations-mscreznf/download' --output '.skill-downloads/bora-automatizar-integrations-mscreznf/SKILL.md.part' && mv '.skill-downloads/bora-automatizar-integrations-mscreznf/SKILL.md.part' '.skill-downloads/bora-automatizar-integrations-mscreznf/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
Tools declared by the author (check availability in your agent): Read Write Bash
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/bora-automatizar-integrations-mscreznf/SKILL.md' && test -s '.skill-downloads/bora-automatizar-integrations-mscreznf/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/ba-integracoes' && cp -R '.skill-downloads/bora-automatizar-integrations-mscreznf' '.claude/skills/ba-integracoes'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/bora-automatizar-integrations-mscreznf'openskills read 'bora-automatizar-integrations-mscreznf'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/bora-automatizar-integrations-mscreznf/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.