pandid-valve-tile

Extract valve candidate rows from a P&ID tile image into a markdown stub.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This legacy tool solves the manual effort of identifying valve candidates from a P&ID tile image by focusing only on those valves whose symbol is within the emit zone, producing a compact stub per tile for downstream reconciliation.

Core Features & Use Cases

  • Legacy per-tile valve extraction from P&ID tiles.
  • Emits a single markdown stub at OUTPUT_PATH per tile, with fields depending on mode.
  • Use case: process a single tile to generate a stub for downstream validation.

Quick Start

Provide a P&ID tile image and run the legacy valve-tile extractor to generate a single markdown stub at OUTPUT_PATH.

Frequently Asked Questions about pandid-valve-tile

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

FAQPage Schema
How do I extract valve symbols from a single P&ID tile image?

To extract valve candidates from a P&ID tile image, provide the tile image path, tile geometry, and output path to generate a single markdown stub containing the identified valve rows for downstream reconciliation.

What inputs are required for per-tile P&ID valve extraction?

Required inputs include SOURCE_PDF_NAME, PAGE_NUM, TILE_ID, TILE_IMAGE_PATH, OUTPUT_PATH, MODE, and TILE_GEOMETRY, ensuring the extraction process correctly identifies valves within the specified emit zone.

When should I use a legacy per-tile extractor instead of full-page processing?

Use a legacy per-tile extractor when processing single P&ID tiles with defined read and emit zones is necessary, producing individual markdown stubs for focused downstream validation rather than full-sheet outputs.

Does the legacy valve-tile extractor support reference sheets and scope files?

The legacy valve-tile extractor respects optional flags including ALLOW_REFERENCE_SHEETS and SCOPE_FILE, enabling users to include reference materials and define extraction boundaries during single-tile processing.

What are the limitations of the obsolete per-tile valve extraction approach?

The obsolete per-tile valve extraction approach is limited to single-tile processing with a defined emit zone, producing basic or detailed markdown stubs but lacking modern multi-tile orchestration capabilities.