agentleFS
Sign inStart free
FracteraFractera/Agentic-Engineering-Infrastructure/.claude/skills/audit-broken-characters/SKILL.md

audit-broken-characters

Skill61 starsChanged 56 days agoMITView on GitHub

Scan the whole project for BROKEN / REPLACEMENT characters in localized text — a control byte (e.g. 0x13) or U+FFFD or mojibake left where an accented letter belonged, which renders as a box (e.g. "Documentación" showing "Documentaci□n"). Use when the owner reports a square / wrong glyph in the UI or content, says "broken character", "weird symbol", "mojibake", "validate encoding", or after authoring multilingual content and before closing a content step. It SHIPS SILENTLY (the file still parses), so run the audit to catch it. One project-root script, nothing external needed.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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. Very specific:

    Every finding reports file · line · column · codepoint (e.g.

    line 41
  2. Distinctive:

    When the owner reports a square / wrong glyph in the UI or a page.

    line 57
  3. Distinctive:

    After adding or translating multilingual content (alongside the content emitters' write-time refusal).

    line 58
  4. Distinctive:

    Before closing a content step (a cheap, decisive integrity gate).

    line 59

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

audit-broken-characters

Informational, not binding. Know a better way for the case in front of you — do it your way and say so. You are trusted with the creative work on this project.

The project's universal encoding-integrity check. A lossy step — voice dictation, copy-paste, a bad transform — can drop an accented letter and leave a control byte (0x13…), U+FFFD (the replacement char), or mojibake in its place. The file still parses, so it ships silently, and the live page shows a box instead of the letter (the real "Documentación" became "Documentaci□n").

Unlike a silently dropped letter, these ARE detectable. This capability is two-sided:

  • Prevention (already wired): the content emitters — create-multilingual-content-entry and expand-site-language's fan-out + translate runner — refuse a broken char on write, in any language.
  • Detection (this skill): the project-root scanner sweeps the whole corpus (every language, every content/UI/data file) and reports what already sits in the tree.

Where it lives & how to run it

Script: scripts/scan-broken-characters.mjs (project root). One command:

npm run check:encoding                       # scan the project root (the slot)
node scripts/scan-broken-characters.mjs --root .          # same, explicit
node scripts/scan-broken-characters.mjs --root services/auth   # point it anywhere (e.g. the 82-lang auth dictionary)
node scripts/scan-broken-characters.mjs --json            # single-line JSON (tooling / CI)

Every finding reports file · line · column · codepoint (e.g. U+0013) · language · context (the line with the bad char shown as a safe [U+XXXX] marker, never the raw corruption). Exit code 1 on any finding — so it works as a pre-commit / CI gate. Read-only: it changes nothing.

The same scan, from the panel: the language-expansion tooling runs the same scan against the slot and returns the findings.

How to FIX what it finds (critical)

Fix each occurrence BY HAND with the correct letter for its word. Do NOT blind-replace the byte — the same control byte or U+FFFD may stand for a different accented letter in different places (á / é / í / ó / ñ). Read the word, restore the right character, then REBUILD (Deploy) to publish. After a fix, re-run npm run check:encoding to confirm the corpus is clean.

When to run it

  • When the owner reports a square / wrong glyph in the UI or a page.
  • After adding or translating multilingual content (alongside the content emitters' write-time refusal).
  • Before closing a content step (a cheap, decisive integrity gate).

Self-sufficient

The scanner is a plain Node-ESM script at the project root — nothing external is required to run it (the panel tool is just a convenience wrapper). It ships with every slot.

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.

Check your setup, free