How do I install the Skill Delivery skill?

Run npx skillmds@latest add ashfordeou/skill-delivery in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Skill Delivery safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Skill Delivery?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Skill Delivery free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under Apache-2.

Who published Skill Delivery?

ashfordeOU (@ashfordeou) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Skill Delivery by ashfordeou — Agent Skill

Name: Skill Delivery
Author: ashfordeOU

Skill Delivery

Use when packaging or delivering domain skills over MCP per SEP-2640: check that a skill package carries a conformant SKILL.md (kebab-case name, description), build the skill URI (skill:// namespace and path), and verify the MCP server exposes the delivery model (resources/read and directory listing behind the directoryRead capability). SEP-2640 serves skills as resources and stays an adapter over the agentskills.io content format, an emerging spec not yet stable. Trigger: SEP-2640, skills over MCP, skill delivery, skill URI, MCP resources, directory read, skill packaging, agentskills.io.

ashfordeOU d3f941e 3 files · 8.6 KB Updated Sep 17, 2026

File contents

SEP-2640 Skill Delivery (cross-cutting/sep2640/skill-delivery)

Use when the task is delivering skills over MCP per SEP-2640: package conformance, skill URIs, and server readiness.

Domain quick reference

SEP-2640 (Skills-over-MCP, MCP working group) serves skills as resources: skill:// URIs, resources/read, and directory listing behind the directoryRead capability.
The agentskills.io SKILL.md format remains the canonical content form; SEP-2640 is an adapter layer for discovery and delivery.
A deliverable package carries a conformant SKILL.md at its root: kebab-case name and a description.
Status: the SEP-2640 spec draft is not yet stable, but the Aero Agent Skills delivery server (packages/aero-agent-skills/lib/mcp.js) implements the resources model TODAY over skill:// URIs — reference files under references/ are served too. Same for Aero Agent Roles (role:// URIs in packages/aero-agent-roles/lib/mcp.js).

Workflow

Check the skill package for conformance (SKILL.md present, kebab-case name, description).
Build the skill URI from the namespace and skill path.
Verify the MCP server exposes the delivery model: skill URIs, resources/read, and directory listing. The in-repo servers speak newline-delimited JSON-RPC 2.0 over stdio (zero deps): node packages/aero-agent-skills/bin/aero-agent-skills.js mcp node packages/aero-agent-roles/bin/aero-agent-roles.js mcp Register them with any MCP host (Hermes mcp_servers config, claude mcp add, VS Code/Cursor/Windsurf .mcp.json) and call resources/list + resources/read.
To read a skill's deep files, read the skill body first — the server appends a skill files: footer listing references/, scripts/, assets/ — then fetch a file at skill://///references/.
Pin the SEP-2640 revision and note the emerging status when you build against the external spec; the in-repo server implements the resources shape so it also works as a reference implementation.

Pitfalls

Shipping a package without a root SKILL.md.
A server without directoryRead claiming directory discovery.
Treating SEP-2640 as stable while the spec is still a draft.
Using the MCP layer as the source of truth instead of the SKILL.md files.
Local-path shadowing: inside readResource, never name the local URI variable path (it shadows node:path; use relPath).
Reference reads must stay under the skill dir — reject ...

Behavior contract (gate 3)

The package-conformance, URI, and readiness logic is exercised by the gate 3 contract test: scripts/test_delivery.py against scripts/delivery_logic.py (stdlib unittest, offline). Run: python3 scripts/test_delivery.py

Compliance

SEP-2640 is an open specification; quote with citation and note the status (emerging, not yet stable) per standards-map.yaml.
compliance: STANDARDS-REF, gated: false.

---name: skill-deliverydescription: Use when packaging or delivering domain skills over MCP per SEP-2640: check that a skill package carries a conformant SKILL.md (kebab-case name, description), build the skill URI (skill:// namespace and path), and verify the MCP server exposes the delivery model (resources/read and directory listing behind the directoryRead capability). SEP-2640 serves skills as resources and stays an adapter over the agentskills.io content format, an emerging spec not yet stable. Trigger: SEP-2640, skills over MCP, skill delivery, skill URI, MCP resources, directory read, skill packaging, agentskills.io.license: Apache-2.0---# SEP-2640 Skill Delivery (cross-cutting/sep2640/skill-delivery)Use when the task is delivering skills over MCP per SEP-2640:package conformance, skill URIs, and server readiness.## Domain quick reference- SEP-2640 (Skills-over-MCP, MCP working group) serves skills as resources: skill:// URIs, resources/read, and directory listing behind the directoryRead capability.- The agentskills.io SKILL.md format remains the canonical content form; SEP-2640 is an adapter layer for discovery and delivery.- A deliverable package carries a conformant SKILL.md at its root: kebab-case name and a description.- Status: the SEP-2640 spec draft is not yet stable, but the Aero Agent Skills delivery server (packages/aero-agent-skills/lib/mcp.js) implements the resources model TODAY over skill:// URIs — reference files under references/ are served too. Same for Aero Agent Roles (role:// URIs in packages/aero-agent-roles/lib/mcp.js).## Workflow1. Check the skill package for conformance (SKILL.md present, kebab-case name, description).2. Build the skill URI from the namespace and skill path.3. Verify the MCP server exposes the delivery model: skill URIs, resources/read, and directory listing. The in-repo servers speak newline-delimited JSON-RPC 2.0 over stdio (zero deps): node packages/aero-agent-skills/bin/aero-agent-skills.js mcp node packages/aero-agent-roles/bin/aero-agent-roles.js mcp Register them with any MCP host (Hermes mcp_servers config, `claude mcp add`, VS Code/Cursor/Windsurf .mcp.json) and call resources/list + resources/read.4. To read a skill's deep files, read the skill body first — the server appends a `skill files:` footer listing references/, scripts/, assets/ — then fetch a file at skill://<family>/<pack>/<leaf>/references/<file>.5. Pin the SEP-2640 revision and note the emerging status when you build against the external spec; the in-repo server implements the resources shape so it also works as a reference implementation.## Pitfalls- Shipping a package without a root SKILL.md.- A server without directoryRead claiming directory discovery.- Treating SEP-2640 as stable while the spec is still a draft.- Using the MCP layer as the source of truth instead of the SKILL.md files.- Local-path shadowing: inside readResource, never name the local URI variable `path` (it shadows node:path; use relPath).- Reference reads must stay under the skill dir — reject `..`.## Behavior contract (gate 3)The package-conformance, URI, and readiness logic is exercised by thegate 3 contract test: scripts/test_delivery.py againstscripts/delivery_logic.py (stdlib unittest, offline). Run:python3 scripts/test_delivery.py## Compliance- SEP-2640 is an open specification; quote with citation and note the status (emerging, not yet stable) per standards-map.yaml.- compliance: STANDARDS-REF, gated: false.

Frequently asked questions