Power-Ups & skills

What an extension changes

A skill contains reusable task instructions. A Power-Up packages a capability with its own metadata and lifecycle. Installing a package is different from enabling or executing it.

Community can use skills and Power-Ups; these are not automatically Pro-only features. A package may still have its own compatibility, access or licensing requirements.

Community package lifecycle

Starter Kit 1.2.0 exposes validate, install, list, enable, disable, update, rollback and uninstall. Use the tagged package reference for exact manifest and command contracts.

From the extracted package, replace the paths with a test vault and a package you have inspected:

./install.ps1 -Target 'PATH-TO-VAULT' -PackageCommand validate -Package 'PATH-TO-PACKAGE'
./install.ps1 -Target 'PATH-TO-VAULT' -PackageCommand install -Package 'PATH-TO-PACKAGE' -DryRun
./install.ps1 -Target 'PATH-TO-VAULT' -PackageCommand install -Package 'PATH-TO-PACKAGE' -Approve
./install.ps1 -Target 'PATH-TO-VAULT' -PackageCommand list

Nonempty permission declarations additionally require reviewed -ApprovePermissions. Inspect the requested access and exact package behavior before granting that approval. Installation is not blanket permission for later external actions.

What is not implied

These local commands do not establish a marketplace, hosted download service, automatic execution, production entitlement verifier or license server. This documentation does not list an unverified package catalog.

Pro packages

Check the package’s declared compatibility against your installed Pro version and use its supplied instructions. Pro’s installed manager is scripts/Manage-KOSPowerUp.ps1; use the version supplied with your Pro package. Do not run Community’s package CLI against a Pro installation.

Set $Vault to your installed Pro vault. Begin with inventory and platform diagnostics:

pwsh -NoProfile -File "$Vault/scripts/Manage-KOSPowerUp.ps1" -RepositoryRoot $Vault -Action List
pwsh -NoProfile -File "$Vault/scripts/Manage-KOSPowerUp.ps1" -RepositoryRoot $Vault -Action Doctor

An empty list means no packages are installed; it is not proof that a marketplace is unavailable or that a package is licensed. For a package you already have and have inspected, replace the placeholder with its source directory:

pwsh -NoProfile -File "$Vault/scripts/Manage-KOSPowerUp.ps1" -RepositoryRoot $Vault -Action Validate -Source 'PATH-TO-PACKAGE'
pwsh -NoProfile -File "$Vault/scripts/Manage-KOSPowerUp.ps1" -RepositoryRoot $Vault -Action Install -Source 'PATH-TO-PACKAGE' -WhatIf

The manager also exposes Discover, Install, Enable, Disable, Resolve, Verify and Uninstall. Review the supplied package contract and permissions before authorizing a mutation; installation, enablement and execution remain separate. Future Power-Up entitlement is not included automatically in Pro’s current grant.

Pro Skills and first-run context

For a supplied Pro installation, follow 00 - System/Pro/Workflows/first-run.md. Complete the owner profile at 00 - System/AI/owner-profile.md, retaining draft/pending metadata until human review. The documented workflow routes it only after explicit approval and activation.

Use .agents/skills/registry.json to identify a Skill’s exact entrypoint, version, scope, compatibility, permissions and enabled state. Read that Skill’s instructions before using it for a matching task. Disabled Skills are not execution candidates. A Power-Up’s Skills become eligible only while that package version is active; do not copy their instructions into another provider’s directory.

For a new project, the supplied initialize-context-details Skill drafts context for review. The activate-memory-handoff Skill handles explicitly approved paired activation; see the quickstart. These file contracts do not demonstrate that a particular AI provider version loaded or executed the Skill successfully.

Verify and recover

Test with synthetic input and narrow permissions. Check the installed/enabled state and actual outputs. Retain a full backup and the prior package before updates; consult the exact package lifecycle reference for rollback limitations.