create-integration

Create custom EvoNexus integration SKILL.md files for external APIs.

520|175|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/evolution-foundation/evo-nexus --skill create-integration-evolution-foundation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-integration
Source: https://github.com/evolution-foundation/evo-nexus/tree/main/.claude/skills/create-integration
Command: npx skills add https://github.com/evolution-foundation/evo-nexus --skill create-integration-evolution-foundation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

EvoNexus users need a consistent way to connect new external tools and APIs to the agent workspace so agents can use them reliably, but many integrations aren’t available out of the box.

Core Features & Use Cases

  • Creates a custom integration skill: Generates a new .claude/skills/custom-int-{slug}/SKILL.md entry that agents can discover and use.
  • Guides integration setup: Collects slug, display name, description, category, required environment variable keys, optional auth method, and optional base URL.
  • Enforces uniqueness and organization: Ensures the chosen slug doesn’t conflict with existing core or custom integrations to avoid duplicate/ambiguous integrations.
  • Supports agent-ready documentation: Produces integration metadata so the dashboard and agents can present it as “Not configured” until env keys are set.

Quick Start

Ask the assistant to create an integration for your external service by specifying the display name, slug, category, required env keys, and how authentication works, so it generates the custom integration’s SKILL.md for your workspace.

Frequently Asked Questions about create-integration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add a custom API integration to my agent workspace?

To add a custom API integration, you specify a unique kebab-case slug, display name, category, and required environment keys. This generates a SKILL.md file that agents can discover and use to call the external service.

Can I connect external services like payments or CRM tools that aren't pre-built into the workspace?

Yes, you can connect unsupported external services like payments, CRM, or messaging apps. The integration setup collects metadata and authentication details to wire up the new tooling for workspace operations.

What do I need to set up a custom integration for an external API?

You need a unique kebab-case slug, display name, description, category, and required environment variable names. You can optionally provide an authentication method and a base URL to complete the setup.

How does the workspace handle authentication for custom integrations?

Authentication for custom integrations is handled by specifying an optional auth method during setup. The system requires environment variable keys to store credentials, displaying the integration as Not configured until those keys are set.

What happens if I try to create a custom integration with a slug that already exists?

The integration setup enforces uniqueness by checking the chosen slug against existing core and custom integrations. This prevents duplicate or ambiguous entries from being created in the workspace.

Are there limitations to the custom integrations I can create for agents?

Custom integrations require a unique slug and manual environment key configuration before they function. They only produce a SKILL.md file for agent discovery, meaning the external API must handle its own operational logic.