Put a published Skill where your agent can use it. One command installs it, and the same command updates it later. Prerequisites: authenticated paperctl v0.21.0 or later, and a published skill in your organization’s library.
Find the skill
paperctl skill list # every skill in your org's library, with slugs
paperctl skill list --query release # only skills matching "release"--query narrows the list to skills matching the text — useful when the library is big and you know roughly what the skill is called. --json emits the raw list for scripts.
Install it
Pick the target your agent reads. Sync accepts a skill slug (exact match) or a skill id (prefix match), and writes the skill’s rendered SKILL.md to its own folder under the skills directory.
paperctl skill sync <slug> --claude # ~/.claude/skills/<slug>/SKILL.md
paperctl skill sync <slug> --claude --local # ./.claude/skills/<slug>/SKILL.md, this project onlypaperctl skill sync <slug> # ~/.agents/skills/<slug>/SKILL.md
paperctl skill sync <slug> --local # ./.agents/skills/<slug>/SKILL.md, this project only--local installs for the current project instead of everywhere. Add --dry-run to any of these to print the resolved target without writing.
You can also download a skill’s SKILL.md from its page in paper console and place the file yourself; sync does the same thing with the paths handled for you.
Update it
Run the same sync again:
paperctl skill sync <slug>Sync overwrites the local file with the skill’s current content. When a teammate publishes a new version, re-running sync brings your copy up to date — check version history in the console to see what changed.
Verify your agent picks it up
Start your agent in a fresh session and ask it to use the skill by name, or check the file landed where you expect:
cat ~/.claude/skills/<slug>/SKILL.mdcat ~/.agents/skills/<slug>/SKILL.mdIf you installed with --local or other flags, re-run your sync command with --dry-run — it prints the exact path that install wrote to.