Polymorph logo

Polymorph

Community
Hmbown
polymorph

This spell is about representation change, not: - Naming changes (same structure, different identifiers) - Execution changes (same code, different runtime) - Architecture changes (new system design) - Duplication (same thing, different place) The key test: Can you point to a source artifact and a target artifact where the same information is expressed in structurally different ways? If yes → Polymorph.

Overview

PublisherHmbown
RepositoryWizards-of-the-Ghosts
Skill namepolymorph
Stars
106
Forks
10
Bundled files
Instructions only
LicenseCC0-1.0
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by Hmbown on GitHub. Read the source before you install it.

Installation

Install the Polymorph AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/Hmbown/Wizards-of-the-Ghosts.git /tmp/Wizards-of-the-Ghosts
mkdir -p .claude/skills
cp -r /tmp/Wizards-of-the-Ghosts/generated/hermes/actions-access-and-automation/polymorph .claude/skills/polymorph
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Polymorph in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Polymorph on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Polymorph is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Polymorph

Transform one representation into another entirely — formats, schemas, protocols, or interfaces.

What This Skill Does

This spell is about representation change, not:

  • Naming changes (same structure, different identifiers)
  • Execution changes (same code, different runtime)
  • Architecture changes (new system design)
  • Duplication (same thing, different place) The key test: Can you point to a source artifact and a target artifact where the same information is expressed in structurally different ways? If yes → Polymorph. In this grimoire, Polymorph is treated as a metaphorical spell with a shipping-now delivery profile. Canonical reference input: Polymorph (spell).

When To Use

  • Activate this spell when the user asks to convert, transform, or migrate data, code, or specifications from one representation format to another where the source and target have different structures and require real semantic mapping.
  • Verbs: "convert", "transform", "translate", "migrate" (between formats)
  • Explicit format pairs: "CSV to JSON", "Python to JavaScript", "REST to GraphQL", "YAML to HCL", "Swagger to OpenAPI", "Avro to JSON Schema"
  • Phrases: "preserve the structure but change the format", "map X concepts to Y", "flag what doesn't translate", "equivalent in [target format]"
  • Scope indicators: "150 test files", "50 components", "entire test suite" (still this spell if it's format conversion at scale)

Prerequisites

  • No extra runtime dependencies beyond Hermes Agent and the normal toolset for this session.

Procedure

  1. Restate the target, the success condition, and any no-touch boundaries before taking action.
  2. Identify source and target representations — name both formats explicitly
  3. Map structural correspondences — list what maps to what; identify what has no equivalent
  4. Execute transformation — convert preserving semantics; flag losses immediately
  5. Validate and report — confirm output is well-formed; document preserved, approximated, and lost elements
  6. Package the result as the deliverables below, with confidence, assumptions, and unresolved risk called out explicitly.

Deliverables

  • The transformed artifact in the target representation.
  • A mapping report showing what was preserved, approximated, and lost in translation.
  • Validation that the output is well-formed in the target format.

Pitfalls / Guardrails

  • Keep the metaphor anchored to a real mechanism instead of drifting into lore.
  • Always report losses — never claim lossless conversion when formats differ in expressive power
  • Flag ambiguous mappings — when source concept has no clean target equivalent, say so
  • Validate output format — the result must be syntactically valid in the target representation
  • Do NOT activate this spell for:
  • Do not use for: Global rename/refactor: "rename module X to Y across the codebase" — same structure, different names
  • Do not use for: Disguise/wrapper layers: "make JSON look like XML without changing backend" — not actual transformation
  • Do not use for: Workflow orchestration: "chain these scripts into a pipeline", "create a DAG" — about execution order, not representation
  • Do not use for: Worker pools/parallelism: "spawn background workers for each record" — about concurrency, not format
  • Do not use for: Full redesign from scratch: "rewrite as blockchain-based system" — new architecture, not mapping
  • Do not use for: Cloning/duplicating: "make staging look like production" — copying, not transforming

Verification

  • Check that the result includes every deliverable promised above.
  • Check that confirmed facts, assumptions, and inferences are visibly separated.
  • Check that the metaphor still maps cleanly to a real operational mechanism.

Example Invocation

text
/polymorph transform this from its current form into the target format, and tell me what survived the conversion and what did not

Frequently asked questions

What does the Polymorph AI skill do?

This spell is about representation change, not: - Naming changes (same structure, different identifiers) - Execution changes (same code, different runtime) - Architecture changes (new system design) - Duplication (same thing, different place) The key test: Can you point to a source artifact and a target artifact where the same information is expressed in structurally different ways? If yes → Polymorph.

Why use Polymorph on TypingMind?

Because you install it once and use it with any model. Polymorph is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Polymorph in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Hmbown/Wizards-of-the-Ghosts/tree/main/generated/hermes/actions-access-and-automation/polymorph. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Polymorph?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Polymorph?

As many as you like. As long as a model supports skills, you can use Polymorph with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Polymorph AI skill free?

Yes. It is published on GitHub by Hmbown under the CC0-1.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇