Glossary

Simple definitions for AIPM terms.

AIPM uses words from package managers, AI tools, and publishing accounts. This page keeps those words short and easy to scan.

AIPM package

A versioned package with a manifest, visibility setting, and the files needed to install an AI skill.

A reusable set of instructions or files that helps an AI assistant do one job.

The aipm.manifest.json file. It tells AIPM the package name, version, entry file, supported tools, description, and license.

The AI tool you want to install into. Current targets are cursor and claude.

Code that writes skill files into the right folder for a target tool.

The scope that owns package names, such as @team in @team/review-helper.

A package name reserved in the dashboard so an org can publish versions for it.

An org package that only authenticated members with access can discover, inspect, and install.

The browser-based aipm login flow that stores a local CLI session for private package reads and installs.

A local auth record stored in ~/.aipm/auth.json so the CLI can refresh access without asking for a token each time.

An org-scoped read token used by CI or automation to install private packages without browser login.

A short-lived token from the dashboard. The CLI uses it when you publish a package version.

Starter SKILL.md content for common tasks like code review, issue summaries, and release notes.

The main file in a package. AIPM reads and installs this as the skill content.

A file that tells AIPM what not to publish, such as secrets, logs, and private notes.

A check that confirms the registry can reach its database and package storage.