Teleport logo

Teleport

Community
Hmbown
teleport

Teleport is FULL-CONTEXT migration, not partial transformation. The defining characteristic is that EVERYTHING must move together and keep working: data, dependencies, auth, traffic routing, background jobs, secrets, and human workflows. The old system must remain recoverable until the new one is proven. This spell IS: Database migrations (RDS→Cloud SQL, self-managed→Atlas), cloud provider moves (on-prem→AWS, Heroku→K8s), environment promotions (staging→prod), account/tenant consolidations, platform migrations (Jenkins→GitHub Actions, SendGrid→SES), identity migrations (AD→Azure AD), cluster upgrades with relocation

Overview

PublisherHmbown
RepositoryWizards-of-the-Ghosts
Skill nameteleport
Stars
106
Forks
10
Bundled files
Instructions only
LicenseCC0-1.0
Links
Skill sourceRepository
  • 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 Teleport 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/teleport .claude/skills/teleport
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Teleport 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 Teleport 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 Teleport 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.

Teleport

Move an entire world without leaving its people stranded.

What This Skill Does

Teleport is FULL-CONTEXT migration, not partial transformation. The defining characteristic is that EVERYTHING must move together and keep working: data, dependencies, auth, traffic routing, background jobs, secrets, and human workflows. The old system must remain recoverable until the new one is proven. This spell IS: Database migrations (RDS→Cloud SQL, self-managed→Atlas), cloud provider moves (on-prem→AWS, Heroku→K8s), environment promotions (staging→prod), account/tenant consolidations, platform migrations (Jenkins→GitHub Actions, SendGrid→SES), identity migrations (AD→Azure AD), cluster upgrades with relocation In this grimoire, Teleport is treated as a hybrid spell with a prototype delivery profile. Canonical reference input: Teleport (spell).

When To Use

  • Trigger this spell when the user describes moving an ENTIRE system, service, or environment from one place to another while PRESERVING state and continuity. Look for these patterns:

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. Define boundaries: Identify source world, destination world, and the 5 invariants that must survive: data integrity, authentication, latency/SLA, dependency graph, rollback viability. If any invariant is undefined, stop and ask.
  3. Inventory everything: List every stateful surface and dependency that must travel or reconnect: databases, caches, queues, background jobs, secrets, DNS records, storage volumes, CI/CD pipelines, monitoring/alerting, human operator workflows, third-party integrations.
  4. Design the safety net FIRST: Before any movement plan, specify: rehearsal strategy (dry run in staging), cutover window (when, how long, who approves), rollback path (exact steps to reverse), validation checks (how to prove arrival succeeded), and failure gates (conditions that abort the migration mid-flight).
  5. Sequence the move: Order operations to minimize risk. Typically: replicate data → verify consistency → switch read traffic → switch write traffic → decommission old (after observation period). Return a runbook with explicit timestamps, owners, and go/no-go checkpoints.
  6. Package the result as the deliverables below, with confidence, assumptions, and unresolved risk called out explicitly.

Deliverables

  • Always produce: (1) Migration runbook with sequencing, (2) Rollback plan with decision thresholds, (3) Post-arrival validation checklist covering data, traffic, permissions, and dependencies.

Pitfalls / Guardrails

  • Call out the glue, permissions, or missing infrastructure before you imply this is fully operational.
  • If the request lacks a rollback path OR a way to validate successful arrival, output ONLY the planning phase. Do not proceed to execution steps. Never claim the move is safe without rehearsals, backups, and integrity verification steps.
  • Do not use for: Simple data copies (one table, one file) → use data extraction spells
  • Do not use for: Format transformations (OpenAPI 2→3, Python→TypeScript) → use translation spells
  • Do not use for: Branch switching or git operations → use version control spells
  • Do not use for: Setting up permanent connections (VPN, tunnels) → use infrastructure spells
  • Do not use for: Multi-environment deployments from same config → use deployment spells
  • Do not use for: Feature toggles or A/B testing → use experimentation spells

Verification

  • Check that the result includes every deliverable promised above.
  • Check that confirmed facts, assumptions, and inferences are visibly separated.
  • Check which parts are concrete actions versus framing, so the user can tell what is real now.
  • Check that any missing glue code, permissions, or future work is labeled before the skill is treated as ready.

Example Invocation

text
/teleport plan a full system migration from this source environment to that destination, including cutover, rollback, and post-arrival verification

Frequently asked questions

What does the Teleport AI skill do?

Teleport is FULL-CONTEXT migration, not partial transformation. The defining characteristic is that EVERYTHING must move together and keep working: data, dependencies, auth, traffic routing, background jobs, secrets, and human workflows. The old system must remain recoverable until the new one is proven. This spell IS: Database migrations (RDS→Cloud SQL, self-managed→Atlas), cloud provider moves (on-prem→AWS, Heroku→K8s), environment promotions (staging→prod), account/tenant consolidations, platform migrations (Jenkins→GitHub Actions, SendGrid→SES), identity migrations (AD→Azure AD), cluste...

Why use Teleport on TypingMind?

Because you install it once and use it with any model. Teleport 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 Teleport 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/teleport. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Teleport?

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 Teleport?

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

Is the Teleport 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.

Related AI Skills

View all
addyosmani logo

Observability And Instrumentation

addyosmani
CommunityPopular

Instruments code so production behavior is visible and diagnosable. Use when adding logging, metrics, tracing, or alerting. Use when shipping any feature that runs in production and you need evidence…

10.1K
95.8K
Instructions
View
addyosmani logo

Performance Optimization

addyosmani
CommunityPopular

Optimizes application performance across frontend, backend, queries, and databases. Use when performance requirements exist, when you suspect performance regressions, when Core Web Vitals or load…

10.1K
95.8K
Instructions
View
addyosmani logo

Shipping And Launch

addyosmani
CommunityPopular

Prepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up…

10.1K
95.8K
Instructions
View
addyosmani logo

Using Agent Skills

addyosmani
CommunityPopular

Discovers and invokes agent skills. Use when starting a session, or when you need to decide which skill or workflow applies to the piece of work at hand. This is the meta-skill that governs how all…

10.1K
95.8K
Instructions
View

Set up your own AI workspace now

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