dump-s

Parse ETHERCLAW.toml files and aggregate package specifications into Markdown reports.

Updated Apr 1, 2026
One-click install
npx skills add https://github.com/shogochiai/vibecoding-demo --skill dump-s
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dump-s
Source: https://github.com/shogochiai/vibecoding-demo/tree/main/.claude/skills/dump-s
Command: npx skills add https://github.com/shogochiai/vibecoding-demo --skill dump-s

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill simplifies the process of aggregating multiple package specifications into a comprehensive document, reducing manual compilation effort.

Core Features & Use Cases

  • Specification Aggregation: Traverses etherclaw's lazy entries to compile all relevant module specifications into a single Markdown report.
  • Use Case: Ideal for developers and project managers who need an up-to-date, unified view of module requirements across multiple packages.
  • Quick Start: Use the dump-s skill to generate an overview of all package specifications for review or documentation purposes.

Quick Start

Run the dump-s command to output all package specifications as a Markdown document.

Frequently Asked Questions about dump-s

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

FAQPage Schema
How do I consolidate package specifications into a single Markdown document?▼

To consolidate package specifications into a single Markdown document, traverse EtherClaw's lazy entries and parse ETHERCLAW.toml files alongside spec files to generate a unified aggregated report.

What's the best way to aggregate module specifications for project documentation?▼

The best way to aggregate module specifications for project documentation is to extract and compile all relevant module requirements from EtherClaw entries, producing a comprehensive unified Markdown overview.

How does parsing ETHERCLAW.toml files work for generating specification reports?▼

Parsing ETHERCLAW.toml files for generating specification reports works by reading the configuration to traverse lazy entries, extracting module specs, and compiling them into an accurate aggregated Markdown format.

Do I need EtherClaw to generate a unified Markdown overview of package requirements?▼

Yes, you need EtherClaw because the aggregation process specifically parses ETHERCLAW.toml files and traverses its lazy entries to extract and compile the necessary module specifications accurately.

Can I use this specification aggregation for project management review processes?▼

Yes, you can use specification aggregation for project management review processes, as it provides developers and managers an up-to-date, unified view of module requirements across multiple packages.

Why does manual compilation of module specifications fail across multiple packages?▼

Manual compilation of module specifications fails across multiple packages due to the effort required to maintain an up-to-date unified view, which is solved by traversing lazy entries to automate the extraction process.