Technical Integrations

What it does

When your agent uses it

• Tasks that involve Third-party API integration

Example prompts

• “/technical-integrations”

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

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

What it can do on your machine

Read from SKILL.md and the folder at commit b83ca13. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  No scripts in the folder and no shell commands in SKILL.md (its code samples are mermaid).

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  No URLs in SKILL.md.

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names no API keys, tokens, secrets or passwords.

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Technical Integrations loads about 625 tokens when it runs, and up to ~1.7k if it reads all its reference files. Until then it costs about 42 tokens; SKILL.md has 168 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~42

When it runs · the whole SKILL.md, loaded when a task matches

~625

With references · SKILL.md plus every file in references/, read only if the agent opens them

~1.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from vincentkoc/dotskills at commit b83ca13, republished under its MIT licence (© vincentkoc). 168 words, ~625 tokens.

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

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 --> [*]

© vincentkoc, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 7 other files (references, assets) in skills/technical-integrations of vincentkoc/dotskills.

• SKILL.md
• agents/openai.yaml
• assets/icon.jpg
• references/design-and-rfc.md
• references/hunt-and-inventory.md
• references/implementation-plan.md
• references/principles.md
• references/review-checklist.md

Open the folder on GitHubat commit b83ca13