Disclosure
Disclosure
Entry 1
What the skill is made of
Claim: The skill is a zip file of Markdown instructions and references, 1 YAML configuration file, PNG and SVG icons, and the licence and notice files. It contains no program and makes no network calls. The release packager refuses to build the zip if any file in the skill folder is executable or a link, or falls outside its list of allowed paths.
Limitation: The packager’s allowlist step checks each file’s path and mode, not its content. Its other checks include the version, name and release-date lines of SKILL.md, the version and name in the Claude plugin manifest, the name and source of the first plugin the marketplace manifest lists, the icons the YAML file names, the archive’s entry list and layout, and that each archived byte equals its git blob. These are structural checks; none of them judges what the instructions say. The repository that publishes the skill also holds code that is not in the zip. That code includes Python and shell tools, GitHub workflows, the site’s JavaScript, and the AIQT Guardrails hooks used while maintaining the repository. Some of those tools read release data from GitHub.
Evidence: Trust and assurance The release packager (opens in a new tab) Distribution and assurance (opens in a new tab)
Entry 2
What it does to your writing
Claim: The skill tells your AI to remove generic AI-writing patterns and to keep facts, figures, names, quotations, citations, and technical terms unchanged. Its precedence order puts factual, technical, legal, and semantic accuracy first, so a style rule gives way when it would change the meaning.
Limitation: Each provider controls how its model applies the instructions, so results vary from one platform to another. A model can still change meaning with these rules in place, so read the result before you rely on it. For legal, medical, financial, safety, or other high-stakes text, have a qualified person review any edit. The skill does not target AI-detector scores.
Evidence: The precedence order Trust and assurance The skill’s source (opens in a new tab)
Entry 3
Where it works
Claim: The install guide gives steps for Claude, ChatGPT, Gemini, Copilot, and other AI systems that accept custom instructions. Each platform’s section names the date its steps were last checked: 27 August 2026 for Claude, ChatGPT, and Gemini, and 1 September 2026 for Copilot.
Limitation: The steps match each platform as checked on that date, and no check in the repository rechecks them. Skill upload is documented for desktop browsers; the mobile apps are not documented to support it. Whether a platform applies the skill automatically or only when you ask varies by platform and account. The condensed and compact instruction files carry less of the finer detail than the full file.
Evidence: Install How to use Clean Language
Entry 4
Downloads and checksums
Claim: Each release publishes a SHA-256 checksum for each zip it ships, and the verify page shows the checksum of the current version. A daily check, tools/check-release-checksum-live.py, reads the verify page as committed in the repository, site/verify/index.html, and compares its checksum with the published release file; it also runs on each change to that page. An offline gate, tools/check-release-links.py, requires the verify page’s checksum and version to match the release record, site-src/release.json.
Limitation: A match shows that your copy matches the published release file. The instruction files download from this site and have no published checksum. Rebuilding the zip yourself gives the same checksum only with the same zip implementation. The daily check passes conditionally in 1 case: the verify page names the current version, that version’s release tag does not exist yet, and the Released line of SKILL.md is well formed and present wherever the version needs one. A malformed Released line, or a tag with no published release, means the check could not complete; another version with no release fails.
Evidence: Verify your download The daily checksum check (opens in a new tab) The offline release gate (opens in a new tab) Releases (opens in a new tab)
Entry 5
Data handling
Claim: The skill carries no telemetry and sends nothing to the project; it runs inside your own AI assistant. The site’s own code sets no cookies, and its scripts make no network calls.
Limitation: Your writing goes to the AI provider you use, under that provider’s terms. Cloudflare delivers the site and GitHub serves the skill download; both receive your requests and keep their own records. Cloudflare may set a security cookie, and the security policy of these pages allows Cloudflare’s own scripts, including its Web Analytics beacon, which reports visits to Cloudflare.
Evidence: The privacy policy (opens in a new tab) The site’s security headers (opens in a new tab)
Security
To report a security vulnerability, see the vulnerability disclosure policy (opens in a new tab). For how personal data is handled on this site, see the privacy policy (opens in a new tab).
Next
Home