majiayu000/claude-skill-registry - Page 74

sy8-synthesize-options

Generate structured options with tradeoffs.

sy8-synthesize-summary

Consolidate inputs into a concise summary.

synthesizer

Use when multiple reviews or paper notes need integration, cross-cutting themes must be identified, or project-specific implications must be drawn from disparate sources

synthesizer

Use when multiple reviews or paper notes need integration, cross-cutting themes must be identified, or project-specific implications must be drawn from disparate sources

synthesizing-findings

Use after layer analysis is complete to validate architecture documentation and generate a strategic rebuild plan focused on re-use decisions

synthesizing-voc

Use when you have customer feedback files (transcripts, tickets, surveys) and need to identify themes and opportunities without hallucinating.

sys-tracking-goals

Monitors active goals against current state. Calculates gaps, scores urgency, detects at-risk goals, generates alerts. Reads goals from strategy/goals/active/, computes progress from metrics, outputs prioritized alerts and updates goal status.

system-review

deeply review a system/architecture area and propose a simplification plan (Elon’s Algorithm).

systematic-literature-review

当用户需要做系统综述/文献综述/related work/相关工作/文献调研时使用：AI 自定检索词，多源检索→去重→AI 逐篇阅读并评分（1–10分语义相关性与子主题分组）→按高分优先比例选文→自动生成"综/述"字数预算（70% 引用段 + 30% 无引用段，三次采样取均值）→资深领域专家自由写作（固定摘要/引言/子主题/讨论/展望/结论），保留正文字数与参考文献数硬校验，强制导出 PDF 与 Word。支持多语言翻译与智能编译（en/zh/ja/de/fr/es）。

Source text: Chinese

tachyon-killer

General-purpose instability detector and killer. Tachyons are runaway modes -- imaginary mass, exponential growth, positive feedback disguised as negative. LRC resonance cancels instability without killing the system. GSO projection enforces symmetry…

taiyo-analyzer

太陽スタイル分析・スコアリングエンジン - 176パターンに基づくコンテンツ品質分析と改善提案

Source text: Japanese

tap-explorer

Tree of Attacks with Pruning for systematic code analysis

tasks-bug-diagnosis

Use when diagnosing bugs, analyzing errors/stack traces, or performing root cause analysis with evidence-based debugging protocols.

tasks-feature-investigation

Use when investigating existing features, understanding logic flow, or exploring how code works.

team-shape

Assess team structure against Skelton's Team Topologies. Evaluate cognitive load, interaction modes, and Conway's Law alignment.

team-shape

Assess team structure against Skelton's Team Topologies. Evaluate cognitive load, interaction modes, and Conway's Law alignment.

team-ultra-analyze

Deep collaborative analysis pipeline. Multi-perspective exploration, deep analysis, user-driven discussion loops, and cross-perspective synthesis. Supports Quick, Standard, and Deep pipeline modes.

team-ultra-analyze

Deep collaborative analysis team skill. All roles route via this SKILL.md. Beat model is coordinator-only (monitor.md). Structure is roles/ + specs/. Triggers on "team ultra-analyze", "team analyze".

teams-deep-analysis

Team-based deep exploration and synthesis workflow using Agent Teams with dynamic planning and hub-and-spoke coordination. Use when asked for "teams deep analysis", "team-based analysis", "collaborative analysis", or "teams-deep-analysis".

tech-article-extractor

技術サイトから特定の技術に関する記事・動画・スライド・論文を抽出・分析します。Qiita、Zenn、Stack Overflow、GitHub、Dev.to、Medium、YouTube、arXiv等50以上のソースから最新記事を検索・フィルタリングし、トレンド分析やキャッチアップに活用できます。

Source text: Japanese

tech-debt-analyzer

This skill should be used when analyzing technical debt in a codebase, documenting code quality issues, creating technical debt registers, or assessing code maintainability. Use this for identifying code smells, architectural issues, dependency problems,…

tech-radar

Build a technology radar for an engineering team, categorizing technologies into Adopt/Trial/Assess/Hold quadrants following the ThoughtWorks Tech Radar format. Use when asked to create a tech radar, evaluate the team's technology landscape, categorize tools…

technical-audit

Technical SEO audit methodology including crawlability, indexability, and Core Web Vitals analysis. Use when auditing pages or sites for technical SEO issues.

technical-discovery

Performs technical research and analysis without implementation. Use when asked to "analyze this", "research this change", "investigate", "what would be involved", "where would changes occur", "scope this work", "technical discovery", or before creating…

technical-research

Explore ideas, validate concepts, and research broadly across technical, business, and market domains. Preliminary phase before discussion-specification-plan-implement-review workflow. Use when: (1) User has a new idea to explore, (2) Need to research a topic…

technology-impact

Systematically analyze societal impacts of technologies using McLuhan's Tetrad of Media Effects. Use when evaluating new technology, planning technology adoption, or analyzing technology policy.

test-analysis

Analyze creative test results using heatmaps and data visualization to identify statistical winners and recommend next steps (scale, iterate, or kill). Use when reviewing test performance, making optimization decisions, or planning next test phases.

test-assumption

Identify hidden assumptions about users in code that could exclude or harm. A focused analysis asking "What am I assuming about the person using this?"

the-oracle

This skill should be used when the user asks to "use the oracle" or "ask the oracle" for deep research, analysis, or architectural questions. The oracle excels at multi-source research combining codebase exploration and web searches, then synthesizing…

the-oracle

Use when the user asks to "use the oracle" or "ask the oracle" for deep research, analysis, or architectural questions requiring multi-source investigation. Combines codebase exploration and web searches, synthesizing findings into actionable answers.

the-oracle

This skill should be used when the user asks to "use the oracle" or "ask the oracle" for deep research, analysis, or architectural questions. The oracle excels at multi-source research combining codebase exploration and web searches, then synthesizing…

think

Strategic analysis, adversarial validation, executive council debate, and discovery mode for complex decisions

think

Strategic analysis, adversarial validation, executive council debate, and discovery mode for complex decisions

think

Use proactively when the user explores ideas, directions, or priorities without a clear problem or urgency. Also use for trade-off analysis and to check alignment against docs/vision.md and docs/core-principles.md.

think

Apply Reflective Thought Composition (RTC) for deep analysis of complex problems. Use when facing complex tasks requiring structured reasoning.

think-tank

Collaborative exploration and reasoning frameworks. Use when ideas need shaping, decisions need analysis, or requirements need clarification. Includes l'entonnoir questioning, incremental validation, YAGNI, and 12 reasoning techniques. Not for execution when…

thinking-frameworks

Collection of mental models and decision-making frameworks (first principles, 5 whys, SWOT, Occam's razor, Pareto, inversion, second-order thinking). Use when analyzing problems, making decisions, evaluating trade-offs, or breaking down complex issues.

thinking-modes

Extended thinking modes for deeper analysis. Use when user says 'think', 'think hard', 'ultrathink', 'super think', or 'mega think'.

thought-partner

Collaborative thinking partner for exploring ideas, challenges, and decisions. Use when the user says "think through", "explore", "brainstorm", "help me figure out", asks open-ended questions about strategy or priorities, or needs to work through a problem…

growth-learning

Analytics, feedback processing, and continuous improvement