1,041 件 ・ 関連度順
概要と使いどころ
Switch the current Cursor workspace to a different project directory using the cursor-app-control MCP. Use when the user asks to switch projects, open another repo, jump to a different codebase, or move to a worktree.
日本語の概要は準備中です。原文の説明を表示しています。
Copy a feature flag from one PostHog project to one or more target projects in the same organization. Use when the user wants to duplicate a flag, promote a flag from staging to production, sync flags across projects, or replicate a flag configuration in a different workspace. Covers cohort remapping, scheduled-change handling, encrypted payloads, and the safe defaults (disabled in target, no scheduled changes).
日本語の概要は準備中です。原文の説明を表示しています。
Plan and execute reproducible computational research with explicit inputs, environments, provenance, deterministic steps, validation, and workspace outputs. Use for analyses that must be rerun, audited, or handed to another researcher.
日本語の概要は準備中です。原文の説明を表示しています。
Package agent-generated scientific code, figures, tables, data, logs, and conclusions into a navigable workspace result with stable paths and a concise manifest. Use near the end of computational tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Defines cell populations in flow and spectral cytometry through manual gates (rectangle, polygon, quadrant, boolean) and reproducible automated gating (openCyto gating templates, flowDensity data-driven thresholds, flowClust model-based gates), organized as a hierarchical GatingSet (flowWorkspace) and round-tripped with FlowJo via CytoML. Covers the canonical gate order (time -> debris -> singlets -> live -> lineage), FMO-vs-isotype boundary setting, gate-order dependence and recompute semantics, rare-event/MRD gating, and per-population statistics. Use when building a gating strategy, automating a manual FlowJo scheme across samples, choosing manual vs data-driven gates, or extracting population frequencies.
日本語の概要は準備中です。原文の説明を表示しています。
Read this before the first Google Drive, Docs, Sheets or Slides connector call whenever the task creates or changes a Google file. Use this skill whenever the user wants to create or change a Google Doc, Sheet or Slides file in their Google Drive. Triggers include: a request that names Google Docs, Sheets, Slides or Drive and asks to make, edit, format, copy or rename a file; a docs.google.com link with a request to change that file, even a one-line fix or suggested edits; and any follow-up change to a Google file from earlier in the chat, even "change it" or "add a tab". Includes helper scripts for document positions, cell ranges and slide layout. However, if the user asks for a doc, deck or spreadsheet without naming Google, or gives a Google file only as source material for something new, use Claude's own output type instead. Do NOT use for read-only questions about a Google file, or for Word, Excel, PowerPoint or PDF files.
日本語の概要は準備中です。原文の説明を表示しています。
Automate Bitbucket repositories, pull requests, branches, issues, and workspace management via Rube MCP (Composio). Always search tools first for current schemas.
日本語の概要は準備中です。原文の説明を表示しています。
Azure Monitor Ingestion SDK for Python. Use for sending custom logs to Log Analytics workspace via Logs Ingestion API.
日本語の概要は準備中です。原文の説明を表示しています。
Azure Monitor Query SDK for Python. Use for querying Log Analytics workspaces and Azure Monitor metrics.
日本語の概要は準備中です。原文の説明を表示しています。
Azure Monitor Query SDK for Java. Execute Kusto queries against Log Analytics workspaces and query metrics from Azure resources.
日本語の概要は準備中です。原文の説明を表示しています。
Azure Machine Learning SDK v2 for Python. Use for ML workspaces, jobs, models, datasets, compute, and pipelines.
日本語の概要は準備中です。原文の説明を表示しています。
Automate Asana tasks via Rube MCP (Composio): tasks, projects, sections, teams, workspaces. Always search tools first for current schemas.
日本語の概要は準備中です。原文の説明を表示しています。
Query PostgreSQL with pg and navigate Openrind Shell's primary FUSE or compatibility workspace; /db is custom-agent-only.
日本語の概要は準備中です。原文の説明を表示しています。
Independent, traceable code review of one SDD Composy task in review_required against its approved PRD, stories, TechSpec, evidence, and project rules, with stable findings and severities. Use when a task passed QA and evidence — 'revisar a TASK-003', 'code review da task', 'review this task's diff'. Do NOT use for code review outside an SDD workspace (use the host code review), for QA (sdd-qa), or for verification (sdd-verify).
日本語の概要は準備中です。原文の説明を表示しています。
Read-only consolidated snapshot of an SDD Composy workspace: lifecycle stage, task contracts, trace integrity, loops, fleets, and the next action, without changing any file. Use for 'em que pé está o SDD', 'status do fluxo', 'qual a próxima ação', 'where are we in the workflow'. Do NOT use for git, CI, infrastructure, or other plugins' status, or to change state.
日本語の概要は準備中です。原文の説明を表示しています。
Deliver a small bounded change inside an initialized SDD Composy workspace through the quick path: at most five implementation files, a registered TASK, TDD, evidence, trace, and a verified verdict, escalating otherwise. Use for a precise objective with no existing task — 'ajuste rápido via SDD', 'quick fix under SDD', 'small change to X in the SDD flow'. Do NOT use for an already registered task (sdd-execute), for architecture, migrations, or destructive work, or in repositories without SDD Composy (other plugins' quick).
日本語の概要は準備中です。原文の説明を表示しています。
Produce a deterministic, read-only evidence map of the repository for SDD Composy (languages, manifests, commands, modules, boundaries, staleness) and publish the context bundle only on request. Use before a PRD or TechSpec, or when the map is stale — 'mapear o repositório', 'atualizar o contexto do código', 'what does this codebase look like for SDD'. Do NOT use for architecture decisions, code review, or repository exploration without an SDD workspace.
日本語の概要は準備中です。原文の説明を表示しています。
Create or revise the problem-first SDD Composy PRD (tasks/prd-SLUG/prd.md) with stable RF/CA identifiers, stopping at the human approval gate. Use when a user problem needs a product contract — 'criar o PRD', 'documento de requisitos', 'revisar o PRD do slug X', 'write the requirements for…'. Do NOT use for user stories (sdd-stories), technical design (sdd-techspec), or PRDs outside an initialized SDD workspace.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants to set up pwdev-prd in a project — 'inicializar o pwdev-prd', 'init prd', 'configurar PRDs' — creating the .planning/prds/ workspace and choosing language and the optional SQLite audit trail. Do NOT use to write a PRD (prd-create).
日本語の概要は準備中です。原文の説明を表示しています。
Use when starting feature work that needs isolation from the current workspace, or before executing an implementation plan
日本語の概要は準備中です。原文の説明を表示しています。
Inventory, archive, and summarize PWDEV Flow project history safely. Use when the user asks to find stale artifacts, archive completed work, clean the Flow workspace without deletion, or generate a changelog from verified history.
日本語の概要は準備中です。原文の説明を表示しています。
Diagnose repository and PWDEV Flow health without changing the project. Use when the user asks for a health check, workspace consistency check, dependency assessment, readiness report, or evidence-based scorecard.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a repository has no PWDEV Power workspace yet, when resuming one, when the codebase map needs refreshing, or when the setup should be checked
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants the project instructions file generated or updated from the detected stack and conventions — 'gerar o arquivo de instruções do projeto', 'criar convenções do projeto', 'setup governance', 'gerar AGENTS'. Writes the shared instructions file read by Claude Code, Codex, Hermes and OpenCode. Do NOT use to analyze the codebase in depth (feat-map) or to initialize the workspace (feat-init).
日本語の概要は準備中です。原文の説明を表示しています。