Skip to content
Limin Zheng

AI Skills & Workflows

Skill installation, migration & repair

Diagnose or adapt an existing Skill for a defined environment.

Choose this when
Choose this for diagnosing installation, migration or compatibility of existing Skills.
Scope unit
One existing Skill and target environment
Possible delivery format
Diagnosis report first; package or client-repo PR after approved repair/migration
Prepare a brief →

You send · You receive

What to send

  • Existing Skill files/repository and usage rights
  • Target host, symptom, errors and versions
  • Expected outcome, change permission and reproduction steps

Start by describing the materials you already have; missing details can be added when we agree the scope. Before work begins, we will confirm the materials, permissions and working conditions needed for your specific task.

Two stages

Stage 1 · Diagnosis

First receive an installation/compatibility assessment of the existing Skill: reproduction results, dependency differences, confirmed findings, hypotheses, blockers and migration or repair feasibility.

Possible outputs

  • Installation/compatibility report, version/dependency differences and migration or repair options

A diagnosis can be the complete order.

You decide whether to continue

Stage 2 · Approved implementation

Repair or migration is separately scoped and quoted after source rights, host/version, permissions and a reproducible environment are confirmed. An adapted package or PR and retests are delivered only for approved implementation.

Possible outputs

  • Adapted package or client-repo PR, configuration/use guide
  • Retests of original cases and known limits

Scoped and quoted separately.

Third-party costsAI host subscriptions, API/model runs, paid tools and asset licenses are not included in the delivery fee. Any additional diagnostic run costs must be agreed in advance.

Key checkSeparate reproduced issues, hypotheses and environment access blockers.

Verifiable acceptance · 3
  • Stage 1 · DiagnosisThe client receives a readable report separating reproduction, hypotheses and access blockers, with migration/repair conditions
  • Stage 2 · Approved implementationRetest original cases and distinguish passed, failed and untested cases
  • Both stagesClosed-source materials are not redistributed without permission

Hypothetical brief & output structure

Illustration · hypothetical

Illustrative example — not a completed client order

The request

An existing Claude Skill fails in Codex; find out whether it can be migrated.

Sample artifacts

  • diagnosis.mdcompatibility and repair options
  • port.patch / adapted-skill.zipif later commissioned

File names are illustrative

Other tasks of this kind

  • Diagnose why an existing Skill stopped handling files after a host upgrade.
Output structure / test path

Compatibility table: dependency | old behavior | target support | effort | test method

Write a brief from this example →

Scope boundaries

Diagnosis is distinct from implementation; verify source rights and target host permissions first.

Not included by default

  • Licensing rights the customer does not possess
  • Guaranteed repair of unreproducible failures
  • Untested all-platform compatibility

What affects the quote

Diagnose first; quote porting or repair separately based on evidence.

Actual project references

  • Reflection Companion ↗

    Published Agent Skill (Alpha)

    Host support follows the public project documentation; Alpha does not mean production-ready on all platforms.

  • Roleward Job Hunting ↗

    Published Agent Skill (Alpha)

    The Codex local workspace is the fully accepted host as of the catalog review; other hosts are not guaranteed.

  • Score Simplifier ↗

    Published Agent Skill (Alpha)

    Published examples verify score-sourced simplification, engraving and PDF/MusicXML/MIDI checks; they do not prove accurate transcription of arbitrary audio recordings.

Self-directed work and published projects demonstrate relevant practice. They are not paid-client delivery records or guarantees for this task.

Start with a short note

Three answers are enough. I will reply with what else is needed and whether a diagnosis comes first. You get a quote before any work starts.

Prepare a brief →

Skill installation, migration & repair

Start with a short note

Three answers are enough. I will reply with what else is needed and whether a diagnosis comes first. You get a quote before any work starts.

What to send
  • Existing Skill files/repository and usage rights
  • Target host, symptom, errors and versions
  • Expected outcome, change permission and reproduction steps
Illustration · hypothetical

Illustrative example — not a completed client order

The request

An existing Claude Skill fails in Codex; find out whether it can be migrated.

Example inputs

  • Authorized source ZIP/repository
  • Failure logs, target host/version and expected behavior

To start, it helps to mention

  • What failed in the existing Skill, and where did it work before?
  • Is the goal diagnosis, version repair or migration?

Confirm before work begins: Authorized Skill source, error/version evidence and target host test access

Public/de-identified information only. Private access requires separate authorization.

Open email draft →

Preview the text
Services brief — A02 Skill installation, migration & repair

First contact does not require a complete specification. Unknown fields may be blank or marked unknown.

What do you want to end up with?


What do you already have?


When do you need it? Any budget range?

Select and copy the brief manually if scripting or clipboard access is unavailable.

Public email is a contact starting point. This site has no booking, payment or file-upload service. zhenglimin.design@gmail.com

← Back to category
Prepare a brief →