Catalog
github/update-markdown-file-index

github

update-markdown-file-index

Update a markdown file section with an index/table of files from a specified folder.

v1.0Latest
New~649Updated Jun 26, 2026

Update Markdown File Index

Update markdown file ${file} with an index/table of files from folder ${input:folder}.

Process

  1. Scan: Read the target markdown file ${file} to understand existing structure
  2. Discover: List all files in the specified folder ${input:folder} matching pattern ${input:pattern}
  3. Analyze: Identify if an existing table/index section exists to update, or create new structure
  4. Structure: Generate appropriate table/list format based on file types and existing content
  5. Update: Replace existing section or add new section with file index
  6. Validate: Ensure markdown syntax is valid and formatting is consistent

File Analysis

For each discovered file, extract:

  • Name: Filename with or without extension based on context
  • Type: File extension and category (e.g., .md, .js, .py)
  • Description: First line comment, header, or inferred purpose
  • Size: File size for reference (optional)
  • Modified: Last modified date (optional)

Table Structure Options

Choose format based on file types and existing content:

Option 1: Simple List

## Files in ${folder}

- [filename.ext](path/to/filename.ext) - Description
- [filename2.ext](path/to/filename2.ext) - Description

Option 2: Detailed Table

File Type Description
filename.ext Extension Description
filename2.ext Extension Description

Option 3: Categorized Sections

Group files by type/category with separate sections or sub-tables.

Update Strategy

  • 🔄 Update existing: If table/index section exists, replace content while preserving structure
  • Add new: If no existing section, create new section using best-fit format
  • 📋 Preserve: Maintain existing markdown formatting, heading levels, and document flow
  • 🔗 Links: Use relative paths for file links within the repository

Section Identification

Look for existing sections with these patterns:

  • Headings containing: "index", "files", "contents", "directory", "list"
  • Tables with file-related columns
  • Lists with file links
  • HTML comments marking file index sections

Requirements

  • Preserve existing markdown structure and formatting
  • Use relative paths for file links
  • Include file descriptions when available
  • Sort files alphabetically by default
  • Handle special characters in filenames
  • Validate all generated markdown syntax
Files1
1 files · 1.0 KB

Select a file to preview

Overall Score

77/100

Grade

B

Good

Safety

82

Quality

73

Clarity

80

Completeness

68

Summary

This skill automates the creation and maintenance of markdown file indexes within documentation. It scans specified folders, extracts file metadata, and updates or inserts structured tables/lists into markdown files using patterns like "index", "files", or "contents" to identify target sections.

Detected Capabilities

read markdown fileslist directory contentsparse file metadatamodify markdown filesinfer file descriptionsgenerate formatted tables and lists

Trigger Keywords

Phrases that MCP clients use to match this skill to user intent.

generate file indexupdate documentation tableauto-index foldermarkdown file listingdocument directory structure

Use Cases

  • Auto-generate file listings in README or documentation files
  • Maintain up-to-date directory indexes as folder contents change
  • Document project file structure and organization
  • Create categorized file tables grouped by type or purpose
  • Link to files within repository documentation

Quality Notes

  • Clear process steps walk through discovery, analysis, and update phases
  • Multiple table format options (list, table, categorized) provide flexibility for different use cases
  • Well-documented section identification patterns help locate target content reliably
  • Scope is appropriately bounded to markdown file updates with no destructive operations
  • Instructions specify preservation of existing structure and relative path usage as safety practices
  • Missing: error handling guidance for edge cases (empty folders, no matching patterns, invalid markdown)
  • Missing: examples of actual before/after markdown transformations
  • Missing: guidance on handling conflicts if multiple matching sections exist
  • Pattern matching for section identification could be ambiguous (headings with 'contents' might match too broadly)
Model: claude-haiku-4-5-20251001Analyzed: Jun 26, 2026

Reviews

Add this skill to your library to leave a review.

No reviews yet

Be the first to share your experience.

Use github/update-markdown-file-index in your dev environment

Command Palette

Search for a command to run...