smithery-manifest

Generate Smithery deployment artifacts from skills.json, aeon.yml, and mcp-server/package.json.

Updated Jun 2, 2026

Search Tags:#automation #documentation #mcp #registry #manifest #smithery #skills.json

Ready to run

npx skills add https://github.com/Atrium-Hermes/atrium-lighthouse --skill smithery-manifest-atrium-hermes

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: smithery-manifest
Source: https://github.com/Atrium-Hermes/atrium-lighthouse/tree/main/skills/smithery-manifest
Command: npx skills add https://github.com/Atrium-Hermes/atrium-lighthouse --skill smithery-manifest-atrium-hermes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the generation of Smithery + MCP Registry submission artifacts from the current skill catalog, eliminating manual document drafting.

Core Features & Use Cases

Generates smithery-manifest.json and smithery-manifest.md from skills.json, aeon.yml, and mcp-server/package.json.
Produces smithery.yaml to configure Smithery for local or CI usage.
Creates smithery-submission.md for MCP Registry submission, including notes about versioning and deployment details.

Quick Start

Run the smithery-manifest skill to refresh all Smithery artifacts from your local clone and push updated docs to docs/.

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 deployment artifacts from a skills.json catalog?▼

You can auto-generate Smithery deployment artifacts by reading skills.json, aeon.yml, and mcp-server/package.json to produce smithery-manifest.json, smithery.yaml, and smithery-submission.md.

How do I create an MCP Registry submission manifest without manual drafting?▼

Creating an MCP Registry submission manifest is automated by generating smithery-submission.md directly from your current skill catalog, including versioning and deployment details.

Does Smithery manifest generation require a version number from mcp-server/package.json?▼

Smithery manifest generation reads the version directly from mcp-server/package.json to ensure accurate deployment artifacts, while gracefully handling any missing inputs.

What is the best way to configure Smithery for CI usage from a local skill catalog?▼

Configuring Smithery for CI usage is done by generating smithery.yaml from your local skill catalog clone, which sets up the necessary deployment configuration.

What happens if aeon.yml or skills.json inputs are missing during Smithery doc generation?▼

Smithery doc generation gracefully handles missing inputs like aeon.yml or skills.json, ensuring the artifact regeneration process completes without failing.

Can I refresh MCP Registry docs and push them to a docs directory automatically?▼

Refreshing MCP Registry docs is done by regenerating smithery-manifest.json and smithery-submission.md, then pushing the updated documentation directly to your docs directory.