728 件 ・ 関連度順
概要と使いどころ
Systematically evaluate scholarly work using the ScholarEval framework, providing structured assessment across research quality dimensions including problem formulation, methodology, analysis, and writing with quantitative scoring and actionable feedback.
日本語の概要は準備中です。原文の説明を表示しています。
Legacy error-resolution reference archive retained for migration. Do not route user tasks here; use systematic-debugging for active bug, stack-trace, and root-cause work.
日本語の概要は準備中です。原文の説明を表示しています。
Systematic debugging with persistent state across context resets
日本語の概要は準備中です。原文の説明を表示しています。
Troubleshoot Golang programs systematically - find and fix the root cause. Use when encountering bugs, crashes, deadlocks, races, or unexpected behavior in Go code. Covers debugging methodology, common Go pitfalls, test-driven debugging, pprof setup and capture, Delve, race detection, GODEBUG tracing, and production debugging. Start here for any 'something is wrong' situation. Not for interpreting profiles or benchmarking (→ See `samber/cc-skills-golang@golang-benchmark` skill), applying optimization patterns (→ See `samber/cc-skills-golang@golang-performance` skill), or designing new code (→ See `samber/cc-skills-golang@golang-safety` skill for defensive coding, `samber/cc-skills-golang@golang-concurrency` skill for concurrency design).
日本語の概要は準備中です。原文の説明を表示しています。
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
日本語の概要は準備中です。原文の説明を表示しています。
Batch effect correction for CRISPR screens. Covers normalization across batches, technical replicate handling, and batch-aware analysis. Use when combining screens from multiple batches or correcting systematic technical variation.
日本語の概要は準備中です。原文の説明を表示しています。
当用户明确要求"做系统综述/文献综述/related work/相关工作/文献调研"，或为研究想法核对强近邻与新颖性时使用；兼容旧名 systematic-literature-review。标准模式执行查询、检索、评分、相关性选文、写作、引用校验与 PDF/Word 导出，novelty-check 模式只交付强近邻、反方证据和未确认项。查询缺失或无效时默认停止，不静默降级为单查询。支持 en/zh/ja/de/fr/es。
日本語の概要は準備中です。原文の説明を表示しています。
当用户明确要求"核查/优化综述 `{主题}_review.tex` 的正文引用"、"运行 research-citation-check"，或要求使用旧名 check-review-alignment skill 时使用。通过宿主 AI 的语义理解逐条核查引用是否与文献内容吻合，只在发现致命性引用错误时对"包含引用的句子"做最小化改写，并优先复用 `research-literature-review` 的渲染脚本输出 PDF/Word，过渡期允许 fallback 到旧名 systematic-literature-review。核心原则：不为了改而改，无法确定是否为致命性错误时保留原样并在报告中警告。⚠️ 不适用：用户只是想生成系统综述正文（应使用 research-literature-review）；用户只是想新增/核对 BibTeX 条目（应使用专门的 bib 管理流程）。
日本語の概要は準備中です。原文の説明を表示しています。
Debugs AWS Lambda function timeout failures by systematically analyzing function configuration, CloudWatch logs and metrics, VPC/networking, cold starts, memory constraints, and downstream dependencies to identify root causes with actionable fixes. Use when a Lambda function is timing out or approaching its timeout limit.
日本語の概要は準備中です。原文の説明を表示しています。
Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to "dogfood", "QA", "exploratory test", "find issues", "bug hunt", "test this app/site/platform", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.
日本語の概要は準備中です。原文の説明を表示しています。
Implement the Entrepreneurial Operating System (EOS) to align vision and execution across a company. Use when the user mentions "EOS", "Entrepreneurial Operating System", "V/TO", "quarterly rocks", "Level 10 meetings", "accountability chart", "IDS process", "my company feels chaotic", "we keep having the same problems", or "get the whole team aligned". Also trigger when a growing company needs meeting structure, goal-setting frameworks, or a systematic way to solve recurring organizational issues. Covers the six EOS components: Vision, People, Data, Issues, Process, Traction. For team motivation design, see drive-motivation. For lean experimentation, see lean-startup.
日本語の概要は準備中です。原文の説明を表示しています。
Systematically trace bugs backward through call stack to find original trigger
日本語の概要は準備中です。原文の説明を表示しています。
Four-phase debugging framework that ensures root cause investigation before attempting fixes. Never jump to solutions.
日本語の概要は準備中です。原文の説明を表示しています。
Use when complex problems require systematic step-by-step reasoning with ability to revise thoughts, branch into alternative approaches, or dynamically adjust scope. Ideal for multi-stage analysis, design planning, problem decomposition, or tasks with initially unclear scope.
日本語の概要は準備中です。原文の説明を表示しています。
Systematic debugging frameworks for finding and fixing bugs - includes root cause analysis, defense-in-depth validation, and verification protocols
日本語の概要は準備中です。原文の説明を表示しています。
Finds the root cause of a bug, test failure, or unexpected behavior before proposing any fix. Use this whenever something is broken and the cause is not yet proven — a failing test, a production error, intermittent behavior, or a symptom that appeared after a change. Also use when a fix has been attempted and did not work, or when the same bug keeps coming back.
日本語の概要は準備中です。原文の説明を表示しています。
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
日本語の概要は準備中です。原文の説明を表示しています。
Screens research papers based on title/abstract and inclusion criteria, providing a structured Yes/No/Maybe decision. Use when you need to filter literature for meta-analysis or systematic reviews.
日本語の概要は準備中です。原文の説明を表示しています。
Generates scientifically sound inclusion and exclusion criteria for Meta-Analysis based on a given title or keywords. Use when user wants to design eligibility criteria for a systematic review or meta-analysis.
日本語の概要は準備中です。原文の説明を表示しています。
Write comprehensive literature reviews for medical imaging AI research. Use when writing survey papers, systematic reviews, or literature analyses on topics like segmentation, detection, classification in CT, MRI, X-ray, ultrasound, or pathology imaging. Triggers on requests f...
日本語の概要は準備中です。原文の説明を表示しています。
Conduct comprehensive, systematic literature reviews using multiple academic databases (PubMed, arXiv, bioRxiv, Semantic Scholar, etc.). Creates professionally formatted markdown documents and PDFs with verified citations in multiple citation styles.
日本語の概要は準備中です。原文の説明を表示しています。
Systematically maps mechanism evidence for a disease from molecules to pathways, cell types, tissues, biological consequences, and clinical phenotypes. Always use this skill when a user needs a layered mechanism evidence chain rather than a flat summary or immediate gap analysis. Formal literature citations must be real and verifiable.
日本語の概要は準備中です。原文の説明を表示しています。
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes. Requires root cause investigation first.
日本語の概要は準備中です。原文の説明を表示しています。
Systematic codebase exploration following the Iron Law - understand the problem before exploring code. Four phases with file-finder and web-researcher agents.
日本語の概要は準備中です。原文の説明を表示しています。