export-csv

Generate a CSV inventory of documentation pages from Markdown frontmatter.

7|7|Updated Feb 2, 2015
One-click install
npx skills add https://github.com/giantswarm/docs --skill export-csv-giantswarm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: export-csv
Source: https://github.com/giantswarm/docs/tree/main/.claude/skills/export-csv
Command: npx skills add https://github.com/giantswarm/docs --skill export-csv-giantswarm

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the generation of a CSV inventory of all documentation pages, including their titles, navigation path levels, and public URLs, simplifying the review, filtering, or analysis of the documentation content.

Core Features & Use Cases

  • Inventory Generation: Automatically creates a CSV file listing all documentation pages.
  • Data Extraction: Extracts page titles, navigation path levels, and URLs from the frontmatter of Markdown files.
  • Use Case: Ideal for content managers who need to review or analyze the structure and content of their documentation.

Quick Start

Run the export-csv skill to generate a CSV inventory of all documentation pages.

Frequently Asked Questions about export-csv

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a CSV inventory of Markdown documentation pages?

Generate a CSV inventory of Markdown documentation pages by running the export-csv script to automatically extract page titles, navigation path levels, and URLs from file frontmatter into a structured spreadsheet.

How do I extract page titles and navigation paths from Markdown frontmatter?

Extract page titles and navigation paths from Markdown frontmatter using a script that parses YAML metadata fields, automatically collecting the title, navigation hierarchy, and URL for each documentation page.

Do I need Python to extract documentation content into a CSV file?

Yes, you need Python to extract documentation content into a CSV file because the generation script relies on Python and YAML parsing capabilities to read Markdown frontmatter and output the inventory data.

What's the best way to create a documentation inventory for content review?

The best way to create a documentation inventory for content review is automating extraction with a script that pulls titles, navigation levels, and URLs from Markdown frontmatter into a single CSV file for filtering and analysis.

Can I include navigation path levels when exporting documentation content to CSV?

Yes, you can include navigation path levels when exporting documentation content to CSV because the script automatically extracts the full navigation hierarchy alongside titles and URLs from each Markdown file's frontmatter.

Why does the CSV inventory export stop working on Markdown files without frontmatter?

The CSV inventory export may stop working on Markdown files without frontmatter because the script depends on YAML metadata to extract titles, navigation path levels, and URLs, which are required fields for populating the inventory.