fix-nested-code-fences
Skill0 starsChanged 3 months agoMITView on GitHub
Use when a markdown file has nested code fences that break rendering — when a ```markdown, ```bash, or similar block appears inside another ``` block anywhere in a generated or edited markdown file.
In this repository17 other files it gives its agents.
- backlinksSkill
- challengeSkill
- connectSkill
- expandSkill
- ghostSkill
- ingestSkill
- learnedSkill
- mapSkill
- meetingSkill
- obsidianSkill
- source-mineSkill
- traceSkill
- vault-indexSkill
- vault-lintSkill
- vault-retrieveSkill
- weekly-learningsSkill
- weekly-signalsSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
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
- Very specific: line 8
When a code block contains inner triple-backtick fences, replace the outer fence with ~~~ — the minimum change that fixes rendering without …
- Distinctive: line 14
When markdown is generated or written that contains code block examples inside other code blocks, the inner fences terminate the outer …
- Distinctive: line 47
Leave inner fences unchanged
≈ “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.
Files
Skill: fix-nested-code-fences
When a code block contains inner triple-backtick fences, replace the outer fence with ~~~ — the minimum change that fixes rendering without altering any content.
Don't: change inner fences — only the outer fence needs replacing. Don't apply this to tilde fences that are already correct.
The Problem
When markdown is generated or written that contains code block examples inside other code blocks, the inner fences terminate the outer block early, breaking rendered output. Common in: skill templates, documentation generators, README examples, any file where markdown is shown inside markdown.
The Fix
Replace the outer fence with ~~~ when the block contains inner ``` fences. Inner fences stay as-is.
Before:
```markdown
## Example
```bash
VAR=value
```
```After:
~~~markdown
## Example
```bash
VAR=value
```
~~~Steps
- Read the file
- Find any fenced code block that contains inner
```fences - Replace the outer opening and closing fences with
~~~ - Leave inner fences unchanged
- Confirm the fix and offer to commit if in a git repo
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
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.