agentleFS
Sign inStart free
Arcanea-LabsArcanea-Labs/Starlight-Intelligence-System/skills/integration/universal-adapter/SKILL.md

integration/universal-adapter

Skill10 starsChanged 2 months agoMITView on GitHub

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.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Default for: Starlight Orchestrator, Starlight Architect

    line 15
  2. Distinctive:

    Check availability and authentication status

    line 26
  3. Distinctive:

    Check for existing adapter configuration

    line 36
  4. Distinctive:

    If no adapter exists:

    line 37
  5. Distinctive:

    Document the external system's capabilities

    line 47

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

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

Procedure 2: API Integration

  1. Identify the target API and required endpoints
  2. Check for existing adapter configuration
  3. If no adapter exists:
    • Research the API documentation
    • Create adapter configuration
    • Store in integrations/apis/
  4. Execute API call with proper authentication
  5. Handle errors gracefully
  6. Parse and normalize response

Procedure 3: New Integration Setup

  1. Document the external system's capabilities
  2. Define the integration points (what data flows where)
  3. Create adapter configuration
  4. Define error handling and retry logic
  5. Test the integration
  6. 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?

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free