企画、営業、経理、法務、プロジェクト管理（4,122 件）
Autonomous AI Sales Development Rep for B2B export — handles lead discovery, BANT qualification, multi-channel outreach (WhatsApp/Email/Telegram), CRM management, and deal pipeline tracking. Built for cross-border trade.
日本語の概要は準備中です。原文の説明を表示しています。
Smart contract and secure API contract security analysis — invariant checking, access control, reentrancy, and integer overflow patterns. Implements Checks-Effects-Interactions pattern, formal invariant verification, and OpenSCV vulnerability taxonomy for Solidity/EVM and Rust/Solana contracts.
日本語の概要は準備中です。原文の説明を表示しています。
OpenAPI contract standards for API specification, versioning, and type generation.
日本語の概要は準備中です。原文の説明を表示しています。
Scaffolds OpenAPI contract component with type generation.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Escalate blocked scraping campaigns with provider-neutral proxy rotation — decide between datacenter, residential, and mobile pools, integrate rotation with scrapling, configure session stickiness for stateful flows, monitor cost and health, and stay inside legal and ethical boundaries. Use as the next step after `headless-web-scraping` client-side stealth (StealthyFetcher, rate limiting, robots.txt) is insufficient and traffic is legitimate.
日本語の概要は準備中です。原文の説明を表示しています。
Plan a complete EU/DACH relocation timeline with dependency mapping between bureaucratic steps, deadline tracking, and country-specific procedure identification. Use when planning a move between EU/DACH countries, relocating from a non-EU country to an EU/DACH destination, coordinating employment-based relocation with employer HR, managing a relocation with tight deadlines, or when needing a single document that maps the entire relocation process end-to-end.
日本語の概要は準備中です。原文の説明を表示しています。
Plan a comprehensive spectroscopic analysis campaign by defining the analytical question, assessing sample characteristics, selecting appropriate techniques using a decision matrix, planning sample preparation for each technique, sequencing analyses from non-destructive to destructive, and defining success criteria with a cross-validation strategy.
日本語の概要は準備中です。原文の説明を表示しています。
Implement electronic signatures compliant with 21 CFR Part 11 Subpart C and EU Annex 11. Covers signature manifestation (signer, date/time, meaning), signature-to-record binding, biometric vs non-biometric controls, policy creation, and user certification requirements. Use when a computerized system requires legally binding electronic signatures for GxP records, when replacing wet-ink signatures in regulated workflows, when implementing batch release or document approval workflows, or when a regulatory gap reveals missing signature controls.
日本語の概要は準備中です。原文の説明を表示しています。
Statically enforce a privacy/redaction boundary on an artifact tree before publication, the way an AST checker enforces a code contract. Builds a two-tier gate — a shape-based deny-list (regex over identifier shapes) plus a structure-aware tier that parses JSON/HTML/SVG/Markdown/code and asserts sensitive content cannot appear in meaningful positions — with a strict exit-code contract, label-only output that never echoes the patterns themselves, and false-positive narrowing instead of suppressions. Use when gating a public mirror, a disclosure draft, a wire-capture export, or any artifact that must pass a leak check before it ships, and when a plain line-grep is too coarse to trust.
日本語の概要は準備中です。原文の説明を表示しています。
Create R-based pictogram glyphs for skill, agent, or team icons in the visualization layer. Covers concept sketching, ggplot2 layer composition using the primitives library, color strategy, registration in the appropriate glyph mapping file and manifest, rendering via the build pipeline, and visual verification of the neon-glow output. Use when a new entity has been added and needs a visual icon for the force-graph visualization, an existing glyph needs replacement, or when batch-creating glyphs for a new domain.
日本語の概要は準備中です。原文の説明を表示しています。
Map the intellectual property landscape for a technology domain or product area. Covers patent cluster analysis, white space identification, competitor IP portfolio assessment, freedom-to-operate preliminary screening, and strategic IP positioning recommendations. Use before starting R&D in a new technology area, when evaluating market entry against incumbents with strong patent portfolios, preparing for investment due diligence, informing a patent filing strategy, or assessing freedom-to-operate risk for a new product.
日本語の概要は準備中です。原文の説明を表示しています。
Systematically identify whether a GPU kernel is compute-bound, memory-bound, or latency-bound using roofline analysis, occupancy calculations, compute/load ratio per tile, and SASS instruction inspection. Produces a decision matrix for optimization strategy selection (cp.async, warp interleaving, tiling, double-buffering, or CuAssembler hand-tuning).
日本語の概要は準備中です。原文の説明を表示しています。
Plan and freeze workflow execution by creating an Execution Contract, setting PLAN_FROZEN/CURRENT_ROLE, and updating PROJECT_STATE decisions and Top 3. Use when starting workflow delivery, re-planning after unfreeze, or when scope/constraints change before execution.
日本語の概要は準備中です。原文の説明を表示しています。
Execute a frozen workflow contract and collect evidence by implementing only approved scope/files and checks. Use when PLAN_FROZEN=true and Execution Contract is complete, then hand off to review.
日本語の概要は準備中です。原文の説明を表示しています。
Review execution against the frozen Execution Contract, produce Evidence/Gaps, and decide pass or unfreeze. Use after ac-execute or at milestone acceptance gates.
日本語の概要は準備中です。原文の説明を表示しています。
用户想预防某个潜在风险或问题时; 当系统出现早期预警信号但尚未爆发时; 当已出现问题需要防止恶化和扩散时; 当需要建立长期防护机制时。 不适用于: 紧急危机处理(系统正在崩溃, 需要急救而非预防); 纯历史回顾 (分析过去发生了什么但不涉及未来预防)。
日本語の概要は準備中です。原文の説明を表示しています。
Comprehensive US stock analysis including fundamental analysis (financial metrics, business quality, valuation), technical analysis (indicators, chart patterns, support/resistance), stock comparisons, and investment report generation. Use when user requests analysis of US stock tickers (e.g., "analyze AAPL", "compare TSLA vs NVDA", "give me a report on Microsoft"), evaluation of financial metrics, technical chart analysis, or investment recommendations for American stocks.
日本語の概要は準備中です。原文の説明を表示しています。
Use when an output artifact, template, schema, example, or handoff field must stay aligned across commands, skills, docs, and validators.
日本語の概要は準備中です。原文の説明を表示しています。
Prospective failure analysis using Gary Klein's pre-mortem technique. Assumes complete failure, works backward to identify risks, leading indicators, and circuit breakers. Counters optimism bias by forcing systematic exploration of failure modes before they materialize. Use for project plans, architecture decisions, technology adoption, business strategy, or feature launches. Triggers on "리스크", "위험", "실패하면", "swing-mortem", "뭐가 잘못될 수 있어", "risk", "what could go wrong", "걱정되는 점", "failure modes", "리스크 분석", "위험 분석".
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user needs to finalize a deal, handle tough objections, or create a "Mutual Action Plan" to close a sale.
日本語の概要は準備中です。原文の説明を表示しています。
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).
日本語の概要は準備中です。原文の説明を表示しています。
Use when an answer is wanted from one named seat only: breaking, business, career, codebase, human, impact, innovation, moat, rent-seeking, skeptic, or stability. Not for multi-lens synthesis: use prism. Not for rebuilding from primitives: use from-first-principle.
日本語の概要は準備中です。原文の説明を表示しています。
Use when C or C++ code needs memory-safety or undefined-behavior guarantees proved with CBMC, or ACSL contracts checked with Frama-C Eva or WP. Not for choosing the proof policy: use proof-driven.
日本語の概要は準備中です。原文の説明を表示しています。