normalize skillA
normalize is agent-read markdown (skill) from xtieume/testcase: Rewrites a casual, rambling everyday prompt into a compact engineering prompt — structured sections, imperative instructions, explicit escalation and done criteria — ready to paste into an AI or in front of a slash command like /goalrun. Use when the user says "chuẩn hóa prompt", "viết lại prompt này", "làm prompt cho gọn", "prompt này dài quá", "rewrite this prompt", "turn this into a proper prompt", "clean up my prompt", "make this a technical prompt", "prompt for /goalrun", or pastes a long i.
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Normalize — everyday prompt → engineering prompt > Same requirements. Less prose. Shape an AI can execute. ## The rule **Every line of the output traces to a phrase in the input.** No invented scope, no added acceptance criteria, no "best practice" section the user never asked for. Dropping a requirement fails the same way inventing one does. This is a rewrite, not a redesign — you have no authority to decide the task is bigger or smaller than stated. Never execute the normalized prompt. The deliverable is the text. ## Workflow - [ ] 1. Extract — pull every requirement out of the input, verbatim-ish - [ ] 2. Shape — group into sections, convert each to an imperative - [ ] 3. Budget — fit the character limit - [ ] 4. Second pass ⚠️ REQUIRED — diff output against input, both directions - [ ] 5. Emit — one fenced block, nothing else ## 1. Extract Read the input twice and answer, in the input's own words: - **Target** — what file, path, URL, repo, ticket or command is this pointed at? Copy it character-for-character. A path is not paraphrasable. - **Goal** — what state does the user want at the end? Usually one sentence buried in the middle of the rambling. …
Read the whole file at its exact version.
How to install
mdr add xtieume/testcase/normalize@git:20260923.288e78fmdr add xtieume/testcase/normalize@sha256:43cde9b6632a68a2Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_lyxldcodcldlksms)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260923.288e78f latest | 2026-09-23 | 288e78f | 7,191 B | A | view · diff |
| git:20260922.ac40a94 | 2026-09-22 | ac40a94 | 6,216 B | A | view |
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 (7191 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
xtieume/testcase · 3 stars · license MIT · pushed 2026-09-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_lyxldcodcldlksms GET https://markdownregistry.com/api/v1/resolve?ref=xtieume/testcase/normalize GET https://markdownregistry.com/api/v1/blob/43cde9b6632a68a24481b0992074ad32e54a4a1a89325111e6565f335c5e17e8
Your agent 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.