이메일, 캘린더, 할 일 관리, 자동화 (7.8천건)
Use when a task needs the judgment of an air traffic controller — sequencing and spacing arrivals/departures, resolving a projected loss of separation, applying wake-turbulence separation between mismatched aircraft categories, deciding when to query a read-back, or working a facility through a saturation/traffic-management event.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a task needs the judgment of an airfield operations specialist — running a Part 139 self-inspection of the movement area, assigning a Runway Condition Code (RwyCC) after snow/ice contamination, deciding whether a discovered hazard needs an immediate NOTAM, triggering a Wildlife Hazard Assessment after a strike or sighting, or judging a FOD find as immediate-closure versus scheduled removal.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a task needs the judgment of an Aircraft Cargo Handling Supervisor — verifying a built ULD against its type's certified max gross weight before it's spotted for loading, running a hazmat item through the segregation table against its actual compartment neighbors, reconciling an actual cargo build against the dispatcher's load plan and deciding whether it clears a last-minute-change threshold or needs a reissued loadsheet, calling a ULD's lock/net restraint good or rejecting it, or running ramp FOD and ground-equipment clearance discipline around an aircraft during turn.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a task needs the judgment of an Agricultural Equipment Operator — calibrating planter seed population and singulation, diagnosing combine header or separator loss, sequencing planting or harvest across fields under a weather-constrained window, sizing machinery capacity in acres/hour against a season's acreage, or evaluating PTO/grain-bin entrapment safety on a job site.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use Chanjing TTS API to convert text to speech (list voices, create tasks, poll, download from returned URLs).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
List, select, and install Volcengine skills from the volcengine-skills marketplace. Use when a user asks which Volcengine skill or plugin handles a task, wants to browse every available skill, needs an optional skill that is not currently installed, or asks to install or check the installation status of a Volcengine skill. Also use to discover any core skill, including this finder. Use as a fallback during a Volcengine operation when the currently loaded or installed skills cannot cover the required product, tool, or workflow; inspect the full catalog, select the missing capability, and install it.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
指导 AI 正确填写任务日志，并在任务完成后自动提取认知价值。当任务完成后、对话即将结束时、或用户提到「写日志」「更新日志」「任务记录」时自动触发。对应 AGENT_RULES.md RULE-01/02/03。版本：v2.0（2026-03-19新增步骤四：认知提取）
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks. Also use when the user says "openspec apply", "opsx apply", or "openspec implement".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Add SLSA build-provenance attestations to existing GitHub Actions workflows. Use when the user wants to add artifact attestations, build provenance, or SLSA attestations to Docker container image builds in GitHub Actions CI/CD pipelines.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends your capabilities with specialized knowledge, workflows, or tool integrations.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Archive a completed OpenSpec change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete. Also use when the user says "openspec archive" or "opsx archive".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Drive running Unity Editor from shell to verify compiles, playmode, scenes, screenshots. Use when editing C# scripts, scenes, or assets in a Unity project and needing to: (1) check compilation succeeds, (2) read console errors, (3) enter/exit Play mode, (4) capture screenshots or frame recordings, (5) select objects or aim the Scene camera, (6) query editor window layout. Injects a file-polling command bridge (UnityRemote.cs) — prefer this over batchmode (fights the Library lock) or GUI automation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Dispatch and execute implementation plans with TDD and checkpoints. Use when plan is ready. Parallel by default for independent tasks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Meta-orchestrator — dispatches to the right skill for the task. Use before any non-trivial work.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create graph-informed implementation plans before writing code. Use before any non-trivial task. Skip for small changes (≤2 files, <20 lines, no hub/bridge).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apply a formal state machine to issues — assign category (bug/enhancement/question/spike) and state (needs-triage → needs-info → ready-for-agent → ready-for-human → wontfix). Issues marked ready-for-agent become inputs to supergraph:plan. Use when processing a backlog, reviewing new issues, or preparing work for automation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Compact current session context into a handoff document for seamless continuation in a new session. Use when context window is exhausted, switching machines, handing work to another agent, or ending a long session mid-task.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
用于实现新前端行为、修复 bug 或重构可先由测试描述预期行为的逻辑。适用于组件、hooks/composables、工具函数、API clients、路由守卫或用户工作流；中文触发词包括 TDD、测试驱动、先写测试、红绿重构、回归测试。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when diagnosing or improving frontend performance, Core Web Vitals, bundle size, runtime rendering cost, network waterfalls, memory leaks, long tasks, Lighthouse findings, or performance budgets; Chinese triggers include performance optimization, page freeze, slow first screen, bundle volume, Web Vitals.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when implementing new observable frontend behavior or fixing a behavior-changing bug where a failing test can describe the missing or incorrect behavior first. Apply to components, hooks/composables, utilities, API clients, route guards, or user workflows; pure behavior-preserving refactoring uses an already-green contract instead.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when creating, reviewing, or restructuring frontend monorepos with pnpm workspace, Turborepo, Nx, multi-package dependency boundaries, task orchestration, package naming, or package publishing; Chinese triggers include monorepo, workspace, multi-package.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Publishes a Replica prototype through its existing workflow and Hub Build. Use for prototype canvas publishing requests that include verified target JSON and a publishing mode.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
MUST be used for Vue.js tasks. Strongly recommends Composition API with `<script setup>` and TypeScript as the standard approach. Covers Vue 3, SSR, Volar, vue-tsc. Load for any Vue, .vue files, Vue Router, Pinia, or Vite with Vue work. ALWAYS use Composition API unless the project explicitly requires Options API.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Prove existing work meets acceptance conditions without expanding scope. Use for validation-only tasks, completion checks, focused gate runs, and last-mile proof.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.