shared-sec-baseline

A shared security baseline enforces secure-by-default behavior across platforms by checking policy during skill activation. It implements a structured refusal framework to reject insecure implementations and automatically proposes safe, secure alternatives instead.

A security baseline refusal framework is a reusable mechanism that standardizes how platform skills refuse insecure implementations. It enforces platform-wide refusal handling across shared baselines, guiding platform skills to maintain consistent output formats and suggest safe alternatives.

To apply security policy checks during skill activation, enable a shared security baseline in your project. This baseline integrates into the activation workflow to enforce platform-wide refusal handling and maintain a minimal, structured output format.

Yes, you can use this baseline to guide platform-specific security skills. Platform security skills reference the shared baseline for its output format and refusal policy, then add their own platform-specific concerns on top of the shared foundation.

You need a shared security baseline when you want to ensure code is secure by default across multiple platforms and maintain consistent refusal policies. It is necessary when platform security skills require a standardized output format and reusable refusal framework.