agentleFS
kamenkurtevkamenkurtev/ui-consistency/.claude/skills/uic-auditing/SKILL.md

uic-auditing

Skill1 starsChanged 10 days agoMITView on GitHub

Audits this plugin's skills and documents against the current guidance for writing skills and for prompting the current Claude models, and reports what to change as a table of findings and proposed issues. Use only when somebody asks for an audit of this repository's skills, rules or documents, or runs /uic-auditing.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If a page has moved, search for it from https://platform.claude.com/docs.

    line 20
  2. Distinctive:

    If a page cannot be reached, name it in the report, and check nothing against it from memory.

    line 21
  3. Very specific:

    Check them also against anything the guidance now says that the list does not: that is a finding about uic-writing itself.

    line 24
  4. Distinctive:

    Start no agent sessions — no evaluation run, no description-triggering loop: a skill change is checked in real work (AGENTS.md).

    line 34
  5. Distinctive:

    Create nothing until a person says yes to the proposed issues.

    line 74

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Auditing the plugin

Overview

Reads the current guidance from its source, checks every skill against it and every document against the skills, names what each shipped skill can lose, and ends with the findings and the issues they would become. It edits nothing, and opens issues only after a person says yes.

Steps

  1. Read the current guidance, every audit, from the source — never from memory:
  2. Check every skill in skills/ and .claude/skills/, file by file, against what .claude/skills/uic-writing/SKILL.md lists under While writing.
    • Check them also against anything the guidance now says that the list does not: that is a finding about uic-writing itself.
  3. Weigh each skill in skills/ as a whole, its SKILL.md first, and note the characters each item frees:
    • what can go without changing what an agent does: two passages of one skill that say one thing, an explanation no step needs, a line the current models follow without being told;
    • what only one case of the work needs — a design, a small change, another process running — which can move to a reference file linked from that case's step.
    • List an item step 2 also found under What each skill can lose, not among the findings.
  4. Check the documents — USING.md, README.md, .claude/CLAUDE.md, AGENTS.md, CONTRIBUTING.md, docs/, .claude/rules/ — for anything they say about the skills that is no longer true.
  5. Look for stale references and contradictions across all of them: every name of a file, section, skill, test or command that points at nothing, and every rule whose copies disagree.
  6. Use the built-in skills that are installed, where they fit, read for their rules only — never their workflow, which edits:
    • claude-md-management:claude-md-improver for .claude/CLAUDE.md and AGENTS.md;
    • skill-creator for the skills and their descriptions.
    • Start no agent sessions — no evaluation run, no description-triggering loop: a skill change is checked in real work (AGENTS.md).
  7. Report, in the shape below.
  • Note every finding as you go, the uncertain ones included.
  • Then report as findings only those whose fix makes the plugin more effective, and name the rest under Left out, with why.
  • Earlier issues, commits and decisions are not arguments for or against one.

The report

## Guidance read
- <page> — read / could not be reached

## Findings

| # | Finding | File:line | What it breaks |
|---|---|---|---|
| 1 | <what is wrong, in one line> | <path:line> | <a guidance page and its rule, a rule in `uic-writing`, or what is no longer true> |

## What each skill can lose

| # | Skill | What, at path:line | Cut or moved | Characters freed |
|---|---|---|---|---|
| 2 | <skill> | <what> | cut / to `<file>.md` | <n> |

- `SKILL.md` sizes: <skill> <n>, …; the seven a new page invokes (`uic-writing`, *A `SKILL.md`*): <total> of 80,000.

## Proposed issues
| Issue | Findings | One logical change |
|---|---|---|
| <title, as a statement of the end state> | 1, 4 | <what the pull request would do> |

## Left out
- <a finding, and why fixing it would not make the plugin more effective>

## Not checked
- <what the audit could not judge, and why>
  • Number the rows of What each skill can lose on from the findings, so a proposed issue can name both.
  • Create nothing until a person says yes to the proposed issues.
  • Then open them as .claude/rules/uic-git.md says.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.