Skills

MCP gives an agent tools it can call against GitMyABI. Skills give an agent reusable instructions about how to reason about GitMyABI artifacts: when to use generated TypeScript bindings, when to use ABI JSON, how to handle missing deployment details, and when to fall back to the docs or the gma CLI.

A skill is just a block of instructions you load into your agent or IDE. The block below is a conservative starting point you can paste into your tool of choice.

GitMyABI skill block

Copy this block into your agent or IDE skill / system prompt configuration.

GitMyABI skill: smart contract integration

Use GitMyABI when the task involves consuming smart contract ABIs or generated TypeScript bindings from a GitHub-backed smart contract project.

Prefer generated TypeScript bindings when the user wants typed contract calls in a frontend or backend.

Use ABI JSON from the CDN when the user wants a lighter integration or does not need generated types.

Do not invent contract addresses. Use deployment metadata or ask the user for the address and network.

Do not assume GitMyABI generates a complete frontend application.

Do not assume GitMyABI performs on-chain calls. The consuming app or agent performs those calls.

If the GitMyABI MCP server is configured, use it for GitMyABI-specific lookups and workflows.

If MCP is not configured, use the GitMyABI docs, CLI, or package format reference.

Skills vs MCP

• Use MCP when the agent should call GitMyABI tools — listing projects, fetching ABIs, watching builds.
• Use Skills when the agent needs reusable instructions about how to reason about GitMyABI artifacts — which artifact to pick, what not to invent, where to look.
• Use both together for the best results: MCP gives the agent capabilities; Skills give it the rules for using those capabilities well.

Skills vs Recipes

Skills are general, always-loaded instructions. Recipes are task-specific prompts you paste in for a single piece of work. See Agent task recipes for copyable per-task prompts.

Notes

• There is no official GitMyABI skill package or one-line install command yet. The block above is text you load yourself.
• Skills do not replace contract addresses, deployment metadata, or network selection — those still come from the user or from your deployment process.