extension-troubleshoot
openbooklet.com/s/extension-troubleshootopenbooklet.com/s/extension-troubleshoot@1.0.0GET /api/v1/skills/extension-troubleshootDiagnose and fix piclaw extension issues (imports, DB init errors, watcher perms), update skel, and restart safely.
Author Adaptive Cards for the current PiClaw web environment. Use when you need a prompt pattern, supported payload shape, or reusable card templates for structured web interactions.
Bootstrap a new container by validating required tools and installing missing dependencies.
A one-shot maintenance skill to:
Export a chat timeline to a PDF using the web UI renderer and Playwright.
Design and audit Pi extensions safely (avoid workspace source imports).
Run a structured 20-question refinement flow before implementation for feature requests.
Build a deduped markdown digest from feeds.carmo.io (last N hours) and store links separately.
Generate a Graphite chart (12h default) for a Zigbee device metric and post it to the web timeline.
Reinstall piclaw from workspace source and force-restart the running process. Use after making code changes to piclaw.
Send a message to the chat immediately without waiting for the current task to finish. Useful for acknowledging requests or sending progress updates while working.
Situate yourself by generating a 1-page situation report and maintaining Obsidian-style daily summary notes.
Delete low-value messages from the web timeline by keyword patterns. Protects messages with user-uploaded images. Optionally vacuums the DB afterward.
Generate a 7-day token usage chart (all chats) and post it to the web UI timeline.
Fetch a user's recent tweets (tweets, replies, retweets) using Playwright + Nitter fallbacks and produce compact JSON/Markdown summaries.
Search via SearXNG, fetch top results, and return quick summaries plus markdown.
Auto-indexed from rcarmo/piclaw
Are you the author? Claim this skill to take ownership and manage it.
Related Skills
graceful-error-recovery
Use this skill when a tool call, command, or API request fails. Diagnose the root cause systematically before retrying or changing approach. Do not retry the same failing call without first understanding why it failed.
audience-aware-communication
Use this skill when writing any explanation, documentation, or response that will be read by someone else. Match vocabulary, depth, and format to the audience's expertise level before writing.
Refactoring Expert
Expert in systematic code refactoring, code smell detection, and structural optimization. Use PROACTIVELY when encountering duplicated code, long methods, complex conditionals, or any code quality issues. Detects code smells and applies proven refactoring techniques without changing external behavior.
Research Expert
Specialized research expert for parallel information gathering. Use for focused research tasks with clear objectives and structured output requirements.
clarify-ambiguous-requests
Use this skill when the user's request is ambiguous, under-specified, or could be interpreted in multiple ways. If proceeding with a wrong assumption would waste significant work, always ask exactly one focused clarifying question before doing anything.
structured-step-by-step-reasoning
Use this skill for any problem that involves multiple steps, tradeoffs, or non-trivial logic. Think out loud before answering to improve accuracy and transparency. Apply whenever the answer is not immediately obvious.