Agent skill

Ok Config Migration

by AliceJump in AliceJump/ok-end-field

Migrate persisted ok-end-field task settings when a key, value format, or owning task changes.

AGPL-3.0Auto-check passed

Install Ok Config Migration

skills CLI
$ npx skills add AliceJump/ok-end-field --skill ok-config-migration -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install AliceJump/ok-end-field ok-config-migration --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/AliceJump/ok-end-field.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/ok-config-migration .claude/skills/ok-config-migration && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
ok-config-migration
GitHub stars
556
Token cost
~750 tokens
SKILL.md length
368 words
Files
1
Skills in repo
14
Repo updated
First seen
Licence
AGPL-3.0

At a glance

Migrate persisted ok-end-field task settings when a key, value format, or owning task changes.

  • Task JSON and account-specific overrides so existing user values survive
  • SKILL.md covers Same task file, Between task files and Verify
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Ok Config Migration is an agent skill from AliceJump/ok-end-field. Migrate persisted ok-end-field task settings when a key, value format, or owning task changes. Use for task JSON and account-specific overrides so existing user values survive.

Its SKILL.md is about 750 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: 终末地 End Field Automation 基于ok-script开发的自动化. The licence is AGPL-3.0.

When your agent uses it

  • Task JSON and account-specific overrides so existing user values survive

Example prompts

  • “/ok-config-migration”

What it can do on your machine

Read from SKILL.md and the folder at commit 31604a6. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Ok Config Migration loads about 750 tokens when it runs. Until then it costs about 49 tokens; SKILL.md has 368 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~49
When it runs · the whole SKILL.md, loaded when a task matches
~750

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from AliceJump/ok-end-field at commit 31604a6, republished under its AGPL-3.0 licence (© AliceJump). 368 words, ~750 tokens.

Download SKILL.mdSave it as .claude/skills/ok-config-migration/SKILL.md (or your agent's skills folder).
name
ok-config-migration
description
Migrate persisted ok-end-field task settings when a key, value format, or owning task changes. Use for task JSON and account-specific overrides so existing user values survive.

OK Script Config Migration

Config.verify_config deletes keys absent from a task's default_config on load. Implement the migration before changing the schema and ship both in the same commit; do not deploy them in stages. Test old persisted data before launching the app, and keep the new key in the target defaults. Paths come from config_folder, not a hard-coded configs/ directory.

Same task file

  • Rename: add config_key_migrations = {"旧键": "新键"} to the task or mixin. BaseEfTask.load_config collects MRO tables and copies values before framework loading; an existing new value wins. The copy helper retains the old key only at that stage: framework loading subsequently removes keys absent from defaults. If rollback must retain the old value, back up the source file or temporarily retain the old default key.
  • Value format: add config_value_migrations = {"新键": transform}. Key copies run first; see src/core/config_migration.py for helpers and _NO_MIGRATION.
  • These tables touch only <TaskClass>.json. If accounts can override the setting, migrate the matching entries in account_scoped_overrides.json through src/tasks/account/account_scope_store.py:update_overrides, preserving existing new values.

Between task files

For the daily task split, append a new batch ID to DAILY_SPLIT_IMPORTS in src/tasks/daily/split_config_migrator.py. Map source task/key to target task/key or a converter; never edit a completed batch because its marker prevents reruns. BaseEfTask.load_config runs pending imports before any task's verify_config. The migrator backs up sources and copies account overrides without deleting source values itself; later framework loading can still remove obsolete keys. For another cross-task move, preserve the same pre-load ordering. Check older migration backups when a previous app version may already have removed source keys.

Show full SKILL.md (113 more words)Show less

Verify

Add a focused test for the actual change: old-only data, existing target value, missing data, rerun, conversion, and account overrides as applicable. Existing examples are tests.TestZipLineConfig and tests.TestDailySplitConfigMigration; they do not cover a new mapping automatically. Update docs that mention renamed keys, including internal keys; update gettext when visible names or options change ($ok-script-i18n).

For recovery, prefer surviving source values or daily_split_migration_backup/<batch>/. If neither exists, inspect the last Config:init log containing the old key rather than the latest initialization, which may already reflect its deletion; logs may contain private data. Restore the value through the migration, then verify the target value survives the next framework load and save before reporting recovery complete.

© AliceJump, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/ok-config-migration of AliceJump/ok-end-field.

Open the folder on GitHubat commit 31604a6

Compare with similar skills

Ok Config Migration next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Ok Config Migration compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Ok Config Migration this skillAliceJump/ok-end-field556—~750Automated safety check: PassAGPL-3.0
Issue Fields Migrationgithub/awesome-copilot40k1 repos~6.1kAutomated safety check: PassMIT
Reversible MigrationJuliusBrussee/caveman111k1 repos~196Automated safety check: PassApache-2.0
Database Migrationsaffaan-m/ECC276k4 repos~3kAutomated safety check: PassMIT
Database Migrationsaffaan-m/ECC276k1 repos~2.4kAutomated safety check: PassMIT
Safe Database Migration Patternsaffaan-m/ECC276k—~3.3kAutomated safety check: PassMIT

Similar skills

  • Issue Fields Migration

    github/awesome-copilot

    Official

    Bulk-migrate metadata to GitHub issue fields from two sources: repo labels (e.g.

    40k GitHub starsUsed in 1 repo~6.1k tokens
    Auto-check passed
  • Reversible Migration

    JuliusBrussee/caveman

    Implement reversible compatibility-safe transitions. Use for schema, data, API, protocol, configuration, or dependency migrations requiring rollback and…

    111k GitHub starsUsed in 1 repo~196 tokens
    DevelopmentAuto-check passed
  • Safe, reversible database migration patterns: forward-only production changes, expand-contract zero-downtime renames, concurrent indexes, batched backfills, and per-tool workflows for PostgreSQL…

    276k GitHub starsUsed in 4 repos~3k tokens
    DatabasesAuto-check passed
  • Şema değişiklikleri, veri migration'ları, rollback'ler ve PostgreSQL, MySQL ve yaygın ORM'ler (Prisma, Drizzle, Django, TypeORM, golang-migrate) arasında sıfır kesinti deployment'ları için…

    276k GitHub starsUsed in 1 repo~2.4k tokens
    DatabasesAuto-check passed
  • Rules and examples for safe, reversible schema changes in production: zero-downtime column and index changes, large data backfills and ORM migration workflows.

    276k GitHub stars~3.3k tokensUpdated 4 days ago
    DatabasesAuto-check passed
  • Migrate Create

    ruvnet/ruflo

    Create a new sequentially numbered database migration with up/down SQL files

    74k GitHub stars~583 tokensUpdated today
    DatabasesAuto-check: notes

More from AliceJump/ok-end-field

All 14 skills in this repo
  • Ok Script I18n

    AliceJump/ok-end-field

    Maintain gettext translations for ok-script task UI and runtime messages.

    556 GitHub stars~828 tokensUpdated today
    Auto-check passed
  • Deploy

    AliceJump/ok-end-field

    Commit validated changes, calculate an annotated stable/beta/alpha version tag, and push the release to the publishing remote.

    556 GitHub stars~625 tokensUpdated today
    Auto-check passed
  • GitHub Rulesets

    AliceJump/ok-end-field

    Diagnose or configure GitHub branch/tag rulesets on ok-script repos.

    556 GitHub stars~595 tokensUpdated today
    Auto-check passed
  • Use Local Venv

    AliceJump/ok-end-field

    Prefer the repository-local Python virtual environment for coding-agent work.

    556 GitHub stars~688 tokensUpdated today
    Auto-check passed
  • Ok Script PR Review

    AliceJump/ok-end-field

    Triage CodeRabbit reviews on ok-script pull requests. An agent skill from AliceJump/ok-end-field.

    556 GitHub stars~904 tokensUpdated today
    Auto-check passed
  • Ok Script Tasks

    AliceJump/ok-end-field

    Create, modify, register, or review ok-script BaseTask and TriggerTask classes.

    556 GitHub stars~619 tokensUpdated today
    Auto-check passed

Questions about Ok Config Migration

What does Ok Config Migration do?

Migrate persisted ok-end-field task settings when a key, value format, or owning task changes. Ok Config Migration is an agent skill from AliceJump/ok-end-field. Migrate persisted ok-end-field task settings when a key, value format, or owning task changes.

When should I use Ok Config Migration?

Ok Config Migration fits situations like: task JSON and account-specific overrides so existing user values survive.

How do I install Ok Config Migration in Claude Code?

Run `npx skills add AliceJump/ok-end-field --skill ok-config-migration -a claude-code`. Or copy the skill folder (.agents/skills/ok-config-migration in AliceJump/ok-end-field) into .claude/skills/ok-config-migration in your project. Claude Code loads it when a task matches its description.

How do I install Ok Config Migration in Codex?

Run `npx skills add AliceJump/ok-end-field --skill ok-config-migration -a codex`. Or copy the skill folder (.agents/skills/ok-config-migration in AliceJump/ok-end-field) into .agents/skills/ok-config-migration in your project. Codex loads it when a task matches its description.

Can I use Ok Config Migration in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add AliceJump/ok-end-field --skill ok-config-migration -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ok-config-migration, .gemini/skills/ok-config-migration, .github/skills/ok-config-migration and .opencode/skills/ok-config-migration in your project.

What does Ok Config Migration need to run?

SKILL.md names no scripts, command-line tools or credentials: Ok Config Migration is instructions for the agent only.

Does Ok Config Migration access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Ok Config Migration safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Ok Config Migration use?

Ok Config Migration is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Ok Config Migration use?

About 750 tokens (SKILL.md is roughly 3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Ok Config Migration?

Skills that share tags, products or a category with Ok Config Migration: Issue Fields Migration (github/awesome-copilot, 40k stars), Reversible Migration (JuliusBrussee/caveman, 111k stars), Database Migrations (affaan-m/ECC, 276k stars) and Database Migrations (affaan-m/ECC, 276k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Ok Config Migration?

AliceJump (a GitHub user) maintains it in AliceJump/ok-end-field, which has 556 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on October 9, 2026.

Source: AliceJump/ok-end-field on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.