find-skillslisted
Install: claude install-skill robotostudio/turbo-start-web-agent
# Installing third-party skills safely
A skill is not documentation — it's instructions an agent will *follow*.
Installing one from outside this project is the same trust decision as adding
a dependency, and deserves the same review: read the whole thing before you
run any part of it. An unreviewed `SKILL.md` is arbitrary instruction
injection with a friendly YAML header.
## Provenance convention
- Skills authored **for this project** live under `.agents/skills/<name>/` with
no special marking — `compose-page`, `sync-changes`, and this skill are all
project-authored. They are not listed in `skills-lock.json`.
- Skills installed **from elsewhere** also live under `.agents/skills/<name>/`
(this directory doubles as both Replit's project-skill location and the
agentskills.io spec's skill directory, so one folder serves both), but they
must additionally:
1. Carry `metadata.source` in their own frontmatter naming the origin repo,
e.g. `metadata: { source: "https://github.com/org/repo" }` — the spec's
`metadata` field is exactly this: an open string map for facts the spec
itself doesn't define.
2. Have a matching entry in `skills-lock.json` at the repo root (see below).
A skill under `.agents/skills/` with no `skills-lock.json` entry and no
`metadata.source` should be treated as unreviewed, regardless of how it got
there.
## Installing one
1. **Read it in full** before copying anything in — the `SKILL.md` body, and
every file under its `scripts