Source profileQuality 61/100

github/awesome-copilot/skills/update-markdown-file-index/SKILL.md

update-markdown-file-index

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

Source repository stars
37,126
Declared platforms
0
Static risk flags
2
Last source update
2026-07-28
Source checked
2026-07-28

Decision brief

What it does—and where it fits

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

Best for

    Not for

    • Tasks that require unconfirmed production actions or broad system permissions.
    • Environments where the pinned source and install steps cannot be inspected.

    Compatibility matrix

    Platform support, with evidence labels

    PlatformStatusEvidenceWhat to check
    CodexNot declaredNo explicit evidencePortability before use
    Claude CodeNot declaredNo explicit evidencePortability before use
    CursorNot declaredNo explicit evidencePortability before use
    Gemini CLINot declaredNo explicit evidencePortability before use
    Open the compatibility checker

    Installation

    Inspect first. Install second.

    The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

    Source-detected install commandSource
    npx skills add https://github.com/github/awesome-copilot --skill "skills/update-markdown-file-index"
    Safe inspection promptEditorial

    Inspect the Agent Skill "update-markdown-file-index" from https://github.com/github/awesome-copilot/blob/9933dcad5be5caeb288cebcd370eeeb2fc2f1685/skills/update-markdown-file-index/SKILL.md at commit 9933dcad5be5caeb288cebcd370eeeb2fc2f1685. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

    Workflow

    What the source asks the agent to do

    1. 01

      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…

      Scan: Read the target markdown file ${file} to understand existing structureDiscover: List all files in the specified folder ${input:folder} matching pattern ${input:pattern}Analyze: Identify if an existing table/index section exists to update, or create new structure
    2. 02

      File Analysis

      For each discovered file, extract:

      Name: Filename with or without extension based on contextType: File extension and category (e.g., .md, .js, .py)Description: First line comment, header, or inferred purpose
    3. 03

      Table Structure Options

      Choose format based on file types and existing content:

      Choose format based on file types and existing content:
    4. 04

      Option 1: Simple List

      Review the “Option 1: Simple List” section in the pinned source before continuing.

      Review and apply the “Option 1: Simple List” source section.

    Permission review

    Static risk signals and limitations

    Writes files

    medium · line 1

    The documentation asks the agent to create, modify, or delete local files.

    # Update Markdown File Index

    Writes files

    medium · line 3

    The documentation asks the agent to create, modify, or delete local files.

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

    Reads files

    low · line 7

    The documentation asks the agent to read local files, directories, or repositories.

    **Scan**: Read the target markdown file `${file}` to understand existing structure

    Evidence record

    Why each signal appears

    EvidenceSourceComputedTestedEditorial
    SignalValueEvidence typeMeaning
    Quality score61/100ComputedDocumentation, specificity, maintenance, and trust rules
    Repository stars37,126SourceRepository attention, not individual Skill quality
    Compatibility0 platformsSourceDeclared in the catalog source record
    Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

    Pinned source

    Provenance and original SKILL.md

    Repository
    github/awesome-copilot
    Skill path
    skills/update-markdown-file-index/SKILL.md
    Commit
    9933dcad5be5caeb288cebcd370eeeb2fc2f1685
    License
    MIT
    Collected
    2026-07-28
    Default branch
    main
    View the original SKILL.md

    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

    FileTypeDescription
    filename.extExtensionDescription
    filename2.extExtensionDescription

    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

    Alternatives

    Compare before choosing

    Computed 10042,015

    coreyhaines31/marketingskills

    ab-testing

    When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program

    Computed 10042,015

    coreyhaines31/marketingskills

    churn-prevention

    When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'people keep canceling,' 'churn rate is too high,' 'how do I keep users,' or 'customers are leaving.' Use this whenever someone is losing subscribers o

    Computed 997

    event4u-app/agent-config

    design-review

    Use when the user says "review the design", "check the UI", or wants a comprehensive UI/UX review. Uses a 7-phase methodology covering interaction, responsiveness, accessibility, and more.

    Computed 9831,966

    K-Dense-AI/scientific-agent-skills

    dask

    Distributed computing for larger-than-RAM pandas/NumPy workflows. Use when you need to scale existing pandas/NumPy code beyond memory or across clusters. Best for parallel file processing, distributed ML, integration with existing pandas code. For out-of-core analytics on single machine use vaex; for in-memory speed use polars.