6,347 件 ・ 関連度順
概要と使いどころ
Analyze existing KiCad projects, schematics, PCB layouts, Gerbers, netlists, and PDF reference schematics. Use when files such as .kicad_sch, .kicad_pcb, .kicad_pro, or Gerbers are supplied and the user wants review, debugging, net tracing, ERC/DRC/DFM, schematic-to-PCB comparison, or pre-fabrication checks. Do not use to create a new design from requirements or for standalone sourcing and ordering.
日本語の概要は準備中です。原文の説明を表示しています。
Search DigiKey by keyword or part number, check stock and price breaks, retrieve component specifications, and download or synchronize datasheets for an electronics project. Use when the user explicitly wants DigiKey data, a DigiKey prototype-order comparison, or direct datasheet synchronization. For distributor-neutral sourcing, multi-vendor price comparison, or order-file generation, use the bom skill instead.
日本語の概要は準備中です。原文の説明を表示しています。
Build-less ESM frontends that run directly in the browser without bundlers. Use this skill when creating static frontends, SPAs without build tools, prototypes, or when the user explicitly wants no Vite/Webpack/bundler. Covers import maps, CDN imports, cache-busting, hash routing, and performance patterns.
日本語の概要は準備中です。原文の説明を表示しています。
Set up and run local LLMs with Harbor. Use when the user wants to run models locally, install Harbor, start Open WebUI, llama.cpp, Ollama, vLLM, Docker Model Runner, MLX, or oMLX, pull GGUF or HuggingFace models, add SearXNG web search, Speaches TTS/STT, or Open Terminal code execution, launch Codex/Claude/Grok/OpenCode against a Harbor backend, or troubleshoot GPU, VRAM, and service startup.
日本語の概要は準備中です。原文の説明を表示しています。
Timeboxed ideation on a topic where lens-driven proposers generate structurally different ideas, blind critics cull them, and pairwise judges rank the survivors on a tournament ladder instead of 1-10 scores, evolving the leaders until the clock runs out. Use when the user wants to brainstorm, explore ideas, discover features, generate options, or think through possibilities for a specified duration. Triggers on requests like "brainstorm X for 30 minutes", "ideate on X", "spend an hour thinking about X", "what features should we build", "explore options for X". Not for executing a task over time (timeboxed-iterating) or optimizing a measurable metric (autoresearch).
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants to systematically fix AI code slop — duplicated logic, over-engineering, silent error swallowing, convention drift, cargo-cult patterns, and other LLM-introduced architectural decay — over a specified duration
日本語の概要は準備中です。原文の説明を表示しています。
Run a task iteratively over a user-specified duration by dispatching subagents. The orchestrator stays strictly linear and time-checked, but each iteration fans out MULTIPLE subagents in parallel over independent units (and those subagents may fan out further). Shared state — a compact progress digest and a growing environment cheatsheet — lives on disk and is passed to every subagent BY REFERENCE, killing the per-subagent rediscovery tax. Every subagent first reads an initialiser preamble that points it at that shared state and makes it write findings back, so the cheatsheet populates itself; role prompts are produced ONCE on the filesystem by a single scaffold command and dispatched by path, never re-typed per dispatch. Subagents persist their results to disk and return only a tiny status, so the orchestrator's context stays small and lasts. The orchestrator classifies the goal as FINITE or OPEN-ENDED: finite lists may finish early; open-ended goals use the full duration, never idle, never manufacture busywork. Use when the user gives a task and a duration and wants it ground out iteratively by subagents over that time.
日本語の概要は準備中です。原文の説明を表示しています。
Household assistant for a whole family. Runs a morning brief, plans meals and builds grocery lists (hunting the best prices), looks ahead at the week's logistics, stays on top of the kids' school, watches prices on things the family wants, and helps book appointments and reservations. Use it for anything that keeps the family's day or week running. Trigger even on implicit asks - "what's on today", "what do the kids have this week", "what should we make for dinner", "add milk to the list", "when's the dentist", "did anything come from school", "remind me about the permission slip", "watch this jacket and tell me if it drops", "book us a table Friday".
日本語の概要は準備中です。原文の説明を表示しています。
Fetch the latest AI/ML news, trending open-source projects, social media discussions, and KOL (Key Opinion Leader) perspectives from 370+ curated sources. Use when the user asks about recent AI news, AI trends, what's happening in machine learning, open-source AI projects, AI Twitter/Reddit discussions, or wants a daily AI briefing.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user invokes Arsenal, needs help choosing an approach, or wants an end-to-end task handled with the installed Arsenal skills.
日本語の概要は準備中です。原文の説明を表示しています。
Best practices for building and maintaining applications with PowerSync: Cloud and self-hosted setup, sync configuration, client SDK usage, backend integration (Supabase, custom Postgres, MongoDB, Azure DocumentDB, MySQL, MSSQL), schema changes, watch and reactive queries (useQuery), attachments, the upload queue, and debugging. Use this skill whenever the user mentions PowerSync, a @powersync/* package (@powersync/web, @powersync/react-native, @powersync/node), the powersync Flutter/Dart package, the powersync Rust crate, wa-sqlite, offline-first sync, local-first architecture, sync rules, sync streams, uploadData, fetchCredentials, disconnectAndClear, logout or user switching in a synced app, real-time data replication, Electric Cloud migration, Electric Shapes, an app stuck on Syncing, data not syncing, or wants to add offline-capable sync to a mobile or web app, even if they do not explicitly name PowerSync.
日本語の概要は準備中です。原文の説明を表示しています。
Write a performance-based job description. Use when the user says "write a JD", "draft a job posting", "create a job description", "help me post this role", "write requirements for this position", or wants to define what success looks like in a role - even if they don't explicitly say "job description". Also use when a hiring manager says "I need someone who can do X, Y, Z" and needs that translated into a structured posting.
日本語の概要は準備中です。原文の説明を表示しています。
Construct a compelling job offer. Use when the user says "write an offer letter", "help me make an offer", "how should I structure this offer", "what should we include in the offer", "how do I explain the equity", "the candidate is negotiating", or wants to convert a candidate from interested to accepted - even if they don't explicitly say "offer letter". Also use when a recruiter needs to explain comp philosophy or total compensation to a candidate.
日本語の概要は準備中です。原文の説明を表示しています。
Handle sales objections using tactical empathy. Use when the user says "how do I handle this objection", "prospect said [X]", "they pushed back on price", "they said they're not ready", "how to respond to 'we already have a solution'", "they said 'send me more information'", "objection response", "they went dark after the proposal", "how to handle 'we don't have budget'", or wants to craft a response to a specific sales objection.
日本語の概要は準備中です。原文の説明を表示しています。
Build a strategic account plan for winning, retaining, or expanding a named account. Use when the user says "build an account plan", "strategic account planning", "how do I grow this account", "account expansion strategy", "whitespace analysis", "QBR prep", "key account review", "map the stakeholders in this account", "land and expand plan", "how do I break into [company]", or wants a structured strategy for a specific account.
日本語の概要は準備中です。原文の説明を表示しています。
Qualify a sales opportunity using the MEDDIC framework. Use when the user says "qualify this deal", "is this deal real", "MEDDIC qualification", "MEDDICC framework", "should I pursue this opportunity", "deal review", "how qualified is this prospect", "pipeline review prep", "forecast this deal", "sanity check on this opportunity", or wants to assess whether a sales opportunity is worth pursuing and at what pipeline stage.
日本語の概要は準備中です。原文の説明を表示しています。
Run a recruiter-hiring manager intake meeting to kick off a search. Use when the user says "I need to kick off hiring", "run the intake call", "prepare for the intake meeting", "align with the hiring manager on this role", "we're opening a req", or wants to define hiring criteria and process before sourcing begins - even if they don't explicitly say "intake meeting". Also use when a recruiter needs to get a hiring manager aligned on what "great" looks like before anyone talks to a single candidate.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Build a candidate sourcing strategy and outreach pipeline. Use when the user says "where do I find candidates for this role", "build a sourcing plan", "write a cold outreach message", "we're not getting enough applicants", "our pipeline is dry", "help me find passive candidates", "write a LinkedIn message", or wants to increase the volume or quality of candidates in the funnel - even if they don't explicitly say "sourcing strategy". Also use when a recruiter needs to go beyond job postings to find talent.
日本語の概要は準備中です。原文の説明を表示しています。
Write a compelling sales proposal. Use when the user says "write a sales proposal", "put together a proposal", "draft a proposal for this prospect", "create a business case", "write up our recommendation", "how to structure a proposal", "proposal template", "executive summary for a deal", or wants to create a written document that moves a prospect toward a decision.
日本語の概要は準備中です。原文の説明を表示しています。
Write user stories with acceptance criteria. Use when the user says "write user stories", "convert this to stories", "create acceptance criteria", "break this into tickets", "story map", "walking skeleton", "story for this feature", or wants to translate a feature idea into sprint-ready items - even if they don't explicitly say "user stories".
日本語の概要は準備中です。原文の説明を表示しています。
Write long-form thought leadership articles, opinion pieces, industry POV essays, and CEO/founder bylines using the Made to Stick SUCCESs framework (Chip and Dan Heath). Use when the user asks for a long-form article, executive byline, opinion piece, industry POV, manifesto, "explain our point of view on X", or wants to publish an authority-building piece (1200-2500 words). Reads brand voice and positioning from knowledge/. For a short-form post, see linkedin-post. For the newsletter, see newsletter-writer. For improving an existing draft, see copy-review.
日本語の概要は準備中です。原文の説明を表示しています。
Identify, score, and mitigate delivery risks for a program or release. Use when the user says "risk review", "what could go wrong", "risk register", "delivery risks for this release", "program risk assessment", "identify blockers before they hit", or wants to pressure-test a plan before committing - even if they don't say "risk review". Based on "The Phoenix Project" by Kim, Behr & Spafford (unplanned work, fragile systems, single points of failure) and "The Art of Project Management" by Scott Berkun (scoping risk, milestone pressure, hidden assumptions).
日本語の概要は準備中です。原文の説明を表示しています。
Analyze flow metrics to identify delivery bottlenecks and improve throughput. Use when the user says "flow metrics", "why is delivery slow", "cycle time analysis", "WIP analysis", "throughput review", "what's our lead time", "DORA metrics", "where is work getting stuck", "Kanban metrics", or wants to diagnose delivery performance using data - even if they don't explicitly say "flow metrics review". Based on "Making Work Visible" by Dominica DeGrandis (WIP limits, flow blockers, time thieves) and "Accelerate" by Forsgren, Humble & Kim (DORA metrics, delivery performance indicators).
日本語の概要は準備中です。原文の説明を表示しています。