Thanks for helping improve Functional Skill Creator.
git clone https://github.com/AGI-comming/functional-skill-creator.git
cd functional-skill-creator
npm install
npm run checkThen let your agent use the built-in skill:
Use skills/fskill-creator to create a functional skill for <workflow>
Use skills/fskill-creator to migrate <path-to-existing-skill-dir>
# Create a basic functional skill skeleton
node skills/fskill-creator/scripts/init_skill.mjs skills/<name>
# Validate functional skill structure integrity
node skills/fskill-creator/scripts/lint_skill.mjs skills/<name>
# Run JSON testcase assertions
node skills/fskill-creator/scripts/test_cases.mjs examples/meeting-notes-to-actions
# Generate migration proposal
node skills/fskill-creator/sub-skills/migrate/scripts/migrate_proposal.mjs path/to/skill-dirnpm run test:skill-scripts
npm run test:example-scripts
npm run test:cases
npm run lint:examples
npm run lint:skills
npm run checkThis project has zero third-party runtime dependencies. Everything uses Node.js built-in modules and node --test.
- Each change should focus on one behavior or one type of documentation improvement.
- Code changes must add or update tests.
- Run
npm run checkbefore submitting a PR. - When user-visible behavior changes, update
README.mdordocs/accordingly. - Do not commit generated traces, local logs, credentials, or customer data.
- Toolkit stays runtime-agnostic.
- Prefer explicit data contracts over hidden conventions.
- Trace and testcase behavior must be auditable.
- Do not introduce model vendor dependencies.
- High-level judgment and orchestration live in
skills/; deterministic actions are pushed down to the corresponding skill'sscripts/.
User-visible changes should be recorded under Unreleased in CHANGELOG.md.