Org skills

Give your team’s AI tools the same instructions: how to use your design system, name things, and work on prototypes. An admin adds a shared skill, and teammates download it with one command.

These are your team’s own instructions. To let an agent publish and read Artor feedback for you, use the separate Artor skill.

If you haven’t set up Artor in your terminal, start with Installing the CLI.

Pinned to an exact version

Everyone who syncs gets the version your team selected. Changes to the original GitHub repository do not reach teammates until a skills manager updates the shared skill.

How to add and distribute a skill (admin)


# Add a skill from a GitHub repo (pin to a branch, tag, or commit with --ref)
artor skill add https://github.com/acme/claude-skills --name acme --ref main   # admin access required
 
# Update to a new version (shows what changed before applying)
artor skill pin acme        # admin access required; shows the diff
artor skill pin acme --yes  # admin access required; applies it
 
# Make it required for everyone
artor skill enforce acme    # admin access required
 
# Remove it
artor skill rm acme         # admin access required; confirms first
artor skill rm acme --yes   # admin access required; required without a terminal

Use the skill’s name in commands. For rm --yes and pin --yes, use its exact name or ID. Removal takes the skill away from the whole organization. Add --enforced when creating it to make it mandatory immediately.

How to get skills on your machine


artor skill sync           # download shared skills; mandatory skills replace local edits
artor skill sync --force   # overwrite your local edits with the org's copy
artor skill list           # see what's available — marks (private) and (enforced) skills

artor init runs skill sync automatically; a new project picks up the team’s skills right away.

Enforced skills

An admin can mark a skill as mandatory. When enforced, every sync and new project installs it and your local edits are overwritten. Changes reach existing projects the next time someone syncs.

Edits are preserved (for optional skills)

If you edit a non-enforced skill locally, sync won’t overwrite it; it reports the conflict and leaves your version in place. Re-run with --force to pull the org version.

Private repos

A private GitHub repo needs an access token. Pass it with --credential when adding the skill. The saved token is never shared with teammates.

A skill source can contain up to 200 MB and 10,000 files.

Dashboard

Open Skills to see the team’s shared instructions, their source, selected version, and whether they are mandatory.

People with permission to manage skills can:

Add from GitHub or Upload zip to share instructions.
Check for updates, then Update the skills they want to refresh. Uploaded zip files aren’t checked for GitHub updates.
Toggle enforced to make a skill mandatory.
Remove a skill the team no longer needs.

Permission gate

Under Settings → Skills & Templates, an admin chooses who can manage skills and templates:

Setting	Who can add, update, remove, or enforce skills
Admins only (default)	Organization owners and admins
All members	Any organization member

The examples above use the default admin-only setting. An admin can change it from the terminal too:


artor settings skills-manager --role member  # allow all members; admin access required
artor settings skills-manager --role admin   # restore admins only;

The Artor Claude Code skill

The org skills above are your team’s own shared instructions. Separately, there’s a ready-made skill that wraps the artor CLI itself, so an AI agent can publish, version, share, read review feedback, remix, and pull prototypes for you. The CLI connection is the primary way an agent works with Artor. The review widget also offers Copy details for AI when someone wants to pass a single thread to an agent manually.

In Claude Code

It’s distributed as a Claude Code plugin from a public repo — install it once:


artor install-claude-plugin

Restart Claude Code after installing. It then offers these /artor:* commands:

/artor:start-here — first-run walkthrough: installs or checks the CLI, signs you in, links the project, and ships your first version.
/artor:publish — build and ship the next version, with a changelog note drafted from your changes.
/artor:share — create or refresh a public share link.
/artor:address-comments — read the review comments on a version and work through them.
/artor:remix — fork a project into a new one you own.
/artor:doctor — check your setup: CLI version, project link, and sign-in.
/artor:org-setup — set up shared configuration, sample data, skills, and private packages.
/artor:pull — download a version’s source and keep working on it.

Keeping the skill up to date

Run artor update to update both the CLI and the installed Artor skill. The CLI also reminds you when a skill update is available.

To let the Claude Code plugin update automatically, set ARTOR_SKILL_AUTO_UPDATE=1. This is off by default and does not run in CI. You can disable reminders with ARTOR_NO_UPDATE_NOTIFIER or --no-update-check.

On any other agent

For Codex, Cursor, Gemini, Copilot, OpenCode, and other supported tools, run:


artor install-skills

Choose your tool when the installer asks. Windows is supported. The /artor:* slash commands above are Claude Code-only — on other tools the agent reads the skill’s knowledge and drives the same artor commands directly.

The CLI reminds you when an update is available. Run artor update and choose the tools to update; these installations do not update silently.

It’s maintained by us at github.com/artorapp/skill — separate from the CLI install, and not the same as the org skills above.

Starter templates — start projects with your team’s setup
Comments — let your coding agent work from review feedback
CLI reference — skill commands