2,100 件 ・ 関連度順
概要と使いどころ
Investigate a bounded Proto UI Contract, Prototype, Module, Host Capability, Adapter, schema, or ownership question and turn a genuinely unresolved direction into one semantic decision packet. Use for spec brainstorming, admission questions, competing semantic models, uncataloged behavior, or unresolved cross-layer boundaries.
日本語の概要は準備中です。原文の説明を表示しています。
Trace a Proto UI change through authoritative spec lifecycle, legacy explanation, dated context, implementation, executable evidence, package surfaces, and public projections. Use before deciding scope, changing behavior, reviewing a pull request, or investigating drift.
日本語の概要は準備中です。原文の説明を表示しています。
Enter explore mode to investigate ideas, systems, problems, and requirements before planning. Use explicit ultra mode when the user wants a durable adaptive research bundle with an index and only the justified C4, ADR, or dependency artifacts.
日本語の概要は準備中です。原文の説明を表示しています。
ES — Critica a fondo una idea, plan, pitch o proyecto entero sin validar ni adular: asume que va a fracasar y lo demuestra por ocho ángulos (premisas, mercado, competencia, viabilidad, números, ejecución, pre-mortem y punto ciego), investiga fracasos reales cuando hay herramientas, y entrega un veredicto franco con la lista priorizada de qué arreglar. Activar con /abogado-del-diablo, "hazme pedazos esto", "critica mi idea sin filtros", "dime por qué va a fallar", "destruye este plan", "segunda opinión brutal", "pre-mortem". EN — Harshly critiques an idea, plan, pitch, or whole project without validating; assumes it will fail and proves it across eight angles, then returns a blunt verdict with a prioritized fix list. Trigger on "devil's advocate", "red team this", "tear this apart", "why will this fail", "brutal second opinion", "pre-mortem".
日本語の概要は準備中です。原文の説明を表示しています。
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
日本語の概要は準備中です。原文の説明を表示しています。
Before any multi-step work with a stated goal — a feature, a bugfix spanning multiple files, a QA sweep, a doc draft + iterations, a multi-day investigation — create an ATO Mission instead of doing it via bare `ato dispatch` calls. A Mission persists the goal + the verifiable success criteria, lets the coordinator tick drive the work across days, captures every event in a structured audit trail (SQLite + markdown narrative), and integrates parallel agents' work via merge strategies. Complement to `ato-warroom` (the cross-family decision before you start) and `ato-review` (the post-code-diff review). Missions is where multi-step work LIVES; war-rooms are where decisions ABOUT it get made; reviews are where the resulting commits get vetted. Fires when: the work has more than one decision point, a verifiable end state, or runs across more than one session. Use it for any ATO development that doesn't fit in a single dispatch.
日本語の概要は準備中です。原文の説明を表示しています。
Choose the authorized worker channel and hand over complete engineering responsibilities, including in-scope self-check, repair and delivery. Use for substantial investigation, implementation, continuation and recovery — an ordinary substantial goal is enough, no special phrasing required; use swarm for approved independent batches. Respect the operator's standing ACP/native choice, explicit solo, and tiny or nearly finished work.
日本語の概要は準備中です。原文の説明を表示しています。
当用户在面临投资/创业/职业选择，群体都在做一个方向但自己有疑虑、或在问"什么时候应该反着来""如何做出不同于大多数人的正确决策""共识什么时候是错的""怎么承受被误解的压力"时激活。 核心信号：用户在做一个与群体共识相反的决策，或者在考虑这样做。 不适用于：技术性问题、纯情感问题、不需要逆群体方向的常规决策。
日本語の概要は準備中です。原文の説明を表示しています。
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
日本語の概要は準備中です。原文の説明を表示しています。
Full Stock Analysis Orchestrator — launches 5 parallel subagents via delegate_task for comprehensive multi-dimensional stock analysis with composite Trade Score (0-100). Triggered by "trade analyze <TICKER>" or "analyze <TICKER> stock".
日本語の概要は準備中です。原文の説明を表示しています。
Stock Screener — pre-built screens (growth, value, momentum, dividend, earnings beats) plus custom natural language criteria. Returns top 10-20 matches ranked by Screen Fit Score (0-100). Triggered by "trade screen growth/value/momentum/dividend/earnings" or "trade screen custom <criteria>".
日本語の概要は準備中です。原文の説明を表示しています。
AI Trading Analyst for Hermes — full stock analysis with 5 parallel subagents, investment thesis, technical/fundamental/sentiment/risk analysis, options strategies, portfolio review, stock screener, and PDF reports. Say "trade analyze AAPL", "trade quick NVDA", "trade screen growth", etc.
日本語の概要は準備中です。原文の説明を表示しています。
Head-to-Head Stock Comparison — compares two stocks across valuation, growth, profitability, financial health, technical setup, sentiment, and risk with category winners and a weighted overall score. Triggered by "trade compare <TICKER1> <TICKER2>".
日本語の概要は準備中です。原文の説明を表示しています。
Create stunning, animation-rich HTML presentations from scratch or by converting PowerPoint files. Zero dependencies — single HTML files with inline CSS/JS. Use when the user wants a presentation, pitch deck, conference talk slides, HTML slideshow, slide deck, investor deck, demo day slides, keynote-style presentation, or says 'make slides', 'presentation', 'pitch deck', 'conference talk', 'convert my PPT', 'HTML slides', 'talk slides', or wants beautiful animated slides without PowerPoint. Also use when someone needs to present something and doesn't have a tool — this replaces Keynote, Google Slides, and PowerPoint with a single HTML file. Includes 12 curated style presets and PPT-to-HTML conversion.
日本語の概要は準備中です。原文の説明を表示しています。
Analyzes Perfetto traces to find the root cause of latency, memory, or jank issues in Android apps. Use when the user provides a Perfetto trace file and asks any question, ongoing investigation, or open-ended request to analyze its contents.
日本語の概要は準備中です。原文の説明を表示しています。
Use for every coding task. Enforce strict TDD workflow: activate Serena, investigate first, clarify+confirm requirements, write per-task REQUIREMENTS.md in .requirements/<datetime>_<feature_name>/, verify APIs via web search, then implement in tiny test-verified steps.
日本語の概要は準備中です。原文の説明を表示しています。
Three-phase code review. Investigates internally, verifies findings, then reports only confirmed issues.
日本語の概要は準備中です。原文の説明を表示しています。
Investigate a topic, library, or approach before planning. Combines user context, prior knowledge, and external sources.
日本語の概要は準備中です。原文の説明を表示しています。
Use when facing 2+ independent tasks or investigations that can be worked on without shared state or sequential dependencies — fan out to specialized sub-agents with isolated context, then synthesize the results.
日本語の概要は準備中です。原文の説明を表示しています。
Debug LangChain and LangGraph agents by fetching execution traces from LangSmith Studio. Use when debugging agent behavior, investigating errors, analyzing tool calls, checking memory operations, or examining agent performance. Automatically fetches recent traces and analyzes execution patterns. Requires langsmith-fetch CLI installed.
日本語の概要は準備中です。原文の説明を表示しています。
Investigate stuck runs and execution failures by tracing Symphony and Codex logs with issue/session identifiers; use when runs stall, retry repeatedly, or fail unexpectedly.
日本語の概要は準備中です。原文の説明を表示しています。
Investigate stuck runs and execution failures by tracing Symphony agent-provider logs with issue/session identifiers; use when runs stall, retry repeatedly, or fail unexpectedly.
日本語の概要は準備中です。原文の説明を表示しています。
Write cold outreach messages that actually get replies, on LinkedIn, in email, or in X (Twitter) DMs. Use this skill whenever the user wants to reach out cold to someone they don't know or barely know, including phrases like "write a cold DM," "cold email," "LinkedIn message to," "reach out to," "pitch [person]," "how do I get [person] to reply," "DM this investor/recruit/partner/podcast host," "email a founder/company I want to work for," "cold email for a job," "land a job at [company]," "reach out about a role," "follow up with someone who ghosted," or any request to draft a first-touch message to a stranger or near-stranger for fundraising, hiring, partnerships/BD, press/podcasts/speaking, or job-seeking. Trigger this even when the user just pastes a name, a role, and "help me reach out," and even when they don't say the word "cold."
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks for a YARA rule, "write YARA for this sample/family", or `/hash-investigation` / `/malware-analysis` surfaces a sample worth a static-content rule. Pattern-matching rules for identifying malicious files.
日本語の概要は準備中です。原文の説明を表示しています。