スキルを探す

Explain how this assistant works and help users understand computer access, confirmation or login blocks, and Slack errors. Use for capability questions and confusing product limitations; verify the actual state and give a supported next step. Also use for questions about their avatar or profile picture (their icon or the picture at the top) or the color of messages they send (message color, chat bubble color, or text bubble color).

日本語の概要は準備中です。原文の説明を表示しています。

Use when reading Slack conversations, deciding when to respond, or sending messages, files, and reactions in Slack.

日本語の概要は準備中です。原文の説明を表示しています。

Coding-agent sessions on every machine you connected, over Herdr where it runs, tmux elsewhere, and MSP for your MSP hosts: one digest of what is waiting on you, ready for review, working or idle; open a session with a brief; read, steer, approve, stop, close; connect a machine in one command. Use for "my sessions", "my agents", "what needs me", another session or machine, "connect <host>", and Herdr asks (workspace, panes, tabs, lanes) when running inside Herdr; not the current pane itself (`herdr`), not peer-session messaging (`list_peer_sessions`).

日本語の概要は準備中です。原文の説明を表示しています。

Manage your private to-do list for the user. Use to add or update tasks, record what they are waiting on, track blockers, mark tasks complete or canceled, and clean up the list. Not for Dreamers or external task trackers.

日本語の概要は準備中です。原文の説明を表示しています。

Source-control safety for Git. Two rules apply whether or not you read the body. First, never commit, amend, push, tag, rebase, cherry-pick, revert, or reset --hard unless the user asked for that exact write in this session. An explicit request to create a new commit counts anywhere in the user's own task text, but it is not a request to amend, push, or tag. Finishing a task without that request is not authorization, so leave your work uncommitted for review. Second, when a Git lock file or corrupt index blocks you, never kill the holding process or bulldoze through with deletions - wait, retry, use the holder's own stop mechanism, or stop and report. Load the body only before writing Git history or recovering Git state.

日本語の概要は準備中です。原文の説明を表示しています。

Fill out online forms (Google Forms, Typeform and similar) or PDF, Word and DocuSign forms; prepare a reviewable draft and get approval before submitting or sending.

日本語の概要は準備中です。原文の説明を表示しています。

Review documents for signature or prepare a signing packet; verify fields and recipients while keeping sending and signing under explicit user authorization.

日本語の概要は準備中です。原文の説明を表示しています。

On an explicit planning request, always call `read_skill` for this skill before answering. Research first, then return one concise inline plan; do not create a plan file unless the user explicitly asks or a governing workflow requires one. Start and end the reply by saying this is not a special mode and `go` executes the plan; do not implement in the planning turn. For ordinary implement, build, fix, debug, or refactor requests, work directly. When an explicit plan divides work into separate diffs, commits, or PRs and the user asks to publish, preserve that split and tell the user before deviating.

日本語の概要は準備中です。原文の説明を表示しています。

Setting up or installing into a Python environment. One rule applies whether or not you read the body - the environment belongs with the project, so create it inside the project directory (.venv) or let uv manage it, and never in a scratch directory like /tmp and never by forcing an install into the system interpreter. Load the body before creating a virtualenv, choosing an installer, or writing run instructions for a Python project.

日本語の概要は準備中です。原文の説明を表示しています。

Load the body before the first implementation edit for a bug fix or behavior change, or when the user or governing specification makes reusable tests a deliverable. It keeps the smallest focused test with the delivered project and updates coverage when behavior changes. Do not load for greenfield work unless reusable tests are explicitly required, behavior-preserving refactors, verification-only work, plan/review/explanation/documentation/formatting/generated-output-only work, explicit no-change or no-tool work, or when the user declines tests.

日本語の概要は準備中です。原文の説明を表示しています。

Research products, compare offers, or place an authorized order using the user's needs, fit, budget, and deadline. Use for purchases and gifts.

日本語の概要は準備中です。原文の説明を表示しています。

Create or update a scheduled task that runs automatically. Use when the user says things like "every day", "each morning", "remind me in an hour", "run this at noon", or wants to reschedule an existing task.

日本語の概要は準備中です。原文の説明を表示しています。

Publish a reusable native Muse Idea with idea.share when the user explicitly asks to share or publish an Idea or asks for a muse.ai/ideas link. Never offer it unprompted. Not for pages or write-ups, sending a result to someone, social posts, or sharing an artifact.

日本語の概要は準備中です。原文の説明を表示しています。

Review Zoom meetings, calls, recordings, and transcripts. Use to catch up on missed calls, summarize decisions, and extract action items and owners; also work with Team Chat, Canvas, Tasks, Whiteboard, Hub, and Revenue Accelerator through Zoom's official MCP servers.

日本語の概要は準備中です。原文の説明を表示しています。

Find restaurants on OpenTable, check availability, and make, change, or cancel reservations. Use for restaurant booking and live reservation data.

日本語の概要は準備中です。原文の説明を表示しています。

Set up Muse's built-in Tailscale connector, join a tailnet or Headscale network, check status, and reach private machines through the TCP tunnel proxy. Read for Tailscale, VPN, MagicDNS, network egress, exit-node, or browser routing questions and supported limits.

日本語の概要は準備中です。原文の説明を表示しています。

Answer questions about the user's Muse subscription, plan, usage, tokens, reset timing, or available plans and prices, or verify information that references the Muse subscription.

日本語の概要は準備中です。原文の説明を表示しています。

Monitor a Tesla vehicle, inspect live state, and run explicit Tessie command endpoints.

日本語の概要は準備中です。原文の説明を表示しています。

Use when the user needs broad parallel research across many independent inputs with a shared output schema.

日本語の概要は準備中です。原文の説明を表示しています。

Use for feedback and feature requests to the Muse team. Whenever your response tells the user you can't do a specific thing they wanted, or accepts them giving up on one, offer once to file feedback in that response. This covers missing integrations you can't do yourself, capabilities you lack, and tasks that keep failing at a specific point. File only on their go-ahead. Also use when asked to send, view, check, or withdraw feedback.

日本語の概要は準備中です。原文の説明を表示しています。

View, create, update, and delete events in the user's Outlook Calendar.

日本語の概要は準備中です。原文の説明を表示しています。

Read, search, send, reply to, and delete messages in the user's Outlook Mail.

日本語の概要は準備中です。原文の説明を表示しています。

Use when the user asks to discover, inspect, or invoke an agentic capability dynamically published by a paired phone or wearable, including device controls, app actions, camera or media actions, and smart-home actions.

日本語の概要は準備中です。原文の説明を表示しています。

Use for any product or shopping question: find, reverse image search, shopping Instagram/Marketplace links, buy, compare, or evaluate real products with prices, images, and product page URLs, including buying or browsing Facebook Marketplace listings. Use when presenting shopping search results from any source. For shopping intent, load this skill first before any other skills.

日本語の概要は準備中です。原文の説明を表示しています。