artifact-upcycle

Consolidate scattered artifacts into structured outputs with metadata normalization.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Artifact-upcycle reduces fragmentation by salvaging orphaned/stale files into structured outputs suitable for reuse and archival.

Core Features & Use Cases

  • Deterministic upcycling workflow that normalizes filenames, adds metadata headers, repairs cross-file links, and archives stale content.
  • Policy-driven invariants ensure safety (dry-run by default, archiving before deletion, one-action-per-pass).
  • Use case: Given a repo with mixed artifacts and references, automatically generate clean artifacts and wire them to dumpster-dive archive.

Quick Start

Run the artifact-upcycle script on a target path to apply the upcycle workflow and produce structured artifacts.

Frequently Asked Questions about artifact-upcycle

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

FAQPage Schema
How do I consolidate scattered artifacts and normalize mixed file types in a repository?

To consolidate scattered artifacts, you can run a policy-driven Python script that normalizes filenames, adds metadata headers, and repairs cross-file links. This deterministic upcycling workflow transforms messy repositories into clean, structured outputs.

What is artifact upcycling and when do I need deterministic file processing?

Artifact upcycling is the process of salvaging orphaned or stale files into structured outputs for reuse and archival. You need it when a repository contains mixed file types requiring deterministic transformations and metadata normalization to reduce fragmentation.

How do I safely archive stale content before deleting files during repository cleanup?

To safely archive stale content, the workflow enforces a dry-run by default and mandates archiving before any deletion. This one-action-per-pass invariant ensures stale content is safely moved to an archive directory without data loss.

Can I use Python to automate cross-file link repairs and metadata normalization?

Yes, you can use a Python-based policy-driven workflow to automate cross-file link repairs and metadata normalization. The script applies deterministic transformations across directories to ensure files are correctly wired and structured.

What are the limitations of one-action-per-pass when upcycling artifacts?

The one-action-per-pass limitation restricts the workflow to a single transformation per execution to enforce safety. This means complex multi-step file processing requires multiple sequential runs to complete the full upcycling and archival process.