Package your skill

Upload one ZIP. Agensi finds every SKILL.md in it, at any depth: one makes a skill, two or more make a skill pack.

The SKILL.md file

Name it SKILL.md and start it with frontmatter. The top SKILL.md must have a name. Give every SKILL.md a description as well: in a pack, the buyer's agent picks a skill by its name and description.

---
name: GEO audit
description: Scores a site's visibility in AI search and lists fixes in priority order.
---

# GEO audit

Instructions for the agent go here.

The upload form also reads summary, version, tags, keywords, use_cases and docs_url from the frontmatter to fill in your listing.

Layouts that work

geo-audit.zip
├── SKILL.md
├── references/scoring-rubric.md
├── scripts/crawl.py
└── templates/report.md

seo-pack.zip
├── README.md              "# SEO Pack" becomes the pack name
├── shared/brand-voice.md  available to every skill in the pack
└── skills/
    ├── audit/SKILL.md
    └── report/SKILL.md

One top folder around everything is fine. A pack doesn't need a SKILL.md at the root; if it has one, that's just one of the included skills. When the agent loads a skill from a pack, it gets that SKILL.md, the other files in its folder, and the shared files outside every skill folder.

What you can include

• Text and code: references, scripts, templates, configs, .env.example. Scripts run in the buyer's session.
• Images and PDFs: allowed, but agents can't read them, because Agensi delivers text files only. Put anything the agent needs in text.
• Executables: fail the File types check (exe, dll, so, dylib, bin, app, dmg, msi, deb, rpm, wasm, class, jar, war).

Limits

Before you upload

• Test the skill with your own agent first. Agensi only serves a listing once it's live.
• Names are unique across Agensi, and a package identical to another creator's is blocked.
• If the upload says the ZIP is damaged, re-create it. Mac system files (__MACOSX folders and ._ files) are ignored.