agentleFS
Sign inStart free
clayloclaylo/pikchr-tools/.claude/skills/markdown-authoring/SKILL.md

markdown-authoring

Skill0 starsChanged 10 months agoApache-2.0View on GitHub

Markdown style patterns to use when writing documents.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. pantheon-org/tekhne★ 10same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository5 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When writing Markdown files:

    line 6
  2. Distinctive:

    When a list item contains a nested list, indent the nested list by 2 spaces.

    line 18
  3. Distinctive:

    Put a blank line before and after each heading (where applicable).

    line 29
  4. Distinctive:

    Put a blank line before a list and a blank line after a list.

    line 35
  5. Distinctive:

    If there are more than 4 sections, add a table of contents

    line 41

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

When writing Markdown files:

  • Start with an H1 as the first heading. The first heading in the file should be a top-level # Heading (not ## or deeper).
  • Use ATX headings only. Headings must use leading # characters (#, ##, ###, …), not Setext (Heading + ====).
  • Unordered list marker is flexible. You may use -, *, or + for bullet lists (no enforcement).
  • Indent nested unordered lists by 2 spaces. When a list item contains a nested list, indent the nested list by 2 spaces.
  • Blank lines are allowed more freely. Extra consecutive blank lines are permitted (no “single blank line only” restriction).
  • Line length limit is effectively very high; but follow sembr For prose, follow the Semantic Line Breaks convention, described in reference/sembr.md. Table rows are not checked for line length.
  • Headings must be surrounded by blank lines. Put a blank line before and after each heading (where applicable).
  • Duplicate headings are allowed. Reusing the same heading text in multiple places is acceptable.
  • Lists must be surrounded by blank lines. Put a blank line before a list and a blank line after a list.
  • Inline HTML is allowed. HTML (like <br>, <details>, etc.) is permitted in Markdown.
  • Add Table of Contents. If there are more than 4 sections, add a table of contents

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