Fskill Creator

Organization

AGI-comming

fskill-creator

Create, maintain, or migrate functional skills; supports creating from a requirement brief and migrating an existing legacy skill directory into a functional skill structure.

Overview

Publisher	AGI-comming
Repository	`functional-skill-creator`
Skill name	`fskill-creator`
Stars	257
Forks	16
Bundled files	27
License	MIT
Links	Skill source Repository

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.
27 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 AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

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.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/AGI-comming/functional-skill-creator/tree/main/skills/fskill-creator
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.

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 .claude/skills/fskill-creator

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

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

Goal

Unify the create and migrate lanes to produce a self-contained, reviewable, testable functional agent skill directory. The main skill handles routing, blueprint normalization, shared artifact generation, runtime capability provisioning, file writing, and validation; sub-skills only handle pre-analysis for their respective input forms.

Use this skill when the user wants to "generate a functional skill", "create a functional skill", "add functions to an existing functional skill", or "migrate an existing legacy skill directory into a functional skill".

Principles

The main SKILL.md only orchestrates the shared create / migrate / enhance / validate workflow.
Create and migrate are two pre-lanes; they must first converge into a unified skill_blueprint.
Function-specific behavior lives in functions/*.md; create / migrate specific pre-behavior lives in sub-skills/*/functions/*.md.
Shared vocabulary, policies, and schemas live in references/*.md.
Deterministic parsing, formatting, validation, and mechanical transforms live in scripts/.
Report, unit test, viewer, and testcase capabilities are maintained only once in the main skill, and vendored into the target skill by add_runtime_capabilities.
Preserve user-provided domain constraints; the migrate lane must also preserve legacy behavior evidence.
When the user has not approved direct modification, generated files should be treated as proposals.

Sub-Skills

Sub-skill	When	Responsibility	Output
`sub-skills/create`	User provides a new skill brief or wants to enhance an existing functional skill	Normalize requirements, target path, inputs/outputs, constraints, and viewer choices	`create_context`
`sub-skills/migrate`	User provides a legacy skill directory, monolithic skill content, or a migration request	Load the legacy skill package, identify behaviors that must be preserved, propose function boundaries and evidence	`migration_context`

Sub-skills do not directly write final target skill files. Their output must go through normalize_skill_blueprint before entering the shared artifact pipeline.

References

Resource	Load Timing	Purpose
`shared_glossary`	On demand	Stable terminology and cross-lane field semantics.
`script_rules`	Before designing or drafting scripts	Rules for deciding whether deterministic work belongs in `scripts/`.
`sub-skills/create`	Create lane	Form `create_context` from user brief.
`sub-skills/migrate`	Migrate lane	Form `migration_context` from a legacy skill directory.

External Inputs

Field	Source	Description
`task_mode`	user or derived	`create`, `migrate`, `enhance`, or `validate`; inferred by `resolve_task_mode` when absent.
`skill_request`	user	Requirement description for creating or enhancing a skill.
`legacy_skill_dir`	user or repository	Path to an existing legacy skill directory containing `SKILL.md` and optional companion files.
`legacy_skill_path`	user or repository	Deprecated alias for `legacy_skill_dir`; may also be a direct path to `SKILL.md`, which resolves to its parent directory.
`legacy_skill_content`	user	Legacy skill markdown provided when the path is inaccessible.
`target_skill_path`	user or derived	Directory where the functional skill should live.
`skill_name`	user or derived	Optional target skill name.
`existing_skill_files`	repository	Optional existing functional skill files.
`migration_constraints`	user	File names, tone, platform rules, or behaviors that must be preserved during migration.
`known_testcases`	user or repository	Existing examples, traces, or expected behaviors.
`existing_scripts`	repository	Helper scripts associated with the legacy skill.
`include_report`	user	Whether to generate report log runtime in the target skill; defaults to `true`.
`include_unittest`	user	Whether to generate unittest / testcase runner in the target skill; defaults to `true`.
`script_runtime`	environment	Whether this skill's own Node.js scripts can be run.
`report_mode`	user	`off`, `local`, or `remote`; defaults to `off`.

Viewers are generated following the capability flags: tools/log_viewer.mjs when include_report=true; tools/tester_viewer.mjs when include_unittest=true.

Execution Pipeline

Step	Function	Purpose	Input	Output
1	`resolve_task_mode`	Determine whether this request should go through create, migrate, enhance, or validate.	`task_modeskill_requestlegacy_skill_dirlegacy_skill_pathlegacy_skill_contentexisting_skill_files`	`task_context`
2A	`sub-skills/create::collect_create_brief`	Create/enhance lane: normalize user brief.	`skill_requesttarget_skill_pathskill_name`	`create_context`
2B	`sub-skills/migrate::load_legacy_skill` + `map_existing_behavior` + `propose_function_split` + `extract_shared_references`	Migrate lane: read the legacy skill package, extract behaviors and migration evidence.	`legacy_skill_dirlegacy_skill_pathlegacy_skill_contentmigration_constraintsinclude_reportinclude_unittestscript_runtime`	`migration_context`
3	`normalize_skill_blueprint`	Converge create / migrate / enhance inputs into a unified blueprint.	`task_contextcreate_contextmigration_contexttarget_skill_pathinclude_reportinclude_unittest`	`skill_blueprint`
4	`design_skill_structure`	Design function pipeline, references, scripts, testcases, and file layout based on blueprint.	`skill_blueprintexisting_skill_filesscript_rules`	`skill_structurescript_plantool_plan`
5	`draft_skill_artifacts`	Draft `SKILL.md`, function contracts, references, script specs, and testcase suggestions.	`skill_blueprintskill_structurescript_plan`	`skill_artifacts`
6	`add_runtime_capabilities`	Provision report log, runtime wrapper, unit testcase runner, viewer, and smoke tests according to include flags.	`skill_blueprint.include_reportskill_blueprint.include_unittestskill_artifacts`	`runtime_artifactsskill_artifacts`
7	`assemble_skill_files`	Generate or update target skill directory files.	`target_skill_pathskill_structureskill_artifactsruntime_artifactsscript_runtime`	`file_plancreated_filesupdated_files`
8	`validate_skill`	Validate functional-skill structure, runtime capabilities, testcases, and migration behavior preservation.	`target_skill_pathfile_planskill_blueprintreport_mode`	`validation_result`

Output Scope

This skill may read legacy skills and create or modify functional skill files under target_skill_path. Do not delete the original legacy skill unless the user explicitly requests deletion; do not modify unrelated repository files unless the user explicitly requests project-level integration.

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

Create, maintain, or migrate functional skills; supports creating from a requirement brief and migrating an existing legacy skill directory into a functional skill structure.

Why use Fskill Creator on TypingMind?

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

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?

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

Is the Fskill Creator 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

Clawdtributor

openclaw

OrganizationPopular

Clawtributor PRs here, last week or another window: discover conversation refs, recheck GitHub, rank by impact.

Control Ui E2e

Use when designing, testing, fixing, or extending the OpenClaw Control UI GUI, including UI stress-test galleries with feedback inputs, Vitest + Playwright end-to-end checks, mocked Gateway flows,…

Discord E2e

Test Discord with Convex-leased QA bots: check credentials without a Gateway, exercise owned messages, or prove OpenClaw replies, files, threads, reactions, streaming, and typing. Distinguish API and…

Openclaw Qa Testing

Run, watch, debug, extend, or explain OpenClaw qa-lab and qa-channel scenarios, artifacts, and live lanes.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

fskill-creator

Goal

Principles

Sub-Skills

References

External Inputs

Execution Pipeline

Output Scope

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now