equipment-costing-extract

Extract costing parameters from KA markdown files into per-KTY CSV files.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/sgttomas/chirality-piping --skill equipment-costing-extract
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: equipment-costing-extract
Source: https://github.com/sgttomas/chirality-piping/tree/main/skills/equipment-costing-extract
Command: npx skills add https://github.com/sgttomas/chirality-piping --skill equipment-costing-extract

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the extraction of costing-relevant design basis parameters for equipment items described in Knowledge Artifacts (KA) within a single Knowledge Type (KTY) folder, enabling rapid construction of equipment-costing registers.

Core Features & Use Cases

  • Read KA-*.md files in a KTY folder to locate equipment items that match a target module type list.
  • Extract structured costing parameters (capacity, power, size, design conditions, and subcomponents) and produce a per-KTY CSV in OUTPUT_ROOT.
  • Optional: enrich subcomponents from an existing Equipment_Extract.md when provided, and cite KA sources for traceability.

Quick Start

Run this skill on a single KTY folder to generate the per-KTY Equipment Costing Extract CSV for downstream consolidation.

Frequently Asked Questions about equipment-costing-extract

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

FAQPage Schema
How do I extract equipment costing parameters from KA markdown files?

Extracting equipment costing data from KA files involves reading KA-*.md, _CONTEXT.md, and _REFERENCES.md within a KTY folder, then writing structured design parameters like capacity and power to a per-KTY CSV output.

What is the best way to build an equipment costing register from Knowledge Artifacts?

Building an equipment costing register from Knowledge Artifacts is best achieved by automating the extraction of structured costing parameters like capacity, power, and size directly from KA markdown files into a per-KTY CSV.

Can I enrich equipment subcomponents using an existing Equipment_Extract.md file?

Yes, you can enrich equipment subcomponents by providing an existing Equipment_Extract.md file, which the skill uses to supplement the extracted costing parameters while maintaining complete source traceability.

Does the extraction process maintain source traceability for costing data?

The extraction process maintains source traceability by using only KA-provided data and enforcing read-only access to KTY folders, ensuring all output CSV parameters can be traced back to their original markdown files.

Are there limitations when extracting costing data from multiple KTY folders?

A limitation is that the extraction process operates on a single Knowledge Type (KTY) folder at a time, generating a per-KTY CSV rather than processing multiple folders simultaneously, requiring downstream consolidation.