checking-legal-and-safety-wording

To check public documentation for legal and safety compliance overclaims, supply the text to identify and remove overreaching statements about legality or certifications. The skill rewrites wording to stay within evidence-based boundaries, separating permissions from assurances.

The best way to temper safety claims in a README file is to apply evidence-tied wording, which detects and rewords statements about compliance to reflect verifiable limitations. This ensures permissions and assurances are clearly separated before release.

To separate license permissions from compliance assurances in rollout templates, the skill analyzes the text and flags unsupported statements for revision. It rewrites the wording to ensure all assurances remain verifiable and distinct from permissions.

Yes, you can use this to review external-facing docs before a rollout. It is ideal for editing README files, license notes, and rollout templates, ensuring wording stays within legal and safety boundaries by flagging unsupported statements for revision.

You should remove overreaching compliance claims from public docs to ensure public text communicates clearly while staying within legal, safety, and compliance boundaries. This prevents misleading statements and ensures all wording reflects verifiable evidence and limitations.

Yes, this skill works for license notes and external text without requiring additional dependencies. It processes the supplied public text directly to identify overreaching claims and applies boundary drafting to keep wording within evidence-based limits.