6,785 件 ・ 関連度順
概要と使いどころ
Assesses underlying asset pools with stratification, concentration analysis, historical performance, and credit quality distribution. Use when analyzing collateral pools, stratifying asset characteristics, or evaluating pool quality.
日本語の概要は準備中です。原文の説明を表示しています。
Evaluates structured product tranche pricing with spread analysis, yield attribution, and comparable structure benchmarking. Use when assessing tranche value, comparing structured product pricing, or analyzing spread components.
日本語の概要は準備中です。原文の説明を表示しています。
Values infrastructure assets with DCF, regulated asset base, and comparable transaction methodologies adjusted for regulatory and contractual frameworks. Use when valuing infrastructure assets, analyzing regulated utilities, or benchmarking infra transactions.
日本語の概要は準備中です。原文の説明を表示しています。
Evaluates regulatory differences across jurisdictions with comparative framework analysis and optimal domicile selection. Use when analyzing regulatory environments, comparing jurisdiction frameworks, or selecting fund domiciles.
日本語の概要は準備中です。原文の説明を表示しています。
Evaluates IPO pricing with comparable company analysis, IPO discount estimation, and investor demand assessment. Use when pricing IPOs, determining offering ranges, or analyzing IPO valuation methodologies.
日本語の概要は準備中です。原文の説明を表示しています。
Evaluates conglomerate discount with SOTP analysis, segment-level valuation, and separation benefit quantification. Use when analyzing conglomerate value, building SOTP models, or evaluating break-up scenarios.
日本語の概要は準備中です。原文の説明を表示しています。
Evaluates competition law exposure with market definition, HHI analysis, and remedy estimation for proposed transactions. Use when assessing merger clearance risk, analyzing market concentration, or preparing HSR filings.
日本語の概要は準備中です。原文の説明を表示しています。
Evaluates multi-jurisdictional restructuring with Chapter 15 recognition, COMI analysis, and parallel proceeding coordination. Use when analyzing cross-border insolvency, assessing jurisdiction selection, or coordinating multi-country restructurings.
日本語の概要は準備中です。原文の説明を表示しています。
Evaluates cornerstone investment commitments with allocation guarantees, lock-up terms, and signaling value assessment. Use when structuring cornerstone tranches, analyzing anchor investors, or evaluating demand signals.
日本語の概要は準備中です。原文の説明を表示しています。
Pick a Linear PBI, spec it, assemble it, then hold at the gate with a Boeing list for HITL clearance. Does NOT ship.
日本語の概要は準備中です。原文の説明を表示しています。
Hunt reflected, stored, and DOM-based Cross-Site Scripting (XSS) including CSP bypass, polyglot payloads, mutation XSS (mXSS), markdown XSS, and template XSS. Use when the user has identified a parameter or input that reflects to the page, or wants to test for XSS in a specific input.
日本語の概要は準備中です。原文の説明を表示しています。
Hunt business logic flaws — race conditions, workflow state bypass, parameter pollution affecting logic, coupon/discount abuse, refund logic, multi-step process bypass, integer overflow, negative quantities, double-spend. Use when looking for non-CVE bugs that require understanding the app's intended workflow.
日本語の概要は準備中です。原文の説明を表示しています。
CMDO architecture standards for Node.js/TypeScript backends with strict layer separation.
日本語の概要は準備中です。原文の説明を表示しています。
Step 3 of the PaperOrchestra pipeline (arXiv:2604.05018). Execute the literature search strategy from outline.json — discover candidate papers via web search, verify them through Semantic Scholar (Levenshtein > 70 fuzzy title match, temporal cutoff, dedup by paperId), build a BibTeX file, and draft Introduction + Related Work using ≥90% of the verified pool. Runs in parallel with the plotting-agent. TRIGGER when the orchestrator delegates Step 3 or when the user asks to "find citations for my paper", "draft the related work", or "build the bibliography".
日本語の概要は準備中です。原文の説明を表示しています。
Use when EZ_math_model runs in multi or hybrid mode and has two or more independent subtasks that can be assigned to subagents without shared files, shared state, or dataflow dependencies.
日本語の概要は準備中です。原文の説明を表示しています。
Step 2 of the PaperOrchestra pipeline (arXiv:2604.05018). Execute the visualization plan from outline.json — render plots and conceptual diagrams from experimental_log.md and idea.md, optionally refine via VLM critique loop, and produce context-aware captions. Runs in parallel with the literature-review-agent. TRIGGER when the orchestrator delegates Step 2 or when the user asks to "generate the figures for my paper" or "render the plots from this experiment log".
日本語の概要は準備中です。原文の説明を表示しています。
Use when EZ_math_model multi or hybrid mode needs several domain-specialist subagents to gather outside knowledge, industry context, model theory, or sensitivity-analysis references in parallel.
日本語の概要は準備中です。原文の説明を表示しています。
Split a bound project manual PDF into individual spec section PDFs and extract searchable text. Triggers: 'split specs', 'break up the project manual', 'separate spec sections', 'extract spec text'. Prerequisite for /submittal-log-generator.
日本語の概要は準備中です。原文の説明を表示しています。
Split a bound drawing set PDF into individual sheet PDFs. Extracts sheet numbers from title blocks via vision, renames files. Triggers: 'split drawings', 'break up the drawing set', 'separate sheets'. Run after /project-setup.
日本語の概要は準備中です。原文の説明を表示しています。
Post-implementation QA planning — independent of /review (the developer chooses whether to run them sequentially or in parallel), only when the change has a running surface worth driving. Interviews the developer to turn the specs and the diff into an executable QA specification (specs/qa/QA-<N>-<slug>.md) that /execute-qa runs. The agent drives browser and shell; the human steps in only at named handoff points. Use only when the user asks to plan manual QA — never trigger automatically.
日本語の概要は準備中です。原文の説明を表示しています。
Phase 3 of 5 — slices the ARCH doc into verification-ready task specs (tdd/test-after/ui/checklist), emitted as a separate TASKS-<N>-<slug>.md file alongside ARCH for the implement skill. Use only when the user asks to run Phase 3 or generate tasks from an ARCH doc — never trigger automatically.
日本語の概要は準備中です。原文の説明を表示しています。
Phase 5 of 5 — triage-first review orchestrator; dispatches up to 17 domain checks in parallel and compiles one report. Use only when the user asks to run Phase 5 or review a PR, branch, or set of changes — never trigger automatically after writing code.
日本語の概要は準備中です。原文の説明を表示しています。
Find the most valuable commercial insight and the monetization point closest to lawful revenue for a project, product, service, website, community, content account, open-source tool, or business idea. Use when a user asks how to monetize, who pays, why people do not buy, what to charge, whether to keep building, what to stop, what to do next, or asks to continue or deepen an earlier business analysis. Answer the user's actual question before asking for more information and carry the analysis forward without repeating it. When the buyer, purchased result, or delivery ability is unknown, do not select them from industry stereotypes; use explicit conditional candidates and an evidence-gathering next step. Not for investment advice, income forecasts, get-rich-quick schemes, or guaranteed results.
日本語の概要は準備中です。原文の説明を表示しています。
Use multiple Claude agents to investigate and fix independent problems concurrently
日本語の概要は準備中です。原文の説明を表示しています。