ops-publish-to-ametyst

Publishes local .claude skills and loops to Ametyst via the runCompound MCP tool.

1|Updated Nov 25, 2021

Search Tags:#automation #claude skills #mcp #deprecation #sync #skill publishing #ametyst

One-click install

npx skills add https://github.com/rstagi/dotfile --skill ops-publish-to-ametyst-rstagi

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: ops-publish-to-ametyst
Source: https://github.com/rstagi/dotfile/tree/main/.claude/skills/ops-publish-to-ametyst
Command: npx skills add https://github.com/rstagi/dotfile --skill ops-publish-to-ametyst-rstagi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Local .claude skills and loops live only on one machine and can drift out of sync. This Skill publishes them to Ametyst verbatim and flattened, optionally retiring the local copies so Ametyst becomes the single source of truth. ## Core Features & Use Cases - Verbatim Publishing: Pushes local skills and loops to Ametyst without rewriting or transforming their content. - Optional Retire-Local: Moves original local files to deprecated-skills/ instead of deleting them, preserving history. - Use Case: After authoring a new skill in .claude/skills, run this compound to publish it to the Ametyst workspace and archive the local copy so all future runs resolve from Ametyst. ## Quick Start Ask the assistant to run the ops-publish-to-ametyst compound via the runCompound MCP tool to publish your local skills to Ametyst.

Frequently Asked Questions about ops-publish-to-ametyst

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

FAQPage Schema

How do I publish local .claude skills to Ametyst?▼

Call the runCompound MCP tool with compound set to ops-publish-to-ametyst, confirming the match first per the stop-gate convention. The compound publishes skills verbatim and flattened to the Ametyst workspace.

What happens to local skill files after publishing to Ametyst?▼

With the optional retire-local step, original local files are moved to a deprecated-skills directory rather than deleted. This makes Ametyst the source of truth while preserving the local history.

What if runCompound returns a 404 for the skill slug?▼

If slug-to-id resolution is not yet landed and run-by-slug returns 404, call getCompound with the slug ops-publish-to-ametyst to fetch the compound body, then execute it inline as a fallback.

Does publishing to Ametyst rewrite or modify skill content?▼

No, publishing is verbatim and flattened with no rewrite of the skill content. The compound transfers the local skills and loops as-is into the Ametyst workspace.