structured-input

Normalize freeform, XML, and file inputs into a canonical object model.

1|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/dsteven12/airtable-sa-skills --skill structured-input
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: structured-input
Source: https://github.com/dsteven12/airtable-sa-skills/tree/main/skills/structured-input
Command: npx skills add https://github.com/dsteven12/airtable-sa-skills --skill structured-input

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Shared input normalization framework for all doc-generating and analysis skills. Dependency read by consuming skills (workflow-doc, technical-design-doc, health-check, training-guide, etc.) before they process user input. Provides: a base XML input schema, a normalization protocol that converts any input into a canonical object, an extension pattern for domain-specific fields, and file/folder input normalization via file-input-schema. Reference when building new doc-generating skills that accept client context, transcripts, or file attachments.

Core Features & Use Cases

  • Base XML Schema: defines a common input wrapper with fields like client, solution, brand_color, stakeholders, content, and file inputs.
  • Extension pattern: skills can add domain-specific fields inside their own wrapper (e.g., <workflow-doc>, <technical-design-doc>, etc.).
  • File-input-schema integration: supports files and folders and normalized metadata with confidence scores.
  • Deterministic normalization: converts freeform or mixed inputs into a canonical object for downstream steps.

Quick Start

Provide structured input to consuming skills following the canonical object defined in this framework.

Frequently Asked Questions about structured-input

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

FAQPage Schema
How do I normalize freeform input for documentation generation?

Input normalization standardizes mixed freeform and XML-structured data into a canonical object model. This ensures consistent downstream behavior for doc-generation and analysis workflows across various input formats.

What is a canonical object model for input validation?

A canonical object model is a standardized data structure representing normalized inputs. It acts as a single source of truth for downstream steps, ensuring consistent processing across documentation generation and analysis workflows.

How do I standardize file and folder inputs for downstream analysis?

You standardize file and folder inputs using the file-input-schema integration. It normalizes file metadata with confidence scores, integrating them into the canonical object for consistent downstream analysis.

Does this input normalization framework support XML schemas for domain-specific fields?

Yes, the framework supports XML schemas for domain-specific fields. It provides a base schema and an extension pattern, allowing consuming skills to add custom fields within their own specific XML wrappers.

When do I need a shared input normalization framework for multiple skills?

You need a shared input normalization framework when building multiple doc-generating or analysis skills that accept diverse inputs like client context, transcripts, or file attachments. It ensures deterministic processing and consistent behavior.

What is the best way to structure mixed inputs for technical design docs?

The best way to structure mixed inputs is using the base XML schema wrapper. This allows you to define domain-specific fields inside a technical-design-doc wrapper while relying on the framework for deterministic normalization.