relay-doc-list

List and summarize design docs and implementation plans from Data Relay vault directories.

Updated Feb 28, 2026
One-click install
npx skills add https://github.com/numeric-io/the-data-relay --skill relay-doc-list
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: relay-doc-list
Source: https://github.com/numeric-io/the-data-relay/tree/main/skills/relay-doc-list
Command: npx skills add https://github.com/numeric-io/the-data-relay --skill relay-doc-list

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you quickly inventory and summarize the design docs and implementation plans stored in the Data Relay vault, enabling faster audits and updates.

Core Features & Use Cases

  • List documents in local/docs/ and local/impls/ with their type, description, associated project, and created date.
  • Group results by type (docs vs impls) and sort by created date (newest first) to surface the most recent work.
  • Use the output to prepare knowledge transfers, project roadmaps, or compliance reports.

Quick Start

List all documents in the local/docs/ and local/impls/ directories and present them grouped by type.

Frequently Asked Questions about relay-doc-list

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

FAQPage Schema
How do I inventory design docs and implementation plans stored in a vault?

You can inventory vault documents by reading YAML frontmatter to extract type, description, project, and created date, then outputting a structured report grouped by document type and sorted by created date.

What is the best way to list knowledge-base documents for a project handoff?

Listing knowledge-base documents for a project handoff is best done by extracting frontmatter metadata from local/docs/ and local/impls/ directories, grouping results by type, and sorting by created date to surface the most recent work first.

How do I extract frontmatter metadata from multiple markdown files for auditing?

Extracting frontmatter metadata for auditing involves reading the YAML frontmatter of files in local/docs/ and local/impls/ to pull type, description, project, and created date fields into a consolidated, structured report.

Can I group vault documents by type and creation date using frontmatter?

Yes, you can group vault documents by type and creation date by parsing the YAML frontmatter of files across local/docs/ and local/impls/, organizing them into docs versus impls categories, and sorting by the created date field.

Does this approach work for generating compliance reports from local docs and impls?

Generating compliance reports from local docs and impls works by scanning the local/docs/ and local/impls/ directories, extracting frontmatter metadata, and producing a structured report suitable for compliance auditing and knowledge transfers.

What are the limitations when summarizing a knowledge-base with frontmatter parsing?

A limitation of summarizing a knowledge-base with frontmatter parsing is that files missing properly formatted YAML frontmatter will not have their type, description, project, or created date extracted, resulting in incomplete inventory reports.