AGI-comming/functional-skill-creator / skills/fskill-creator/sub-skills/migrate
fskill-creator-migrate
VerifiedMigrate lane for fskill-creator; analyzes a legacy skill directory into behavior map, function split proposal, and source evidence.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 4.3 KB |
| functions/extract_shared_references.md | markdown | 1.5 KB |
| functions/load_legacy_skill.md | markdown | 2.2 KB |
| functions/map_existing_behavior.md | markdown | 1.6 KB |
| functions/propose_function_split.md | markdown | 2.8 KB |
| logs/runs/.gitkeep | other | 1 B |
| references/script-rules.md | markdown | 1.3 KB |
| references/shared-glossary.md | markdown | 1.6 KB |
| scripts/.gitkeep | other | 1 B |
| scripts/lint_skill.mjs | script | 2.1 KB |
| scripts/migrate_proposal.mjs | script | 8.6 KB |
| scripts/migrate_proposal.test.mjs | script | 4.0 KB |
| scripts/test_cases.mjs | script | 4.5 KB |
| testcases/unit/propose_function_split.basic.case.json | config | 2.0 KB |
references/script-rules.md
View on GitHub# Script Rules
Use `scripts/` to preserve deterministic legacy behavior as code rather than fragile prompt instructions.
## When to Migrate to Scripts
- Legacy skill describes mechanical parsing, formatting, or validation;
- A step must produce consistent results across every run;
- The behavior has clear input and output objects;
- Existing examples can become script tests;
- Logic is shared across multiple migrated functions.
## When to Keep in Function Contracts
- The step requires model judgment;
- Source behavior is ambiguous and needs human review;
- Deciding function boundaries or domain tradeoffs;
- Output is user-facing prose.
## Migration Requirements
Each migrated script must preserve or record:
- Source section or legacy script path;
- Input object or file scope;
- Output object or file changes;
- Failure behavior;
- Script tests or reason tests are deferred.
## Viewer Tools
`tools/` is for optional local viewers in the migrated skill and does not carry legacy behavior that must be preserved.
- `tools/log_viewer.mjs` reads `logs/runs/*.jsonl` and summarizes function traces.
- `tools/tester_viewer.mjs` reads `testcases/**/*.case.json` and summarizes regression coverage.
- If the user has not explicitly passed `include_viewers`, explain the purpose and ask before generating; do not generate by default.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 468k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |