markdown-img-alt-text_skill

This skill adds thorough alt text to markdown images by analyzing content and updating Obsidian or standard markdown embeds.
  • Shell

49

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill richtabor/agent-skills --skill markdown-img-alt-text

  • skill.md3.3 KB

Overview

This skill scans markdown files and adds detailed alt text to image embeds that are missing it. It supports both Obsidian wiki-style embeds (![[image]]) and standard markdown (). The skill reads each image, generates a single-line, descriptive alt text that captures visual and textual details, and updates the embed inline. It reports counts of found images, skipped items, and updates applied.

How this skill works

The skill searches the specified scope (file, folder, or project) for image embeds that lack alt text: Obsidian embeds without a pipe (|) and standard markdown with empty square brackets. For each found image it resolves the path, reads the image file using the Read tool, and writes a single continuous descriptive alt text that covers visible text, layout, colors, and relevant details. Finally it updates the markdown using the Edit tool in the same embed format the file uses and summarizes the results.

When to use it

  • When you ask to add or update alt text for images across notes or a repo
  • When you want your documentation or notes to be accessible to screen readers
  • When you need searchable, descriptive image metadata for indexing
  • When preparing content for publication or sharing with people who rely on descriptions
  • When converting quick image-heavy notes into production-ready documentation

Best practices

  • Run the skill on a single file or folder first to verify descriptions before bulk changes
  • Provide the scope explicitly (file, folder, or whole project) to avoid unintended edits
  • Prefer concise but specific descriptions: include visible text, key colors, layout, and data values
  • Keep alt text as one continuous sentence per embed and avoid phrases like "Image of" or "Screenshot of"
  • Skip images meant to be purely decorative by marking them manually or leaving them out of the scope

Example use cases

  • Add descriptive alt text across an Obsidian vault so notes become accessible to screen readers
  • Update a docs folder of markdown files with descriptive captions for product screenshots
  • Describe diagrams and charts in a research notebook so collaborators can understand results without images
  • Prepare a blog repository for publishing by ensuring all images include meaningful alt text
  • Generate searchable image descriptions to improve internal knowledge base discoverability

FAQ

Both Obsidian wiki-style embeds (![[image.png]]) and standard markdown images (alt or ).

Will it overwrite existing alt text?

No — images that already include alt text in either format are skipped by default; you can request updates explicitly.

How does the skill handle image paths?

It resolves relative and common project paths (attachments, images folders, public/images) to open the image file before generating descriptions.

What kind of descriptions are generated?

Single-line, detailed descriptions that cover visible text, layout, color cues, UI elements, and data values so someone can understand the image without seeing it.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational