Publish internal or product skills that stay aligned with Tradeics docs structure. Use this page when your team needs a custom skill on top of the official pack.
Principles
- Structure first — mirror official section headings so maintenance is mechanical.
- Link out — skills should point at guides/references, not duplicate full HTTP contracts.
- Version deliberately — bump skill version when REST groups or MCP tool names change.
- Secrets never live in skills — only env var names.
Recommended file layout
tradeics-<name>/
SKILL.md # required frontmatter + instructions
references.md # optional deep links
examples/ # optional prompts / evalsFrontmatter pattern (placeholder)
---
name: tradeics-custom-erp
description: ERP sync patterns for Acme on Tradeics REST V2
---Drafting checklist
| Section | Include |
|---|---|
| When to use | Trigger phrases and out-of-scope cases |
| Sources | Absolute developers.tradeics.com URLs |
| Auth | Pointer to Getting Started → Authentication |
| Domains | Tables like Platform / API skills |
| Safety | Write confirmation rules |
| Eval prompts | 3–5 prompts that prove the skill works |
Review gates
- Does it invent endpoints? Reject.
- Does it conflict with MCP tool conventions? Align names.
- Does it duplicate Best practices? Link instead.