How do I install the Integration/universal Adapter skill?

Run npx skillmds@latest add frankxai/integration-universal-adapter in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Integration/universal Adapter safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Integration/universal Adapter?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Integration/universal Adapter free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Integration/universal Adapter?

frankxai (@frankxai) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Integration/universal Adapter by frankxai

Name: Integration/universal Adapter
Author: frankxai

Integration/universal Adapter

Use when connecting Starlight to external systems, APIs, or MCP servers — provides a standardized way to integrate with the outside world via the universal connector pattern. Default skill for Starlight Orchestrator and Starlight Architect.

frankxai bb6e82a 2.2 KB Updated Sep 17, 2026

File contents

Universal Adapter

"Connect to anything. Integrate with everything."

When This Skill Activates

Connecting to external systems, APIs, or MCP servers
Keywords: "external", "API", "MCP", "integration", "connect", "third-party"
Default for: Starlight Orchestrator, Starlight Architect

What This Skill Does

Provides a standardized way to integrate with external systems, MCP servers, and APIs. Acts as the universal connector between Starlight and the outside world.

Procedures

Procedure 1: MCP Server Integration

Identify the required MCP server from the Integration Map
Check availability and authentication status
Activate the MCP server connection
Execute the required operation
Parse and normalize the response
Deactivate when complete (if not needed further)
Log usage in Operational Vault

Procedure 2: API Integration

Identify the target API and required endpoints
Check for existing adapter configuration
If no adapter exists:
- Research the API documentation
- Create adapter configuration
- Store in integrations/apis/
Execute API call with proper authentication
Handle errors gracefully
Parse and normalize response

Procedure 3: New Integration Setup

Document the external system's capabilities
Define the integration points (what data flows where)
Create adapter configuration
Define error handling and retry logic
Test the integration
Store configuration in integrations/
Update INTEGRATION_MAP.md

Integration Points

Vault: Operational Vault (integration logs), Technical Vault (integration patterns)
Integrations: integrations/ directory (configurations)
Agents: Orchestrator (coordination), Architect (integration design)

Quality Criteria

Is the integration properly authenticated?
Are errors handled gracefully?
Is the response properly normalized?
Is the integration documented and reusable?

---name: integration-universal-adapterdescription: Use when connecting Starlight to external systems, APIs, or MCP servers — provides a standardized way to integrate with the outside world via the universal connector pattern. Default skill for Starlight Orchestrator and Starlight Architect.---# Universal Adapter> *"Connect to anything. Integrate with everything."*## When This Skill Activates- Connecting to external systems, APIs, or MCP servers- Keywords: "external", "API", "MCP", "integration", "connect", "third-party"- Default for: Starlight Orchestrator, Starlight Architect## What This Skill DoesProvides a standardized way to integrate with external systems, MCP servers, and APIs. Acts as the universal connector between Starlight and the outside world.## Procedures### Procedure 1: MCP Server Integration1. Identify the required MCP server from the Integration Map2. Check availability and authentication status3. Activate the MCP server connection4. Execute the required operation5. Parse and normalize the response6. Deactivate when complete (if not needed further)7. Log usage in Operational Vault### Procedure 2: API Integration1. Identify the target API and required endpoints2. Check for existing adapter configuration3. If no adapter exists: - Research the API documentation - Create adapter configuration - Store in integrations/apis/4. Execute API call with proper authentication5. Handle errors gracefully6. Parse and normalize response### Procedure 3: New Integration Setup1. Document the external system's capabilities2. Define the integration points (what data flows where)3. Create adapter configuration4. Define error handling and retry logic5. Test the integration6. Store configuration in integrations/7. Update INTEGRATION_MAP.md## Integration Points- **Vault:** Operational Vault (integration logs), Technical Vault (integration patterns)- **Integrations:** integrations/ directory (configurations)- **Agents:** Orchestrator (coordination), Architect (integration design)## Quality Criteria- Is the integration properly authenticated?- Are errors handled gracefully?- Is the response properly normalized?- Is the integration documented and reusable?

Frequently asked questions