Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Premium Skill Creator by Kevin Jeppesen (The Operator Vault). Create better OpenClaw skills with a premium first-use setup wizard pattern, minimal context bl...
Premium Skill Creator by Kevin Jeppesen (The Operator Vault). Create better OpenClaw skills with a premium first-use setup wizard pattern, minimal context bl...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
This skill helps you create new OpenClaw skills that feel premium. Premium means: On first use, the skill runs a short conversational setup wizard (only asks what must be personalized). It persists config to disk (so prompts do not grow forever). It keeps SKILL.md short and uses progressive disclosure (move long docs into references/ and only load them when needed).
"create a new skill" "scaffold a skill" "make a premium skill with a setup wizard" "package this workflow as a skill"
For a new skill <slug> it creates: <skillsDir>/<slug>/SKILL.md <skillsDir>/<slug>/references/ <skillsDir>/<slug>/scripts/ (optional helper scripts) A config path convention (choose one): Workspace: <workspace>/.skill-config/<slug>.json Global: ~/.openclaw/config/skills/<slug>.json (only when truly global)
On first use, if config missing: Ask permission and give time estimate ("60 seconds"). Ask only 3 to 8 questions max. Use defaults, keep advanced options behind a single extra question. Summarize choices, ask for confirmation. Write config to the workspace (recommended): <workspace>/.skill-config/<slug>.json. Run a tiny test. Tell user how to reconfigure. If user says "skip", continue with safest defaults and warn about reduced capability.
Default: workspace config file. Optional global config only when the integration is truly global. Never store secrets in long term memory files.
If the user has a local search tool (for example QMD), keep bulk docs outside SKILL.md and store them in a user chosen folder that their search tool indexes. Do not assume any particular directory layout.
Ask in chat: "Create a premium skill called <slug> that does <outcome>." Or run the scaffolder: node {baseDir}/scripts/scaffold-skill.mjs <slug> "<one sentence description>"
Ask: "Upgrade skill <slug> to premium standard."
If the user asks to publish: Confirm slug, name, version, and changelog. Ensure clawhub whoami is authenticated. Run clawhub publish <path> --slug <slug> --name "<Name>" --version <x.y.z> --changelog "...". Safety: Review files for accidental personal paths, tokens, or private info before publishing.
See references/LINKS.md for Kevin Jeppesen links and Operator Vault info.
Agent frameworks, memory systems, reasoning layers, and model-native orchestration.
Largest current source with strong distribution and engagement signals.