Mysk Extractor

Migrate and crossbreed skills between repositories while documenting provenance for reproducibility research.

Processes

This skill defines six processes, named after mycological and cellular biology:

| Process | File | Description | |---------|------|-------------| | Conidiation | substrate/conidiation.md | Spore production - create/update the portable extraction tool | | Fragmentation | substrate/fragmentation.md | Asexual reproduction - extract a skill from a single source repo | | Plasmogamy | substrate/plasmogamy.md | Sexual reproduction - fuse two skills into a hybrid | | Homeostasis | substrate/homeostasis.md | Self-regulation - maintain process consistency across repositories | | Apoptosis | substrate/apoptosis.md | Programmed death - controlled removal/uninstallation | | Tropism | substrate/tropism.md | Sensory process - discover and locate skills from external sources |

Pedigree Schema

Every extracted skill gets a genealogy file documenting its lineage.

Schema Structure

See genealogy/templates/pedigree.json for the schema template.

Field Reference

| Field | Purpose | |-------|---------| | date | When the extraction occurred | | sourceURL | Git URL of the source repository | | sourcePath | Path to skill within source repo | | sourceCommitID | Exact commit hash at extraction time | | destURL | Git URL of the destination repository | | destPath | Path to skill within destination repo | | destCommitID | Commit hash after extraction was committed | | destOperator | The skill file that performed the extraction | | destModel | Claude model ID that executed the operator |

Crossbreeding Support

The pedigree array supports multiple entries for hybrid skills:

Single entry = conidiation (one parent)
Multiple entries = plasmogamy (multiple parents fused)

Experimental Design: Isolated Agents

Why Exclude Human Input

The pedigree schema captures all variables needed to theoretically reproduce a skill extraction:

Source content (via sourceCommitID)
Transformation logic (via destOperator at destCommitID)
Model version (via destModel)

However, if human prompts influence the extraction, they become an uncontrolled variable that breaks reproducibility.

Isolating Claude's Non-Determinism

By designing extraction processes to:

Spawn subagents rather than work in the main conversation
Feed structured data rather than conversation history
Exclude human prompt context from the transformation

We control for all external variables, leaving Claude's inherent non-determinism as the only remaining variable.

This enables experiments like:

Run identical extractions N times → measure output variance
Compare variance across different operator designs
Correlate variance with task complexity

The pedigree file serves dual purposes:

Genealogy record - trace skill ancestry
Experimental control log - prove all controllable variables were fixed

Implications for Process Design

Both fragmentation.md and plasmogamy.md processes MUST:

Use the Task tool to spawn isolated subagents
Provide all context via structured parameters, not conversation history
Record the exact operator and model in the pedigree

Templates

| File | Purpose | |------|---------| | genealogy/templates/migration-config.json | Migration configuration structure | | genealogy/templates/pedigree.json | Pedigree file template |

Workflow (Fragmentation)

See substrate/fragmentation.md for the full single-source extraction workflow.

High-level phases:

Configure - Define source/destination and cleanup rules
Copy - Transfer skill files
Cleanup - Generalize project-specific references
Genealogy - Create pedigree record
Commit - Finalize with descriptive message

Checklist

[ ] Process spawns isolated subagent (no conversation context)
[ ] Subagent receives structured data only
[ ] Skills copied to destination
[ ] Project names generalized
[ ] Domain terms universalized
[ ] Pedigree file created with all fields populated
[ ] destCommitID recorded after commit