2,563 件 ・ 関連度順
概要と使いどころ
Design, audit, and strengthen experimental validation for IEEE manuscripts using routed claim-evidence checks. Use when planning experiments, selecting baselines, designing ablations, choosing metrics, checking fairness, adding robustness tests, explaining results, analyzing complexity, building claim-to-evidence matrices, or responding to reviewer concerns about insufficient experiments.
日本語の概要は準備中です。原文の説明を表示しています。
Update an OpenSpec change by revising its existing planning artifacts and keeping them coherent with one another. Use when the user wants to revise a change's plan, fold new decisions into it, or reconcile its artifacts after an edit. Never edits code.
日本語の概要は準備中です。原文の説明を表示しています。
Calculate code occupant loads by area with gross/net factors and jurisdiction checks. Use for "how many people can this space hold," IBC Table 1004.5, egress inputs, or occupancy-load reports; not for workplace headcount planning.
日本語の概要は準備中です。原文の説明を表示しています。
Cell type annotation strategy for scRNA-seq: name clusters manually from canonical markers, transfer labels from a reference (CellTypist, popV), or do both and validate one against the other. Covers matching tissue and developmental stage, marker evidence, annotation confidence, doublets, unresolved clusters. Use when planning or troubleshooting how to annotate cells.
日本語の概要は準備中です。原文の説明を表示しています。
Systematic strategies for searching scientific literature across PubMed, arXiv, Google Scholar, and AI-assisted tools. Covers PICO framework for clinical questions, three-tiered search (database-specific, AI-assisted, content extraction), PubMed field tags and MeSH, boolean query construction, and full-text extraction. Use when planning a literature search or choosing a search tier.
日本語の概要は準備中です。原文の説明を表示しています。
Conducting systematic, scoping, and narrative literature reviews. Covers PRISMA/PRISMA-ScR protocols, search strategy (Boolean, MeSH), database selection (PubMed, Scopus, Web of Science, Embase), screening, data extraction, evidence synthesis (narrative, meta-analysis, thematic), and reporting. Use when planning or executing a formal literature review.
日本語の概要は準備中です。原文の説明を表示しています。
Foundational software design principles applied specifically to robotics module development. Use this skill when designing robot software modules, structuring codebases, making architecture decisions, reviewing robotics code, or building reusable robotics libraries. Trigger whenever the user mentions SOLID principles for robots, modular robotics software, clean architecture for robots, dependency injection in robotics, interface design for hardware, real-time design constraints, error handling strategies for robots, configuration management, separation of concerns in perception-planning- control, composability of robot behaviors, or any discussion of software craftsmanship in a robotics context. Also trigger for code reviews of robotics code, refactoring robot software, or designing APIs for robotics libraries.
日本語の概要は準備中です。原文の説明を表示しています。
Architecture patterns, design principles, and proven recipes for building robust robotics software. Use this skill when designing robot software architectures, choosing between behavioral frameworks, structuring perception-planning-control pipelines, implementing state machines, designing safety systems, or architecting multi-robot systems. Trigger whenever the user mentions behavior trees, finite state machines, subsumption architecture, sensor fusion, robot safety, watchdogs, heartbeats, graceful degradation, hardware abstraction layers, real-time constraints, or software architecture for robots. Also applies to sim-to-real transfer, digital twins, and robot fleet management.
日本語の概要は準備中です。原文の説明を表示しています。
Testing strategies, patterns, and tools for robotics software. Use this skill when writing unit tests, integration tests, simulation tests, or hardware-in-the-loop tests for robot systems. Trigger whenever the user mentions testing ROS nodes, pytest with ROS, launch_testing, simulation testing, CI/CD for robotics, test fixtures for sensors, mock hardware, deterministic replay, regression testing for robot behaviors, or validating perception/planning/control pipelines. Also covers property-based testing for kinematics, fuzz testing for message handlers, and golden-file testing for trajectories.
日本語の概要は準備中です。原文の説明を表示しています。
Use when planning a new article. The agent Googles the keyword, reads the top 10 results, classifies intent, maps the content gap, and produces a writer-ready brief with structure, outline, and on-page artifacts. No keyword tool required.
日本語の概要は準備中です。原文の説明を表示しています。
Use when planning to rank for a specific keyword. The agent Googles it, reads the top 10, classifies intent, reads the top 3 competitor pages, and produces a 90-day ranking plan with intent, SERP analysis, and content recommendations.
日本語の概要は準備中です。原文の説明を表示しています。
Use when planning link acquisition. Classifies the site's authority phase from site age and visible signals, then recommends phase-appropriate tactics from the bundled tactic playbook library. No backlink tool required.
日本語の概要は準備中です。原文の説明を表示しています。
When the user needs to organize product initiatives into a prioritized, time-sequenced plan with outcomes and dependencies.
日本語の概要は準備中です。原文の説明を表示しています。
When a founder needs demo scripts, discovery call frameworks, objection handling, RFP/RFI responses, competitive feature matrices, POC planning, or closing playbooks. Activate for sales calls, demo prep, talk tracks, bid responses, competitor comparisons, or pre-sales engineering.
日本語の概要は準備中です。原文の説明を表示しています。
Interview the user one question at a time to resolve remaining ambiguity before implementation. Use when planning or brainstorming is done but unknowns remain, or when the user asks to be interviewed about a task or spec.
日本語の概要は準備中です。原文の説明を表示しています。
Write an implementation plan that leads with the decisions the user is most likely to change, and buries the mechanical work at the bottom. Use when planning is requested before a build, especially after brainstorming or an interview.
日本語の概要は準備中です。原文の説明を表示しています。
Profile construction data to understand characteristics, distributions, quality metrics, and patterns. Essential for data quality assessment and ETL planning.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze weather data impact on construction schedules. Predict weather delays, optimize work scheduling based on forecasts, and calculate weather-related risk factors for project planning.
日本語の概要は準備中です。原文の説明を表示しています。
Account assignment by revenue potential, geography, relationship. Workload balancing, TAM/SAM calculation, coverage models.
日本語の概要は準備中です。原文の説明を表示しています。
複雑なタスクをファイルベースで計画管理するスキル。task_plan.md、findings.md、progress.mdを作成。 「計画を立てて」「タスクを整理して」「プランニング」等のリクエストで発動。
Generate QA Contract with numbered Gherkin scenarios (G#N) and acceptance criteria (AC#N)
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrates Spec Driven Development by coordinating spec, plan, and task skills. Use when running the full speckit workflow from spec to implementation.
日本語の概要は準備中です。原文の説明を表示しています。
Creates clear, testable specifications from feature descriptions with user stories. Use when starting a new feature and needing a spec before planning.
日本語の概要は準備中です。原文の説明を表示しています。
Initializes a stacked branch set from an ordered plan, one branch per slice with parent-child links. Use when a plan has 2+ sequentially dependent changes.
日本語の概要は準備中です。原文の説明を表示しています。