Hierarchy & tiers

Skills are scoped like other Prompt Manager artifacts, with one extra tier for sharing:

Organization
 └── Project          ← project-scoped skills (this repo’s special rules)
 └── Organization     ← org-wide skills (security, style — every project inherits)
Global / Marketplace  ← shared skills any authenticated consumer can install

What each tier is for

Tier	Scope id	Typical use
Project	Project UUID	Repo-specific conventions, domain runbooks
Organization	Org UUID	Company-wide security / style contracts
Global	sentinel global	Marketplace / platform skills

Names are unique within (scope, scope_id). The same kebab-case name can exist at multiple tiers; resolution picks a winner.

Inheritance vs installs

• Org skills are visible to projects in that org through resolution (subject to membership).
• Global skills reach a project only after an install (pin) in the UI — or when they appear in the resolved set per product rules for your deployment.
• Promotion copies a skill up a tier (project → org, or org → global) with provenance; the original remains.

Roles (summary)

Action	Typical gate
Create/edit project skill	Project member
Approve project skill	Project approver
Create/publish org skill	Org member / admin (org publish is scan-gated)
Marketplace create / promote / install	Marketplace feature flag + role checks
CLI pull / list	Any key whose owner can access the project

Details: Lifecycle, Authentication.