okhp3-refolddec-core
Core ReFolDec transformation skill. Use when the task is explicitly about transforming an artifact from one representation type to another — folding an idea or process into a compact form, unfolding an artifact into its primitives, or refolding across representation types (diagram to documentation, documentation to SKILL.md, SKILL.md to procedure). Also use when semantic loss across a transformation needs to be tracked or compared. This is not a general writing or diagramming skill — it is a representation-change skill. Load domain skills (okhp3-mermaid-core, okhp3-recurring-task-capture) alongside this skill when the transformation target is a diagram or a skill skeleton.
Target: Target not categorized. Automatically collected · unverified.
Excerpt from the author’s documentation
Extracted from a fixed version of SKILL.md in its original language. This is the author’s documentation; installation, compatibility and runtime results have not been verified by this site.
Read the original English text
Topics in the source
- okhp3-refolddec-core
- 1. Identify the Transformation
- 2. Inventory the Source
- 3. Track Semantic Loss
- 4. Execute the Transformation
- 5. Produce the Loss Note
- 6. Cross-Representation Compare (optional)
- What this skill does not do
OverKill Hill P³ · overkillhill.com · github.com/OKHP3 Transformation-aware execution for fold, unfold, and refold operations across representation types. Before executing, name the operation clearly: Fold — the source is a complex artifact; the target is a more abstract or compact form. Examples: process narrative → SKILL.md, set of observations → taxonomy, long document → diagram. Unfold — the source is a compact or abstract artifact; the target exposes its constituent parts. Examples: SKILL.md → step-by-step procedure, diagram → process narrative, taxonomy → flat item list. Refold — the source and target are in different representation types; semantic content is preserved across the change. Examples: diagram → documentation, documentation → SKILL.md, SKILL.md → structured prompt, process → diagram. State the transformation type explicitly before proceeding. "I am refolding [source type] into [target type]." Before transforming, inventory what the source artifact contains: Entities — what things are named or described Relationships — how those things connect, depend on, or act on each other Conditions — decision points, exceptions, and branching logic Constraints — rules, limits,
This is an excerpt. Refer to the complete source and its current requirements.
- Source repository
- OKHP3/skillz
- Source file
- refolddec/okhp3-refolddec-core/SKILL.md
- Fixed revision
- 7b187777d42ab7bc7bab1e5f2c940cd3139ecebf
Sources and evidence
This record was collected automatically. Its documentation, suitability and runtime behavior have not been manually verified.
Author: OKHP3/skillz · original repository metadata. Documentation review: Not reviewed. Last source check: 2026-11-10T10:00:55.534Z.
Categories are inferred from names, descriptions and paths. They do not establish compatibility.
License and attribution
MIT. Third-party content and copyright remain with their authors. Refer to the original license and terms.
Original license ↗Synchronization, copying and user-reported success do not mark a resource as runtime-tested.
Limitations and notes
- Collecting metadata does not mean this site has installed, adapted, runtime-tested or security-reviewed the resource.