Skip to content
Skill Authoring
Skill

/markdown-documentation

Master markdown formatting, GitHub Flavored Markdown, README files, and documentation formatting. Use when writing markdown docs, READMEs, or formatting documentation.

From plugin
useful-ai-prompts
309200 skills
Install
$ npx -y skills add aj-geddes/useful-ai-prompts --skill markdown-documentation --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/markdown-documentation

Context preview

The summary Claude sees to decide when to auto-load this skill.

Master markdown formatting, GitHub Flavored Markdown, README files, and documentation formatting. Use when writing markdown docs, READMEs, or formatting documentation.

SKILL.md

markdown-documentation.SKILL.md
name: markdown-documentation
description: >
  Master markdown formatting, GitHub Flavored Markdown, README files, and
  documentation formatting. Use when writing markdown docs, READMEs, or
  formatting documentation.

Markdown Documentation

Table of Contents

  • [Overview](#overview)
  • [When to Use](#when-to-use)
  • [Quick Start](#quick-start)
  • [Reference Guides](#reference-guides)
  • [Best Practices](#best-practices)

Overview

Master markdown syntax and best practices for creating well-formatted, readable documentation using standard Markdown and GitHub Flavored Markdown (GFM).

When to Use

  • README files
  • Documentation pages
  • GitHub/GitLab wikis
  • Blog posts
  • Technical writing
  • Project documentation
  • Comment formatting

Quick Start

  • Comment formatting
# H1 Header

## H2 Header

### H3 Header

#### H4 Header

##### H5 Header

###### H6 Header

# Alternative H1

## Alternative H2

Reference Guides

Detailed implementations in the `references/` directory:

| Guide | Contents | |---|---| | [Text Formatting](references/text-formatting.md) | Text Formatting | | [Lists](references/lists.md) | Lists | | [Links and Images](references/links-and-images.md) | Links and Images, Code Blocks, Tables | | [Extended Syntax (GitHub Flavored Markdown)](references/extended-syntax-github-flavored-markdown.md) | Extended Syntax (GitHub Flavored Markdown) | | [Collapsible Sections](references/collapsible-sections.md) | Collapsible Sections, Syntax Highlighting, Badges | | [Alerts and Callouts](references/alerts-and-callouts.md) | Alerts and Callouts | | [Mermaid Diagrams](references/mermaid-diagrams.md) | Mermaid Diagrams |

Best Practices

✅ DO

  • Use descriptive link text
  • Include table of contents for long documents
  • Add alt text to images
  • Use code blocks with language specification
  • Keep lines under 80-100 characters
  • Use relative links for internal docs
  • Add badges for build status, coverage, etc.
  • Include examples and screenshots
  • Use semantic line breaks
  • Test all links regularly

❌ DON'T

  • Use "click here" as link text
  • Forget alt text on images
  • Mix HTML and Markdown unnecessarily
  • Use absolute paths for local files
  • Create walls of text without breaks
  • Skip language specification in code blocks
  • Use images for text content (accessibility)
Read more
Ships withuseful-ai-prompts

488 production-ready AI prompts, all following a standardized template with validated quality gates. Transform ChatGPT, Claude, and other AI assistants into expert consultants.

Get the whole plugin