Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Convert memory, conversation history, or completed tasks into publishable OpenClaw skills. Use when (1) A task or workflow should be reusable, (2) Extracting...
Convert memory, conversation history, or completed tasks into publishable OpenClaw skills. Use when (1) A task or workflow should be reusable, (2) Extracting...
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.
Transform your work into reusable skills. Extract workflows, solutions, and patterns from conversation history or memory files, package them as skills, and publish to GitHub and ClawHub.
This skill automates the complete workflow: Extract - Parse conversation history or memory for reusable patterns Design - Structure as a proper skill with SKILL.md and resources Create - Generate skill files and scripts Publish - Push to GitHub and publish to ClawHub
# Analyze last conversation and create skill draft ./scripts/extract-from-history.sh /path/to/session.jsonl ./my-new-skill # Or specify a time range ./scripts/extract-from-history.sh /path/to/session.jsonl ./my-new-skill --since "2026-02-03" --pattern "backup"
# Extract from memory markdown ./scripts/extract-from-memory.sh /path/to/memory/2026-02-04.md ./my-new-skill
# One command: extract, create, and publish ./scripts/create-and-publish.sh \ --source /path/to/session.jsonl \ --skill-name "my-automation" \ --github-repo "user/my-skills" \ --clawhub-slug "my-automation"
Identify from conversation/memory: Task Pattern: What workflow was solved? Inputs/Outputs: What goes in, what comes out? Scripts/Tools: What code was written? Key Decisions: What choices were made?
Decide resource types: scripts/ - For reusable code references/ - For documentation assets/ - For templates/files
Generate: SKILL.md with frontmatter and instructions Scripts in scripts/ Any reference files
Push to GitHub and publish to ClawHub: ./scripts/publish.sh ./my-skill \ --github "user/repo" \ --clawhub-slug "my-skill" \ --version "1.0.0"
Parse conversation JSONL for skill content. ./scripts/extract-from-history.sh <session.jsonl> <output-dir> [options] Options: --since DATE Only extract from DATE onwards --pattern REGEX Filter messages matching pattern --tools-only Only extract tool usage patterns
Parse memory markdown files. ./scripts/extract-from-memory.sh <memory.md> <output-dir>
Generate skill structure from extracted content. ./scripts/create-skill.sh <extracted-content-dir> <skill-name> Options: --description "..." Skill description --type workflow Skill type (workflow|tool|reference)
Complete publish workflow. ./scripts/publish.sh <skill-path> [options] Options: --github REPO GitHub repo (owner/repo) --clawhub-slug ClawHub slug --version VER Version tag --skip-github Skip GitHub push --skip-clawhub Skip ClawHub publish
User: "帮我设置每天自动备份OpenClaw配置" → Agent creates backup scripts + cron setup
Extract: ./scripts/extract-from-history.sh \ ~/.openclaw/agents/main/sessions/latest.jsonl \ ./extracted-backup Design: Type: Workflow skill Scripts: backup.sh, setup-cron.sh, cleanup.sh No assets needed Create: ./scripts/create-skill.sh ./extracted-backup cron-backup \ --description "Automated backup scheduling with cron" \ --type workflow Publish: ./scripts/publish.sh ./cron-backup \ --github "zfanmy/openclaw-skills" \ --clawhub-slug "cron-backup" \ --version "1.0.0"
✅ Do: Single, well-defined purpose Reusable across contexts Includes working scripts Clear usage examples Progressive disclosure design ❌ Don't: Too broad or vague Hardcoded personal paths Missing error handling Undocumented assumptions
Look for these patterns: "帮我写一个脚本..." "设置定时任务..." "以后每次都要..." "这个流程可以复用..."
Required setup: # Configure git git config --global user.name "Your Name" git config --global user.email "your@email.com" # Setup SSH key for GitHub ssh-keygen -t ed25519 -C "your@email.com" # Add ~/.ssh/id_ed25519.pub to GitHub Settings → SSH Keys # Login to ClawHub clawhub login
Follow semantic versioning: 1.0.0 - Initial release 1.0.1 - Bug fix 1.1.0 - New feature 2.0.0 - Breaking change
Check session file path Verify date range with --since Try broader pattern matching
Verify SSH key is added to GitHub Check repo exists and you have access Ensure git config user.name/email set
Run clawhub login first Check skill validation passes Verify slug is unique
Test scripts manually first Check for hardcoded paths Verify all dependencies listed Run with --examples flag when creating
skill-creator - Low-level skill creation utilities cron-backup - Example output skill (backup automation) clawhub - ClawHub CLI operations
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.