Skip to main content
Six things happen to a skill. Each has exactly one word. This page is the only place they are defined, so that they cannot drift apart again.

​
The three verbs

Install

Link a skill into your workspace. No copy. Your agents get the author’s updates as they publish them, the way an extension marketplace works.

Fork

Take an editable copy. It becomes your skill, in your org, and it stops tracking the author. Same meaning as on GitHub.

Export

Write the files to disk. For runtimes that load SKILL.md themselves — Claude Code, Cursor. Takes no copy and needs no fork.
Each verb has an inverse, and only Install’s is a distinct action: Uninstall removes the link. It clears the skill from every agent at once, and it is safe to repeat — removing a skill you no longer have succeeds and reports that nothing changed. A fork is your own skill, so you delete it like any other; an export is just files, so you delete the files. Install and Fork answer what do I have. Export answers where do the bytes live. They are separate questions, so you can export a skill you installed without forking it:
Uninstall is in the app and on the API today. The SDK call ships in a later release — until then, remove a link with:
decimalai skills install and router.install() still exist and still do fork-then-write. They are deprecated in favour of the three above, and they have not changed behaviour — only the recommendation.
The Claude Code plugin’s /decimalai:install is an Export by the table above: it writes SKILL.md and its attachments to .claude/skills/, takes no copy, creates no link, and leaves no record on the platform. It is spelled install because that is the word a plugin user types — nothing about your workspace changes when you run it.

​
The two public usage numbers

Repeated runs by the same user increase Times used without increasing Users. Both numbers retain anonymous statistical credits after account removal, uninstall or private trace erasure. A full skill body delivered to a model or an explicit skill activation earns one use per invocation and public source. Multiple versions, delivery sites or retries in that same invocation do not create extra uses. Offering a skill in a menu or downloading its body without model delivery does not earn a use. Installation and routing stages are workspace diagnostics. They are separate from the public lifetime counters and from qualified task evaluations and AI ratings. SkillScore explains those quality measurements and their 30-day windows.

​
One more, for the SDK

instrument turns on tracing for a framework — decimalai.langchain, decimalai.openai_agents, and so on. It has nothing to do with skills; it is here only because it used to be spelled install() too.

​
Words we deliberately do not use

  • “Used by N teams” — use distinct Users and Times used.
  • “Subscribe” — an older name for Install. The database table is still called skill_subscription; nothing user-facing says it.
  • “Activations” — the internal name for the last stage above. Say Uses.
  • install_count — counts fork events, never decremented. It is not the adoption number and is not rendered as one.