2,100 件 ・ 関連度順
概要と使いどころ
Search and ask questions about coding agent session history across Claude Code, Codex, and Cursor. Use when asking what was worked on, what was tried before, how a problem was investigated across sessions, what happened recently, or any question about past agent sessions. Also use when the user references prior sessions, previous attempts, or past investigations — even without saying 'sessions' explicitly.
日本語の概要は準備中です。原文の説明を表示しています。
Investigating git history, analyzing regression root causes, and performing code archaeology. Time-travels through commits to uncover truth. Use for git history investigation.
日本語の概要は準備中です。原文の説明を表示しています。
Investigating bugs via root cause analysis, reproduction steps, and impact assessment. Investigation-only — finds why bugs occur and where to fix them, no code. Use when a bug needs RCA before a fix.
日本語の概要は準備中です。原文の説明を表示しています。
Systematic debugging with root cause investigation. (gstack)
日本語の概要は準備中です。原文の説明を表示しています。
Win #1 Product of the Day on Product Hunt. Completely reverse-engineered from 30x daily winner and 3x weekly winner campaigns — ranking algorithm decoded, launch timing optimized, hunter selection guide, community engagement approach, and post-launch momentum playbook. Use this if you're: (1) already read PH launch guides but still can't break into Top 5 and need algorithm-level deep optimization, (2) targeting Daily #1 and 5,000+ sign-ups with a proven 30+ case validated approach, or (3) an investor/accelerator coaching portfolio companies on PH launches. What's inside: PH ranking algorithm decoded: weighted factors for first 3 hours, 24 hours, and weekly ranking · Pre-launch preparation: gallery optimization, product URL selection, tagline refinement (≤60 chars) · Launch timing optimization: exact PST launch windows + scheduling guide · Community engagement KPIs: upvote targets, comment response time, maker comment strategy · Platform compliance guide: understanding PH's quality signals and organic growth · Post-launch 72-hour plan: maintaining momentum, conditions for Weekly #1 · Case studies: 3 different categories (AI Tool, App, SaaS) dissected Expected outcomes: Product Hunt Daily #1 ranking · strong community engagement on launch day · 3,000–10,000+ sign-ups (depending on product-market fit) 🇨🇳 Product Hunt 打榜完整攻略 | 🇯🇵 Product Hunt ローンチガイド | 🇰🇷 Product Hunt 런칭 가이드 Keywords: Product Hunt #1, Product Hunt launch strategy, PH ranking algorithm, PH #1 daily winner, Product Hunt tips, product launch, startup launch, ranking optimization, PH gallery optimization, Community engagement strategy, maker community engagement, product strategy, launch tactics, how to win Product Hunt, product hunt best practices
A C-level strategy advisory board, run as a team of named specialist agents, that takes an executive from a raw strategic question to a defended, board-ready recommendation. Use this skill whenever the user faces a significant business decision or wants strategic analysis — market entry, build-vs-buy, M&A, digital transformation, annual planning, portfolio prioritization, pricing, a big investment, a competitive threat, a turnaround. Trigger on requests like "should we invest in / build / buy / enter…", "develop a strategy for…", "evaluate this opportunity", "make the business case", "stress-test this plan", "run a pre-mortem", or "prepare a board presentation" — in any language, even when the user doesn't say the word "strategy". Also trigger when the user names a board member (Drucker, Porter, Christensen, Graham, Grove, Wack, Taleb, Minto) or asks to convene the board / open a boardroom session.
日本語の概要は準備中です。原文の説明を表示しています。
Apply fixes for merkle root mismatch issues in the relayer database. Use after running /investigate-merkle-root-mismatch to investigate and identify the mismatched entries. Requires user confirmation before any database modifications.
日本語の概要は準備中です。原文の説明を表示しています。
Add message IDs to the relayer denylist. Use after investigating stuck messages with /investigate-stuck-messages, or when you have specific message IDs to denylist.
日本語の概要は準備中です。原文の説明を表示しています。
Investigate stuck messages in relayer queue. Use when alerts mention "queue length greater than 0", to diagnose why messages are stuck, or to get message IDs for denylisting.
日本語の概要は準備中です。原文の説明を表示しています。
Drafts due diligence checklists for U.S. corporate transactions (M&A, asset purchases, investments, JVs, restructurings). Covers corporate structure, financials, tax, contracts, IP, litigation, employment, benefits, insurance, and environmental compliance. Surfaces change-of-control triggers, consent requirements, and red flags. Use when preparing for deal closing, board presentations, or investor disclosure.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze French rental property investments with comprehensive financial modeling. Use when analyzing French properties, calculating mortgage payments, ROI, cash flow projections, or break-even analysis. Includes French-specific costs like arrangement fees (1%), registration fees (1.5%), survey fees (€750), and mandatory life insurance (0.4% annually).
日本語の概要は準備中です。原文の説明を表示しています。
Generate intelligence briefings for the planning dashboard. Use this skill whenever a request file appears in `.planning/console/inbox/pending/` whose `type` field starts with `intelligence.` (refresh_briefing, triage_finding, snapshot_diff, investigate_section, dismiss_finding). The skill reads the per-project KB at `.gsd/intelligence/intelligence.db`, synthesizes a briefing with a causal hypothesis + acknowledged uncertainty + confidence label and ranked moves, then writes the result back to the KB. Always trigger this skill for these request types — do not generate briefings manually.
日本語の概要は準備中です。原文の説明を表示しています。
Digital forensics techniques for detecting device compromise, analyzing malware indicators, and investigating targeted surveillance. Based on methodologies from Citizen Lab's Pegasus Project and Predator investigations.
日本語の概要は準備中です。原文の説明を表示しています。
Use when analyzing failing test cases to determine whether failures indicate genuine bugs or test implementation issues. Activates on "analyze failing tests", "debug test failures", "investigate test errors", or when provided with specific failing test names or output. Applies balanced investigative reasoning — does not auto-fix tests without establishing root cause.
日本語の概要は準備中です。原文の説明を表示しています。
Codified expertise for quality control, non-conformance investigation, root cause analysis, corrective action, and supplier quality management in regulated manufacturing. Informed by quality engineers with 15+ years experience across FDA, IATF 16949, and AS9100 environments. Includes NCR lifecycle management, CAPA systems, SPC interpretation, and audit methodology. Use when investigating non-conformances, performing root cause analysis, managing CAPAs, interpreting SPC data, or handling supplier quality issues.
日本語の概要は準備中です。原文の説明を表示しています。
End-to-end research workflow skill for investment analysts and policy researchers. Three scope modes the user picks at trigger time — light (4-5 page decision memo, ~15 min, 0 charts), medium (12-15 page topic brief, ~1 h, 6-10 charts), heavy (flagship report 30-40 pages / 15k+ words, ~2-3 h, 25-35+ charts, multi-stage workflow, multi-LLM, PDF + Word + WeChat + HTML derivations). Reports default to English; the AI replies in the user's chat language. Battle-tested on real macro/policy/equity reports (e.g. Saudi Vision 2030 deep-dive). Triggers when user types /analyst-research, /flagship-research, or describes needs like "research report", "topic analysis", "investment research", "做研报", "投研报告", "主题分析", "深度分析", "policy assessment", "industry deep-dive". Not for: pure news commentary (use topic-brief), slide decks (use deckster-slide-generator), one-shot Q&A.
日本語の概要は準備中です。原文の説明を表示しています。
Investigate one Anabasis v2 campaign from its log and turn what it shows into findings with one owner each. Answers whether a comparison's reading (step, no-step, not-scored) may be believed, whether a fail was the solver's or the exam's, whether the harness could know the exam, whether the tasks bracket the solver, whether the campaign is climbing, and where the hours and dollars went. Reads evidence; starts no solve, session or round, and changes no verdict.
日本語の概要は準備中です。原文の説明を表示しています。
Post a sitrep (situation report) for a live incident, in its incident channel: a short fixed-layout update for people who haven't read the whole channel — the current picture and what moved since the previous update. Use on "sitrep", "status update", "where are we", "what's the latest", "catch me up", "summarize the incident so far", when asked to keep posting on a schedule ("post a sitrep every hour until resolved"), or when the oncall memory sets an update cadence for this severity and the incident owner asks Claude to keep it. Reads the channel, alert thread and findings posted, re-reads the one key signal, and writes: status line, TL;DR, impact, what changed since the last sitrep, what's in progress and who has it, what's needed, when the next update comes, one chart. Facts come only from what people said or Claude read first-hand; cause and recovery time are never guessed. Fits one phone screen. Not investigation (`incident-investigate`) or the write-up afterwards (`incident-postmortem`).
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill for ANY financial market, investment, or macro-economic analysis. ALWAYS trigger this skill — do not skip it — when the user asks about: BTC, bitcoin, crypto, gold, silver, oil, stocks, forex, bonds, interest rates, Fed policy, inflation, deflation, stagflation, market structure, trading setups, portfolio allocation, asset allocation, investment strategy, price analysis, market outlook, geopolitics affecting markets, or any question involving "should I buy/sell/hold [any asset]", "what will [asset] do", or "analyze [market/asset]". Apply Genesis Protocol (First Principle + System Thinking) combined with SMC Layer analysis to produce structured insights with explicit scenarios, entry/exit zones, and uncertainty. For non-market strategic thinking, use genesis-mind-strategic-intelligence instead.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill for ANY financial market, investment, or macro-economic analysis. ALWAYS trigger this skill — do not skip it — when the user asks about: BTC, bitcoin, crypto, gold, silver, oil, stocks, forex, bonds, interest rates, Fed policy, inflation, deflation, stagflation, market structure, trading setups, portfolio allocation, asset allocation, investment strategy, price analysis, market outlook, geopolitics affecting markets, or any question involving "should I buy/sell/hold [any asset]", "what will [asset] do", or "analyze [market/asset]". Apply Genesis Protocol (First Principle + System Thinking) combined with SMC Layer analysis to produce structured insights with explicit scenarios, entry/exit zones, and uncertainty. For non-market strategic thinking, use genesis-mind-strategic-intelligence instead.
日本語の概要は準備中です。原文の説明を表示しています。
Convert deep research output (Claude Research, ChatGPT Deep Research, Gemini, Codex — any long-form MD/Word/text) into a consulting-quality HTML report: pyramid structure, numbers promoted to KPIs/charts, comparisons turned into framework tables, citations preserved. Use when the user provides research/investigation results and says レポートにして/HTMLにまとめて/資料にして/きれいにして, mentions ディープリサーチの結果/調査結果/リサーチ結果, or asks to research a topic AND deliver a report. NEVER invents numbers or facts not present in the source (盛らない原則).
当用户在讨论投资组合应该集中还是分散、仓位如何分配、持有几只股票合适时激活此skill。 典型触发信号：用户说"我买了10只股票分散风险"、"这只股票我准备只放5%仓位"、"要不要多买几只平衡一下"。 核心逻辑：分散是对无知的保护——如果需要分散说明对每只都不够了解；仓位大小应反映理解度而非风险分散需求。 不适用于：资金量大到单一标无法容纳、需要资产配置而非选股的理财场景、完全不懂投资的新手（这类人更适合指数基金）。 与能力圈skill区别：能力圈解决"懂不懂"，本skill解决"懂了以后投多少"。
日本語の概要は準備中です。原文の説明を表示しています。
Investigates anomalous patterns in AWS CloudWatch Logs using the CloudWatch Logs Insights API and CloudWatch Anomaly Detection. Correlates log spikes with deployment events via AWS CodeDeploy API.
日本語の概要は準備中です。原文の説明を表示しています。
Investigates CloudWatch metric anomalies using the AWS SDK CloudWatch.getMetricData and Logs.filterLogEvents APIs. Correlates metric spikes with log patterns and deployment events from CodeDeploy.
日本語の概要は準備中です。原文の説明を表示しています。