agentleFS
D-SheyD-Shey/autoharness/.agents/skills/markdown-vague/SKILL.md

markdown-vague

Skill10 starsChanged todayMITView on GitHub

Markdown parsing skipping fenced code blocks in step validation

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 2 are distinctive, and 3 are 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.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use when extracting lists, steps, and procedures from Markdown documents while ignoring nested or illustrative code snippets.

    line 9
  2. Very specific:

    When encountering a fence delimiter, toggle in_fence and reset any current item accumulator.

    line 16
  3. Very specific:

    Run vague step heuristics (vague_step) only on genuine procedural items.

    line 19
  4. Very specific:

    Run pytest testing vague.vague_steps on Markdown containing fenced code blocks with dash lines (e.g.

    line 22
  5. Distinctive:

    Verify that no false positive warnings or trailing fence markers are produced.

    line 23

≈ “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

markdown-vague

When to use

Use when extracting lists, steps, and procedures from Markdown documents while ignoring nested or illustrative code snippets.

Steps

  1. Detect fenced code blocks in Markdown:
    • Identify triple backtick (```) or triple tilde (~~~) delimiters with optional language tags.
    • Maintain a boolean in_fence state across line iterations.
  2. In list item extraction (vague.items):
    • When encountering a fence delimiter, toggle in_fence and reset any current item accumulator.
    • While in_fence is true, ignore list item markers (-, *, +, 1.) so code lines are never treated as procedural steps.
  3. Validate steps outside code blocks:
    • Run vague step heuristics (vague_step) only on genuine procedural items.

How to verify

  1. Run pytest testing vague.vague_steps on Markdown containing fenced code blocks with dash lines (e.g. - do it properly).
  2. Verify that no false positive warnings or trailing fence markers are produced.

Facts found here

  • Standard Markdown fenced code blocks start and end with at least three consecutive backticks or tildes at line start (source: https://spec.commonmark.org/0.31.2/#fenced-code-blocks).
  • Lines inside code blocks frequently use dash prefixes for CLI flags, bullet comments, or diffs that must not be parsed as CommonMark list items.

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.