738건 · 관련도순
Orchestrates a systematic review and meta-analysis workflow following PRISMA 2020 guidelines, from protocol development through multi-database search, screening, data extraction, and evidence synthesis. Use when conducting evidence-based reviews, meta-analyses, or scoping revi...
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Builds professional search strategies for PubMed, Embase, Web of Science, and similar databases. Use when a user needs to construct a MeSH-based Boolean query, design a systematic review search, expand a concept with synonyms, apply study-type or date filters, or adapt a query across multiple databases. Also triggers when the user says "help me search for papers on X", "build a search strategy", "what are the MeSH terms for", or "I need a systematic review search string".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when evaluating Ed Seykota-style systematic trend following: mechanical rules, long-term trend capture, small losses, position sizing, whipsaw tolerance, and emotional discipline.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Performs systematic root cause analysis to identify the true source of bugs, errors, and unexpected behavior through structured investigation phases — not just treating symptoms. Use when a user reports a bug, crash, error, or broken behavior and needs to debug, troubleshoot, or investigate why something is not working; especially for complex or intermittent issues across multiple components. Applies the Five Whys method, hypothesis-driven testing, stack trace analysis, git blame/log evidence gathering, and causal chain documentation to isolate and confirm root causes before applying any fix.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Systematic strategic planning framework for philosophy and interdisciplinary academic papers targeting preprint platforms (PhilArchive, arXiv, PhilSci-Archive). Use when users want to: (1) plan a paper on a specific topic, (2) identify research gaps and assess originality, (3) develop optimized paper outlines, (4) prepare for preprint submission, or (5) understand platform requirements and writing standards. Triggered by phrases like 'plan a paper on,' 'help me design a paper about,' 'identify research gaps in,' 'is this idea original,' or when users need structured research planning. The skill guides through three phases: Platform Analysis (identifying target venue and studying sample papers), Theoretical Framework (AI-driven literature search and gap identification), and Outline Optimization (structured design with reviewer-perspective self-assessment). Each phase includes quality evaluation standards and validation checkpoints. Output: optimized detailed outline ready for systematic writing (use with academic-paper-composer skill).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Systematic writing framework for philosophy and interdisciplinary academic papers from optimized outline to submission-ready manuscript. Use when users want to: (1) write a paper from a detailed outline, (2) ensure quality control during writing, (3) maintain consistency across chapters, (4) prepare a submission-ready manuscript, or (5) systematically execute a planned paper. Triggered by phrases like 'write the paper from this outline,' 'compose the full manuscript,' 'execute the outline,' or when users have completed strategic planning (academic-paper-strategist skill) and are ready to write. Takes optimized outline as input; outputs complete manuscript with iterative quality checks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when systematically gathering, coding, and synthesizing a management/organization literature for an Academy of Management Annals (Annals) review — the search-and-coverage methodology and the choice of narrative vs. systematic vs. bibliometric integration. Builds the corpus and synthesis notes; it does not impose the organizing spine (amann-organizing-framework) or write prose.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Systematic approach to diagnosing and fixing errors
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run a comprehensive WCAG accessibility audit covering perceivable, operable, understandable, and robust principles. Use this skill whenever the user wants to audit accessibility, review WCAG compliance, fix accessibility issues, prepare for accessibility certification, address an accessibility lawsuit risk, or systematically improve a site's accessibility. Triggers on accessibility audit, WCAG audit, a11y audit, accessibility compliance, ADA compliance, screen reader test, keyboard navigation, accessibility report, fix accessibility, axe scan. Also triggers when accessibility issues have been reported and need systematic remediation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Systematically QA test a web application with browser-based bug fixing. Four modes: diff-aware (automatic on feature branches), full (systematic exploration), quick (30-second smoke test), regression (compare against baseline). Atomic bug-fix workflow with regression testing. Health scoring across 8 categories.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert guidance for systematic backtesting of trading strategies. Use when developing, testing, stress-testing, or validating quantitative trading strategies. Covers "beating ideas to death" methodology, parameter robustness testing, slippage modeling, bias prevention, and interpreting backtest results. Applicable when user asks about backtesting, strategy validation, robustness testing, avoiding overfitting, or systematic trading development.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Systematic literature review across multiple arXiv papers.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Agent Performance Optimization Workflow workflow skill. Use this skill when the user needs Systematic improvement of existing agents through performance analysis, prompt engineering, and continuous iteration and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Agent Performance Optimization Workflow workflow skill. Use this skill when the user needs Systematic improvement of existing agents through performance analysis, prompt engineering, and continuous iteration and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guides systematic root-cause debugging. Use when tests fail, builds break, something that worked yesterday broke, behavior doesn't match expectations, or you encounter any unexpected error. Use when you need to figure out what broke and why — a systematic approach to finding and fixing the root cause rather than guessing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Recognition and mitigation of systematic reasoning errors documented in the heuristics and biases tradition. Covers confirmation bias, availability, anchoring, representativeness, framing effects, hindsight bias, overconfidence, and motivated reasoning. Each bias is presented with its mechanism, diagnostic signal, and structured mitigation. Use when you suspect your own or another reasoner's conclusions may be shaped by systematic cognitive distortion rather than evidence.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Multi-step reasoning engine for complex analysis and systematic problem solving. Use when: (1) Complex debugging scenarios with multiple layers, (2) Architectural analysis and system design, (3) Problems requiring hypothesis testing and validation, (4) Multi-component failure investigation, (5) Performance bottleneck identification. Triggers: "--think", "--think-hard", "--ultrathink", "analyze step by step", "break down this problem", "systematic analysis". IMPORTANT: Do NOT use for simple single-step tasks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Field identification of minerals and ores using hardness, streak, luster, cleavage, crystal habit, and simple chemical tests. Covers the systematic elimination methodology, Mohs scale application, and common ore indicators for precious metals, gemstones, and industrial minerals. Use when encountering an unknown rock or mineral specimen, when prospecting and assessing whether a site shows valuable mineral indicators, when distinguishing ore-bearing rock from barren rock in the field, or when building geological literacy through systematic observation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Specialized research and analysis prompt methodology for Claude. Provides 11 tested approaches (3 identity, 4 reasoning, 4 output) for data analysis, policy research, systematic evidence review, investigative research, and research-specific deliverables. Use when building prompts for quantitative data interpretation, evidence-based policy recommendations, literature reviews, causal analysis, hypothesis-driven investigation, or briefing documents. Trigger on: "prompt for data analysis," "research prompt," "policy brief prompt," "literature review prompt," "prompt for investigating," "systematic review prompt," "build a prompt for evidence synthesis," "causal analysis prompt," "briefing document prompt." Also use when user describes a research or analytical task and needs a structured Claude prompt for it. Do NOT use for evaluating existing prompts (use rootnode-prompt-validation if available) or auditing Claude Projects (use rootnode-project-audit if available).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
This skill provides systematic bug detection and discovery capabilities for VS Code extensions. Use when searching for hidden bugs, analyzing code for potential issues, investigating suspicious behavior, performing code audits, or proactively finding bugs before they manifest. Covers static analysis patterns, dynamic analysis techniques, code smell detection, and systematic codebase investigation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Systematically QA test a web application. Use when asked to "qa", "QA", "test this site", "find bugs", "dogfood", or review quality. Four modes: diff-aware (automatic on feature branches — analyzes git diff, identifies affected pages, tests them), full (systematic exploration), quick (30-second smoke test), regression (compare against baseline). Produces structured report with health score, screenshots, and repro steps.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
4-phase systematic debugging methodology with root cause analysis and evidence-based verification. Use when debugging complex issues.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Systematic debugging methodology. Reproduce → Isolate → Hypothesize → Verify → Fix → Confirm.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guides systematic root-cause debugging. Use when tests fail, builds break, behavior doesn't match expectations, or you encounter any unexpected error. Use when you need a systematic approach to finding and fixing the root cause rather than guessing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.