「ak sk」の検索結果

Use when the user asks to forge, scaffold, author, or ship a new skill or agent — the skill-creator's own namesake artifacts. Drives the skill-forge loop (create → fill → validate → critique → ship → publish) via the skill-creator CLI.

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

A live visual Kanban board and continuity layer for long-running agentic tasks. Nobody wants to read a markdown plan or stare at raw HTML while an agent grinds for an hour, so Plandeck turns the plan into a board that organizes itself. Use it when a task is multi-step, long-running, or needs visual planning. Break the work into cards, declare which card depends on which, and Plandeck computes the critical path, auto-promotes cards to Ready as their dependencies clear, rolls up story-point estimates into an honest percent complete, and names the one next action. Plans, observed transitions, and last-known-good snapshots stay as plain files on disk, so they survive /clear and context resets. After a reset, run plandeck next to recover the single next move and its recent history. If the plan stops parsing, run plandeck doctor before using git. Renders a live board in the browser over SSE. Triggers on plan a project, break down a task, kanban board, task board, visual plan, long-running agent, agentic task, track dependencies, critical path, story-point estimates, what is next, mission journal, recover plan, plandeck.

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

Use when creating a new feature development task — scaffolds a structured task file at .claude/tasks/{feature-name}.md with phased breakdown (Design, Implementation, Testing, Documentation), acceptance criteria, context preservation, and TaskCreate tracking. Activates on "create a feature task", "set up development tracking", "plan a feature implementation", or when preparing work for python-cli-architect or python-pytest-architect agents.

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

診斷並清理 macOS 磁碟空間，特別是「系統資料 / System Data」這類看不出內容的用量。涵蓋開發者工具殘骸（Xcode iOS DeviceSupport、Simulator runtime、DerivedData）、套件管理器快取（Homebrew、pnpm、pip、npm、cargo、go、uv）、容器與 VM 磁碟（Docker、podman、lima）、瀏覽器 profile、以及已移除 app 的孤兒 container。使用時機：(1) 使用者說磁碟快滿了、System Data 佔太多、想清空間 (2) 詢問某個資料夾或快取能不能刪 (3) 移除 app 後想清乾淨殘留檔案、完整解除安裝 (4) 想知道 Docker.raw、Group Containers、Library/Caches 這些是什麼、佔了多少。Also triggers in English — disk full, startup disk almost full, free up disk space, clean up Mac storage, what is System Data on my Mac, what is taking up space, safe to delete this cache, uninstall app leftovers, reclaim disk space, Docker.raw huge, Xcode taking too much space

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

実装計画・設計書からタスクを分解し、ファイル単位の依存関係を分析して 並列実行可能な Wave に自動グルーピングするスキル。 編集ファイルが被らないタスクは全て同時並列にし、 Mermaid 依存関係図 + ディレクトリ分割された TODO ファイル群を出力する。 team-plan の後工程、team-implement の前工程として使える。 Use when: 実装計画を並列タスクに分解したい、Wave 実行順序を設計したい、 タスクの依存関係を可視化したい、分業できる部分を洗い出したい。 Triggers: "タスク分解", "並列タスク", "parallel task", "Wave 設計", "依存関係を整理", "分業", "タスクリスト作成", "並列計画", "task breakdown", "parallel plan", "wave planning", "同時に進められる"

Update an EXISTING Tip in the ai-product-dev-tips repository — edit its README, add or fix code, refresh outdated information, fix mistakes — while keeping the repo's format conventions and syncing the root README link. Use this whenever the user wants to update, edit, fix, revise, refresh, correct, or complete an existing Tip in this repo — e.g. "nlp_processing/29 の README を更新して", "〇〇の Tip を最新仕様に直して", "image_processing/11 の説明を修正して", "あの Tip のリンク切れを直して", "この Tip を完成版にして". It locates the target Tip, studies the current format conventions (shared with the ai-product-dev-tips-create skill), applies consistent edits, verifies the content with web research (no fabrication), and syncs the root README link (title text / [In-progress]). This is for UPDATING existing Tips, not creating new ones — to add a brand-new Tip use the ai-product-dev-tips-create skill instead. Trigger this even if the user doesn't say "skill".

Takes a repeating task from your work, breaks it into Cowork steps, and builds it into a documented, reusable workflow — optionally turning it into a custom skill. For converting manual repeating tasks into automated systems, when documenting a process for consistent execution, or during a productivity overhaul. Use when the user says "build a workflow", "automate my process", "I do this every week", "create a system", "repeating task", "I keep doing the same thing", or "make this a workflow".

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

Teaches you how to break large tasks into stages, save your place between sessions, and recover smoothly when a task gets interrupted. Use when planning a multi-day project, for breaking down large work into manageable stages, during recovery from an interrupted session, when managing complex ongoing work, or when the user says "cowork stopped in the middle", "token limit", "task too large", "context management", "how to do big tasks", "session got cut off", "cowork forgot what we were doing", "how do I work on something over multiple days", "it lost track of the project", or "my task is too big for one session".

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

Synchronize curated Agent Skills across approved repositories with policy checks and verification. Use when publishing or updating managed skills, validating a repository mirror, or selecting a safe sync scope. Triggers on "sync public skills", "publish skills", "public 公開", "skill sync", "repository mirror".

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

Reflect reusable learnings into a private Agent Skills repository with scoped safety gates and same-run private commit/push. Not for ~/.copilot personal assets, VS Code User Data assets, or workspace/repository assets. Use when: skill retro, private skill authoring, skill repository fix, create or update SKILL.md.

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

Reflect reusable learnings into the current workspace / repository design and automation assets (.github/**, AGENTS.md, repo scripts/tasks). Not for ~/.copilot personal assets, VS Code User Data assets, or a private skills repository. Use when running a workspace/repo retro from CLI or Scout. Detects whether a project folder exists and, if not, asks before creating one. Triggers on "retro workspace", "repo retro", "workspace cleanup", "ワークスペース知見反映".

"Apply flow theory to diagnose optimal experience conditions and design environments that balance challenge and skill for sustained engagement. Use this skill when the user needs to explain why users disengage from tasks, optimize task difficulty for peak performance, design learning progressions or gamification systems, or when they ask 'why do people lose focus', 'how to design for engagement', or 'what conditions produce peak performance'.".

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

Post-review intake closing skill. After an intake is resolved (whether accepted via review/meta PR merge or rejected/deferred at triage/evidence review), run this skill to post standardized, personalized closing comments on the PR (if any) and each intake issue. Comments include: evidence pipeline findings with /trust-appraise TM output, per-row artifact scores, decisions rationale, path-to-promotion/acceptance guidance, and a mandatory badge status note including the universal Powered by Gaia badge. Use after curation completes, before or immediately after merge for accepted intakes, or immediately upon rejection.

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

Build psychological safety in your team using Simon Sinek's Leaders Eat Last Circle of Safety model and Amy Edmondson's research. Use when a leader says "my team doesn't speak up", "people are afraid to fail", "nobody challenges bad ideas", "people only tell me what I want to hear", "I want my team to take more risks", "there's a blame culture", "people hide mistakes", or "I want to create a safe environment". Also trigger when someone describes a team where postmortems turn into blame sessions, where people stay quiet in meetings and then vent privately, where mistakes are hidden until they become crises, or where the same person speaks 80% of the time in every meeting. Psychological safety is not about comfort - it is the condition that makes high performance possible.

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

Accept or apply for a task on OpenAnt. Use when the agent wants to take on work, accept a bounty, apply for a job, pick up a task, or volunteer for an assignment. Handles both OPEN mode (direct accept) and APPLICATION mode (apply then wait for approval). Covers "accept task", "take this task", "apply for", "pick up work", "I want to do this".

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

Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.

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

Estimates time-scaled phylogenies, molecular-clock rates, effective reproduction number R_e, and population dynamics from dated pathogen genomes using TreeTime (maximum-likelihood) and BEAST2 (Bayesian; strict/relaxed clocks; coalescent, Bayesian-Skyline, Skygrid, Birth-Death-Skyline, and sampled-ancestor priors; structured coalescent via MASCOT). Covers root-to-tip clock QC via TempEst, date-randomisation tests, recombination masking via Gubbins/ClonalFrameML before clock inference for recombining bacteria, BDSKY origin-vs-rootHeight pitfalls, sampling-bias correction, multi-chain convergence diagnostics, and reconciling phylodynamic R_e with case-based R_t. Use when dating outbreak origins, estimating substitution rates, inferring R_e through time, building time-calibrated Nextstrain Augur trees, choosing between strict and relaxed clocks, fitting Birth-Death-Skyline models, diagnosing temporal-signal failure, running MASCOT for structured-population analyses, or using UShER for pandemic-scale placement.

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

Annotates ChIP-seq peaks to genomic features, nearest genes, ENCODE candidate cis-regulatory elements (cCREs), and regulatory domains. Uses ChIPseeker (R), HOMER annotatePeaks.pl (CLI), pyranges (Python), GREAT/rGREAT (regulatory domain gene-set enrichment), ChIP-Enrich (locus-length-adjusted), ENCODE SCREEN cCRE classification (PLS/pELS/dELS/CA-CTCF/CA-H3K4me3), and ENCODE-rE2G for cell-type-specific enhancer-gene linking. Handles nearest-TSS vs host-gene ambiguity, promoter window definition, and feature priority. Use when assigning genomic context to peaks, linking enhancer peaks to target genes, classifying peaks against ENCODE cCRE registry, or running gene-set enrichment on peak-associated genes.

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

Derive an execution roadmap from a project's vision/spec docs by first principles, then diff that fresh derivation against the existing roadmap to prove the task ORDER is correct. Use this whenever the user wants to review, validate, re-derive, or sanity-check an execution roadmap or delivery plan; asks whether the tasks/epics are "in the right order"; suspects a task is scheduled before its prerequisite (a producer-after-consumer / dependency-inversion error like "OpenAPI after the web client that consumes it", OR a cross-cutting inherited default like observability/auth/tenancy scheduled after the feature work that inherits it — a seam-after-consumer error); wants to find missing tasks, circular dependencies, or over-fragmented epics; or wants to compact a plan to raise velocity. Also trigger on "review the roadmap", "re-derive the plan from the spec", "is this the right build order", "check the dependency graph of our epics", "which task should come first". It reads the vision + spec corpus, decomposes actors → use-cases → modules → epics → typed tasks, identifies cross-cutting inherited-default seams, builds a real dependency graph with hard + soft (seam) edges (deterministic helper), breaks cycles, topologically orders, compacts, and emits a derived roadmap PLUS a delta report against the current one — it never blindly overwrites a hand-crafted roadmap.

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

Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.

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

Generate beautiful, on-brand HTML artifacts — reports, diagrams, diff reviews, slide decks, plans, recaps, dashboards. Loads on creation intents ("create a plan", "make me an implementation plan", "generate a diagram", "build a slide deck", "draft a recap", "visualize this", "render this as HTML", "make me a status update") and exploration intents ("show me three layouts", "explore document shapes", "compare visual treatments", "explore a new design system", "compare replacement brand directions") and iteration intents ("make this beautiful", "polish this report", "make this less generic", "design this", "theme this", "use my brand", "iterate on this design", "review this artifact", "make this bolder", "make this quieter", "simplify this design", "animate this", "improve the look of", "give this a refresh"). Captures brand from the user's codebase, asking, or live site, then applies it to every artifact.

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

At the end of a long working session, produce a counterfactual trace note — a backward walk through the session that identifies the small number of load-bearing moments (observations, failures, accidents, decisions) without which the final outcome would not exist. Use this whenever the user asks to "close the session", "run the butterfly", "trace back", "what actually mattered here", asks for a session retrospective, or asks how the session arrived at its result. Also use it when a session ends with a significant outcome (a fix, a design decision, a shipped artifact) and the user wants a note capturing why it happened, not just what happened. Do NOT use for simple summaries of short sessions — this skill is for causal tracing, and it only earns its cost when the session was long enough to contain real forks.

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

Professional project management skill aligned with PMBOK® 6th/7th Edition standards. Use this skill when you need to define requirements (ISO/IEC/IEEE 29148), review project plans, generate progress reports with Earned Value Management (EVM), conduct risk analysis, estimate costs, or provide project health assessments. Ideal for creating comprehensive project documentation, analyzing project performance metrics (SPI, CPI, EAC), managing risks across 14 categories, and ensuring stakeholder alignment. Triggers: "create project plan", "analyze project health", "calculate EVM", "risk assessment", "requirements definition", "progress report", "cost estimation", or requests involving PMBOK knowledge areas.

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

Professional business analysis skill aligned with BABOK® Guide v3 standards. Use this skill when you need to elicit and document requirements, analyze business processes, conduct stakeholder analysis, develop business cases, perform gap analysis, or create business requirements documents (BRD). Ideal for requirements gathering, process mapping (BPMN), financial analysis (ROI, NPV), stakeholder engagement, and solution evaluation. Triggers: "gather requirements", "create business case", "analyze process", "stakeholder analysis", "gap analysis", "BRD", "functional requirements", or requests involving business analysis tasks.

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