Skip to main content
This recipe builds spend-export from scratch — a skill that lets an agent pull a structured CSV of spend data for a given account and date range. The skill follows the same scaffold used by every package in the OSS Cathedral. Audience: contributors who want to author and publish a new @glideco/* skill.

Prerequisites

Steps

1. Scaffold the skill package

This creates packages/skills/spend-export/ with:

2. Write the SkillManifest

Validate:

3. Define input/output schemas

4. Write the policy template

The policy template is the minimum AgentPolicyEnvelope a principal must grant before this skill can execute. It is advisory — the gateway always checks the actual live envelope at call time.

6. Write the skill entry point

7. Write the smoke test

Run:

Run it

Expected output:

Extend it

  • Add a json format branch to run() that uploads a JSONL file instead of CSV.
  • Add a maxRows cap and return a truncated: true flag in the output when hit.
  • Wire the skill into the MCP gateway by registering it in apps/mcp/src/skills/registry.ts.
  • Publish under @glideco/skill-spend-export using node scripts/publish-glide-skill.mjs spend-export.
  • Add an anomaly heuristic that fires when the exported row count exceeds 2× the account’s 30-day average.

Source

github.com/darshanbathija/axtior-neobank/tree/main/examples/build-a-skill-spend-export

Reading list