• AIPM package
A versioned package with a manifest, visibility setting, and the files needed to install an AI skill.• Skill
A reusable set of instructions or files that helps an AI assistant do one job.• Manifest
The aipm.manifest.json file. It tells AIPM the package name, version, entry file, supported tools, description, and license.• Target
The AI tool you want to install into. Current targets are cursor and claude.• Adapter
Code that writes skill files into the right folder for a target tool.• Org namespace
The scope that owns package names, such as @team in @team/review-helper.• Package reservation
A package name reserved in the dashboard so an org can publish versions for it.• Private package
An org package that only authenticated members with access can discover, inspect, and install.• CLI login
The browser-based aipm login flow that stores a local CLI session for private package reads and installs.• CLI session
A local auth record stored in ~/.aipm/auth.json so the CLI can refresh access without asking for a token each time.• Install token
An org-scoped read token used by CI or automation to install private packages without browser login.• Publish token
A short-lived token from the dashboard. The CLI uses it when you publish a package version.• Template
Starter SKILL.md content for common tasks like code review, issue summaries, and release notes.• --no-init
A flag on aipm add, update, and remove. It installs or manages a skill without creating or updating aipm.package.json and aipm-lock.json. Install without project tracking• SKILL.md frontmatter
The YAML block between --- lines at the top of SKILL.md. name and description are required; other fields depend on the AI tool. SKILL.md frontmatter reference• Entry file
The main file in a package. AIPM reads and installs this as the skill content.• .aipmignore
A file that tells AIPM what not to publish, such as secrets, logs, and private notes.• Readiness
A check that confirms the registry can reach its database and package storage.