agentsclimarketplace

Claude md improver

Skill M0rtalPhe0nix/dotfiles/.claude/skills/claude-md-improver

Opinionated workstation setup for Apple Silicon macOS and Debian or Ubuntu desktops.

Install
npx -y skills add M0rtalPhe0nix/dotfiles --skill claude-md-improver

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 19 days oldThe repository was created 19 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Audit and improve CLAUDE.md project instructions. Use when the user asks to check, audit, update, improve, or maintain CLAUDE.md files or project memory.

SKILL.md

2.3 KB, as published. Nobody here has run it

CLAUDE.md Improver

Audit CLAUDE.md files against the current codebase and propose concise, targeted improvements. This is an OpenCode-compatible adaptation of Anthropic's claude-md-management plugin skill.

Workflow

  1. Discover CLAUDE.md, .claude.md, and .claude.local.md files with Glob. Include root, package, and nested instruction files.
  2. Inspect the repository's manifests, scripts, tests, configuration, and architecture. Verify documented commands rather than assuming they work.
  3. Score each instruction file from 0 to 100 using these criteria:
    • Commands and workflows: 20
    • Architecture clarity: 20
    • Non-obvious patterns and gotchas: 15
    • Conciseness: 15
    • Currency: 15
    • Actionability: 15
  4. Present a quality report before editing. For every file, include its score, specific issues, and recommended additions or removals.
  5. Show a focused diff and ask for approval before changing any instruction file.
  6. Apply only approved changes while preserving the existing structure and voice.

Update Rules

  • Add project-specific commands, architecture, testing patterns, environment requirements, and recurring gotchas.
  • Remove stale or contradicted guidance.
  • Keep each concept as short as practical because instruction files consume context.
  • Do not add generic best practices, obvious facts, one-off fixes, secrets, or host-specific values.
  • Put shared guidance in CLAUDE.md and personal guidance in .claude.local.md.
  • Never edit an instruction file before presenting the report and receiving approval.

Report Format

## CLAUDE.md Quality Report

### Summary
- Files found: X
- Average score: X/100
- Files needing updates: X

### ./CLAUDE.md
**Score: XX/100 (Grade: X)**

| Criterion | Score | Notes |
|---|---:|---|
| Commands and workflows | X/20 | ... |
| Architecture clarity | X/20 | ... |
| Non-obvious patterns | X/15 | ... |
| Conciseness | X/15 | ... |
| Currency | X/15 | ... |
| Actionability | X/15 | ... |

**Issues:** ...

**Recommended changes:** ...

Use grades A for 90-100, B for 70-89, C for 50-69, D for 30-49, and F below 30.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.