/ops-publish-to-ametyst
Publish local .claude skills/loops to Ametyst — verbatim, flattened, no brain rewrite; optional retire-local (MOVE originals to deprecated-skills/, never delete) makes Ametyst the source of truth.
Claude Code
$ npx -y skills add ratel-ai/ratel --skill ops-publish-to-ametyst --agent claude-code
Codex
$ npx skills add ratel-ai/ratel --skill ops-publish-to-ametyst -a codex -y
Cursor
$ npx skills add ratel-ai/ratel --skill ops-publish-to-ametyst -a cursor -y
Gemini CLI
$ npx skills add ratel-ai/ratel --skill ops-publish-to-ametyst -a gemini-cli -y
GitHub Copilot
$ npx skills add ratel-ai/ratel --skill ops-publish-to-ametyst -a github-copilot -y
OpenCode
$ npx skills add ratel-ai/ratel --skill ops-publish-to-ametyst -a opencode -y
Windsurf
$ npx skills add ratel-ai/ratel --skill ops-publish-to-ametyst -a windsurf -y
SKILL.md
ops-publish-to-ametyst.SKILL.mdname: ops-publish-to-ametyst description: "Publish local .claude skills/loops to Ametyst — verbatim, flattened, no brain rewrite; optional retire-local (MOVE originals to deprecated-skills/, never delete) makes Ametyst the source of truth."
<!-- ametyst-managed: sync-skills -->
This is a pointer to the Ametyst compound `ops-publish-to-ametyst` — the real compound lives in the Ametyst workspace, not in this file.
To run it, call the `runCompound` MCP tool with compound="ops-publish-to-ametyst" (present the match and get confirmation first, per the getCompound/getLoop stop-gate convention).
Fallback: if run-by-slug returns 404 (slug→id resolution is not landed yet), call `getCompound` with the slug "ops-publish-to-ametyst" to fetch the body, then execute it inline.
Context engineering for AI agents. ~80% fewer tokens. Fix tool overload. Skills and memory with in-process BM25 and semantic retrieval. Progressive Disclosure. No vector DB.
Other skills on ratel.
More skills from other plugins.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
ask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
Questions about ops-publish-to-ametyst.
- Which coding agents can use ops-publish-to-ametyst?
- ops-publish-to-ametyst installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.

