equipment-extract

Extract physical equipment items from KA-*.md files into a per-KTY equipment register.

Updated Aug 27, 2026

Search Tags:#equipment #data-extraction #extract #knowledge-artifact #knowledge-type #ka-files #kty

Ready to run

npx skills add https://github.com/sgttomas/chirality-piping --skill equipment-extract

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: equipment-extract
Source: https://github.com/sgttomas/chirality-piping/tree/main/skills/equipment-extract
Command: npx skills add https://github.com/sgttomas/chirality-piping --skill equipment-extract

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Extracts discrete physical equipment items from Knowledge Artifact files within a single DOMAIN Knowledge Type folder to support per-KTY equipment registers.

Core Features & Use Cases

Reads KA-*.md within a KTY folder and identifies physically instantiated equipment items (vessels, tanks, heat exchangers, valves, instruments, etc.) as named tags.
Produces a structured per-KTY Equipment Extract document at OUTPUT_ROOT, with source-traceable item rows and a summary.
Supports strict read/write boundaries and traceability for downstream audits.

Quick Start

Run the skill against a target KTY folder containing KA-*.md and generate OUTPUT_ROOT/{KTY_ID}_Equipment_Extract.md

Frequently Asked Questions about equipment-extract

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

FAQPage Schema

How do I extract equipment items from Knowledge Artifact markdown files?▼

Equipment extraction from Knowledge Artifact markdown files involves reading KA-*.md documents within a specific Knowledge Type folder to identify physically instantiated items like vessels, tanks, and valves. It generates a structured equipment register document with source-traceable item rows and a summary count.

What is a per-KTY equipment register and when do I need to build one?▼

A per-KTY equipment register is a structured document cataloging discrete physical equipment items extracted from Knowledge Artifact files. You need to build one when you require a traceable inventory of physical assets like heat exchangers, instruments, and tanks from a specific Knowledge Type folder for downstream audits.

Can I generate an equipment extract from a folder with only _CONTEXT.md and _REFERENCES.md files?▼

No, generating an equipment extract requires KA-*.md files within the target Knowledge Type folder. While the extraction process reads _CONTEXT.md and _REFERENCES.md for related metadata, the core equipment identification relies on parsing the KA-*.md files to produce the OUTPUT_ROOT/{KTY_ID}_Equipment_Extract.md document.

What is the best way to build a traceable equipment register from KA files?▼

The best way to build a traceable equipment register from KA files is to process a single Knowledge Type folder and extract named tags representing physical equipment. This method enforces strict read/write boundaries and produces an output markdown file with a structured table, notes, and a total item count.

Does equipment extraction support downstream audits of physical assets?▼

Yes, equipment extraction supports downstream audits by maintaining strict read/write boundaries and source traceability. The resulting per-KTY equipment register document contains source-traceable item rows extracted directly from KA-*.md files, ensuring data integrity for physical asset verification.

What types of physical equipment items can be extracted from KA-*.md files?▼

Extractable physical equipment items from KA-*.md files include vessels, tanks, heat exchangers, valves, and instruments. The extraction process identifies these physically instantiated assets as named tags within the Knowledge Artifact documents to populate the structured equipment register table.