4.9万 件 ・ 関連度順
概要と使いどころ
Show what this NanoClaw instance can do — installed skills, available tools, and system info. Read-only. Use when the user asks what the bot can do, what's installed, or runs /capabilities.
日本語の概要は準備中です。原文の説明を表示しています。
Debug container agent issues. Use when things aren't working, container fails, authentication problems, or to understand how the container system works. Covers logs, environment variables, mounts, and common issues.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants local voice transcription instead of OpenAI Whisper API. Switches to whisper.cpp running on Apple Silicon. WhatsApp only for now. Requires voice-transcription skill to be applied first.
日本語の概要は準備中です。原文の説明を表示しています。
Add new capabilities or modify NanoClaw behavior. Use when user wants to add channels (Telegram, Slack, email input), change triggers, add integrations, modify the router, or make any other customizations. This is an interactive skill that asks questions to understand what the user wants.
日本語の概要は準備中です。原文の説明を表示しています。
Add Gmail integration to NanoClaw. Can be configured as a tool (agent reads/sends emails when triggered from WhatsApp) or as a full channel (emails can trigger the agent, schedule tasks, and receive replies). Guides through GCP OAuth setup and implements the integration.
日本語の概要は準備中です。原文の説明を表示しています。
Switch from Docker to Apple Container for macOS-native container isolation. Use when the user wants Apple Container instead of Docker, or is setting up on macOS and prefers the native runtime. Triggers on "apple container", "convert to apple container", "switch to apple container", or "use apple container".
日本語の概要は準備中です。原文の説明を表示しています。
Run initial NanoClaw setup. Use when user wants to install dependencies, authenticate messaging channels, register their main channel, or start the background services. Triggers on "setup", "install", "configure nanoclaw", or first-time setup requests.
日本語の概要は準備中です。原文の説明を表示しています。
Quick read-only health check — session context, workspace mounts, tool availability, and task snapshot. Use when the user asks for system status or runs /status.
日本語の概要は準備中です。原文の説明を表示しています。
Format messages for Slack using mrkdwn syntax. Use when responding to Slack channels (folder starts with "slack_" or JID contains slack identifiers).
日本語の概要は準備中です。原文の説明を表示しています。
Turn a Git repository URL or local path into one elegant, self-contained HTML learning page that teaches the project's value, architecture, and operating principles top-down with diagrams. Use when the user wants to understand, learn, onboard, explain, map, or study a repository.
日本語の概要は準備中です。原文の説明を表示しています。
Use before starting any coding task when Superpowers is not present.
日本語の概要は準備中です。原文の説明を表示しています。
MUST USE when asked to find, read, list, search, inspect, fetch, export, or reconstruct coding-agent sessions across Codex, Claude Code/Desktop, Aside, OpenCode, Senpi/pi, OpenClaw, Factory Droid, Amp, Gemini/Kimi/Qwen CLIs, Codebuff, Roo/Kilo/Cline, Kodu, Cursor CLI, Aider, Kiro, Goose, Hermes, Crush, Zed, or unknown local agent logs. Uses the repo-backed TypeScript coding-agent-sessions CLI for transcripts, session IDs, rollout JSONL, state SQLite, Claude histories, Aside messages.jsonl, OpenCode sessions, child linkage, cwd/model/time/token filters, archives, and cost clues.
日本語の概要は準備中です。原文の説明を表示しています。
Create or update dewee.sh custom pages (/p/<slug>), blog posts and media through the dewee-web CLI or the remote MCP server at https://dewee.sh/mcp. Use when asked to publish an announcement, write a blog post, build a landing page from blocks, or upload an image to cdn.dewee.sh.
日本語の概要は準備中です。原文の説明を表示しています。
Build, improve, package, and review Codex skills from rough ideas, workflows, scripts, README/API/CLI docs, or existing skill folders. Use when the user wants to create a new Codex skill, convert a repeatable workflow into a reusable skill, scaffold SKILL.md plus references/scripts/assets, validate a skill, or prepare a skill for sharing on GitHub.
日本語の概要は準備中です。原文の説明を表示しています。
Maintain the official OpenMeld Changelog from repository evidence. Use when deciding whether a change needs a Changelog entry, writing or publishing an entry, preparing release notes, validating generated Changelog files, or historically backfilling missing changes.
日本語の概要は準備中です。原文の説明を表示しています。
Use when asked to deploy, release, publish, or ship OpenMeld to production — workers, Web, CLI, or local components. Routes to the guarded release lanes; never deploy raw.
日本語の概要は準備中です。原文の説明を表示しています。
Debugs failing GitHub Actions CI runs for PostHog PRs, commits, and branches, and answers broad CI-health questions ("is CI red?", "is master green today?", "what's broken right now?"). Use when the user asks why CI is red, asks for the current CI or master status, or mentions a failing check, GitHub Actions run, Depot runner, workflow, job, shard, merge queue kick, flaky test, lint failure, typecheck failure, snapshot diff, migration check, generated types drift, or skills build failure. Start with the `hogli ci:insights` digest (cross-run CI history from engineering analytics), then guides read-only inspection, failure classification, smallest local reproduction with hogli, and safe reporting without rerunning CI or posting to GitHub. Running unattended as the "Master-red diagnosis" workflow: see references/master-red-incident.md.
日本語の概要は準備中です。原文の説明を表示しています。
Use when diagnosing a Wake that failed, stalled, or produced no visible reply — dispatch, setup handoff, or reply-path issues. Routes to the deterministic trace evidence path.
日本語の概要は準備中です。原文の説明を表示しています。
Use when deciding whether an OpenMeld change needs a Changelog entry, writing or publishing an entry, preparing release notes, validating Changelog projections, or historically backfilling missing changes.
日本語の概要は準備中です。原文の説明を表示しています。
Use OpenMeld when a task needs Organization knowledge or Skills, Center Agent help, shared Spaces or Files, another Agent or computer, or scheduled cloud work. Also use for OpenMeld setup and Wake replies.
日本語の概要は準備中です。原文の説明を表示しています。
Use when closing out a feature, tidying developing/ documentation, or asked to check docs health — runs the lifecycle linter and applies the README deletion rules.
日本語の概要は準備中です。原文の説明を表示しています。