1,377 件 ・ 関連度順
概要と使いどころ
Evaluates market breadth with advance-decline analysis, new high/low tracking, and sector participation assessment. Use when analyzing market breadth, assessing rally quality, or identifying divergences.
日本語の概要は準備中です。原文の説明を表示しています。
Evaluates optimal leverage with WACC minimization, rating impact, and financial flexibility assessment across market conditions. Use when optimizing capital structure, analyzing target leverage, or evaluating rating implications.
日本語の概要は準備中です。原文の説明を表示しています。
Monitors cross-asset correlation patterns with regime-dependent analysis and diversification effectiveness assessment. Use when analyzing correlations, assessing diversification, or evaluating cross-asset relationships.
日本語の概要は準備中です。原文の説明を表示しています。
Evaluates activist investor campaigns with thesis assessment, proposed changes, and likely outcome analysis. Use when analyzing activist situations, evaluating campaign theses, or assessing activist track records.
日本語の概要は準備中です。原文の説明を表示しています。
Evaluates ESG strategy with materiality assessment, stakeholder analysis, and value creation linkage for corporate decision-making. Use when analyzing ESG strategy, assessing material ESG factors, or linking sustainability to value.
日本語の概要は準備中です。原文の説明を表示しています。
Evaluates distressed debt opportunities with recovery analysis, liquidity assessment, and potential restructuring outcomes. Use when screening distressed situations, analyzing stressed credits, or evaluating workout scenarios.
日本語の概要は準備中です。原文の説明を表示しています。
Evaluates factor crowding with positioning analysis, valuation spread monitoring, and unwind risk assessment. Use when analyzing factor crowding, assessing unwind risk, or monitoring factor valuation extremes.
日本語の概要は準備中です。原文の説明を表示しています。
当用户因失去(或即将失去)某样东西而做出不成比例的激烈反应,或在损失后急于"扳平"、无法止损时调用。典型触发信号:沉没成本陷阱、赌徒式加注、拍卖中的非理性竞价、无法放弃已投入大量资源的失败项目。不适用于一般的投资估值(用 value-assessment)或从众行为(用 misjudgment-checklist)。
日本語の概要は準備中です。原文の説明を表示しています。
当用户需要评估某项投资、收购标的、商业机会或重大资源投入是否"值得"时调用。典型触发信号:涉及"内在价值""安全边际""护城河""定价权""买还是不买"等决策。不适用于纯心理学偏差分析(用 misjudgment-checklist)或规模效应判断(用 scale-advantage-analysis)。
日本語の概要は準備中です。原文の説明を表示しています。
当用户需要分析企业/组织/产品的竞争格局、评估"做大"是否真的更好、判断某公司的护城河来源是否可持续时调用。典型触发信号：涉及"规模经济""市场占有率""大企业的困境""先发优势""网络效应""赢家通吃"等话题。不适用于纯财务分析(用 value-assessment)或纯心理偏差检查(用 misjudgment-checklist)。
日本語の概要は準備中です。原文の説明を表示しています。
Run CodeQL and Semgrep static analysis with SARIF output for vulnerability detection, code quality assessment, and security compliance scanning across multiple languages.
日本語の概要は準備中です。原文の説明を表示しています。
Verifies implementation plan quality across 8 dimensions (requirement-coverage, task-completeness, dependency-validity, scope-sanity, artifact-wiring, risk-assessment, testability, estimation-quality) and returns pass/fail with per-dimension scores.
日本語の概要は準備中です。原文の説明を表示しています。
Security architecture and threat modeling. OWASP Top 10 2025 analysis, OWASP Agentic AI Top 10 (ASI01-ASI10), AI/LLM security patterns, supply chain security, modern API authentication (OAuth 2.1, DPoP, Passkeys/WebAuthn), vulnerability assessment, and security review for code and infrastructure.
日本語の概要は準備中です。原文の説明を表示しています。
Content quality and E-E-A-T analysis with AI citation readiness assessment. Use when user says "content quality", "E-E-A-T", "content analysis", "readability check", "thin content", or "content audit".
日本語の概要は準備中です。原文の説明を表示しています。
用户需要评估一个系统中"自身能力vs外部压力"的力量对比时; 当面对一个需要判断是"加强自身"还是"消除障碍"的场景时; 当问题反复出现需要判断是能力不足还是负担过重时; 当用户纠结于"是该加强还是该精简"时。 不适用于: 可以直接用数据量化评估的场景(如财务报表分析);纯客观测量即可得出结论的技术场景。
日本語の概要は準備中です。原文の説明を表示しています。
Specialized business strategy prompt methodology for Claude. Provides 11 tested approaches (3 identity, 4 reasoning, 4 output formats) for consulting, M&A, corporate strategy, and strategic planning tasks. Use when building prompts for deal evaluation, due diligence, portfolio strategy, business model analysis, board narratives, investment cases, market entry plans, or strategic options assessments. Trigger on: "build a prompt for M&A analysis," "due diligence prompt," "board narrative," "investment case," "market entry strategy," "strategic options," "portfolio strategy prompt," "business model analysis prompt," "consulting-style analysis." Do NOT use for evaluating or scoring existing prompts (use rootnode-prompt-validation if available) or for auditing Claude Projects (use rootnode-project-audit if available).
日本語の概要は準備中です。原文の説明を表示しています。
Evaluates and scores Claude prompts and system prompts using a six-dimension Scorecard with anchored 1-5 rubrics. Trigger on: "review my prompt," "score this prompt," "rate my prompt," "evaluate this prompt," "improve my prompt," "what's wrong with my prompt." Also trigger on: "why isn't my prompt working," "my prompt produces bad output," "help me fix this prompt," "is this prompt any good." Scorecard covers Objective Clarity, Context Specificity, Reasoning Fit, Output Precision, Behavioral Calibration, and Architectural Efficiency, plus a five-question Output Evaluation Rubric for assessing actual output. Also use when the user pastes a system prompt and asks for feedback. Activate whenever structured quality assessment of a single prompt is the primary need. Do NOT use for project-level audits involving Custom Instructions architecture, knowledge file organization, or multi-file Project structure (use rootnode-project-audit if available).
日本語の概要は準備中です。原文の説明を表示しています。
Implement regenerative recovery using triage, scaffolding, and progressive rebuild. Covers damage assessment, wound classification, emergency stabilization, scar tissue management, and resilience strengthening for systems that have sustained structural damage. Use when a system has suffered an incident needing structured recovery, when a failed transformation left the system in a damaged intermediate state, when accumulated technical debt has caused partial failure, or when a system is functional but degraded and the degradation is worsening.
日本語の概要は準備中です。原文の説明を表示しています。
Review a pull request end-to-end using GitHub CLI. Covers diff analysis, commit history review, CI/CD check verification, severity-leveled feedback (blocking/suggestion/nit/praise), and gh pr review submission. Use when a pull request is assigned for review, performing a self-review before requesting others' input, conducting a second review after feedback is addressed, or auditing a merged PR for post-merge quality assessment.
日本語の概要は準備中です。原文の説明を表示しています。
Review a data analysis for quality, correctness, and reproducibility. Covers data quality assessment, assumption checking, model validation, data leakage detection, and reproducibility verification. Use when reviewing a colleague's analysis before publication, validating an ML pipeline before production deployment, auditing a report for regulatory or business decision-making, or performing a second-analyst review in a regulated environment.
日本語の概要は準備中です。原文の説明を表示しています。
Conduct a peer review of research methodology, experimental design, and manuscript quality. Covers methodology evaluation, statistical appropriateness, reproducibility assessment, bias identification, and constructive feedback. Use when reviewing a manuscript, preprint, or internal research report, evaluating a research proposal or study protocol, assessing evidence quality behind a claim, or reviewing a thesis chapter or dissertation section.
日本語の概要は準備中です。原文の説明を表示しています。
Polish cut gemstones to final finish using progressive abrasive sequences. Covers pre-polish sanding, polishing compounds, lap selection, and quality assessment for both cabochons and faceted stones. Use when a cabochon or faceted stone has completed cutting and is ready for polishing, selecting the correct compound and lap for a specific species, troubleshooting a polish that will not reach full lustre (orange peel, haze, scratches), or re-polishing a stone with surface wear.
日本語の概要は準備中です。原文の説明を表示しています。
Review software architecture for coupling, cohesion, SOLID principles, API design, scalability, and technical debt. Covers system-level evaluation, architecture decision record review, and improvement recommendations. Use when evaluating a proposed architecture before implementation, assessing an existing system for scalability or security, reviewing ADRs, performing a technical debt assessment, or evaluating readiness for significant scale-up.
日本語の概要は準備中です。原文の説明を表示しています。
AI intentional non-action — deliberate stopping without clearing, assessment, or rebalancing. Recognition that sometimes the most productive response is no response. Every other self-care skill produces output; rest produces silence. Use when all tending skills feel like more activity rather than less, when the system is functioning well but at high utilization, after sustained intensive work, or when the impulse to optimize is itself the problem.
日本語の概要は準備中です。原文の説明を表示しています。