skillpack creator

AI Community

Skill notes

Overview

Turn a successful task into a reusable SkillPack. Extract the stable workflow, decide what belongs in a local skill versus pack-level prompts, generate the pack structure, and package it only after the workflow is explicit and repeatable.

1. Normalize the source task

Reduce the finished task into a clean execution spec: Capture the user goal, concrete deliverable, and the final successful workflow (not the full exploratory transcript). List required skills, tools, files, secrets, and environment assumptions. Separate deterministic steps from heuristic steps; remove dead ends and debugging noise. If the task is still too broad, narrow the scope instead of writing a vague mega-skill. If key success conditions depend on hidden human judgment, mark the pack as a best-effort assistant workflow.

2. Decide what the pack should contain

Local skill (skills/): reusable procedural knowledge. Keep scripts minimal unless reproducibility depends on exact file generation or repetitive shell steps. Scripts (scripts/): repeated shell or file-generation logic where reliability matters. References (references/): detailed schemas, API notes, or conventions that should not bloat SKILL.md. Prompts (skillpack.json): 1–3 pack-level starter inputs for the UI — not a DAG or state machine. See references/skillpack-format.md for exact pack semantics.

3. Create the pack specification

Before writing files, define the pack spec. Prefer one local orchestrator skill plus a small number of external skills. Example minimal manifest:

4. Create the local orchestrator skill

Create skills/<skill-name>/SKILL.md with frontmatter and imperative workflow instructions: Write the stable workflow as imperative steps in the body. Add scripts/ only for fragile or repeated operations; add references/ only for detailed information.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
AI
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@CreminiAI · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
macOS · Linux · Windows
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Output preview skillpack-creator.preview
# 6. Validate the result

- The manifest matches the intended pack scope
- Every declared skill has a valid `name`, `source`, and `description`
- Local skills are present under the target pack's `skills/`
- Starter prompts are concrete enough to reproduce the workflow
- Zip only after the pack runs as a directory

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.