[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73CS25XSWV4FJ3XKW6HWBJ7":3,"skill-same:01M73CS25XSWV4FJ3XKW6HWBJ7":59},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":37,"commitSha":38,"skillDirectory":39,"forksCount":40,"repositoryHtmlUrl":41,"repositoryHomepageUrl":6,"ownerHtmlUrl":42,"ownerBlogUrl":43,"ownerDescription":6,"updatedAt":44,"install":45,"resources":58},"01M73CS25XSWV4FJ3XKW6HWBJ7","transmute",null,"Transform a single function, module, or data structure from one form to another while preserving its essential behavior. Lighter-weight than the full athanor cycle, suitable for targeted conversions where the input and output forms are well-understood. Use when converting a function between languages, shifting a module between paradigms, migrating an API consumer to a new version, converting data formats, or replacing a dependency — when the transformation scope is a single function, class, or module rather than a full system.","roohe\u002Fagentic-super-skills","roohe","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F99054084?v=4","01M734WCDFP6RZVT5CNM00QR26","01M734WCE4BD0T4NZS5PCV9V5F",10,"MIT","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Ftransmute\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: transmute\nlocale: caveman-lite\nsource_locale: en\nsource_commit: 82c77053\ntranslator: \"Julius Brussee homage — caveman\"\ntranslation_date: \"2026-05-03\"\ndescription: >\n  Transform a single function, module, or data structure from one form to\n  another while preserving its essential behavior. Lighter-weight than the full\n  athanor cycle, suitable for targeted conversions where the input and output\n  forms are well-understood. Use when converting a function between languages,\n  shifting a module between paradigms, migrating an API consumer to a new\n  version, converting data formats, or replacing a dependency — when the\n  transformation scope is a single function, class, or module rather than a\n  full system.\nlicense: MIT\nallowed-tools: Read Write Edit Bash Grep Glob\nmetadata:\n  author: Philipp Thoss\n  version: \"1.0\"\n  domain: alchemy\n  complexity: intermediate\n  language: multi\n  tags: alchemy, transmutation, conversion, refactoring, transformation, targeted\n---\n\n# Transmute\n\nTransform a specific piece of code or data from one form to another — language translation, paradigm shift, format conversion, or API migration — while preserving essential behavior and semantics.\n\n## When to Use\n\n- Converting a function from one language to another (Python to R, JavaScript to TypeScript)\n- Shifting a module from one paradigm (class-based to functional, callbacks to async\u002Fawait)\n- Migrating an API consumer from v1 to v2 of an external service\n- Converting data between formats (CSV to Parquet, REST to GraphQL schema)\n- Replacing a dependency with an equivalent (moment.js to date-fns, jQuery to vanilla JS)\n- When the transformation scope is a single function, class, or module (not a full system)\n\n## Inputs\n\n- **Required**: Source material (file path, function name, or data sample)\n- **Required**: Target form (language, paradigm, format, or API version)\n- **Optional**: Behavioral contract (tests, type signatures, or expected I\u002FO pairs)\n- **Optional**: Constraints (must maintain backward compatibility, performance budget)\n\n## Procedure\n\n### Step 1: Analyze the Source Material\n\nUnderstand exactly what the source does before attempting transformation.\n\n1. Read the source completely — every branch, edge case, and error path\n2. Identify the **behavioral contract**:\n   - What inputs does it accept? (types, ranges, edge cases)\n   - What outputs does it produce? (return values, side effects, error signals)\n   - What invariants does it maintain? (ordering, uniqueness, referential integrity)\n3. Catalog dependencies: what does the source import, call, or rely on?\n4. If tests exist, read them to understand expected behavior\n5. If no tests exist, write behavioral characterization tests before transmuting\n\n**Got:** A complete understanding of what the source does (not how it does it). The behavioral contract is explicit and testable.\n\n**If fail:** If the source is too complex for a single transmute, consider breaking it into smaller pieces or escalating to the full `athanor` procedure. If behavior is ambiguous, ask for clarification rather than guessing.\n\n### Step 2: Map Source to Target Form\n\nDesign the transformation mapping.\n\n1. For each element in the source, identify the target equivalent:\n   - Language constructs: loops → map\u002Ffilter, classes → closures, etc.\n   - API calls: old endpoint → new endpoint, request\u002Fresponse shape changes\n   - Data types: data frame columns → schema fields, nested JSON → flat tables\n2. Identify elements with **no direct equivalent**:\n   - Source features missing in target (e.g., pattern matching in a language without it)\n   - Target idioms that don't exist in source (e.g., R's vectorization vs. Python loops)\n3. For each gap, choose an adaptation strategy:\n   - Emulate: reproduce the behavior with target-native constructs\n   - Simplify: if the source construct was a workaround, use the target's native solution\n   - Document: if behavior changes slightly, note the difference explicitly\n4. Write the **transformation map**: source element → target element, for every piece\n\n**Got:** A complete mapping where every source element has a target destination. Gaps are identified and adaptation strategies chosen.\n\n**If fail:** If too many elements lack direct equivalents, the transformation may be inappropriate (e.g., transmuting a highly object-oriented design into a language without classes). Reconsider the target form or escalate to `athanor`.\n\n### Step 3: Execute the Transformation\n\nWrite the target form following the map.\n\n1. Create the target file(s) with appropriate structure and boilerplate\n2. Transmute each element following the map from Step 2:\n   - Preserve the behavioral contract — same inputs produce same outputs\n   - Use target-native idioms rather than literal translations\n   - Maintain or improve error handling\n3. Handle dependencies:\n   - Replace source dependencies with target equivalents\n   - If a dependency has no equivalent, implement a minimal adapter\n4. Add inline comments only where the transformation was non-obvious\n\n**Got:** A complete target implementation that follows the transformation map. The code reads like it was written natively in the target form, not mechanically translated.\n\n**If fail:** If a specific element resists transformation, isolate it. Transform everything else first, then tackle the resistant element with focused attention. If it truly cannot be transmuted, document why and provide a workaround.\n\n### Step 4: Verify Behavioral Equivalence\n\nConfirm the transmuted form preserves the original's behavior.\n\n1. Run the behavioral contract tests against the target implementation\n2. For each test case, verify:\n   - Same inputs → same outputs (within acceptable tolerance for numeric conversions)\n   - Same error conditions → equivalent error signals\n   - Side effects (if any) are preserved or documented as changed\n3. Check edge cases explicitly:\n   - Null\u002FNA\u002Fundefined handling\n   - Empty collections\n   - Boundary values (max int, empty string, zero-length arrays)\n4. If the target form adds capabilities (e.g., type safety), verify those too\n\n**Got:** All behavioral contract tests pass. Edge cases are handled equivalently. Any behavioral differences are documented and intentional.\n\n**If fail:** If tests fail, diff the source and target behavior to find the divergence. Fix the target to match the source contract. If the divergence is intentional (e.g., fixing a bug in the original), document it explicitly.\n\n## Validation Checklist\n\n- [ ] Source material fully analyzed with explicit behavioral contract\n- [ ] Transformation map covers every source element\n- [ ] Gaps identified with adaptation strategies documented\n- [ ] Target implementation uses native idioms (not literal translation)\n- [ ] All behavioral contract tests pass against target\n- [ ] Edge cases verified (null, empty, boundary values)\n- [ ] Dependencies resolved with target equivalents\n- [ ] Any behavioral differences documented and intentional\n\n## Pitfalls\n\n- **Literal translation**: Writing Python-in-R or Java-in-JavaScript instead of using target idioms. The result should look native\n- **Skipping behavioral tests**: Transmuting without tests means you can't verify equivalence. Write characterization tests first\n- **Ignoring edge cases**: The happy path transmutes easily; edge cases are where bugs hide\n- **Over-engineering the adapter**: If a dependency needs a 200-line adapter, the transmutation scope is too large\n- **Transmuting comments verbatim**: Comments should explain the target code, not echo the source. Rewrite them\n\n## Related Skills\n\n- `athanor` — Full four-stage transformation for systems too large for a single transmute\n- `chrysopoeia` — Optimizing transmuted code for maximum value extraction\n- `review-software-architecture` — Post-transmutation architecture review for larger conversions\n- `serialize-data-formats` — Specialized data format conversion procedures\n","# Transmute\n\nTransform a specific piece of code or data from one form to another — language translation, paradigm shift, format conversion, or API migration — while preserving essential behavior and semantics.\n\n## When to Use\n\n- Converting a function from one language to another (Python to R, JavaScript to TypeScript)\n- Shifting a module from one paradigm (class-based to functional, callbacks to async\u002Fawait)\n- Migrating an API consumer from v1 to v2 of an external service\n- Converting data between formats (CSV to Parquet, REST to GraphQL schema)\n- Replacing a dependency with an equivalent (moment.js to date-fns, jQuery to vanilla JS)\n- When the transformation scope is a single function, class, or module (not a full system)\n\n## Inputs\n\n- **Required**: Source material (file path, function name, or data sample)\n- **Required**: Target form (language, paradigm, format, or API version)\n- **Optional**: Behavioral contract (tests, type signatures, or expected I\u002FO pairs)\n- **Optional**: Constraints (must maintain backward compatibility, performance budget)\n\n## Procedure\n\n### Step 1: Analyze the Source Material\n\nUnderstand exactly what the source does before attempting transformation.\n\n1. Read the source completely — every branch, edge case, and error path\n2. Identify the **behavioral contract**:\n   - What inputs does it accept? (types, ranges, edge cases)\n   - What outputs does it produce? (return values, side effects, error signals)\n   - What invariants does it maintain? (ordering, uniqueness, referential integrity)\n3. Catalog dependencies: what does the source import, call, or rely on?\n4. If tests exist, read them to understand expected behavior\n5. If no tests exist, write behavioral characterization tests before transmuting\n\n**Got:** A complete understanding of what the source does (not how it does it). The behavioral contract is explicit and testable.\n\n**If fail:** If the source is too complex for a single transmute, consider breaking it into smaller pieces or escalating to the full `athanor` procedure. If behavior is ambiguous, ask for clarification rather than guessing.\n\n### Step 2: Map Source to Target Form\n\nDesign the transformation mapping.\n\n1. For each element in the source, identify the target equivalent:\n   - Language constructs: loops → map\u002Ffilter, classes → closures, etc.\n   - API calls: old endpoint → new endpoint, request\u002Fresponse shape changes\n   - Data types: data frame columns → schema fields, nested JSON → flat tables\n2. Identify elements with **no direct equivalent**:\n   - Source features missing in target (e.g., pattern matching in a language without it)\n   - Target idioms that don't exist in source (e.g., R's vectorization vs. Python loops)\n3. For each gap, choose an adaptation strategy:\n   - Emulate: reproduce the behavior with target-native constructs\n   - Simplify: if the source construct was a workaround, use the target's native solution\n   - Document: if behavior changes slightly, note the difference explicitly\n4. Write the **transformation map**: source element → target element, for every piece\n\n**Got:** A complete mapping where every source element has a target destination. Gaps are identified and adaptation strategies chosen.\n\n**If fail:** If too many elements lack direct equivalents, the transformation may be inappropriate (e.g., transmuting a highly object-oriented design into a language without classes). Reconsider the target form or escalate to `athanor`.\n\n### Step 3: Execute the Transformation\n\nWrite the target form following the map.\n\n1. Create the target file(s) with appropriate structure and boilerplate\n2. Transmute each element following the map from Step 2:\n   - Preserve the behavioral contract — same inputs produce same outputs\n   - Use target-native idioms rather than literal translations\n   - Maintain or improve error handling\n3. Handle dependencies:\n   - Replace source dependencies with target equivalents\n   - If a dependency has no equivalent, implement a minimal adapter\n4. Add inline comments only where the transformation was non-obvious\n\n**Got:** A complete target implementation that follows the transformation map. The code reads like it was written natively in the target form, not mechanically translated.\n\n**If fail:** If a specific element resists transformation, isolate it. Transform everything else first, then tackle the resistant element with focused attention. If it truly cannot be transmuted, document why and provide a workaround.\n\n### Step 4: Verify Behavioral Equivalence\n\nConfirm the transmuted form preserves the original's behavior.\n\n1. Run the behavioral contract tests against the target implementation\n2. For each test case, verify:\n   - Same inputs → same outputs (within acceptable tolerance for numeric conversions)\n   - Same error conditions → equivalent error signals\n   - Side effects (if any) are preserved or documented as changed\n3. Check edge cases explicitly:\n   - Null\u002FNA\u002Fundefined handling\n   - Empty collections\n   - Boundary values (max int, empty string, zero-length arrays)\n4. If the target form adds capabilities (e.g., type safety), verify those too\n\n**Got:** All behavioral contract tests pass. Edge cases are handled equivalently. Any behavioral differences are documented and intentional.\n\n**If fail:** If tests fail, diff the source and target behavior to find the divergence. Fix the target to match the source contract. If the divergence is intentional (e.g., fixing a bug in the original), document it explicitly.\n\n## Validation Checklist\n\n- [ ] Source material fully analyzed with explicit behavioral contract\n- [ ] Transformation map covers every source element\n- [ ] Gaps identified with adaptation strategies documented\n- [ ] Target implementation uses native idioms (not literal translation)\n- [ ] All behavioral contract tests pass against target\n- [ ] Edge cases verified (null, empty, boundary values)\n- [ ] Dependencies resolved with target equivalents\n- [ ] Any behavioral differences documented and intentional\n\n## Pitfalls\n\n- **Literal translation**: Writing Python-in-R or Java-in-JavaScript instead of using target idioms. The result should look native\n- **Skipping behavioral tests**: Transmuting without tests means you can't verify equivalence. Write characterization tests first\n- **Ignoring edge cases**: The happy path transmutes easily; edge cases are where bugs hide\n- **Over-engineering the adapter**: If a dependency needs a 200-line adapter, the transmutation scope is too large\n- **Transmuting comments verbatim**: Comments should explain the target code, not echo the source. Rewrite them\n\n## Related Skills\n\n- `athanor` — Full four-stage transformation for systems too large for a single transmute\n- `chrysopoeia` — Optimizing transmuted code for maximum value extraction\n- `review-software-architecture` — Post-transmutation architecture review for larger conversions\n- `serialize-data-formats` — Specialized data format conversion procedures\n",{"name":5,"locale":23,"license":14,"metadata":24,"translator":31,"description":32,"allowed-tools":33,"source_commit":34,"source_locale":35,"translation_date":36},"caveman-lite",{"tags":25,"author":26,"domain":27,"version":28,"language":29,"complexity":30},"alchemy, transmutation, conversion, refactoring, transformation, targeted","Philipp Thoss","alchemy","1.0","multi","intermediate","Julius Brussee homage — caveman","Transform a single function, module, or data structure from one form to another while preserving its essential behavior. Lighter-weight than the full athanor cycle, suitable for targeted conversions where the input and output forms are well-understood. Use when converting a function between languages, shifting a module between paradigms, migrating an API consumer to a new version, converting data formats, or replacing a dependency — when the transformation scope is a single function, class, or module rather than a full system.\n","Read Write Edit Bash Grep Glob","82c77053","en","2026-05-03","master","f483e54f3ad5f202a77d45f2e57f8d970b71195f","skills_library\u002Ftransmute",2,"https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills","https:\u002F\u002Fgithub.com\u002Froohe","yoou.link","2026-05-19 15:56:07",{"source":8,"skillName":5,"commands":46,"prompt":56,"zipAvailable":57},[47,50,53],{"tool":48,"command":49},"npx","npx skills add roohe\u002Fagentic-super-skills --skill transmute",{"tool":51,"command":52},"bunx","bunx skills add roohe\u002Fagentic-super-skills --skill transmute",{"tool":54,"command":55},"pnpm","pnpm dlx skills add roohe\u002Fagentic-super-skills --skill transmute","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Ftransmute\u002FSKILL.md",true,[],[60,67,74,81,88,95],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":18},"01M73D865CZME2FCMKA4PQM348","zarr-python","Chunked N-D arrays for cloud storage. Compressed arrays, parallel I\u002FO, S3\u002FGCS integration, NumPy\u002FDask\u002FXarray compatible, for large-scale scientific computing pipelines.","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fzarr-python\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":18},"01M73D7Z64J4ABWZJD7P44XBBF","youtube-downloader","Download and process YouTube content for research. Use when: downloading competitor videos for analysis; extracting audio for podcasts; getting transcripts for content repurposing; archiving webinars; research content curation","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fyoutube-downloader\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":18},"01M73D7K8778TGZV3GJFR3703D","yc-pitch-deck","Create a compelling startup pitch deck that follows the structure proven to raise billions from top investors. Master the YC and Sequoia formats that get founders funded. Use when: **Fundraising** to create investor pitch decks; **YC application** to structure your narrative; **Demo Day prep** to craft your 2-minute pitch; **Angel investors** to communicate your opportunity; **Partnership pitches** to structure compelling asks","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fyc-pitch-deck\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":18},"01M73D70KJSE0E8Z28YMNNRT04","x-twitter-scraper","Use when the user needs X (Twitter) data or confirmation-gated X actions through Xquik: tweet search, user lookup, follower extraction, media download, monitoring, webhooks, MCP, SDKs, posting, likes, DMs, and profile updates. Requires a Xquik API key. Never ask for X login material.","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fx-twitter-scraper\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":18},"01M73D6ED01GV077R7K4NZNFZJ","write-vignette","Create R package vignettes using R Markdown or Quarto. Covers vignette setup, YAML configuration, code chunk options, building and testing, and CRAN requirements for vignettes. Use when adding a Getting Started tutorial, documenting complex workflows spanning multiple functions, creating domain-specific guides, or when CRAN submission requires user-facing documentation beyond function help pages.","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fwrite-vignette\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":18},"01M73D69YJR0BK3NFHE0CYG3EF","write-validation-documentation","Write IQ\u002FOQ\u002FPQ validation documentation for computerized systems in regulated environments. Covers protocols, reports, test scripts, deviation handling, and approval workflows. Use when validating R or other software for regulated use, preparing for a regulatory audit, documenting qualification of computing environments, or creating and updating validation protocols and reports for new or re-qualified systems.","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fwrite-validation-documentation\u002FSKILL.md",[],[]]