xlsx-parser

Parse XLSX test documentation into a structured JSON manifest.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/midas44/ttt-expert-v2 --skill xlsx-parser
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: xlsx-parser
Source: https://github.com/midas44/ttt-expert-v2/tree/main/.claude/skills/xlsx-parser
Command: npx skills add https://github.com/midas44/ttt-expert-v2 --skill xlsx-parser

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Parse XLSX test documentation into a JSON manifest for test automation. Use this skill when you need to convert module-specific XLSX workbooks from test-docs/ into a structured manifest consumed by the autotest generator, refresh manifests, or assess test coverage.

Core Features & Use Cases

  • Parse and transform XLSX workbooks into a single JSON manifest that maps test cases to modules, IDs, titles, preconditions, steps, priorities, and tags.
  • Handle merged cells and multi-line step descriptions to preserve data fidelity across worksheets.
  • Use case: when new test documentation is added to test-docs/, run the parser to produce an up-to-date manifest for autotest generation and analytics.

Quick Start

Run the parser by executing the command to process XLSX files into manifest.json (the exact command is provided in the script notes).

Frequently Asked Questions about xlsx-parser

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

FAQPage Schema
How do I convert XLSX test documentation into a structured JSON manifest?

To convert XLSX test documentation into a structured JSON manifest, you can use a parser that reads .xlsx workbooks, iterates through sheets, and extracts test-case data like IDs, modules, steps, and expected results into a single output file.

Can I parse XLSX test cases with merged cells and multi-line steps without losing data?

Yes, parsing XLSX test cases with merged cells and multi-line step descriptions is supported to preserve data fidelity. The parser handles these worksheet complexities while extracting structured test-case data into the manifest.

What is the best way to generate a test automation manifest from multiple Excel workbooks?

The best way to generate a test automation manifest from multiple Excel workbooks is to run a parser that reads all .xlsx files from your input directory, extracts structured test-case data across modules, and outputs a single consolidated JSON manifest.

When do I need to refresh an existing test automation manifest?

You need to refresh an existing test automation manifest when new test documentation is added to your input directory. Running the parser produces an up-to-date manifest for autotest generation and coverage assessment.

Does the parser extract preconditions, priorities, and tags from test docs?

Yes, the parser extracts preconditions, priorities, and tags from test docs. It maps test cases to modules, IDs, titles, steps, and expected results to ensure comprehensive structured data for automation.

How does parsing XLSX test docs into JSON help with test coverage assessment?

Parsing XLSX test docs into JSON helps with test coverage assessment by structuring scattered workbook data into a unified manifest. This structured output enables analytics and validates existing manifests against current documentation.