Three-layer verification pipeline for AI output. Extracts verifiable claims, finds supporting or contradicting sources via web search, runs adversarial review for hallucination patterns, and produces a structured verification report with source links for human review. Use when AI-generated text with factual claims must be checked before it is published or relied on.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Creates, configures, and deploys Azure Static Web Apps with the SWA CLI, including local emulation, API backends, auth simulation, and staticwebapp.config.json. Use when hosting a static frontend with optional serverless APIs on Azure or debugging an SWA deployment.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Updates Azure Verified Module (AVM) references in a Bicep file to their latest versions, applying only non-breaking changes and reporting the result as a table. Use when Bicep templates pin outdated AVM versions or before an infrastructure release.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when auditing a CPython C/C++/Cython/Rust extension for free-threaded Python, a `t`-suffixed ABI wheel, GIL opt-out, native race, callback crash, or free-threaded release gate.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Document analysis with inline source screenshots. When you ask Copilot to analyze a document, Eyeball generates a Word doc where every factual claim includes a highlighted screenshot from the source material so you can verify it with your own eyes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when writing, reviewing, or refactoring production code where reliability, portability, maintainability, explicit contracts, resource safety, and cross-language coding standards matter across Python, TS/JS, C, C++, Rust, or Go.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Produces a concrete plan before a multi-file refactor: scope, sequence, risks, and verification for each step. Use when the user asks to plan, sequence, or safely execute a refactor across several files, before any code changes are made.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate personalized status briefings on demand. Pulls from your configured data sources (GitHub, email, Teams, Slack, and more), synthesizes across them, and drafts updates in your own communication style for any audience you define
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Tests in real browsers via Chrome DevTools MCP. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data. Requires the chrome-devtools MCP server to be configured.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Conducts a multi-axis code review (correctness, readability, architecture, security, performance) before merging. Use before merging any change, after finishing a feature or bug fix, when reviewing code another agent or person wrote, or when asked to review a diff or pull request.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Product leadership for scaling companies. Product vision, portfolio strategy, product-market fit, and product org design. Use when setting product vision, managing a product portfolio, measuring PMF, designing product teams, prioritizing at the portfolio level, reporting to the board on product, or when user mentions CPO, product strategy, product-market fit, product organization, portfolio prioritization, or roadmap strategy.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Revenue leadership for B2B SaaS companies. Revenue forecasting, sales model design, pricing strategy, net revenue retention, and sales team scaling. Use when designing the revenue engine, setting quotas, modeling NRR, evaluating pricing, building board forecasts, or when user mentions CRO, chief revenue officer, revenue strategy, sales model, ARR growth, NRR, expansion revenue, churn, pricing strategy, or sales capacity.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Coaches founders and CEOs on their own development: leadership archetype, delegation, blind spots, and the decisions that change as the company scales. Use when a founder is the bottleneck, struggles to delegate, or is outgrowing their current way of leading.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Founder onboarding interview that captures company context across 7 dimensions. Invoke with /cs:setup for initial interview or /cs:update for quarterly refresh. Generates ~/.claude/company-context.md used by all C-suite advisor skills. Use when setting up the C-suite advisors for the first time, or when company context is missing or more than 90 days old — e.g. after a fundraise or pivot.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Technical leadership guidance for engineering teams, architecture decisions, and technology strategy. Use when assessing technical debt, scaling engineering teams, evaluating technologies, making architecture decisions, establishing engineering metrics, or when user mentions CTO, tech debt, technical debt, team scaling, architecture decisions, technology evaluation, engineering metrics, DORA metrics, or technology strategy.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build, measure, and evolve company culture as operational behavior — not wall posters. Covers mission/vision/values workshops, values-to-behaviors translation, culture code creation, culture health assessment, and cultural rituals by stage. Use when building company values, assessing culture health, designing cultural rituals, creating culture codes, handling culture clashes, or when user mentions culture, values, culture debt, founder culture, or culture code.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Adversarial thinking partner for founders and executives. Stress-tests plans, prepares for brutal board meetings, dissects decisions with no good options, and forces honest post-mortems. Use when a plan needs hard scrutiny, a board meeting is coming, a painful decision has been avoided, or a failure needs an honest post-mortem.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Assembles comprehensive board and investor update decks by pulling perspectives from all C-suite roles. Use when preparing board meetings, investor updates, quarterly business reviews, or fundraising narratives. Covers structure, narrative framework, bad news delivery, and common mistakes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Two-layer memory architecture for board meeting decisions. Manages raw transcripts (Layer 1) and approved decisions (Layer 2). Use when logging decisions after a board meeting, reviewing past decisions with /cs:decisions, or checking overdue action items with /cs:review. Invoked automatically by the board-meeting skill after Phase 5 founder approval.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Ranks any list of impediments and their countermeasures using a value-stream scoring model (ROI, Cost to Implement, Ease of Deployment, Risk Factor) and a fixed prioritization formula. Use when someone asks to prioritize, rank, sequence, or triage impediments, countermeasures, remediation items, risks, findings, gaps, action items, or backlog entries; or mentions value-stream prioritization, A3 / lean countermeasure ranking, ROI vs. effort scoring, or building a remediation / improvement backlog. Works with GHQR findings, audit results, retrospective action items, risk registers, architecture review gaps, or any free-form `{impediment, countermeasure}` list.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Multi-agent board meeting protocol for strategic decisions. Runs a structured 6-phase deliberation: context loading, independent C-suite contributions (isolated, no cross-pollination), critic analysis, synthesis, founder review, and decision extraction. Use when the user invokes /cs:boardroom, calls a board meeting, or wants structured multi-perspective executive deliberation on a strategic question.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Turn vague "what did I do?" into evidence-backed impact statements for performance reviews, self-reviews, promotion packets, and weekly updates. Uniquely mines Copilot CLI session logs to reconstruct forgotten work, plus git commits and GitHub PRs. Enforces a 3-part impact contract (action → result → evidence). Works standalone with zero dependencies. Trigger for: "brag", "log work", "what did I do", "backfill my work history", "performance review", "self-review", "self assessment", "write impact statement", "review prep", "promo packet", "promotion case", "weekly update", "status report", "accomplishments", "what did I ship", "I forgot to log my work", "summarize my work", "track my wins", "what should I highlight", "end of half", "career growth", "work journal", or any request to document, summarize, or organize work accomplishments.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyze Azure resource health, diagnose issues from logs and telemetry, and create a remediation plan for identified problems. Use when an Azure resource is unhealthy, slow, or failing and the cause is unknown.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Fetches real-time Azure retail pricing using the Azure Retail Prices API (prices.azure.com) and estimates Copilot Studio agent credit consumption. Use when asked what an Azure service costs, to compare regions or SKUs, to estimate a workload, or about reserved, savings plan, or spot pricing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.