wr-risk-scorer:assess-external-comms

To check an outbound GitHub issue body for confidential information leaks, provide the draft text to assess it against RISK-POLICY.md, returning a structured risk verdict and audit key before posting.

Preflighting npm publish content for secret-leak risk involves validating the draft body against RISK-POLICY.md, executing the external-comms gate, and returning a structured risk verdict to prevent leaks.

Yes, you can review security advisories before publishing to third-party channels by passing the advisory draft for confidential-information assessment, which delegates to the external-comms gate and yields a risk verdict.

This risk assessment tool works with .changeset/*.md bodies, reviewing the markdown content for confidential-information leaks per RISK-POLICY.md before changesets are committed or published.

To get a structured risk verdict for a pull request body, submit the draft prose for validation against the RISK-POLICY.md, pre-satisfying the external-comms gate marker for your current session.

To run an external-comms risk review on a draft, you need to provide the draft body or a surface hint, allowing the tool to delegate the assessment and return a structured risk verdict with an audit key.