llm-friendly-context SKILL.md skillA
This file is byte-identical to the first copy the registry indexed, one of 5 indexed copies. Same content hash, so the same checks give both the same grade.
llm-friendly-context from shinpr/claude-code-workflows is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add shinpr/claude-code-workflows/llm-friendly-context@git:20261019.de01f9ePins git:20261019.de01f9e in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- shinpr/claude-code-workflows
- Path
dev-workflows-fullstack/skills/llm-friendly-context/SKILL.md- Versions recorded
- 7
- Latest version
- git:20261019.de01f9e, committed Oct 19, 2026
- First version recorded
- Aug 5, 2026
- Size
- 5,922 bytes
- Repository stars
- 707
- License
- MIT
Clarifies inputs, outputs, success criteria, decisions, and unresolved conditions so downstream consumers can execute without guessing. Use when writing or revising LLM-facing prompts, handoffs, planning artifacts, reviews, reports, or generated instructions.
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
# LLM-Friendly Context The goal is stable downstream execution: the next consumer should know what to read, what to do, what counts as success, and which unresolved decisions can change the result. ## Core Rules 1. **Use positive, executable instructions** - State what the next consumer should do. - Convert quality policies into positive criteria. - Keep a prohibition only when it protects an irreversible boundary or shipped contract. Name the protected condition and the allowed action. - Example: "Preserve existing public API behavior across the documented compatibility cases." 2. **Make vague instructions concrete** - Clarify wording when plausible interpretations would change the outcome, scope, authority or proof. Supply purpose, evidence and selection criteria for reversible choices; reserve exact selections for actual consumer contracts and user-owned decisions. - Terms that often need clarification when they leave a decision to the next consumer: `appropriate`, `proper`, `related`, `existing behavior`, `optional`, `as needed`, `if needed`, `per convention`, unresolved alternatives, `TBD`, `placeholder`. 3. **Specify output shape** …
Read the whole file at its exact version.
How to install
mdr add shinpr/claude-code-workflows/llm-friendly-context@sha256:9f5e10af90877baaThe line at the top of this page pins the label git:20261019.de01f9e, 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_f5mvww6a3nxedfsd)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 7 versions of this file, between Aug 5, 2026 and Oct 19, 2026, about one every 13 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261019.de01f9e latest | 2026-10-19 | de01f9e | 5,922 B | A | view · diff |
| git:20261019.e544b5c | 2026-10-19 | e544b5c | 5,953 B | A | view · diff |
| git:20260917.73d4471 | 2026-09-17 | 73d4471 | 5,531 B | A | view · diff |
| git:20260809.6130272 | 2026-08-09 | 6130272 | 5,238 B | A | view · diff |
| git:20260808.b090d30 | 2026-08-08 | b090d30 | 5,274 B | A | view · diff |
| git:20260806.d8a29d4 | 2026-08-06 | d8a29d4 | 5,448 B | A | view · diff |
| git:20260805.456abcb | 2026-08-05 | 456abcb | 5,465 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 (5922 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
shinpr/claude-code-workflows · 707 stars · license MIT · pushed 2026-10-29 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_f5mvww6a3nxedfsd GET https://markdownregistry.com/api/v1/resolve?ref=shinpr/claude-code-workflows/llm-friendly-context GET https://markdownregistry.com/api/v1/blob/9f5e10af90877baa96b71940f310e21d67e9cd034ceeaba344d435d05707053d
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.
More from shinpr/claude-code-workflows
Every file in shinpr/claude-code-workflows