1.8万 件 ・ 関連度順
概要と使いどころ
Use when the task touches a backend API, database or worker - booting it from the task branch, driving real requests and verifying side effects (DB rows, outbound calls, logs) as evidence
日本語の概要は準備中です。原文の説明を表示しています。
Use when opening an analiz task for the system-architect - the required fields, what the criteria may say, and what the description must hand over
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task changes any screen, form, dialog, menu or control - Lighthouse/axe scan of the changed screens, a keyboard walk, and the thresholds that fail a task
日本語の概要は準備中です。原文の説明を表示しています。
Use when you create an implementation board task directly - the required fields, one-role-one-deliverable rule, and dependency ordering
日本語の概要は準備中です。原文の説明を表示しています。
Use when the stakeholder asks for release notes or a changelog - group done/released work into Added, Changed, Deprecated, Removed, Fixed and Security, in outcome language, with task references
日本語の概要は準備中です。原文の説明を表示しています。
Use when a product decision or feature needs a written record - what to capture in a task document (PRD, decision record) and where to attach it, since TaskTrooper has no epic
日本語の概要は準備中です。原文の説明を表示しています。
How to work a production incident remediation task. Use when the task title starts with "Incident:" or its description carries an incident id and a suggest/auto_fix policy.
日本語の概要は準備中です。原文の説明を表示しています。
Use when starting a backend task that could be built in either language - decide Go vs Java (Quarkus/Spring) from the task's shape and the repository's existing stack
日本語の概要は準備中です。原文の説明を表示しています。
Root-cause debugging discipline. Use when a test, build or pipeline fails, behaviour does not match expectations, a bug task arrives, or a task comes back in need_revision — before proposing any fix.
日本語の概要は準備中です。原文の説明を表示しています。
The local task workspace, the build/test commands the hand-off gate runs, and the file and exploration tools. Use when starting work in a task workspace or before running any build, test or verification command.
日本語の概要は準備中です。原文の説明を表示しています。
How to work a task returned with review, QA or UAT findings. Use when a task is in need_revision or PR review comments are in your context.
日本語の概要は準備中です。原文の説明を表示しています。
Windows 11 system administration with PowerShell — system info reporting, hardware monitoring, package management (winget/scoop), disk cleanup, performance optimization, environment configuration, PowerShell profile setup with aliases and autocomplete, and Task Scheduler automation. Use when user asks to check system info, install tools on Windows, clean up disk space, set up PowerShell profile, or automate Windows tasks. Do NOT use for Linux administration, cross-platform scripting, or network infrastructure management.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill on every programming task — writing code, fixing bugs, refactoring, explaining code, running tools, or answering technical questions. Apply token-saving and quality-preserving practices throughout. Activate even when the user doesn't explicitly ask for efficiency — this skill is always relevant for software development work. Do not skip this skill for "simple" tasks; the rules apply at every scale.
日本語の概要は準備中です。原文の説明を表示しています。
Before coding, determine what to ask. Max 2 yes/no questions. Never ask technical questions.
日本語の概要は準備中です。原文の説明を表示しています。
Bug-fix routine that fixes the whole class of bug, not just the reported instance. Use for any bug report, failing production behaviour, monitoring alert, audit finding or review finding that does real harm (a smaller review finding goes on the item's list, as ship-check says), and whenever the same kind of bug has been seen before. Reproduces it with a failing test, names the failure class, searches the task's scope for the same pattern (the whole codebase when the user's own prompt asks for the fix, not when it is picked from a task's list), fixes or records every hit, and adds the rule, invariant, helper or check that stops it coming back.
日本語の概要は準備中です。原文の説明を表示しています。
A dated chronology of one topic across the user's recorded coding-agent sessions — the lessons the graph learned about it and the prompts that named it, oldest first. Use only when the user explicitly asks for the history or timeline of a topic across their sessions ("how did X evolve", "when did we first discuss X") or asks for the `cognee-timeline` skill by name. Not for questions about code or the current task.
日本語の概要は準備中です。原文の説明を表示しています。
A multi-day digest of the user's own coding-agent sessions — sessions per day and project, most-edited files, and every lesson Cognee distilled into the knowledge graph in that window. Use only when the user explicitly asks for a weekly digest, a retro, a recap or report of their recent sessions, or asks for the `cognee-digest` skill by name. Not for questions about code or the current task.
日本語の概要は準備中です。原文の説明を表示しています。
A standup or status update built from the coding-agent sessions Cognee recorded — prompts, tool calls, edited files, what was left open — per project. Use only when the user explicitly asks for a standup, a status update, a catch-up on their own recent sessions ("what did I work on yesterday / this week"), or asks for the `cognee-standup` skill by name. Not for questions about code, files or the current task.
日本語の概要は準備中です。原文の説明を表示しています。
Ask the AgentDB bandit which RL algorithm / skill / pattern fits the current task best. Use at task start when there are multiple plausible approaches and you want the data-driven pick.
日本語の概要は準備中です。原文の説明を表示しています。
Retrieve relevant memories for the current task from AgentDB. Use at the start of a task to load prior knowledge, when stuck to surface what worked before, or when the user asks "what do we know about X" / "have we done this before?"
日本語の概要は準備中です。原文の説明を表示しています。
Generate product descriptions and other text asynchronously, or query an existing text-generation task by taskId. Use this skill for ecommerce copywriting, text/image/video-assisted content generation, task creation, status polling, and result retrieval.
日本語の概要は準備中です。原文の説明を表示しています。
Diagnose motivation problems in a task using self-determination theory and redesign for autonomy, competence, and relatedness. Use when students are disengaged, resistant, or going through the motions.
日本語の概要は準備中です。原文の説明を表示しています。
Design discipline-specific critical thinking tasks grounded in knowledge-contingent reasoning rather than generic skills. Use when embedding higher-order thinking into subject content.
日本語の概要は準備中です。原文の説明を表示しています。
Analyse a learning task for cognitive load problems and recommend specific design improvements. Use when tasks overwhelm students, instructions feel complex, or materials need simplifying.
日本語の概要は準備中です。原文の説明を表示しています。