Decide Fit First

• Core job: $HOME/.akashic/workspace/skills/{skill-name}/ ← 用户自定义技能（优先） SKILL.md ← 必须 scripts/ ← 可选，放辅助脚本 references/ ← 可选，放参考文档 项目/skills/{…
• Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
• Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

• Structure: The skill is organized around “技能目录结构”, “SKILL.md 格式”, “frontmatter 字段说明”, “写作原则”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
• Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
• Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

• Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
• Invocation: Name skill-creater directly; if the source includes slash commands, start with the command and then add task context.
• Validation: Start small and check whether the result follows “技能目录结构 / SKILL.md 格式 / frontmatter 字段说明” before expanding.

Boundaries And Review

• Dependencies: Prepare Vendor-specific API keys before running a full task.
• Permissions: Declared permissions include read / env-read; ask the agent to state file, command, and rollback boundaries before acting.
• Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.