Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Experience summaries for OpenClaw tasks, including common installation problems, troubleshooting steps, and best practices for packages, configurations, and...
Experience summaries for OpenClaw tasks, including common installation problems, troubleshooting steps, and best practices for packages, configurations, and...
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 provides curated experience summaries from real OpenClaw tasks, including: Installation/packaging problems and solutions Common error messages and root causes Package search and discovery methods Configuration patterns and environment setups Tool-specific troubleshooting steps Best practices for documenting new experiences Each entry includes: Problem โ Solutions โ Key Lessons โ Prevention Steps.
Purpose: Search, install, update, and publish OpenClaw skills from clawhub.com. Installation: npm install -g clawhub Usage: # Search for skills clawhub search "keyword" # Install a skill clawhub install "skill-name" # List installed skills clawhub list # Publish a new skill (when ready) clawhub publish "skill-directory" Authentication: Token: clh_<token> Username: @<username> Available at: https://clawhub.ai
Purpose: AI-optimized web search via Tavily API. Configuration: # Set environment variable set TAVILY_API_KEY=your-api-key-here Usage: Search query: web_search tool API key location: <skill-dir>/README_CONFIG.md Quality: High relevance for AI agents
Problem: npm 404 Not Found Scenario: Install command fails with "404 Not Found" Solutions: Check package name spelling Search ClawHub: clawhub search "keyword" Try npm search: npm search "keyword" Verify the package exists in npm registry Typical Fixes: Wrong package name (e.g., tavily-search โ correct: tavily-mcp) Package removed or renamed Typo in command Key Lesson: Always verify package existence before installation. Use search tools. Problem: Windows Permission EEXIST Error Scenario: Installation fails with "EEXIST: file already exists" Solution: npm i -g clawhub --force Root Cause: Old version files remain, blocking installation Prevention: Use --force for global installations on Windows if issues occur Problem: Unknown Package Name Scenario Package not found in npm registry Solutions: Use ClawHub search: clawhub search "keyword" Try broader search terms Check if the skill is hosted on ClawHub (OpenClaw's official registry) Example: Initial attempt: npm install "find-skills" โ 404 Solution: clawhub search "find-skills" โ Found "find-skills v0.1.0" Result: clawhub install "find-skills" โ Success Key Lesson: ClawHub is the first place to check for OpenClaw skills
Environment Variables Standard Pattern: # SET in current session set ENV_VAR=value # For persistent settings, add to shell config # (e.g., .bashrc, .zshrc, PowerShell profile) Common Variables: TAVILY_API_KEY - For web search tools OPENAI_API_KEY - If needed for OpenAI-based skills Custom credentials for specific tools Verification: echo $TAVILY_API_KEY # Unix-like echo %TAVILY_API_KEY% # PowerShell/CMD
OpenClaw Browser Extension Symptom: "tab not found" errors after browser operations Solutions: Restart OpenClaw Gateway (OpenClaw.app โ Restart) Keep Chrome extension badge ON (not OFF) Do not close browser tab between operations Reseat connection: Open Extension โ Attach Tab โ Badge ON Best Practice: Browser tool is for one-time operations or screenshots Not suitable for long-lived automated sessions Direct browser interaction is more reliable for persistent needs Browser Profile Issues Symptom: Multiple profiles causing conflicts Solutions: Use --profile=chrome for managed Chrome browser Use --profile=openclaw for isolated browser Test with clean profile if issues persist Status Check: openclaw gateway status
Determine if the issue belongs to: Installation problems Configuration issues Tool-specific malfunctions Package discovery Platform-specific behavior (Windows/Linux/macOS)
Use the tables and categorized entries above: Match symptoms to category Review associated solutions Try recommended fixes
Apply suggested fixes in order: Most common/simplest solution first Platform-specific fixes second Advanced configurations third
When to Document: Successfully resolved an unknown problem Discovered a pattern or workaround Learned a configuration trick Found that a documented solution works differently How to Document: Record the problem clearly Note the solution steps Include platform-specific details Add prevention/prevention steps Update relevant section in this SKILL.md Template for New Entry: ### Problem: [Clear description] **Scenario:** [Context where problem occurs] **Solution:** [Step-by-step resolution] **Root Cause:** [Why this happens] **Prevention:** [How to avoid] **Platform Notes:** [If platform-specific]
Review after using the skill: Are entries clear and actionable? Are symptoms and solutions well-matched? Is formatting consistent? Any missing common issues?
Issue TypeSymptomsPrimary ToolKey CommandPackage not found404, npm errorsnpm, ClawHubclawhub search "keyword"Permission errorsEEXIST, access deniednpm install--force flagConfiguration missingTool failsEnvironment variablesset VAR=valueBrowser connectionTab not foundBrowser toolsRestart Gateway + Badge ONUnknown packageCannot installclawhub listclawhub install "name"
Search Before Guessing: Always use search tools first Document Solutions: Write down everything you learn Categorize Issues: Group by type for easy lookup Platform Notes: Track Windows/macOS/Linux differences Prevention Over Cure: Add prevention steps to avoid recurrence Keep It Practical: Focus on actionable steps, not theory
# User asks: "I need a weather skill for checking forecasts" # Step 1: Search clawhub search "weather" # Step 2: Identify candidate Found: "weather v1.0" - Get current weather and forecasts (no API key required) # Step 3: Install clawhub install "weather" # Step 4: Configure (if needed) # Check README_CONFIG.md for required environment variables # Step 5: Use # Use web_search tool with query: "weather today"
# Symptom: Browser tool reports "tab not found" # Step 1: Restart Gateway (first fix) OpenClaw.app โ Restart # Step 2: Check extension โ Badge indicator should be ON โ Running state โ CDP Ready (Chrome DevTools Protocol) # Step 3: Reattach if needed Click OpenClaw extension icon โ Attach tab โ Badge ON # Step 4: Verify Try browser open โ snapshot
# Symptom: "I need an RSS feed parser" - package unknown # Step 1: ClawHub search clawhub search "rss" # Step 2: Identify Found: "rss-parser skill v0.5.0" with description "Parse RSS feeds" # Step 3: Install clawhub install "rss-parser" # Result: Success
All entries are based on actual resolved issues Platform-specific behaviors are noted when applicable Configuration details refer to current workspace setup For newer issues, always consult official documentation before relying on summaries
Writing, remixing, publishing, visual generation, and marketing content production.
Largest current source with strong distribution and engagement signals.