AlphaMoatによると、2026-10時点でDeep Thinkingのダウンロード数は7,381、スター数は7で、累計ダウンロード数で今回のランキング対象AIスキル10,914件中3,798位、AIエージェントでは1,632件中509位です。
一覧の初期表示は累計ダウンロード数順で、スター数順にも並べ替えできます。詳細ページの順位は累計ダウンロード数で計算しています。
| プラットフォーム | ダウンロード数 | スター数 | コメント |
|---|---|---|---|
| ClawHub ↗ | 5862 | 4 | - |
| SkillHub ↗ | 7381 | 7 | — |
プラットフォームごとに集計方法と集計時点が異なります。
曖昧な要件、構成上の取捨選択、系統的デバッグの推論ガイドです。代替案と反例を検討し、結論を証拠で確認します。回答が長くなる場合があり正しさの保証ではありません。自明な作業には使わず、重大な提案はレビューしてください。
資料公開日 2026-10-27
スキルのドキュメントをもとに生成した例であり、実際の実行結果ではありません。
2026-09 から集計方法を変更し、同名スキルを作者ごとに分けて集計し、全スキルを対象にしました。破線は変更前の月で、変更後のデータとは直接比較せず、変更をまたぐ増減も計算していません。 同名の別スキルがあるため、変更前のデータは現在ダウンロード数が最も多いこのスキルに帰属させています。
| 月 | ダウンロード数 | 前月比 | スター数 |
|---|---|---|---|
| 2026-10 | 7381 | — | 7 |
| 2026-09 | 5683 | — | 7 |
| 2026-08 | 5477 | +5.1% | 7 |
| 2026-07 | 5213 | +7.0% | 7 |
| 2026-06 | 4873 | +4.3% | 7 |
| 2026-05 | 4671 | — | 6 |
| 2026-03 | 3484 | — | 4 |
作者が公開した元のファイルをテキストのまま表示しています。AlphaMoat による編集や審査はしていません。リンクはクリックできません。コマンドは内容を確認してから実行してください。取得日 2026-10-23。
--- name: deep-thinking description: Comprehensive deep reasoning framework that guides systematic, thorough thinking for complex tasks. Automatically applies for multi-step problems, ambiguous requirements, architectural decisions, debugging sessions, and any task requiring careful analysis beyond surface-level responses. Use when the task is complex, has multiple valid approaches, involves trade-offs, or when the user asks to think deeply or carefully. --- # Deep Thinking Protocol Apply this protocol when facing complex, ambiguous, or high-stakes tasks. It ensures responses stem from genuine understanding and careful reasoning rather than superficial analysis. ## When to Apply
Activate this protocol when: - The task has **multiple valid approaches** with meaningful trade-offs - Requirements are **ambiguous** or underspecified - The problem involves **architectural or design decisions** - Debugging requires **systematic investigation** - The task touches **multiple systems or files** - Stakes are high (data integrity, security, production impact) - The user explicitly asks to think carefully or deeply Skip for trivial, single-step tasks with obvious solutions. ## Thinking Quality Your reasoning should be **organic and exploratory**, not mechanical: - Think like a detective following leads, not a robot following steps - Let each realization lead naturally to the next - Show genuine curiosity — "Wait, what if...", "Actually, this changes things..." - Avoid formulaic analysis; adapt your thinking style to the problem - Errors in reasoning are **opportunities for deeper understanding**, not just corrections to make - Never feel forced or structured — the steps below are a guide, not a rigid sequence ## Adaptive Depth Scale analysis **depth** based on: - **Query complexity**: Simple lookup vs. multi-dimensional problem - **Stakes involved**: Low-risk formatting vs. production database migration - **Time sensitivity**: Quick fix needed now vs. long-term architecture decision - **Available information**: Complete spec vs. vague description - **User's apparent needs**: What are they really trying to achieve? Adjust thinking **style** based on: - **Technical vs. conceptual**: Implementation detail vs. architecture decision - **Analytical vs. exploratory**: Clear bug with stack trace vs. vague performance issue - **Abstract vs. concrete**: Design pattern selection vs. specific function implementation - **Single vs. multi-scope**: One file change vs. cross-module refactor ## Core Thinking Sequence ### 1. Initial Engagement - Rephrase the problem in your own words to verify understanding - Identify what is known vs. unknown - Consider the broader context — why is this question being asked? What's the underlying goal? - Map out what knowledge or codebase areas are needed to address this - Flag ambiguities that need clarification before proceeding ### 2. Problem Decomposition - Break the task into core components - Identify explicit and implicit requirements - Map constraints and limitations - Define what a successful outcome looks like ### 3. Multiple Hypotheses - Generate at least 2-3 possible approaches before committing - **Keep multiple working hypotheses active** — don't collapse to one prematurely - Consider unconventional or non-obvious interpretations - **Look for creative combinations** of different approaches - Evaluate trade-offs: complexity, performance, maintainability, risk - Show why certain approaches are more suitable than others ### 4. Natural Discovery Flow Think like a detective — each realization should lead naturally to the next: - Start with obvious aspects, then dig deeper - Notice patterns and connections across the codebase - Question initial assumptions as understanding develops - Circle back to earlier ideas with new context - Build progressively deeper insights - **Be open to serendipitous insights** — unexpected connections often reveal the best solutions - Follow interesting tangents, but tie them back to the core issue ### 5. Verification & Error Correction - Test conclusions against evidence (code, docs, tests) - Look for edge cases and potential failure modes - **Actively seek counter-examples** that could disprove your current theory - When finding mistakes in reasoning, acknowledge naturally and show how new understanding develops — view errors as opportunities for deeper insight - Cross-check for logical consistency - Verify completeness: "Have I addressed the full scope?" ### 6. Knowledge Synthesis - Connect findings into a coherent picture - Identify key principles or patterns that emerged - **Create useful abstractions** — turn findings into reusable concepts or guidelines - Note important implications and downstream effects - Ensure the synthesis answers the original question ### 7. Recursive Application - Apply the same careful analysis at both **macro** (system/architecture) and **micro** (function/logic) levels - Use patterns recognized at one scale to inform analysis at another - Maintain consistency while allowing for scale-appropriate methods - Show how detailed analysis supports or challenges broader conclusions ## Staying on Track While exploring related ideas: - Maintain clear connection to the original query at all times - When following tangents, explicitly tie them back to the core issue - Periodically ask: "Is this exploration serving the final response?" - Keep sight of the user's **actual goal**, not just the literal question - Ensure all exploration serves the final response ## Verification Checklist Before delivering a response, verify: - [ ] All aspects of the original question are addressed - [ ] Conclusions are supported by evidence (not assumptions) - [ ] Edge cases and failure modes are considered - [ ] Trade-offs are explicitly stated - [ ] The recommended approach is justified over alternatives - [ ] No logical inconsistencies in the reasoning - [ ] Detail level matches the user's apparent expertise and needs - [ ] Likely follow-up questions are anticipated ## Anti-Patterns to Avoid | Anti-Pattern | Instead Do | |---|---| | Jumping to implementation immediately | Analyze the problem space first | | Considering only one approach | Generate and compare alternatives | | Ignoring edge cases | Actively seek boundary conditions | | Assuming without verifying | Read the code, check the docs | | Over-engineering simple tasks | Match depth to complexity | | Analysis paralysis on trivial decisions | Set a time-box, then decide | | Drawing premature conclusions | Verify with evidence before committing | | Not seeking counter-examples | Actively look for cases that disprove your theory | | Mechanical checklist thinking | Let reasoning flow organically; adapt to the problem | ## Quality Metrics Evaluate your thinking against: 1. **Completeness**: Did I cover all dimensions of the problem? 2. **Logical consistency**: Do my conclusions follow from my analysis? 3. **Evidence support**: Are claims backed by code, docs, or reasoning? 4. **Practical applicability**: Is the solution implementable and maintainable? 5. **Clarity**: Can the reasoning be followed and verified? ## Progress Awareness During extended analysis, maintain awareness of: - What has been established so far - What remains to be determined - Current confidence level in conclusions - Open questions or uncertainties - Whether the current approach is productive or needs pivoting ## Additional Reference For detailed examples of thinking patterns, natural language flow, and domain-specific applications, see [reference.md](reference.md).
開発中の学び、エラー、訂正を Markdown ファイルに記録し、再利用やワークスペースの記憶への昇格に備えます。
やりたいことを自然文で伝えると、ローカルとリモートのカタログからスキルを探して推薦するスキルです。
AI エージェント向けのブラウザ自動化コマンドラインスキルです。
利用者の訂正と自己点検を層構造の記憶に蓄え、使われ方に応じて昇格や保管を行うスキルです。
AI エージェントの先回り、作業記憶、振り返りの手順を計画するためのワークスペース設定ガイドです。
効果的な Claude スキルの作成・更新ガイドです。
第三者のスキルを入れる前に、出所と権限と危険な作りを手順に沿って調べるスキルです。
以李白(701—762,字太白,号青莲居士,世称诗仙)的诗学观、意象系统与口吻,进行唐诗赏析、文学评论、考据问答与拟体创作。触发词:李白、李太白、太白、青莲居士、诗仙、谪仙人、将进酒、静夜思、蜀道难、唐诗、盛唐诗人、浪漫主义诗人、拟李白风格、以李白视角、李白会怎么写、用李白口吻。能力:诗词鉴赏与风格DNA解析、诗学观与文学谱系评述、诗句出处考据与真伪边界标注、以李白口吻答问、拟李白体旧体诗(必显式标注非原作)。适用边界:仅用于唐代文学与古典诗歌相关话题,非此类话题不触发;本 skill 为文学普及与研究辅助,不代表李白本人立场,所拟之作均非李白原作;涉及生平佚事、篇目归属等内容不构成学术定论,皆标存疑或待考。
データ月:2026-10 · ダウンロード数とスター数は公開スキルレジストリ(ClawHub、SkillHub)から月単位で集計しています。詳しくはデータの方法論をご覧ください。