Fskill Creator Migrate logo

Fskill Creator Migrate

Organization
AGI-comming
fskill-creator-migrate

Migrate lane for fskill-creator; analyzes a legacy skill directory into behavior map, function split proposal, and source evidence.

Overview

PublisherAGI-comming
Repositoryfunctional-skill-creator
Skill namefskill-creator-migrate
Stars
257
Forks
16
Bundled files
11
LicenseMIT
Links
  • 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.

  • 11 bundled files

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

  • Open source

    Published by AGI-comming on GitHub. Read the source before you install it.

Installation

Install the Fskill Creator Migrate 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/AGI-comming/functional-skill-creator/tree/main/skills/fskill-creator/sub-skills/migrate
  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/AGI-comming/functional-skill-creator.git /tmp/functional-skill-creator
mkdir -p .claude/skills
cp -r /tmp/functional-skill-creator/skills/fskill-creator/sub-skills/migrate .claude/skills/fskill-creator-migrate
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Fskill Creator Migrate 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 Fskill Creator Migrate 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 Fskill Creator Migrate 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.

fskill-creator-migrate

Goal

Analyze a large or hard-to-maintain legacy skill directory into structured migration context while preserving behavior. This sub-skill only performs migration pre-analysis and does not directly write final functional skill files; final artifact generation, runtime capability provisioning, file writing, and validation are handled by the main fskill-creator.

Invoked by the main skill when the user has an existing monolithic skill and wants to "refactor into functional", "migrate to functional skill", or "restructure into functions/references/scripts".

Principles

  • Preserve existing behavior first, then optimize structure.
  • Load the whole legacy skill package, not only SKILL.md.
  • Keep source section and file evidence so reviewers can trace migrated content.
  • Only output migration_context; must not directly write target skill files.
  • Duplicated rules, schemas, and vocabulary move to reference_plan.
  • Existing references/, scripts/, and tools/ are inventoried before proposing splits.
  • Deterministic parsing, formatting, validation, or mechanical transforms are identified as script_plan, to be generated or preserved later by the main skill.
  • Optional viewers only enter tool_plan; final files are generated uniformly by the main skill's add_runtime_capabilities.

References

ResourceLoad TimingPurpose
shared_glossaryOn demandStable migration terminology and output fields.
script_rulesBefore proposing scriptsRules for deciding what belongs in scripts/.

External Inputs

FieldSourceDescription
legacy_skill_diruser or repositoryPath to the legacy skill directory containing SKILL.md.
legacy_skill_pathuser or repositoryDeprecated alias for legacy_skill_dir; may also be a direct path to SKILL.md, which resolves to its parent directory.
legacy_skill_contentuser or repositoryExisting skill markdown content when the directory is inaccessible.
migration_constraintsuserConstraints such as preserving file names, tone, or platform rules.
known_testcasesuser or repositoryExisting examples, traces, or expected behaviors.
existing_scriptsrepositoryExisting helper scripts associated with the legacy skill.
include_viewersuserWhether to suggest generating tools/log_viewer.mjs and tools/tester_viewer.mjs.
script_runtimeenvironmentWhether this sub-skill's own Node.js scripts can be run.

Execution Pipeline

StepFunctionPurposeInputOutput
1load_legacy_skillLoad and normalize the legacy skill package.legacy_skill_dirlegacy_skill_pathlegacy_skill_contentlegacy_skill
2map_existing_behaviorIdentify goals, rules, inputs, outputs, and behaviors that must be preserved.legacy_skillmigration_constraintsbehavior_map
3propose_function_splitPropose function boundaries, script opportunities, optional viewer tools, and target file layout.legacy_skillbehavior_mapscript_rulesinclude_viewersscript_runtimemigration_proposalscript_plantool_plan
4extract_shared_referencesMove duplicated or shared rules into references.legacy_skillmigration_proposalscript_planreference_plan

Output

The main skill combines the above outputs into:

FieldDescription
migration_context.legacy_skillLoaded source skill package data.
migration_context.behavior_mapBehaviors that must be preserved.
migration_context.migration_proposalFunction split and target structure proposal.
migration_context.reference_planTerms, rules, and schemas that should go into shared references.
migration_context.script_planDeterministic helpers to generate, preserve, or refactor.
migration_context.tool_planOptional viewer choices.
migration_context.source_evidenceLegacy source sections, companion files, and behavior preservation evidence.

Output Scope

Only output migration context; must not directly write target skill files or delete the legacy skill.

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 Fskill Creator Migrate AI skill do?

Migrate lane for fskill-creator; analyzes a legacy skill directory into behavior map, function split proposal, and source evidence.

Why use Fskill Creator Migrate on TypingMind?

Because you install it once and use it with any model. Fskill Creator Migrate 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 Fskill Creator Migrate in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/AGI-comming/functional-skill-creator/tree/main/skills/fskill-creator/sub-skills/migrate. 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 Fskill Creator Migrate?

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 Fskill Creator Migrate?

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

Is the Fskill Creator Migrate AI skill free?

Yes. It is published on GitHub by AGI-comming 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.

View all

Set up your own AI workspace now

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