migrate-to-projects

migrate-to-projects is a skill for Claude Code, Codex from jerpint/woltspace. It costs 42 tokens per session (1,111 once invoked), scanned A, original, MIT.

A recovery guide for work accidentally edited inside Woltspace's platform code. It moves the user's work into the platform's app folder and restores the platform files to a clean state.

In plain words
What is it for?
Checking changed and untracked files, identifying which are user projects or configuration changes, and moving user work into wolt/apps/. It also helps reset platform code after the changes are understood.
Why use it?
Platform changes can be overwritten by updates or create merge conflicts. This guide helps separate personal work from code that belongs to the platform while preserving the work.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: reads .claude/ paths.

Good fit Checking changed and untracked files, identifying which are user projects or configuration changes, and moving user work into wolt/apps/. It also helps reset platform code after the changes are understood.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jerpint/woltspace/migrate-to-projects
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add jerpint/woltspace --skill migrate-to-projects
Clone the repo
git clone --depth 1 https://github.com/jerpint/woltspace

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for migrate-to-projects

README.md
[![agentmods](https://agentmods.dev/badge/skills/jerpint/woltspace/migrate-to-projects/github.svg)](https://agentmods.dev/skills/jerpint/woltspace/migrate-to-projects)
Your own site
<a href="https://agentmods.dev/skills/jerpint/woltspace/migrate-to-projects"><img src="https://agentmods.dev/badge/skills/jerpint/woltspace/migrate-to-projects/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for migrate-to-projects

Your own site · 80×15
<a href="https://agentmods.dev/skills/jerpint/woltspace/migrate-to-projects"><img src="https://agentmods.dev/badge/skills/jerpint/woltspace/migrate-to-projects.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 42 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,111 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00042 $0.01111
Opus 5.5 $0.00017 $0.00444
Sonnet 5.5 $0.00008 $0.00222
Haiku 4.5 $0.00004 $0.00111

Measured 1mo ago against content hash 1ef4750dd7f4, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

migrate-to-projects scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

container/legacy-skills/migrate-to-projects/SKILL.md · 131 lines

How it starts

The opening of the file, as written. The whole thing — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Migrate to Projects

Your human (or a previous session) edited files in /workspace/woltspace/ — the platform code. This causes problems: when the platform updates, those changes get overwritten or cause merge conflicts. Your job is to safely extract their work into wolt/apps/ and restore the platform to a clean state.

Be careful. This is a recovery operation. Don't lose anyone's work.

Step 1: Assess the damage

Check what's been modified in the platform directory:

cd /workspace/woltspace
git status
git diff --stat

Categorize the changes:

  • User code — new files, new features, apps they built (these need to be saved)
  • Config tweaks — changes to server.js, entrypoint, bot code (these need to be understood, then discarded)
  • Untracked files — new files that aren't part of the platform (likely user work)

Tell the human what you found. Be specific: "You have 3 modified files and 5 new files in the platform directory. Here's what I see..."

Step 2: Extract user work

For each piece of user work you find:

  1. Create an app directory: mkdir -p wolt/apps/{name}
  2. Copy the files there: cp -r /workspace/woltspace/{path} wolt/apps/{name}/
  3. If it's an app that was running on a port, note the port in woltspace.json
  4. If it depends on platform code (imports from server.js, etc.), refactor those dependencies out — the app should be self-contained

Example extractions:

  • Custom API endpoint added to server.js → extract into its own FastAPI/Express server in an app
  • Modified bot behavior → document what they wanted in a memory file, suggest filing an issue
  • New HTML pages in public/ → move to wolt/site/ or an app
  • New scripts in container/bin/ → move to an app

Step 3: Document config changes

Some changes are config tweaks rather than new code. For these:

  • Note what was changed and why (ask the human if unclear)
  • Check if there's a proper way to achieve the same thing (env vars, wolt-specific overrides, skill customization)
  • If it's a legitimate feature request, suggest filing an issue on the woltspace repo

Read the full file on GitHub · 131 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago First seen · 131 lines · 42 tokens per session scan A 1ef4750dd7f4

Subscribe to this mod's changes

migrate-to-projects is a skill published in the GitHub repository jerpint/woltspace (20 stars, last pushed today), licensed MIT. It adds 42 tokens to every session and 1,111 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

story-readiness

Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.

Donchitos/Claude-Code-Game-Studios · 48 tokens

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

qa-project-bootstrap

Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…

petrkindlmann/qa-skills · 124 tokens

handle-linkedin-connection-request-signal

Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…

swan-gtm/gtm-skills · 160 tokens