🇺🇸 User Interview & Cold-Start Operations Playbook — Battle-tested framework from HeyGen's 937 interviews to PMF. Complete SOP for user screening, interview execution, Beta testing methodology, cold-start user operations, churn analysis, and user grading systems. 🇨🇳 用户访谈与冷启动运营实战手册 — 基于 HeyGen 937 场访谈验证的 PMF 方法论。包含用户筛选、访谈执行、Beta 测试设计、冷启动用户运营、流失分析、用户分级体系完整 SOP。 🇯🇵 ユーザーインタビュー＆コールドスタート運営プレイブック — HeyGenの937回インタビューで検証されたPMF方法論。ユーザースクリーニング、インタビュー実行、Betaテスト設計、コールドスタートユーザー運営、離脱分析、ユーザーグレーディング。 🇰🇷 사용자 인터뷰 & 콜드 스타트 운영 플레이북 — HeyGen 937회 인터뷰로 검증된 PMF 방법론. 사용자 스크리닝, 인터뷰 실행, Beta 테스트 설계, 콜드 스타트 사용자 운영, 이탈 분석, 사용자 등급 시스템. Triggers: "user interview" | "user research" | "customer discovery" | "PMF" | "product-market fit" | "beta test" | "beta testing" | "cold start users" | "cold start operations" | "churn analysis" | "user grading" | "用户访谈" | "用户调研" | "冷启动" | "冷启动运营" | "Beta测试" | "流失分析" | "用户分级"
「discovery」の検索結果
1,445 件 ・ 関連度順
概要と使いどころ
Use when starting a new feature, gathering requirements for an unfamiliar domain, refining a vague idea into actionable scope, or when a user request is ambiguous or underspecified. Conducts SAM Stage 1 discovery — structured requirements gathering through user discussion, asking WHO/WHAT/WHEN/WHY and never HOW. Produces the ARTIFACT:DISCOVERY document containing feature requirements, NFRs, goals, anti-goals, references, and resolved questions. Supports backlog item self-initialization via a
日本語の概要は準備中です。原文の説明を表示しています。
Deprecated alias. This skill was renamed to `deepline-scoring`. Use when a user or script still invokes `/niche-signal-discovery`: immediately load and follow the `deepline-scoring` skill instead. Triggers: ICP analysis, niche signals, won vs lost analysis, differential signals, signal discovery, ICP signal report, account scoring signals, lead scoring, first-party signals, buyer signals.
日本語の概要は準備中です。原文の説明を表示しています。
Разговор-распаковка неудовлетворённостей (discovery-стратегирование). Сократический разбор сырой рефлексии и заметок на триаду Проблема/Неудовлетворённость/Эмоция → состояние пилота → приоритеты месяца (WHAT/WHY). Роль R1 Стратег, метод DP.METHOD.053. Триггеры — «разбери неудовлетворённости», «помоги со стратегией месяца», «что для меня сейчас важно», «/discovery-session».
日本語の概要は準備中です。原文の説明を表示しています。
Strategic product leadership guidance for SaaS and technology companies. Covers product strategy, roadmap planning, product discovery, user research, growth product management, platform strategy, product analytics, and product launches. Use when defining product vision, prioritizing features, conducting discovery, analyzing metrics, or launching products. Use for "product strategy", "roadmap planning", "feature prioritization", "product discovery", "product metrics", "PRD writing".
日本語の概要は準備中です。原文の説明を表示しています。
Audit and repair Claude Code discovery symlinks for skills, agents, and teams. Compares registries against .claude/ directories at project and global levels, detects missing, broken, and extraneous symlinks, distinguishes almanac content from external projects, and optionally repairs gaps. Use after adding new skills or agents, after a repository rename or move, when slash commands stop working, or as a periodic health check.
日本語の概要は準備中です。原文の説明を表示しています。
Eliciting and documenting a sales process before it is built in Salesforce: stage sequencing, entry/exit criteria per stage, win/loss analysis requirements, and stage transition rules. Trigger keywords: sales process design, stage discovery, entry criteria, exit criteria, stage gate, win/loss categorisation, sales methodology, pipeline stages, opportunity stage mapping, stage ladder, probability ladder, forecast category mapping, required fields per stage, stage swim lane, discovery workshop, handoff brief. NOT for configuring OpportunityStage, Sales Processes or Path in Setup — use admin/opportunity-management. NOT for cross-functional swim-lane maps — use admin/process-flow-as-is-to-be.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when configuring FSC financial planning objects, designing periodic review cycles, modeling risk assessment workflows, or tracking goal progress in Financial Services Cloud. Trigger keywords: FinancialGoal, FinancialPlan, goal tracking, risk tolerance, review cycle, financial planning workflow, Discovery Framework, Revenue Insights. NOT for wealth management process discovery — use admin/wealth-management-requirements. NOT for Action Plan template mechanics — use admin/fsc-action-plans.
日本語の概要は準備中です。原文の説明を表示しています。
Drafts California Superior Court discovery verification pages under CCP §§ 2030.250 and 2031.250 with proper CCP § 2015.5 perjury declarations. Trigger when the user needs a verification page for interrogatory or inspection/RPD responses, mentions California discovery verification, party vs. attorney signing, information-and-belief clauses, or fixing unverified responses. CA Superior Court only — not federal.
日本語の概要は準備中です。原文の説明を表示しています。
Controls error rates across thousands of simultaneous tests in genomics discovery using false-discovery-rate methods (Benjamini-Hochberg 1995; Benjamini-Yekutieli 2001 for arbitrary dependence; Storey q-value with pi0 estimation; local FDR; independent filtering Bourgon 2010; covariate-weighted FDR via IHW Ignatiadis 2016), plus family-wise error control (Bonferroni, Holm) and the GWAS genome-wide threshold. Covers the FDR-versus-FWER choice as the discovery-versus-confirmatory distinction, the dependence assumptions behind BH (PRDS) versus BY, pi0 estimation, the independent-filtering and false-coverage-rate traps, and reproducibility ranking via IDR (Li 2011). Use when correcting p-values from genome-wide tests, choosing between BH/BY/q-value/Bonferroni, setting an FDR threshold, applying IHW or independent filtering, or interpreting q-values. For confirmatory trials with few pre-specified endpoints (closed testing, graphical/gatekeeping), see clinical-biostatistics/multiplicity-graphical.
日本語の概要は準備中です。原文の説明を表示しています。
Do market research, user research, and product validation on Reddit with semantic search across 50K+ subreddits, 20M+ posts, and 40M+ comments via reddapi.dev - search by meaning, not keywords, no Reddit OAuth or app registration needed. Use when the user wants to research what people say on Reddit, find user pain points and complaints, validate a product or niche idea, do competitor and market research, track subreddit trends over a date range, or discover which subreddits discuss a topic. Also use when the user mentions 'Reddit research', 'Reddit 调研', 'search Reddit', 'subreddit discovery', 'niche validation', 'pain points', 'user complaints', or 'Reddit trends'. Requires REDDAPI_API_KEY. For B2B lead scoring, see reddit-leads; for a bare API reference, see reddit-search-api.
日本語の概要は準備中です。原文の説明を表示しています。
Automated discovery and matching of agent skills for dynamic task routing and capability assessment
日本語の概要は準備中です。原文の説明を表示しています。
Route ordinary public-web information tasks to the correct Tavily CLI operation. Use when the task concerns publicly accessible webpages and needs web discovery, clean extraction, URL mapping, same-site crawling, or public-web-only research, but the exact Tavily operation is not yet clear or several operations must be sequenced. Prefer the specific leaf skill when intent is clear: tavily-search for discovery without a URL, tavily-extract for known URLs, tavily-map for URL/site-structure discovery, tavily-crawl for content from many pages on one site, tavily-research for cited multi-source synthesis, and tavily-dynamic-search for programmatic filtering with context isolation. Do not use for named social/community/media/career/code platforms, login or cookie-dependent content, platform-native discussions, or cross-platform collection; use Agent Reach there. Do not use for local files, Git operations, deployments, or ordinary code editing.
日本語の概要は準備中です。原文の説明を表示しています。
Product-discovery coach for Fishbowl engineers — inspired by Marty Cagan's work (never impersonates him). Stage-routes between opportunity brief, research, PRD, ticket drafting, and outcome review. Triggers on "product coach", "help me with product", "I need to write a PRD", "I want to do discovery", "opportunity assessment", "who is this for", "why are we building this", or when an engineer is starting, resuming, or post-mortem-ing product-adjacent work. Invoke with a short description of what you want to do, or invoke bare to be surveyed and routed.
日本語の概要は準備中です。原文の説明を表示しています。
Conduct a Marty-Cagan-style opportunity assessment interview and produce a ~2-page Opportunity Brief in Confluence. Covers business objective, customer, problem, success metric, current alternatives, assumptions/risks, and what we don't know yet. Triggers on "opportunity brief", "opportunity assessment", "discovery brief", "who is this for", "why are we building this", "validate this idea", "product discovery", or any request to frame a feature before implementation. One question at a time. Records accepted research gaps as structured Confluence Decision pages with bidirectional links.
日本語の概要は準備中です。原文の説明を表示しています。
Prepares a discovery call brief from what the user has on a prospect (CRM record, inbound form, emails, notes, public material the user supplies): what is known with sources, gaps against the qualification dimensions, hypotheses to test, questions in priority order and what to listen for. Returns a DRAFT Markdown brief in the chat. Use when the user asks to "prep me for the discovery call with <prospect>", "what should I ask on this first call", "intro call brief", "questions for the qualification call" or "what do we know before we speak to them". Do not use for scoring leads against a rubric, use lead-qualification-scorer instead; for an existing customer's account review use account-plan-builder. Drafts for human review; never approves, authorises or signs off.
日本語の概要は準備中です。原文の説明を表示しています。
Expert en eDiscovery (document review, data processing, ESI, litigation hold, TAR)
日本語の概要は準備中です。原文の説明を表示しています。
open Issue を triage して「次の仕事候補（N 件 + 推奨 1 件）」を窓口が人間へ提示する。 候補はオペレーターが書いたゴール台帳（registry/goals/）の条項に当たるものだけで、条項順に並ぶ。 tools/work_discovery_scan.py を 1 回実行し、その候補 JSON を 設計書 §5.2 / §12 の人間可読フォーマットでレンダリングするところで停止する（propose-only）。 起動主体は窓口に限定。手動 / イベント起動のみ（常駐 /loop なし）。 「次の仕事候補出して」「triage して」「次なにやる？」や PR マージ後の proactive next-dispatch で窓口が手動起動する。
Controls error rates across thousands of simultaneous tests in genomics discovery using false-discovery-rate methods (Benjamini-Hochberg 1995; Benjamini-Yekutieli 2001 for arbitrary dependence; Storey q-value with pi0 estimation; local FDR; independent filtering Bourgon 2010; covariate-weighted FDR via IHW Ignatiadis 2016), plus family-wise error control (Bonferroni, Holm) and the GWAS genome-wide threshold. Covers the FDR-versus-FWER choice as the discovery-versus-confirmatory distinction, the dependence assumptions behind BH (PRDS) versus BY, pi0 estimation, the independent-filtering and false-coverage-rate traps, and reproducibility ranking via IDR (Li 2011). Use when correcting p-values from genome-wide tests, choosing between BH/BY/q-value/Bonferroni, setting an FDR threshold, applying IHW or independent filtering, or interpreting q-values. For confirmatory trials with few pre-specified endpoints (closed testing, graphical/gatekeeping), see clinical-biostatistics/multiplicity-graphical.
日本語の概要は準備中です。原文の説明を表示しています。
Controls error rates across thousands of simultaneous tests in genomics discovery using false-discovery-rate methods (Benjamini-Hochberg 1995; Benjamini-Yekutieli 2001 for arbitrary dependence; Storey q-value with pi0 estimation; local FDR; independent filtering Bourgon 2010; covariate-weighted FDR via IHW Ignatiadis 2016), plus family-wise error control (Bonferroni, Holm) and the GWAS genome-wide threshold. Covers the FDR-versus-FWER choice as the discovery-versus-confirmatory distinction, the dependence assumptions behind BH (PRDS) versus BY, pi0 estimation, the independent-filtering and false-coverage-rate traps, and reproducibility ranking via IDR (Li 2011). Use when correcting p-values from genome-wide tests, choosing between BH/BY/q-value/Bonferroni, setting an FDR threshold, applying IHW or independent filtering, or interpreting q-values. For confirmatory trials with few pre-specified endpoints (closed testing, graphical/gatekeeping), see clinical-biostatistics/multiplicity-graphical.
日本語の概要は準備中です。原文の説明を表示しています。
Analyzes alternative splicing from PacBio Iso-Seq (HiFi, Kinnex/MAS-Iso-seq) and Oxford Nanopore (direct cDNA, direct RNA, R10.4.1+) long-read RNA-seq with full-isoform resolution. Tools include FLAIR (correct/collapse/quantify/diffSplice for PacBio + ONT), IsoQuant (de-novo or annotation-guided isoform discovery 2024 SOTA), Bambu (annotation-aware Bayesian discovery + quantification with Novel Discovery Rate), SQANTI3/SQANTI-LR (isoform classification: FSM/ISM/NIC/NNC + artifact flags), rMATS-long (event calling on long-read isoforms), and minimap2 (-ax splice:hq for HiFi; -ax splice -k14 for ONT cDNA; add -uf only for direct RNA or stranded cDNA preps). Solves microexon detection, recursive splicing, complex multi-exon isoforms, and DTU without transcript-quantification uncertainty. Use when short-read AS limitations (anchor length, complex isoforms, microexons, recursive splicing, transcript ambiguity) demand full-isoform resolution.
日本語の概要は準備中です。原文の説明を表示しています。
Run Mom Test–style customer-discovery interviews to validate or kill an unbuilt idea — generate a non-leading interview guide, conduct or coach the conversations, and synthesize signal vs compliments. Load when the user asks to do customer discovery, run problem interviews, validate an idea with users, run a Mom Test, design an interview guide, or says "talk to customers", "validate the problem", "interview users", "Mom Test this", "did real users want it", "synthesize my interviews", "I just talked to N people". Sub-skill of `venture-exploration`. Hard-bans "would you use this?", solution-pitching, friend/family-only ICP, and treating compliments as validation. Calls `secure-*` before synthesizing any pasted external transcripts.
日本語の概要は準備中です。原文の説明を表示しています。
Controls error rates across thousands of simultaneous tests in genomics discovery using false-discovery-rate methods (Benjamini-Hochberg 1995; Benjamini-Yekutieli 2001 for arbitrary dependence; Storey q-value with pi0 estimation; local FDR; independent filtering Bourgon 2010; covariate-weighted FDR via IHW Ignatiadis 2016), plus family-wise error control (Bonferroni, Holm) and the GWAS genome-wide threshold. Covers the FDR-versus-FWER choice as the discovery-versus-confirmatory distinction, the dependence assumptions behind BH (PRDS) versus BY, pi0 estimation, the independent-filtering and false-coverage-rate traps, and reproducibility ranking via IDR (Li 2011). Use when correcting p-values from genome-wide tests, choosing between BH/BY/q-value/Bonferroni, setting an FDR threshold, applying IHW or independent filtering, or interpreting q-values. For confirmatory trials with few pre-specified endpoints (closed testing, graphical/gatekeeping), see clinical-biostatistics/multiplicity-graphical.
日本語の概要は準備中です。原文の説明を表示しています。
Analyzes alternative splicing from PacBio Iso-Seq (HiFi, Kinnex/MAS-Iso-seq) and Oxford Nanopore (direct cDNA, direct RNA, R10.4.1+) long-read RNA-seq with full-isoform resolution. Tools include FLAIR (correct/collapse/quantify/diffSplice for PacBio + ONT), IsoQuant (de-novo or annotation-guided isoform discovery 2024 SOTA), Bambu (annotation-aware Bayesian discovery + quantification with Novel Discovery Rate), SQANTI3/SQANTI-LR (isoform classification: FSM/ISM/NIC/NNC + artifact flags), rMATS-long (event calling on long-read isoforms), and minimap2 (-ax splice:hq for HiFi; -ax splice -k14 for ONT cDNA; add -uf only for direct RNA or stranded cDNA preps). Solves microexon detection, recursive splicing, complex multi-exon isoforms, and DTU without transcript-quantification uncertainty. Use when short-read AS limitations (anchor length, complex isoforms, microexons, recursive splicing, transcript ambiguity) demand full-isoform resolution.
日本語の概要は準備中です。原文の説明を表示しています。