「questions」の検索結果

Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

日本語の概要は準備中です。原文の説明を表示しています。

Due diligence checklists for A-share investments and M&A transactions. Adapted from the original dd-checklist skill for Chinese market due diligence requirements, regulatory filings, and business practices. Triggers on "A股尽调清单", "尽调清单", "due diligence China", "DD checklist A-share", "尽调checklist [company]", or "due diligence questions [company]".

日本語の概要は準備中です。原文の説明を表示しています。

mastR is an R package designed for automated screening of signatures of interest for specific research questions. The package is developed for generating refined lists of signature genes from multiple group comparisons based on the results from edgeR and limma differential expression (DE) analysis workflow. It also takes into account the background noise of tissue-specificity, which is often ignored by other marker generation tools. This package is particularly useful for the identification of g

日本語の概要は準備中です。原文の説明を表示しています。

The ggbio package extends and specializes the grammar of graphics for biological data. The graphics are designed to answer common scientific questions, in particular those often asked of high throughput genomics data. All core Bioconductor

日本語の概要は準備中です。原文の説明を表示しています。

Expert guidance for designing, assessing, and optimizing Azure workloads using Azure Well Architected. Covers design review checklists, recommendations, design principles, tradeoffs, service guides, workload patterns, and assessment questions. Use when designing AI, HPC, SaaS, AVD/AVS workloads, choosing regions/AZs, or configuring core Azure services, and other Azure Well Architected related development tasks.

日本語の概要は準備中です。原文の説明を表示しています。

Summary of the [REPLACE: CHANNEL_PLATFORM] channel [REPLACE: CHANNEL_NAME] — top [REPLACE: TOP_N_THREADS] threads + open questions

日本語の概要は準備中です。原文の説明を表示しています。

Single "start here" orchestrator for new cold email operators. Asks infrastructure-status questions first, then runs /icp-onboarding → /lead-magnet-brainstorm → /campaign-strategy in sequence, producing a consolidated campaign-plan.md. Ends with an interactive menu of next skills branched on whether the user already has domains/inboxes. Use as the very first invocation on any new repo checkout or when onboarding someone to cold email from zero.

日本語の概要は準備中です。原文の説明を表示しています。

Guides collaborative requirements discovery before implementation. Creates task directory, seeds PRD, asks high-value questions one at a time, researches technical choices, and converges on MVP scope. Use when requirements are unclear, there are multiple valid approaches, or the user describes a new feature or complex task.

日本語の概要は準備中です。原文の説明を表示しています。

Comprehensive product research and opportunity analysis for Amazon sellers. Analyzes demand, competition, profit potential, market entry barriers, and validates product ideas. Covers product sourcing, pricing strategy, and go-to-market planning. Use when the user asks about researching a product to sell, validating product ideas, product opportunity analysis, market research for Amazon, competition analysis, profit potential, should I sell this product, product viability, or any general product research questions.

日本語の概要は準備中です。原文の説明を表示しています。

Amazon keyword research and market opportunity analysis for sellers. Retrieve autocomplete suggestions (long-tail keywords), analyze competitor landscape, and assess market opportunity for any keyword on 12 Amazon marketplaces (US/UK/DE/FR/IT/ES/JP/CA/AU/IN/MX/BR). No API key required. Make sure to use this skill whenever the user mentions Amazon product research, finding products to sell on Amazon, Amazon keyword ideas, niche analysis, competition analysis for Amazon, market opportunity on Amazon, comparing Amazon keywords, evaluating whether a product is worth selling, Amazon autocomplete data, seasonal demand for Amazon products, or anything related to researching what to sell on Amazon — even if they don't explicitly say 'keyword research'. Also trigger when the user asks vague questions like 'is this a good product to sell?', 'what's the competition like for X on Amazon?', 'should I sell X or Y?', or 'what are people searching for on Amazon?'.

日本語の概要は準備中です。原文の説明を表示しています。

Trending products and rising categories discovery for Amazon sellers. Analyzes Best Seller Rank patterns, seasonal trends, new release momentum, and emerging niches. Identifies product opportunities before they peak. Use when the user asks about what's trending on Amazon, hot products, rising categories, seasonal opportunities, viral products, what to sell next, emerging niches, or early-mover opportunities. Also trigger for questions like 'what should I sell now?', 'what products are doing well?', 'find me trending niches', or 'what's hot on Amazon?'.

日本語の概要は準備中です。原文の説明を表示しています。

Use when starting any conversation in a loopkit-enabled project - establishes how to find and use loopkit's 49 skills, requiring skill invocation before ANY response including clarifying questions.

日本語の概要は準備中です。原文の説明を表示しています。

Applies Neil Rackham's SPIN methodology (Situation/Problem/Implication/Need-payoff questions) to major B2B sales. Use for complex multi-call sales cycles, enterprise deals where the customer must justify the decision to others, when objections are mounting, when calls end in vague continuations instead of advances, when traditional closing techniques are backfiring on large deals, or when designing discovery-call structure. Triggers include 'my deal isn't closing', 'too many objections', 'B2B sales coaching', 'discovery call structure', 'stuck in the middle of the sale'. Not for transactional sub-$50 sales, pure consumer impulse, or PLG self-serve products.

日本語の概要は準備中です。原文の説明を表示しています。

Provides multi-school trading Q&A, chart/OHLCV analysis, annotation, and fresh-market workflows covering ICT/SMC, ChanLun, Wyckoff, Price Action, Order Flow, VSA, and Elliott Wave. Use for trading concepts; capability-discovery questions about available analysis lenses, Schools, models, modes, or data sources; attached charts; pasted OHLCV; chart annotation; or asset-plus-timeframe requests across crypto, stocks, or forex. Defaults unselected market analysis to strict ICT/SMC, honors explicit School/source selectors, and fails closed when no native analyzer exists. Phase 1 comparison is Q&A-only; fetch fresh Mobius Quant API data only after the capability gate.

日本語の概要は準備中です。原文の説明を表示しています。

Build and maintain a Karpathy-style LLM knowledge base — a self-compiling Obsidian markdown wiki where an Agent ingests raw sources, compiles cross-linked concept/entity/summary pages, answers queries against the corpus, lints the graph for health, and audits in-context human feedback filed from Obsidian or the local web viewer. Use when (1) scaffolding a new knowledge base for any research topic, (2) ingesting articles/papers/PDFs/web pages into raw/, (3) compiling or restructuring wiki articles from existing raw material, (4) answering questions against the wiki and filing durable answers back, (5) running lint passes for dead links / orphan pages / coverage gaps / audit shape, (6) processing human feedback from the audit/ directory and applying corrections. Not for general note-taking, daily journals, or non-wiki Obsidian use.

日本語の概要は準備中です。原文の説明を表示しています。

Convert a local file (PDF, DOCX, XLSX, HTML, …) to markdown, or answer questions about its content. Use whenever the input is a file path, not a URL.

日本語の概要は準備中です。原文の説明を表示しています。

Find the papers that answer a research query in Firecrawl's research paper index — a corpus of paper abstracts whose largest share is biomedical and life-science literature (PubMed, bioRxiv, medRxiv), alongside arXiv preprints in CS, physics, and math — using semantic search, semantic and structural expansion, and in-body verification. Use this skill for literature-finding and paper-retrieval tasks of any kind, including clinical, biomedical, drug, gene, disease, and other life-science questions, whether the answer is a single paper or a full multi-paper set. The index is reached only through the `firecrawl_research_*` MCP tools or the `firecrawl research` CLI subcommands. Calling `firecrawl_search` with its `categories` option set to `["research"]` is a different feature — it filters ordinary web search to research-affiliated websites (the list includes PubMed, bioRxiv, medRxiv, arXiv, and publisher sites) and returns page results from them, without querying the paper records in this index.

日本語の概要は準備中です。原文の説明を表示しています。

Scaffolds a structured investigation in scratch/ for empirical research and documentation. Use when the user says "start an investigation" or wants to: trace code paths or data flow ("trace from X to Y", "what touches X", "follow the wiring"), document system architecture comprehensively ("document how the system works", "archeology"), investigate bugs ("figure out why X happens"), explore technical feasibility ("can we do X?"), or explore design options ("explore the API", "gather context", "design alternatives"). Creates dated folder with README. NOT for simple code questions or single-file searches.

日本語の概要は準備中です。原文の説明を表示しています。

Wave methodology knowledge for the buddy agent — what each wave does, its inputs and outputs, and how to route questions.

日本語の概要は準備中です。原文の説明を表示しています。

How the nWave buddy agent reads a project to answer questions — detection, order of inspection, and citation discipline.

日本語の概要は準備中です。原文の説明を表示しています。

Observe answer visibility for approved buyer questions, audit discoverability and file evidence-backed improvement cards.

日本語の概要は準備中です。原文の説明を表示しています。

Weekly on a Wednesday, light browser lane. Turns the questions that keep coming back into the answer that only has to be written once. It reads the ticket ledger over the recurrence window, finds every theme that crossed its threshold, checks the member's own help center and the existing macros for an answer that already covers it, and writes a reusable macro and a help article draft for every theme that has neither. It publishes only where you released the channel an article, never edits a live help center page, sends only where you released the channel, spends only where you released it, and never touches a credential.

日本語の概要は準備中です。原文の説明を表示しています。

Use when the user needs to understand customers deeply enough to write copy and pick targeting — consumer versus shopper, JTBD, layered persona, internal monologue, pain map, objection list, journey map, and a customer language bank pulled from real reviews and DMs. Trigger on 'customer insight', 'buyer persona', 'who is my customer', 'what do they actually want', 'jobs to be done', 'why do they hesitate before buying'. Also use when the user cannot explain who the product is for. Not for — intake questions when an agency signs a new client, see `20-client-intake-brief-global`; paid audience targeting setup, see `51-audience-research-global`; competitor study, see `08-competitor-research-global`.

日本語の概要は準備中です。原文の説明を表示しています。

Use when the user wants to show up in OTHER communities without astroturfing — Reddit, Facebook Groups, Discord, Slack, LinkedIn groups, Quora, and niche forums: a prioritized community list with the rules of each space, a named participant roster, post types written in full, reply scripts, a participation calendar, and red lines. Trigger on 'community marketing', 'Reddit marketing', 'seeding plan', 'post in Facebook groups', 'answer questions on Quora', 'we got banned from a group'. Not for — building your OWN paid or private community, see `28-community-building-global`; monitoring mentions across the web, see `15-social-listening-global`; briefing paid creators, see `06-ugc-egc-brief-global`.

日本語の概要は準備中です。原文の説明を表示しています。