skill-scope-decision

To decide if a skill should be shared globally or kept private locally, evaluate if it is reusable across gateways, independent of private contexts, and stable enough to be reviewed. This classification prevents private behavior from leaking into shared infrastructure.

A shared-global skill is published to a shared registry for cross-gateway reuse, while a private-local skill is excluded from Git-backed sync to prevent reliance on gateway- or agent-specific context from entering shared infrastructure.

A skill is classified as not-ready when it lacks the stability required for review and publishing, or if it fails to meet the criteria for cross-gateway reuse, meaning it cannot safely enter the shared-global registry or remain private-local.

To prevent private context from leaking into shared skill governance, classify skills relying on gateway- or agent-specific context as private-local, excluding them from Git-backed sync and keeping them out of the shared global registry.

Yes, a skill must be stable enough to be reviewed and published before entering the shared global registry. This ensures reusable policy guidance and prevents untested behaviors from affecting cross-gateway infrastructure.

Yes, evaluating skills that depend on specific agent contexts will result in a private-local classification, ensuring they are excluded from Git-backed sync to protect shared infrastructure from agent-specific behavior.