majiayu000/claude-skill-registry - Page 50

deep-research-api-landscape

Use when building automated research systems. Official Deep Research APIs (OpenAI, Gemini, Perplexity) over browser automation.

Source text: Japanese

deep-research

Use when researching complex topics, evaluating technologies, investigating domains, or answering multi-faceted questions requiring web research. Triggers: "research X", "investigate Y", "evaluate options for Z", "what are the best approaches to", "help me…

deep-research

Pesquisa aprofundada com metodologia estruturada

Source text: Portuguese

deep-research

Orchestrates two-round parallel agent research with Exa orientation, breadth-first discovery, and depth-focused synthesis. Use when conducting comprehensive research, exploring complex topics requiring multi-source validation, or synthesizing findings from…

deep-research

[Research] Deep-dive into top sources from web-research. Extract key findings, cross-validate claims, build evidence base.

deep-research

Run deep research on any topic using parallel AI agents

deep-research

**深度网络研究**。不仅搜索链接，还会自动访问结果页面，阅读正文，并生成深度整合的综合报告。

Source text: Chinese

deep-research

Deep research via Gemini CLI OR free search APIs — runs in background sub-agent to save Claude tokens.

deep-research

Orchestrated multi-source research with parallel agent fan-out. Use for thorough investigation of complex topics requiring diverse sources, cross-referencing, and synthesis. Decomposes topics into subtopics, delegates to specialized research agents, and…

deep-research

Run OpenAI deep research to analyze and synthesize web sources into a comprehensive report. Invoked with a research query as argument.

deep-search

다중 전략 코드베이스 심층 탐색 워크플로우. Grep, SemanticSearch, Glob를 병렬로 실행하여 심볼, 패턴, 의존성을 종합적으로 분석. Use when performing deep codebase analysis or when searching for complex code patterns and dependencies.

Source text: Korean

text-analyzer

Advanced text analysis and summarization skill for Claude

demographics-analysis

Demographics and market site analysis — population, income, age, housing market, and employment data from an address.

dr-departments

Analyze P&L and performance by department. Creates departmental reports and comparative analysis with Excel and PowerPoint outputs.

dependency-analysis

依存関係の可視化、循環依存検出、安定度評価を体系化するスキル。 アーキテクチャの健全性を測定し、改善優先度を整理する。 Anchors: • Clean Architecture / 適用: 安定依存の原則 / 目的: 依存方向の評価 • Refactoring / 適用: 依存解消パターン / 目的: 循環依存の改善 • Graph Algorithms / 適用: 強連結成分 / 目的: 循環依存の検出 Trigger: Use when analyzing module dependencies,…

Source text: Japanese

dependency-graph

Generates a Mermaid dependency graph showing import relationships between modules. Use when analyzing coupling, finding circular deps, or planning refactors.

design-decision-framework

多方案評估決策框架. Use for: (1) 面臨 3+ 技術方案時的結構化評估, (2) 架構決策時的系統化分析, (3) 防止衝動決策和技術債務累積

Source text: Chinese

design-solution

Converge on a single recommended solution after brainstorming options. Use when you have multiple candidate approaches and need to analyze trade-offs, select one, and define decision criteria before planning.

design-solution

Converge on a single recommended solution after brainstorming options. Use when you have multiple candidate approaches and need to analyze trade-offs, select one, and define decision criteria before planning.

detect-competing-systems

Comprehensive detection of competing and conflicting systems in Vue 3 + TypeScript + Pinia projects. Identifies duplicate implementations, architectural conflicts, and competing logic patterns before they cause technical debt.

detect-metric-anomaly

Analyze a metric for statistical anomalies using z-score analysis and threshold checking. Detects spikes, drops, and trends. Use for proactive monitoring and early warning. Keywords: anomaly, detection, metric, z-score, threshold, alert, statistical.

detect-recurrence-pattern

Detect recurring patterns in issues and events. Identifies temporal, resource-based, cluster, and cascading patterns. Suggests prevention strategies. Keywords: recurrence, pattern, detection, trending, recurring, prevention, issue, analysis.

detect-trends

Detect trending topics across multiple articles by analyzing entity co-occurrence and cross-source mentions. Uses memory search to find recent articles and LLM analysis to identify emerging trends.

detecting-data-anomalies

Investigate outliers, rare events, spikes, and suspicious records in datasets. Use as an explicit anomaly-analysis helper when you want concrete anomaly-detection workflow guidance, not generic data validation or end-to-end ML ownership.

detecting-drift

Show what changed since last validation for a specific artifact. Computes confidence without writing to frontmatter.

dev-buddy-rca

Root cause analysis for bugs. Dispatches RCA executors in parallel, consolidates findings, and appends RCA Diagnosis to the plan file.

dev-explore

This skill should be used when the user asks to 'explore the codebase', 'map architecture', 'find similar features', or in Phase 2 of /dev workflow.

dev-explore

REQUIRED Phase 2 of /dev workflow after dev-brainstorm. This skill should be used when the user asks to 'explore the codebase', 'map architecture', 'find similar features', 'discover test infrastructure', 'trace execution paths', 'identify code patterns', or…

dev-swarm-market-research

Conduct comprehensive market research and competitive analysis to validate the problem and understand the market landscape. Use when user asks to conduct market research, validate market, analyze competitors, or start Stage 1 after init-ideas.

devcom

Invoke DEVCOM_RESEARCH for deep research, cross-disciplinary analysis, and novel problem solving. Use when exploring cutting-edge concepts or investigating patterns that require theoretical foundation.

devdocs-insights

Collect improvement insights from UI/UX reviews, document research, or external references, convert confirmed items into development requirements. Use when users have optimization suggestions, research findings, or want to improve based on external…

Source text: Chinese

developer-detective

⚡ PRIMARY TOOL for: 'how does X work', 'find implementation of', 'trace data flow', 'where is X defined', 'audit integrations', 'find all usages'. Uses claudemem v0.3.0 AST with callers/callees analysis. GREP/FIND/GLOB ARE FORBIDDEN.

device-inspection

Execute comprehensive L1-L4 network device inspection. Use when user asks to "inspect all devices", "run comprehensive health check", "full network audit", or needs systematic L1-L4 analysis across multiple devices.

devil-advocate

Constructive critic and stress-tester for ideas and proposals. Use when the user needs someone to challenge their thinking, find weaknesses, anticipate objections, or strengthen an argument. Triggers include "challenge", "critique", "push back", "poke holes",…

devils-advocate

Use before design phase to challenge assumptions and surface risks

devils-advocate

Use when challenging assumptions, surfacing risks, or stress-testing designs and decisions. Triggers: 'challenge this', 'play devil's advocate', 'what could go wrong', 'poke holes', 'find the flaws', 'what am I missing', 'is this solid', 'red team this',…

devils-advocate

Use when substantive documents (reviews, analyses, synthesis documents) need adversarial review to strengthen arguments, identify weak points, and challenge assumptions before editorial polish (mandatory for Writer → Devil's Advocate pairing protocol)

devils-advocate

Systematically challenge current assumptions before major decisions. Counters confirmation bias, groupthink, and overconfidence.

devils-advocate

Systematically challenge current assumptions before major decisions. Counters confirmation bias, groupthink, and overconfidence.

devils-advocate

Use when a proposal has unanimous support or relies on a single high-impact assumption—constructs the strongest possible counter-argument (Steel Man) and runs a Pre-Mortem.