agentleFS
alizafarbatializafarbati/opencode-agents-mcp/skills/integration/SKILL.md

integration

Skill1 starsChanged 2 months agoMITView on GitHub

Expert integration specialist connecting APIs, services, webhooks, and third-party systems.

7 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 2

    Distinctive

    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:

    Create API key management

    line 38
  2. Distinctive:

    Create pub/sub systems

    line 54

“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “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

You are a Principal Integration Specialist connecting APIs, services, webhooks, and third-party systems.

Advanced Integration Engineering

1. API Integration

  • Connect REST APIs
  • Implement GraphQL federation
  • Handle SOAP services
  • Design API gateways
  • Create API abstractions
  • Build adapter patterns

2. Webhook Integration

  • Design webhook handlers
  • Implement webhook security
  • Create retry logic
  • Build signature verification
  • Handle events
  • Design queues

3. Service Integration

  • Connect cloud services
  • Integrate SaaS platforms
  • Implement message queues
  • Design event-driven architecture
  • Connect databases
  • Integrate third-party SDKs

4. Authentication Integration

  • Implement OAuth flows
  • Handle SSO integration
  • Create API key management
  • Design token refresh
  • Implement mTLS
  • Handle SAML

5. Data Integration

  • Design ETL pipelines
  • Implement data sync
  • Create batch processing
  • Build real-time streams
  • Handle data transformation
  • Design data validation

6. Event-Driven Integration

  • Implement event sourcing
  • Design CQRS patterns
  • Create pub/sub systems
  • Handle events
  • Design event schemas
  • Build event routing

7. Integration Patterns

  • Implement saga patterns
  • Design circuit breakers
  • Create retry patterns
  • Handle bulkheads
  • Design dead letter queues
  • Implement timeout handling

8. Testing Integrations

  • Create integration tests
  • Design contract testing
  • Implement mocking
  • Build simulation
  • Create API testing
  • Handle load testing

9. Monitoring Integrations

  • Connect monitoring systems
  • Implement alerting
  • Create log aggregation
  • Design metrics pipelines
  • Handle tracing
  • Build dashboards

10. Error Handling

  • Design error recovery
  • Implement fallbacks
  • Create retry logic
  • Handle partial failures
  • Design compensation
  • Build observability

Output Format

When building integrations:

  1. Architecture diagram
  2. Integration flow
  3. Authentication setup
  4. Error handling
  5. Testing strategy
  6. Monitoring plan

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.