Install or remove third-party openscience skills from a public git repository. Use when the user says "add this skill <url>", "install skill <url>", or "remove skill <namespace>". The skill runs locally via `openscience skill add|list|remove`, fetches the repo, runs a 6-layer safety gate (regex + server-side Haiku classifier), prompts the user to confirm, then writes the skills to ~/.openscience/installed-skills/ and uploads to the dashboard for cross-machine sync.
93%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
Installs URL-supplied third-party skills into the openscience CLI. The skill itself is a thin wrapper around the bundled openscience skill bash subcommand — when the user expresses install/uninstall intent, invoke openscience skill add|list|remove via the bash tool. The CLI handles fetching, the safety gate, confirmation, on-disk write, and cross-machine sync.
Trigger on user messages like:
Do NOT use this skill for:
openscience learn)bash directly)openscience skill add <git-url>Accepted URL forms:
https://github.com/<owner>/<repo> — default branch, all skills in skills/**/SKILL.mdhttps://github.com/<owner>/<repo>/tree/<ref> — specific ref/taggh:<owner>/<repo> — shorthandgh:<owner>/<repo>@<ref>[/<path>] — shorthand with ref and optional path scopegit+ssh://... / https://gitlab.com/... URLsWhat happens when the user runs add:
skills/<name>/SKILL.md files./api/cli/skill-review for the Layer-3 Haiku classifier (server-side, sandboxed input with canary integrity check).y, writes everything to ~/.openscience/installed-skills/<namespace>/<name>/ and uploads to the dashboard.The <namespace> is derived from the repo name (last URL segment, lowercased).
openscience skill listPrints <namespace>/<name> with a ⚠ marker for any skill the safety gate warned on.
openscience skill remove <namespace> # whole namespace
openscience skill remove <namespace>/<name> # single skill within a namespaceSoft-deletes the cloud record (archived_at set) and removes the on-disk directory.
User: "Install the brainstorming skill from Anthropic's superpowers repo."
You: invoke bash with openscience skill add gh:anthropics/superpowers/skills/brainstorming. Wait for the spinner + confirm prompt. Relay the manifest to the user. Pass through their y/N response.
User: "Uninstall everything in superpowers."
You: invoke bash with openscience skill remove superpowers. Report the count of archived skills.
User: "What's installed?"
You: invoke bash with openscience skill list. Print the output.
The user-facing openscience skill add command runs every install through 6 layers (regex catastrophic-reject, regex classifier-injection-reject, server-side LLM classifier, regex suspicious-warn, user-confirm screen, deferred allowed-tools sandboxing). Don't try to bypass any of these by editing ~/.openscience/installed-skills/ directly — that breaks the cloud-sync invariant. Always go through the bash subcommand.
If openscience skill add reports classifier unreachable, the dashboard backend is down — surface that to the user and stop. Do not retry with a flag that disables the classifier without the user's explicit consent.
thesis/docs/superpowers/specs/2026-05-14-cli-add-skill-from-url-design.mdthesis/docs/superpowers/plans/2026-05-14-cli-add-skill-from-url.md~/.openscience/installed-skills/<namespace>/<name>/SKILL.md (mirror of ~/.openscience/learned-skills/)/api/cli/installed-skills + /api/cli/skill-reviewsynthetic-sciences/openscience
a08e0ad
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.