mcpField
T
technical-integrations

technical-integrations

github.com/vincentkocDevelopment11194 installsUpdated 2d ago
Repository

About technical-integrations

A workflow skill for designing and reviewing external-vendor integrations using existing repository patterns. It supports discovery, RFC-quality proposals, API and SDK plans, and validation and rollout checklists.

Key features

  1. 01Classify integration work modes
  2. 02Inventory existing integration patterns
  3. 03Apply vendor-agnostic principles
  4. 04Draft architecture and RFC proposals
  5. 05Plan execution, validation, and rollout

Use cases

  1. 01Assess patterns before adding a vendor
  2. 02Review an integration RFC
  3. 03Plan API or SDK integration points
  4. 04Prepare rollout checks and identify risks

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/vincentkoc/dotskills --skill technical-integrations

After installing, type/technical-integrationsin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

agents/
openai.yaml
references/
design-and-rfc.md
hunt-and-inventory.md
implementation-plan.md
principles.md
review-checklist.md

Details

From the project README

Technical Integrations

Purpose

Design and review external-vendor integrations using existing internal patterns, with vendor/framework-agnostic workflows for API, RFC, SDK, and rollout planning.

When to use

  • Adding a new third-party/vendor integration.
  • Evolving an existing integration surface without breaking compatibility.
  • Writing or reviewing integration RFCs before implementation.
  • Defining SDK/API integration points and delivery plans.

Workflow

  1. Classify mode: discover, design, review, or implementation-plan.
  2. Run references/hunt-and-inventory.md to gather current integration evidence and patterns.
  3. Use references/principles.md to enforce vendor/framework-agnostic constraints.
  4. For architecture and proposal work, follow references/design-and-rfc.md.
  5. For execution sequencing, follow references/implementation-plan.md.
  6. For QA pass, apply references/review-checklist.md.
  7. Return deliverables with explicit decisions, tradeoffs, and open risks.

Flow

stateDiagram-v2
    [*] --> ClassifyRequest
    ClassifyRequest --> HuntAndInventory
    HuntAndInventory --> ApplyPrinciples
    ApplyPrinciples --> SelectWork
    state SelectWork <<choice>>
    SelectWork --> Deliverables: discovery only
    SelectWork --> DesignAndRFC: architecture or proposal
    SelectWork --> ImplementationPlan: execution sequencing
    SelectWork --> ReviewChecklist: review
    DesignAndRFC --> ReviewChecklist: QA pass in scope
    DesignAndRFC --> Deliverables: proposal only
    ImplementationPlan --> ReviewChecklist: QA pass in scope
    ImplementationPlan --> Deliverables: plan only
    ReviewChecklist --> Deliverables
    Deliverables --> [*]

Inputs

  • Integration objective and target vendor capability.
  • Existing repo patterns (API, SDK, auth, observability, error model).
  • Compatibility constraints (backward compatibility, versioning, rollout policy).
  • Scope (discovery only, RFC draft, implementation plan, or full review).

Outputs

  • Integration inventory and pattern baseline.
  • RFC-quality proposal with options and decision rationale.
  • API and SDK integration design plan.
  • Validation and rollout checklist with unresolved risks.

Comments

Markdown supported