Skip to main content

Publishing a skill

Skills are the high-leverage layer of bank2ai: write once, work against every compliant bank server. Here's how to ship one.

Prerequisites​

  • A working skill (a SKILL.md plus any supporting prompts/resources).
  • A clear declaration of which bank2ai tools the skill needs.
  • A demo or test against bank2ai-demo showing the skill behaves correctly with the reference server.

Package as a Claude Code plugin​

bank2ai-budgeting-helper/
├── plugin.json
└── SKILL.md

Example plugin.json:

{
  "name": "bank2ai-budgeting-helper",
  "version": "0.1.0",
  "description": "Compare spending against budget targets and flag overruns.",
  "type": "skill",
  "requires": [
    "bank2ai/0.1",
    "bank2ai:transactions",
    "bank2ai:get-transactions-summary",
    "bank2ai:get-categories"
  ],
  "homepage": "https://github.com/your-org/bank2ai-budgeting-helper"
}

The requires field declares both the spec version and the specific tools your skill needs. Installers can warn users whose currently installed server doesn't register all of them.

Submit to the registry​

Same flow as servers, fork bank2ai/marketplace, add an entry, open a PR.

Skill review checklist​

  • Tool-only dependencies. The skill works against any compliant bank2ai server, not just one bank.
  • Honest in requires. It declares every tool it actually uses, no more.
  • Confirms before executing. If the skill triggers transfers, it always goes through prepare-transfer first and surfaces the prepared item to the user.
  • Tolerates unknown fields. Doesn't break when a server returns extras on Account / Transaction / Recipient.
  • Localized prompts. If the skill assumes a locale, it says so up front (and ideally is structured so other locales can be added).

See Build an agent skill for the full design guidance.