「question」の検索結果

Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.

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

Create, import, analyze, resume, or revise an end-to-end Circuit Weaver electronic design from requirements through validated functional KiCad schematics, placement review, and a truthful manufacturing handoff. Use for new designs and for existing KiCad/PCB/Gerber projects that need durable state. Use kicad for one-off file inspection, bom for standalone sourcing, and design-wizard only when the user explicitly requests the slower questionnaire.

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

Electrical and electronic engineering reference — circuit analysis, component selection, power supply design, signal integrity, RF, thermal, EMC, and test & measurement. Use for design questions, calculations, component vetting, and first-principles analysis. Do not orchestrate a complete new board from requirements; use circuit-weaver for that end-to-end workflow.

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

Use only for an explicitly requested step-by-step Circuit Weaver questionnaire. Load the canonical workflow from skills/design-wizard/SKILL.md; use circuit-weaver for ordinary automatic new-design requests.

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

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.

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

Use for any product or shopping question: find, reverse image search, shopping Instagram/Facebook/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.

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

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.

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

Use this skill when an active or proposed trip needs planning, logistics, feasibility, entry or transit checks, itinerary work, or investigation of an airport process, immigration, ground transport, a transfer, or fast-track service, even for a narrow question with no booking intent. Route a bounded flight, hotel, restaurant, event, or other item ready for live availability or booking directly to Booking. Skip this skill for a stable travel fact alone or flight status.

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

Read Instagram profiles, followers, posts, comments, likes, stories, feed, saved content, and account insights. Answer questions about posts, reels, and Instagram links. Manage interests and profile details, and publish stories, reels, posts, or carousels on request.

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

Use for questions about Muse's general early access program, requests to join it, checking or withdrawing a join request, and admission updates.

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

Use to connect HealthEx and ask questions about your medications, lab results, and other health records.

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

Use for questions about a specific flight’s departure or arrival time, including “when’s my flight?” and confirmation of remembered times, plus flight status, delays, and cancellations. Verify the exact dated flight before answering; memory identifies the itinerary but does not verify its current schedule. Use FlightAware to monitor operational changes for an upcoming booked flight when the user directly asks for ongoing monitoring.

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

Primary entry point for direct flight, hotel, restaurant, or event-ticket transactions and for bounded live availability checks delegated by Travel Planning. Always use before provider-specific skills or browser work when the user asks to find live availability or prices, compare bookable options, book, or continue an active booking. Do not use for trip planning itself, broad inspiration, opening hours, schedules, flight status, or other factual questions without transaction intent.

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

Generate a complete structured interview kit for a role — 3-5 role-specific competencies, one behavioral (STAR-format) question per competency, 1-5 scoring rubric with explicit behavioral anchors at each level, per-panel scorecards, interviewer debrief template.

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

Run multi-source web research with adversarial verification and produce a cited report: decomposes the question into 3-6 distinct queries (broad, specific, comparative, recency-anchored), searches and ranks sources by authority, recency, and specificity.

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

Search the web for evidence using the available Exa tools. Prefer concise results and stop when the question is answered.

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

Build a structured interview scorecard for a role. Use when the user says "create an interview scorecard", "build an interview guide", "what questions should I ask for this role", "help me evaluate candidates consistently", "design the interview process", or wants to assess candidates against defined criteria - even if they don't explicitly say "scorecard". Also use when a recruiter or hiring manager wants to prevent gut-feel hiring.

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

Structure and prepare for a sales discovery call. Use when the user says "prep for discovery call", "discovery call questions", "how to structure my discovery call", "first call with a prospect", "what to ask on a discovery call", "sales call prep", "plan my discovery call", "initial call framework", or wants to prepare for or debrief a first sales conversation.

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

Design a research study. Use when the user says "study design", "design my research", "what research method should I use", "how do I test this hypothesis", "research plan", "methodology section", "experimental design", "survey design", "qualitative study design", "how to structure my study", "sample size", "data collection plan", or needs to plan how to test a research question or hypothesis - even if they don't explicitly say "study design".

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

Update a product spec from a meeting transcript — extract decisions, open questions, spec changes, and flowchart updates. Use this skill when: - A meeting discussed changes to a product spec and you need to update the local .md + wiki page - The user shares a meeting URL or transcript ID and says "update the spec" - The user says "what needs to change in the spec from this meeting" - After processing a meeting, when decisions affect a spec's content (not just action items) Trigger phrases: "update spec from meeting", "what changed in the spec", "meeting to spec", "sync meeting decisions to spec", "add meeting decisions to spec"

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

Structure and run effective 1:1 meetings with direct reports using Camille Fournier's Manager's Path and Andy Grove's High Output Management frameworks. Use when a manager says "help me structure my 1:1s", "my 1:1s feel like status updates", "I don't know what to talk about in 1:1s", "my reports don't open up", "how do I make 1:1s useful", "what questions should I ask in 1:1s", or "I need a 1:1 template". Also trigger when someone mentions their 1:1s feel transactional, that they keep canceling them, or that they're not sure if their report is happy.

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

Use when the user says "run customer discovery", "help me interview customers", "write customer interview questions", "validate my assumption", "talk to users", "synthesize customer interviews", "what are my customers saying", "user research for my startup", "mom test interview", "are we solving a real problem", or wants to extract real insight from conversations with potential or existing customers.

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

Generate, score, and shortlist brand names through a guided interview. Use when the user says "name my brand", "help me name", "come up with a name", "naming ideas", "what should I call this", "brand name", "product name", "company name", "rename", "rebrand", or is stuck choosing between names. Self-contained and brand-agnostic: it does not read knowledge/, so it works for naming a brand-new venture, product, service, feature, or rebrand from scratch, before any brand context exists. Runs on Alexandra Watkins' SMILE and SCRATCH tests to generate and filter, Marty Neumeier's 7 criteria to score, and the Lexicon Branding method for sound symbolism and strategy. Asks the user questions before generating. For the positioning the name has to carry, see positioning-doc. For the message architecture built on top of it, see messaging-framework.

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

Build or refine the Ideal Customer Profile (ICP) and personas using the Jobs-to-be-Done framework (Clayton Christensen / Bob Moesta). Use when the user asks for ICP research, persona development, "who are our customers", buyer personas, audience research, "build our ICP", target customer definition, or wants to update persona docs. JTBD interview questions, three job dimensions (functional/emotional/social), and the Four Forces of Progress are wired into every persona. Writes to knowledge/icp/personas.md so all other skills get smarter. For the individual buyer persona rather than the segment, see customer-persona. For sourcing real customer language, see customer-research.

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