Any agent with skills
Install the Cloudy agent skill in OpenCode, Antigravity or any agent that reads SKILL.md, with skills.sh or the CLI.
Most coding agents now read skills: a SKILL.md file in a known folder. The Cloudy skill works in any of
them, as long as the agent can run commands.
Install with skills.sh
npx skills add Cloudtifact/pluginsIt finds the cloudtifact skill and asks which agents to install it for.
Install with the CLI
npm i -g usecloudy
cloudy skill installThis writes cloudtifact/SKILL.md into the skills folder of every agent it finds on your machine:
~/.claude/skills, ~/.codex/skills, ~/.agents/skills, ~/.cursor/skills and
~/.config/opencode/skills.
Each copy carries the version of the CLI that wrote it, and the CLI keeps it current: after an update the next
command rewrites the copies that are out of date, so the agent never follows advice from a CLI you no longer have.
To check by hand, run cloudy skill status (or cloudy skill install --check), which lists each copy, the
version it was written with, and exits 1 when one is behind. cloudy skill install refreshes them.
What the skill does
- When someone wants a page, report, dashboard or prototype to look at or share, the agent publishes it with
cloudy publishand gives the link, instead of a throwaway preview. - Before editing published docs, it reads the open comments (
cloudy comments --toon). - After a fix, it replies with what changed and resolves the thread. If it disagrees or needs a decision, it replies and leaves the thread open.
- Before building something interactive, it checks what the space allows (
cloudy settings --space <id>,cloudy capabilities --space <id>) and what the space's database can't do, instead of finding out when a visitor's form fails. - Spaces are private: only members of your workspace can open them. The agent makes one public only when you ask
for a public link, with
--publicon the first publish orcloudy settings --space <id> --visibility publiclater (--visibility privatemakes it private again). Space admins only. - It never prints or commits your sign-in token.
The full text is in the plugin repo.