TypingMindTypingMindThe best frontend for AI
Verify Skill Migration logo

Verify Skill Migration

Community
zuharz
verify-skill-migration

Validator-backed migration QA for Codex skills and related docs

Overview

Publisherzuharz
Repositoryccode-to-codex
Skill nameverify-skill-migration
Stars
76
Forks
5
Bundled files
1
LicenseMIT
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.

  • 1 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

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

Installation

Install the Verify Skill Migration 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.
    https://github.com/zuharz/ccode-to-codex/tree/main/.codex/skills/verify-skill-migration
  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/zuharz/ccode-to-codex.git /tmp/ccode-to-codex
mkdir -p .claude/skills
cp -r /tmp/ccode-to-codex/.codex/skills/verify-skill-migration .claude/skills/verify-skill-migration
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Verify Skill Migration 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 Verify Skill Migration 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 Verify Skill Migration 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.

Verify Skill Migration

Use the canonical migration validator after each batch and before finalizing a migrated skill set.

The validator implementation lives at:

  • .codex/skills/verify-skill-migration/scripts/validate_skill_migration.py

Use the stable repo entrypoint for normal runs:

bash
python3 tools/migration_support/validate_names.py

Checks

structural-integrity

  • Fails on MCP callable namespaces that still preserve hyphenated server IDs

frontmatter

  • Applies to SKILL.md entrypoints only
  • Parses YAML frontmatter
  • Requires name and description
  • Fails on prohibited keys: allowed-tools, effort, metadata

line-count

  • Warns when a SKILL.md file reaches 500+ lines
  • Warning only, not a failure

references

  • Validates references/ directories under the scan scope
  • Fails on empty references/ directories
  • Fails on empty reference files, including nested files

Cross-References Check

  • Warns on unknown skill references
  • Uses discovered skill names instead of treating arbitrary backticked words as skills

skill-remnants

  • Fails on legacy skill primitive call syntax in Codex artifacts

stale-paths

  • Fails on operational legacy migration path references
  • Ignores provenance banner lines such as Source: and Generated by:

operator-guidance

  • Applies to the migration-family skill packages
  • Fails on operator-facing repo paths that do not resolve there
  • Fails on mistaken filesystem-root repo paths such as /.codex/...
  • Fails on legacy slash-skill invocations in migration-family operational guidance
  • Resolves skill-local references/... and scripts/... before repo-root paths

agent-dependencies

  • Fails on unresolved named agent runtime dependencies
  • Treats only .codex/agents/*.toml as authoritative runtime contracts
  • Does not let legacy .codex/agents/*.md references satisfy dependency resolution

agent-flattening

  • Warns when spawn_agent(...) appears to lose explicit opus / sonnet / haiku runtime intent
  • Looks for nearby model-intent context without matching model or reasoning_effort overrides

agent-api-shape

  • Warns on migrated-artifact examples that still use legacy positional wait_agent(...) call shapes
  • Targets migration references and Tier 3 migrated skill artifacts without blocking unrelated older skills

executable-primitives

  • Fails on Claude primitives in operational Codex guidance
  • Ignores migration/comparison references and mapping-table contexts where primitive names are discussed, not executed

environment-readiness

  • Inspects an explicit Codex home, defaulting to repo-local .codex
  • Parses config.toml when present
  • Warns on missing MCP commands by default because PATH is host-dependent
  • Parses optional hooks.json and checks referenced hook commands/scripts
  • Warns on oversized or legacy-reference-heavy AGENTS.md
  • Validates plugin manifest JSON when plugin files exist
  • Use --strict-environment-readiness when these host warnings should fail

Usage

Run the full validator during post-flight:

bash
python3 tools/migration_support/validate_names.py

Run a targeted scope:

bash
python3 tools/migration_support/validate_names.py \
  --scan-dir .codex/skills/verify-skill-migration

Run specific checks only:

bash
python3 tools/migration_support/validate_names.py \
  --check frontmatter \
  --check cross-references \
  --check operator-guidance \
  --check agent-dependencies \
  --check agent-api-shape

Run environment readiness against the repo-local Codex config:

bash
python3 tools/migration_support/validate_names.py \
  --check environment-readiness \
  --codex-home .codex

List available checks:

bash
python3 tools/migration_support/validate_names.py --list-checks

Result Semantics

  • FAIL: migration blockers or invalid Codex artifacts
  • WARN: quality issues that should be reviewed but do not block execution
  • PASS: no findings

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Verify Skill Migration AI skill do?

Validator-backed migration QA for Codex skills and related docs

Why use Verify Skill Migration on TypingMind?

Because you install it once and use it with any model. Verify Skill Migration 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 Verify Skill Migration in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/zuharz/ccode-to-codex/tree/main/.codex/skills/verify-skill-migration. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Verify Skill Migration?

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 Verify Skill Migration?

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

Is the Verify Skill Migration AI skill free?

Yes. It is published on GitHub by zuharz under the MIT 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
openclaw logo

Openclaw Refactor Docs

openclaw
OrganizationPopular

Refactor an existing OpenClaw docs page with source-audited preservation, restructuring, and verification.

82.2K
391K
Instructions
View
openclaw logo

Openclaw Repair Sweep

openclaw
OrganizationPopular

Run scoped OpenClaw issue/PR repair campaigns: coordinate workers, prove root causes, and land or close verified work under the requested authority.

82.2K
391K
1 files
View
openclaw logo

Openclaw Test Performance

openclaw
OrganizationPopular

Benchmark, diagnose, and optimize OpenClaw test and plugin-suite runtime, import hotspots, CPU/RSS, heap growth, and slow coverage paths.

82.2K
391K
1 files
View
openclaw logo

Openclaw Testing

openclaw
OrganizationPopular

Choose proportional OpenClaw tests and checks, diagnose failures, and route environment-sensitive or release proof to its owner.

82.2K
391K
2 files
View

Set up your own AI workspace now

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