write-ste SKILL.md skillA
write-ste from kdy1/kdy1-scripts is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add kdy1/kdy1-scripts/write-ste@git:20261004.019bb02Pins git:20261004.019bb02 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- kdy1/kdy1-scripts
- Path
skills/write-ste/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261004.019bb02, committed Oct 4, 2026
- Size
- 4,807 bytes
- Repository stars
- 32
- License
- none declared
Write or revise human-readable technical text with practical ASD-STE100 principles. Use automatically for PR and issue titles and bodies, review comments, technical documentation, and code explanations, including technical chat replies. Preserve the text's language and meaning; apply clarity principles to languages other than English. Exclude ordinary conversation and marketing copy.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Write STE Apply ASD-STE100 clarity principles to technical writing. This is a practical adaptation, not full standard compliance. It does not check the official approved vocabulary or certify compliance. For background, see the [official ASD-STE100 FAQ](https://www.asd-ste100.org/STE_faq.html). ## Apply within the task - Apply these rules when drafting or revising technical text, including the prose in requested code comments and docstrings. Do not rewrite unrelated existing text. - Follow explicit user instructions for language, voice, length, and format. Otherwise, preserve the source language or the language established by the task. Do not translate solely to apply STE. - Keep repository templates, required headings and fields, issue references, and required disclosures. Use this skill alongside other skills without changing their workflow, required content, or authorization boundaries. - Return the requested text or artifact. Do not append a STE checklist, compliance notice, or before-and-after comparison unless requested. ## Preserve meaning and protected text …
Read the whole file at its exact version.
How to install
mdr add kdy1/kdy1-scripts/write-ste@sha256:40f28e6761cb20a8The line at the top of this page pins the label git:20261004.019bb02, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_3cyzivao7lvbyuuv)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 4, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (4807 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
kdy1/kdy1-scripts · 32 stars · license none declared · pushed 2026-10-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_3cyzivao7lvbyuuv GET https://markdownregistry.com/api/v1/resolve?ref=kdy1/kdy1-scripts/write-ste GET https://markdownregistry.com/api/v1/blob/40f28e6761cb20a878aac02de9ef22079896a850e16749fef59baee08f841506
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.