script-envelope

Standardize script metadata envelopes with canonical headers and extraction heuristics.

Updated Nov 30, 2025
One-click install
npx skills add https://github.com/poisontr33s/chthonic-archive --skill script-envelope
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: script-envelope
Source: https://github.com/poisontr33s/chthonic-archive/tree/main/.codex/skills/script-envelope
Command: npx skills add https://github.com/poisontr33s/chthonic-archive --skill script-envelope

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Script envelope standards address inconsistent script headers and metadata, preventing tooling and automation misreads.

Core Features & Use Cases

  • Canonical envelope construction and extraction for script metadata (title, module, spectral frequency, semantic ID, purpose, exports, flags, cross-references).
  • Automated normalization of Python headers and open-sided envelopes to maintain consistency across repositories.
  • Optional component directories (scripts, references, assets) for extended metadata, references, and assets.

Quick Start

Run the envelope tool on a target script to generate and align the canonical metadata header and envelope.

Frequently Asked Questions about script-envelope

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

FAQPage Schema
How do I standardize script metadata headers across multiple repositories?

Standardizing script metadata headers ensures consistent headers across scripts by applying a canonical envelope builder to repository-level script conventions. This prevents tooling and automation misreads caused by inconsistent script metadata formats.

What is a canonical script metadata envelope and when do I need one?

A canonical script metadata envelope is a standardized header block containing title, module, purpose, exports, flags, and cross-references. You need one for automation workflows that require deterministic metadata blocks across different programming languages.

Does script envelope normalization work with both Python and PowerShell scripts?

Script envelope normalization supports cross-language envelopes by implementing metadata extraction heuristics specifically for Python and PowerShell. It automatically normalizes Python headers and open-sided envelopes to maintain consistency across repositories.

How do I extract metadata from existing scripts to build a standardized header?

Extracting metadata from existing scripts uses built-in heuristics for Python and PowerShell to identify existing header information. The canonical envelope builder then aligns this extracted data into a standardized metadata block with title, module, and semantic ID.

What's the best way to enforce deterministic metadata blocks for automation workflows?

Enforcing deterministic metadata blocks for automation workflows requires a canonical envelope builder that standardizes script headers. This approach ensures tooling reads consistent metadata, preventing misreads during automated repository-level processing.

Can I include optional component directories like references and assets with script envelopes?

Optional component directories for scripts, references, and assets can be included to manage extended metadata and references. The envelope builder implements safety checks to ensure these directories align with canonical metadata standards.