context-file-tuneup SKILL.md skillB

context-file-tuneup from markphelps/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add markphelps/skills/context-file-tuneup@git:20260523.c579973

Pins git:20260523.c579973 in mdr.lock. Pin the fingerprint instead.

Audit grade
B, 16 of 17 checks passed
Kind
SKILL.md skill
Repository
markphelps/skills
Path
skills/context-file-tuneup/SKILL.md
Versions recorded
2
Latest version
git:20260523.c579973, committed May 23, 2026
First version recorded
May 23, 2026
Size
12,607 bytes
Repository stars
6
License
MIT

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

# Context File Tune-up

A `CLAUDE.md` or `AGENTS.md` file is loaded into an agent's context on every
task. Different agents and repos use different filenames, and some repos keep
one as a symlink or compatibility alias to the other. Treat them as the same
class of file: high-leverage repo instructions for coding agents. A good one
silently prevents whole classes of mistakes; a bloated or vague one wastes the
context budget and gets ignored. This skill audits the target context file
against a known-good structure, derives what it _should_ contain by inspecting
the repo, proposes a full rewrite, and applies it only after the user confirms.

The core loop is **inspect → audit → propose → confirm → apply**. Never skip the
confirm step — this file encodes human judgment about a codebase, so the user
gets the final say before anything is written.

## What "good" looks like

Internalize this target before auditing anything. A great context file is
**short, specific, and verifiable**. The enemy is generic advice the model
already knows ("write clean code", "follow best practices") — it costs tokens
and teaches nothing.
…

Read the whole file at its exact version.

How to install

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_gvp4latwbojevg4c/f436264154674852e63ad4e034226a728bf334273b24fa83e87cdd49062fd7a2.json

Then /plugin install context-file-tuneup@markdownregistry-gvp4latwbojevg4c in Claude Code. It installs git:20260523.c579973, the one graded B here, pinned to the commit it was graded at, and leaves it there.

The exact contents, by fingerprint
mdr add markphelps/skills/context-file-tuneup@sha256:f436264154674852

The line at the top of this page pins the label git:20260523.c579973, 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.

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_gvp4latwbojevg4c.svg)](https://markdownregistry.com/a/art_gvp4latwbojevg4c)

1 badge image fetches in 30 days. What the badge shows.

Ask from your agent
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry

Then ask it: what changed in markphelps/skills/context-file-tuneup since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.

Got a copy of context-file-tuneup from somewhere else? Ask it: where did my context-file-tuneup come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.

Versions

The registry has recorded 2 versions of this file, all committed on May 23, 2026.

Watch this file (sign in, one email per new version)

versioncommittedcommitsizeaudit
git:20260523.c579973 latest2026-05-23 c579973 12,607 BB view · diff
git:20260523.7ad65ae2026-05-23 7ad65ae 10,682 BB view
Keep it current by itself, install once

Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

Install on GitHub

It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.

Keep it current by itself

Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml

It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.

Check a whole project

From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies

In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies

No sha256sum on your machine? shasum -a 256 prints the same lines.

Audit of the latest version

B  16 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • fail: Frontmatter declares a description
  • pass: Frontmatter block present
  • pass: Frontmatter declares a name
  • pass: Size between 200 bytes and 200 KB (12607 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

Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.

Source

GitHub

markphelps/skills · 6 stars · license MIT · pushed 2026-11-15 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_gvp4latwbojevg4c
GET https://markdownregistry.com/api/v1/resolve?ref=markphelps/skills/context-file-tuneup
GET https://markdownregistry.com/api/v1/blob/f436264154674852e63ad4e034226a728bf334273b24fa83e87cdd49062fd7a2

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 markphelps/skills

AGENTS.md AGENTS.md file
markphelps/skills · AGENTS.md
git:20260928.fb986fd · audit A · 6 stars
AGENTS.md@development AGENTS.md file
markphelps/skills · development/AGENTS.md
git:20261115.1fb19c9 · audit A · 6 stars
cli-design SKILL.md skill
markphelps/skills · development/skills/cli-design/SKILL.md · Design, build, or review command-line interfaces using the Command Line Interface Guidelines from clig.dev. Use this…
git:20260625.24602d6 · audit A · 6 stars
codebase-landing-copy SKILL.md skill
markphelps/skills · development/skills/codebase-landing-copy/SKILL.md
git:20260919.81b4b4e · audit B · 6 stars
context-file-tuneup SKILL.md skill
markphelps/skills · development/skills/context-file-tuneup/SKILL.md
git:20260523.c579973 · audit B · 6 stars
council SKILL.md skill
markphelps/skills · development/skills/council/SKILL.md
git:20261115.1fb19c9 · audit B · 6 stars
course-notes SKILL.md skill
markphelps/skills · development/skills/course-notes/SKILL.md
git:20261014.72d6c82 · audit C · 6 stars
decision-records SKILL.md skill
markphelps/skills · development/skills/decision-records/SKILL.md
git:20260913.a6ef6f5 · audit B · 6 stars
feature-map SKILL.md skill
markphelps/skills · development/skills/feature-map/SKILL.md
git:20260924.fb60020 · audit B · 6 stars
github-pr-fixup SKILL.md skill
markphelps/skills · development/skills/github-pr-fixup/SKILL.md
git:20260528.5314212 · audit B · 6 stars
github-self-hosted-runner SKILL.md skill
markphelps/skills · development/skills/github-self-hosted-runner/SKILL.md
git:20261004.11832f3 · audit B · 6 stars
oss-marketing SKILL.md skill
markphelps/skills · development/skills/oss-marketing/SKILL.md
git:20260702.608072d · audit B · 6 stars

Every file in markphelps/skills

Other files named context-file-tuneup

context-file-tuneup SKILL.md skill
markphelps/skills · development/skills/context-file-tuneup/SKILL.md
git:20260523.c579973 · audit B · 6 stars

Browse by kind, by grade B, or by owner.