업무 효율화 스킬

Search Mouser Electronics for electronic components — secondary source for prototype orders. Find parts, check pricing/stock, download datasheets, analyze specifications. Use with KiCad for BOM creation and part selection. Use this skill when the user specifically mentions Mouser, when DigiKey is out of stock or has worse pricing, when comparing prices across distributors, or when searching for parts that DigiKey doesn't carry. For package cross-reference tables and BOM workflow, see the `bom` skill.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

PCBWay fabrication and turnkey assembly workflows. Load the canonical Circuit Weaver skill from `skills/pcbway/SKILL.md`.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Vivado and FPGA workflow guidance. Load the canonical Circuit Weaver skill from `skills/vivado/SKILL.md`.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Circuit simulation workflows — SPICE simulation via ngspice, confidence scoring, RF chain analysis (scikit-rf), power/clock transient and AC analysis. Trigger on: "simulate", "run simulation", "spice", "check stability", "ripple analysis". Load the canonical sim skill from `project-skills/sim/SKILL.md`.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Write a product brief and its task list when the user requests a product specification. Never implement it.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when the user invokes Arsenal, needs help choosing an approach, or wants an end-to-end task handled with the installed Arsenal skills.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Generate structured weekly or fortnightly status updates for leadership and stakeholders. Use this skill when: - You need to prepare a weekly or fortnightly status report - You want to summarize recent progress across git commits, tickets, and spec changes - You need a formatted update ready for Slack, email, or a stakeholder meeting - You want multi-project updates in one report

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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"

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when the user says "write my investor update", "monthly update for investors", "quarterly investor email", "investor communication", "LP update", "board update", "shareholder update", "what do I tell my investors this month", "how do I write a good investor update", or wants to communicate progress, metrics, and needs to existing investors or board members on a recurring basis.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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 "write a cold email to investors", "investor outreach email", "how do I cold email a VC", "fundraising cold outreach", "email to angel investor", "reach out to investors", "get a meeting with investors", "intro email for fundraising", "follow up with investor", "warm intro email", or wants to draft any outbound investor communication to generate a first meeting or advance a fundraising conversation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Draft professional emails (MoM, status updates, decisions, stakeholder communication) and save as a draft in your email provider. Use this skill after a meeting, decision, spec update, or any event that needs email communication. Trigger phrases: "send MoM email", "draft meeting minutes email", "MoM email for [meeting]", "create MoM draft", "email the meeting notes", "draft MoM", "draft email", "send update email", "draft email for [topic]". Reads context from meetings, specs, tickets, and conversation. Looks up attendee emails from a local team directory, formats as HTML email, and pushes to the email provider as a draft (never sends).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Generate diagrams of any kind from a description, ticket, spec, or file. Outputs Mermaid syntax (renders natively in GitHub, Notion, Confluence, Obsidian, Slack with apps) plus an optional single-file HTML preview that renders the diagram in the browser. Use this skill when the user says: - "draw a flowchart", "create a diagram", "visualize this flow" - "sequence diagram", "state diagram", "ER diagram", "class diagram" - "user journey", "mindmap", "timeline", "gantt", "org chart" - "sankey", "quadrant chart", "git graph" - or pastes a ticket / spec / description and asks for a visual Picks the right Mermaid diagram type for the input, asks if ambiguous, then emits clean syntax + an optional preview file.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Create Jira tickets from meeting notes, user stories, or quick lists. Use this skill when: - User says "create tickets", "make Jira tickets from", "push to Jira" - User has meeting action items to convert to tickets - User has user stories from a spec to push to the backlog - User wants to batch-create tasks, stories, or bugs

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Run, document, or review a structured month-end close process. Use when an accountant says "help me with month-end close", "close checklist", "end of month tasks", "what do I need to do to close the books", "journal entries for close", "reconciliation checklist", "accruals and prepaids", "intercompany eliminations", "trial balance review", "close sign-off", or anything related to closing a financial period. Also trigger when someone is preparing for a quarterly or year-end close and needs a structured approach - even if they don't say "month-end close" explicitly.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Analyze customer health signals, identify churn risk flags, and generate an intervention playbook. Use when user says "churn risk", "customer at risk", "red account", "at-risk customer", "health score dropped", "renewal at risk", "customer going dark", "cancel risk", or "what's wrong with this account" - even if they don't say "churn" explicitly. Applies to CSMs triaging accounts or building proactive retention workflows.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Comprehensive guide for visualizing ENCODE data including deeptools heatmaps, IGV screenshots, UCSC track hubs, and publication-quality plots. Use when users need to create visualizations of ChIP-seq signal, peak landscapes, genome browser views, or any visual representation of ENCODE data. Trigger on: heatmap, visualization, genome browser, track hub, IGV, deeptools, signal plot, peak visualization, profile plot, publication figure, bigWig visualization.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Creates feature branches with optimized short naming, auto-incrementing, and commit type detection (feat/fix/refactor). Supports manual descriptions and auto-generation from uncommitted git changes. Use when user requests to create branch, start new branch, make branch, checkout new branch, switch branch, new task, start working on, begin work on feature, begin feature, create feature branch, run /create-branch command, or mentions "branch", "feature", "new feature", "feat", "fix", or "checkout".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Install Taskfile (task) and scaffold or audit Taskfile.yml configurations with ecosystem-aware templates. Auto-detects Node.js/pnpm, JVM/Gradle, Python/uv, Docker, and recommends single-file or multi-file (includes) patterns based on project complexity. Use when user runs /devtools:taskfile-setup, mentions "taskfile setup", "setup task runner", "audit taskfile", "scaffold taskfile", "add taskfile", "taskfile.yml", or "developer tasks".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Coordinate structured thinking and multi-agent parallel execution for complex tasks. Use when tackling multi-step projects, planning parallel work, breaking down complex problems, coordinating specialist tasks, facing architectural decisions, or when user mentions "workflow", "orchestration", "multi-step", "coordinate", "parallel execution", "structured thinking", "break this down", "plan this out", "how should I approach", or needs help planning complex implementations.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Execute an autonomous development loop that picks one task per iteration, implements it, verifies it, and commits the result — each iteration in a fresh context window. Use when user runs /ralph, mentions "ralph loop", "autonomous loop", "builder verifier", "run tasks automatically", "iterate on tasks", "develop autonomously", or wants an automated build-verify-commit cycle with task tracking.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when starting any conversation - establishes how arkhe skills bootstrap on Claude Code, Antigravity CLI (agy) / Gemini CLI, and Codex CLI, and maps Claude-only tools (AskUserQuestion, TaskCreate, EnterPlanMode, the Skill tool, the Agent tool) to their cross-platform equivalents

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Create Product Requirements Document (PRD) and setup for Ralph autonomous loop. Use when user runs /create-prd command, wants to set up a project for Ralph, mentions "ralph setup", "create prd", "product requirements", or needs to generate tasks for autonomous development.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use this whenever a downstream Vue project needs to absorb upstream Devkit Vue changes — triggers on "update stack", "sync with devkit", "merge upstream", "pull stack updates", "resolve stack conflicts". Two-phase: ISO merge (stack modules stay byte-identical to upstream) then project alignment (apply MIGRATIONS.md, diff project modules vs `tasks` reference, /verify). Stack-code failures get an issue on `pierreb-devkit/Vue`.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.