Skill Evolution Api logo

Skill Evolution Api

Organization
IAPro-Community
skill-evolution-api

Use for WhatsApp automation with Evolution API, including instance lifecycle, QR pairing, inbound and outbound messages, webhooks, consent, tenant isolation, queues, idempotency, rate limits, retries, audit logs, and reliable delivery.

Overview

PublisherIAPro-Community
RepositoryOrquestrador-Maestro
Skill nameskill-evolution-api
Stars
63
Forks
11
Bundled files
Instructions only
LicenseApache-2.0
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by IAPro-Community on GitHub. Read the source before you install it.

Installation

Install the Skill Evolution Api AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/IAPro-Community/Orquestrador-Maestro/tree/v1/codex/skills/skill-evolution-api
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/IAPro-Community/Orquestrador-Maestro.git /tmp/Orquestrador-Maestro
mkdir -p .claude/skills
cp -r /tmp/Orquestrador-Maestro/codex/skills/skill-evolution-api .claude/skills/skill-evolution-api
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Skill Evolution Api in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Skill Evolution Api on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Skill Evolution Api is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Evolution API

Use this skill when integrating WhatsApp through Evolution API. Treat every message as sensitive customer communication.

Core Workflow

  1. Confirm the tenant, WhatsApp account owner, business purpose, user consent model, and allowed message categories.
  2. Keep Evolution API keys, webhook secrets, and instance credentials server-side only.
  3. Model each instance as tenant-owned state with lifecycle, QR pairing state, webhook status, heartbeat, and disconnect reason.
  4. Queue outbound sends. Apply per-instance, per-tenant, and per-contact rate limits before enqueueing.
  5. Assign every outbound request a stable idempotency key based on tenant, instance, recipient, template or body hash, and campaign or workflow ID.
  6. Treat webhooks as at-least-once delivery. Verify signature when available, dedupe by provider message ID, and make handlers idempotent.
  7. Persist delivery, read, inbound, disconnect, reconnect, and pairing events as append-only state transitions.
  8. Redact message bodies in logs unless a support or audit policy explicitly requires short-lived encrypted retention.
  9. Surface recoverable admin states: QR expired, disconnected, webhook failing, send queued, send failed, rate limited, and consent missing.

Current API Boundary

  • Target Evolution API v2+ and use the instance's documented base URL plus the apikey header.
  • Common v2 routes include POST /instance/create and POST /message/sendText/{instanceName}; verify the exact route in the deployed instance's OpenAPI/docs before coding because route shapes can differ between v1 and v2.
  • Starting with Evolution API v2.4.0, self-hosted instances require activation/licensing before business endpoints serve traffic. Add license status/activation to deployment readiness checks and surface 503 activation failures distinctly from WhatsApp failures.

Consent and Compliance

  • Require explicit opt-in before sending non-transactional messages.
  • Store consent source, timestamp, contact identity, tenant, scope, and revocation timestamp.
  • Stop queued campaign or automation messages immediately when consent is revoked.
  • Keep templates, campaign labels, and operator identity attached to sends for audit.

Minimal Data Model

  • whatsapp_instances: tenant ID, owner ID, instance name, status, QR state, webhook status, last heartbeat, disconnect reason.
  • whatsapp_contacts: tenant ID, normalized number, profile name, consent state, consent scope, last inbound time.
  • message_events: tenant ID, instance ID, provider message ID, idempotency key, direction, status, retry count, error class, timestamps.
  • message_threads: tenant ID, contact ID, assignment state, last message time, unread count.

Verification

  • Test QR pairing, reconnect, disconnect, outbound queueing, duplicate outbound retry, inbound webhook dedupe, revoked consent, and rate-limit behavior.
  • Confirm API keys and message bodies are absent from client bundles and normal logs.
  • Replay the same webhook payload twice and verify only one business effect occurs.

Official References

Related Skills

  • skill-saas-admin-dashboard
  • skill-unified-analytics
  • skill-security-hooks

Frequently asked questions

What does the Skill Evolution Api AI skill do?

Use for WhatsApp automation with Evolution API, including instance lifecycle, QR pairing, inbound and outbound messages, webhooks, consent, tenant isolation, queues, idempotency, rate limits, retries, audit logs, and reliable delivery.

Why use Skill Evolution Api on TypingMind?

Because you install it once and use it with any model. Skill Evolution Api is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Skill Evolution Api in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/IAPro-Community/Orquestrador-Maestro/tree/v1/codex/skills/skill-evolution-api. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Skill Evolution Api?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Skill Evolution Api?

As many as you like. As long as a model supports skills, you can use Skill Evolution Api with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Skill Evolution Api AI skill free?

Yes. It is published on GitHub by IAPro-Community under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇