<< All versions
Skill v1.0.2
currentAutomated scan100/100vincentkoc/dotskills/technical-integrations
~3 modified
──Details
PublishedOctober 20, 2026 at 04:42 PM
Content Hashsha256:e5d12ccb2e5609cc...
Git SHAc806ab3e846d
Bump Typepatch
──Files
Files (1 file, 2.5 KB)
SKILL.md2.5 KBactive
SKILL.md · 67 lines · 2.5 KB
version: "1.0.2" name: technical-integrations description: Hunt existing integration patterns and design vendor/framework-agnostic API, RFC, SDK, and integration plans for new external vendor integrations. license: MIT metadata: source: "https://github.com/vincentkoc/dotskills"
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
- Classify mode:
discover,design,review, orimplementation-plan. - Run
references/hunt-and-inventory.mdto gather current integration evidence and patterns. - Use
references/principles.mdto enforce vendor/framework-agnostic constraints. - For architecture and proposal work, follow
references/design-and-rfc.md. - For execution sequencing, follow
references/implementation-plan.md. - For QA pass, apply
references/review-checklist.md. - Return deliverables with explicit decisions, tradeoffs, and open risks.
Flow
mermaid
stateDiagram-v2[*] --> ClassifyRequestClassifyRequest --> HuntAndInventoryHuntAndInventory --> ApplyPrinciplesApplyPrinciples --> SelectWorkstate SelectWork <<choice>>SelectWork --> Deliverables: discovery onlySelectWork --> DesignAndRFC: architecture or proposalSelectWork --> ImplementationPlan: execution sequencingSelectWork --> ReviewChecklist: reviewDesignAndRFC --> ReviewChecklist: QA pass in scopeDesignAndRFC --> Deliverables: proposal onlyImplementationPlan --> ReviewChecklist: QA pass in scopeImplementationPlan --> Deliverables: plan onlyReviewChecklist --> DeliverablesDeliverables --> [*]
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.