vincentkoc/dotskills

technical-integrations

Hunt existing integration patterns and design vendor/framework-agnostic API, RFC, SDK, and integration plans for new external vendor integrations.

First seen Feb 17, 2026

Installation

$ npx skills add vincentkoc/dotskills --skill technical-integrations

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from vincentkoc/dotskills · top by installs.

npx skills add vincentkoc/dotskills

Browse all from vincentkoc/dotskills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 102
License LICENSE
Default branch main
Open issues 4
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

LicenseMIT
More metadata
source
https://github.com/vincentkoc/dotskills

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,794 B
  • docs SUMMARY.md 176 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 91 installs

SKILL.md

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.

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.