technical-integrations
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
More from vincentkoc/dotskills
technical-documentation
Build and review high-quality technical docs as well as agent instruction files in your repository.
121technical-deslop
Remove AI-style noise from staged and branch diffs while preserving behavior and repository style.
67technical-skill-finder
Mine coding agent logs (Codex/Cursor/session histories and similar telemetry) to discover high-value candidate skills, then draft structured skill creation/reuse recommendations.
62opik-optimizer
Optimize LLM prompts, tools, and agents in Opik using standardized optimizer workflows (prompt optimization, tool optimization, and parameter tuning), dataset/metric wiring, and result interpretation.
36example-skill
Template skill for repository authors; excluded from public publishing.
34opik-integrations-auditor
Audit, compare, and document Opik integrations across Python SDK, TypeScript SDK, and OTEL/API backend. Use when adding a new integration, reviewing an existing one, or generating first-pass integration docs and gap analysis.
33