smithery-manifest

Generate Smithery manifest and MCP Registry submission documents from the Aeon skill catalog.

Updated Jun 3, 2026
One-click install
npx skills add https://github.com/swarm-ai-research/aeon --skill smithery-manifest-swarm-ai-research
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: smithery-manifest
Source: https://github.com/swarm-ai-research/aeon/tree/main/skills/smithery-manifest
Command: npx skills add https://github.com/swarm-ai-research/aeon --skill smithery-manifest-swarm-ai-research

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the bottleneck of producing Smithery + MCP Registry submission artifacts by automatically generating the needed manifest and submission documents from the current skill catalog and Aeon MCP server configuration.

Core Features & Use Cases

  • Read inputs: skills.json (canonical catalog), aeon.yml (enabled flags), mcp-server/package.json (version), README.md (first paragraph) to build Smithery artifacts.
  • Generate outputs: docs/smithery-manifest.json (server.json schema), docs/smithery.yaml (Smithery config for stdio-based server), docs/smithery-submission.md (paste-ready submission form).
  • Ensure up-to-date discovery: Keeps Smithery and MCP Registry listings aligned with the live skill catalog; simplifies onboarding and operator workflow.

Quick Start

Regenerate the Smithery + MCP submission artifacts from the current skill catalog.

Frequently Asked Questions about smithery-manifest

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I auto-generate Smithery and MCP Registry submission artifacts from a skill catalog?

To auto-generate Smithery and MCP Registry submission artifacts, process inputs like skills.json, aeon.yml, and mcp-server/package.json to output server.json, smithery.yaml, and a Markdown submission document. This keeps your listings aligned with the live skill catalog.

What files do I need to prepare a Smithery manifest for a stdio-based MCP server?

Preparing a Smithery manifest requires skills.json for the canonical catalog, aeon.yml for enabled flags, mcp-server/package.json for the version, and README.md for the description. These inputs produce the server.json schema and smithery.yaml config for a stdio-based server.

Does generating a Smithery submission require an API key at runtime?

Generating a Smithery submission does not require an API key at runtime. The process outputs a smithery.yaml configuration for a stdio-based server that operates without API key dependencies, simplifying operator onboarding and workflow.

How do I keep MCP Registry listings aligned with an updated Aeon skill catalog?

Keep MCP Registry listings aligned with an updated Aeon skill catalog by regenerating manifest artifacts whenever the catalog changes. Reading the current skills.json and aeon.yml ensures the output server.json and submission documents reflect the latest enabled skills.

What is the best way to create a paste-ready MCP Registry submission document?

The best way to create a paste-ready MCP Registry submission document is to extract the first paragraph from README.md and the version from package.json, generating a Markdown file that adheres to the MCP Registry server schema and Smithery expectations.