Skip to main content
Each term here has one meaning. Where the app, the SDK and the command line spell a thing differently, this page says so.

The three verbs

You can take a registry skill in three ways, and none of them implies another. What each one does when the author publishes a new version, and how to undo it, is in Update, pin or fork a skill. decimalai skills add depends on the project. In a project connected to DecimalAI (it has .decimal/link.toml), or with --to-agent, it links the skill and writes no files. Otherwise it copies to disk, and records the copy in .decimal/skills.lock. decimalai skills pull is a loose copy that no lock records. Skills on disk covers the file commands.

”Install” isn’t a term here

The word appears in three places, with a different meaning in each.

The two public usage numbers

Being offered on a skill list, or being downloaded, doesn’t earn a use. SkillScore owns the definition.

The three things called an agent

agent_config() loads no agent: you build your own and give it the config’s pieces. One user message to your agent, from the question to the final answer, is a run. A chat of several messages is a conversation. The values that fill a saved prompt’s {{name}} slots are its variables, and the skills offered to the model in a run are its skill list.

Words we deliberately do not use

  • “Used by N teams”: say Users and Times used.
  • “Subscribe”: an older name for Link.
  • “Activation”: an older name for Loaded, which API fields such as active_skills still carry.
  • install_count: a registry API field that counts forks taken and never goes down. It isn’t an adoption number.

A to Z