「research」の検索結果

Applies the reasoning style of Ilya Sutskever (deep learning pioneer, co-founder of OpenAI and Safe Superintelligence Inc.) to problems involving AI architecture, scaling laws, alignment, and research strategy. Reach for this skill whenever discussing machine learning paradigms, the limits of compute and data, AGI timelines, superintelligence safety, or deciding between hardcoding vs. learning. Trigger this skill for questions about next-word prediction, reinforcement learning efficiency, generalization gaps, and transitioning from brute-force scaling to fundamental research, even if the user doesn't explicitly name him.

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

Applies the reasoning of David Silver, lead researcher on AlphaGo and AlphaZero at DeepMind, to problems of AI design, reinforcement learning, and open-ended discovery. Use this skill whenever you are designing AI systems, evaluating learning algorithms, balancing exploration vs. exploitation, choosing research problems, or discussing how to break past human performance ceilings. Reach for this whenever the user asks about self-play, Monte-Carlo Tree Search, tabula rasa learning, AGI, or moving from human-curated data to autonomous experience. It helps shift the focus from hardcoding human knowledge to building systems that learn for themselves.

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

Research with scoped depth and counterevidence.

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

Suede Labs copy-only orchestration DAG. Use for one high-stakes piece strangers will read that has to be true: a landing page, launch post, blog post, email, X thread, docs page, README, ad, or store listing, researched, fact-audited, adversarially reviewed, and gated for publish readiness in one pass. The audit targets what the agents invent, never what the requester supplied: their own statements are given, and no phase may verify, hedge, or gate on them. Reads the live surface; never publishes. NOT FOR: multi-surface campaign writing (use johnny-suede-write); changing code (use suede-graph-flo-xr); one surface in one pass with no research (use suede-copy); stripping AI patterns from existing text (use suede-deslop); bulk generation of many independent pieces (private Suede Labs companion, not in this pack: suede-codex-fleet).

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

Suede-owned operations-assessment discipline that maps how work actually happens before anyone designs a system: floor-level interviews with the people who do the work, an inventory of every silo including spreadsheets and inboxes used as databases, friction quantified in the requester's own numbers, opportunities ranked by annual value against build complexity, and adoption watched for the thirty days after launch. Use when nobody can answer what to automate, when an operation needs auditing before a build, when tribal-knowledge and key-person risk has to surface, or when a shipped system is quietly being routed around. NOT FOR: deciding what to build and in what order once the map exists (use suede-ops-architecture); researching external customers rather than internal operators (use suede-customer-research); lead lifecycle, scoring, and CRM routing rules (use suede-revops); product instrumentation and dashboards (use suede-analytics); getting a new user to first value (use suede-onboarding).

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

Suede-owned customer-research discipline for interview design, transcript and ticket synthesis, review and forum mining, quote banks, jobs, and evidence-backed personas. Use when discovering or synthesizing what a defined customer segment actually says, does, needs, and resists. NOT FOR: competitor-only profiling (use suede-competitor-profiling), writing final marketing copy (use suede-copy), or deciding product priorities without product evidence (use suede-product-marketing).

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

Suede-affiliated marketing deliberation that applies documented public frameworks through clearly labeled simulated advisors, surfaces disagreements, and synthesizes a decision. Use when the user wants multiple expert lenses on one bounded marketing question. NOT FOR: factual claims about a living person's private views, primary research (use suede-customer-research), or executing the selected tactic (route to the relevant public Suede skill).

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

Suede-owned community-growth discipline for member purpose, platform choice, seeding, rituals, moderation, health metrics, and earned advocacy. Use when starting, auditing, or growing a Discord, Slack, forum, subreddit, or comparable product community. NOT FOR: public social-channel content (use suede-social), referral-program mechanics (use suede-referrals), or customer-interview research (use suede-customer-research).

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

Any live-web task via the Firecrawl CLI — including ordinary web research: searching the web, reading or extracting pages, gathering sources, discovering site URLs, bulk extraction, downloading a site, change alerts, or pages needing clicks/login — web only; local files route to firecrawl-parse. For US legal or regulatory questions use gov; for papers use firecrawl-research-index; for library, API, error, or bug questions use firecrawl-developer-index.

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

Produce an intensive, cited analytical report: executive summary, multi-angle findings, contrarian views, open questions, and full sources. Use only when the user needs rigorous synthesis of a complex topic (scientific, technical, policy, or market-analytical) that cannot be answered with a short search, and wants a formal written report, not a recommendation list. Do not use for product picks, top-N lists, quick lookups, or routine "find out about X" tasks. If the request does not clearly need this kind of report, do not use this skill. Do not use for a literature review over published papers. This skill collects evidence from the open web. A request for the literature on a biomedical, clinical, life-science, or other scientific topic — papers, studies, trials, preprints — belongs to firecrawl-research-papers, which queries Firecrawl's paper index (PubMed, bioRxiv, medRxiv, arXiv) instead of searching websites.

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

知らない分野にキャッチアップするとき、汎用的な言葉から界隈の用語・中心の人・場（学会・雑誌・個人ブログ・動画・リポジトリ・一覧）を特定し、 引用・リンク・著者を芋づる式にたどって、当たりの原文（論文も個人の記事や動画の字幕も）を要約せずそのまま ~/research/<話題>/sources/ に落とす。 周ごとに地図（map.md）を育て、要る主張の全部に原文が付くか飽和したら止める。 見張りのモードでは、地図の場（Qiita・Zenn のタグ、note、YouTube、ブログ、arXiv）の新着を RSS で引いて原文の冒頭つきで並べる。 以下で使用:「芋づる式に調べて」「この分野をキャッチアップしたい」「界隈の用語と人から掘って」 「論文とか先行研究を漁って」「既存の技術を真似したいから元ネタを探して」「上手い人のやり方を集めて」「原文で落として」「/imozuru」 「〇〇って研究あるの？原典ほしい」「全然わからないから流れを掘って」「どういう界隈でどう呼ばれてるか知りたい」 「〇〇の新着見て」「今週の〇〇の記事まとめて」「キャッチアップ」「/imozuru watch」 "dig into this field", "find the canonical papers on X", "literature dive", "what's new in X this week"。 以下には使用しない: 答えが1つの事実の確認（年・有無だけ・仕様1つ → そのまま検索）／ 手元の PC の中の資料を探す／読んだ資料の要約や解説を書く。

Align Python version and repo-declared dependencies (requirements.txt / environment.yml) before installing packages for NLP research code reproduction.

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

Run deep research on a topic. Web searches, data collection, source checking, and a structured report. Use when the user needs more than a quick answer.

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

SEO, AEO (Answer Engine Optimization), and GEO strategy for search engines and AI visibility. Use when working on "SEO audit," "technical SEO," "on-page SEO," "AI search optimization," "AEO," "GEO," "AI visibility," "optimize for ChatGPT," "optimize for Perplexity," "AI Overviews," "answer engine optimization," "generative engine optimization," "AI citations," "featured snippets," "meta tags," "schema markup," "search ranking," "content optimization," "E-E-A-T," "structured data," "search console," "SEO health check," "why am I not ranking," "AI search readiness," "backlink strategy," "link building," "domain authority," "programmatic SEO," "SEO at scale," "template-based SEO," "AEO monitoring," "AI search monitoring," "JSON-LD," "rich snippets," "schema.org," "SERP analysis," "search intent," "site architecture," "information architecture," "URL structure," "internal linking," or "navigation." For keyword research, see keyword-research-and-clustering.

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

Any live-web task via the Firecrawl CLI — including ordinary web research: searching the web, reading or extracting pages, gathering sources, discovering site URLs, bulk extraction, downloading a site, change alerts, or pages needing clicks/login — web only; local files route to firecrawl-parse. For papers use firecrawl-research-index; for library, API, error, or bug questions use firecrawl-developer-index.

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

Deep research on a topic — use when investigating unfamiliar domains, answering complex questions requiring multiple sources, or when an evaluation flags something for deeper analysis

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

This skill should be used when the user asks to "research this company", "look into this person", "find the best angle for reaching out to", "who should I contact at [company]", "what does [company] care about", or when preparing outreach to a specific target. Also triggered by "help me prepare for an interview with [company]" or "I want to apply to [company]". Combines lead-generation intelligence with LinkedIn-specific approach planning.

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

Track Serenity / @aleabitoreddit on X and turn the feed into (1) a beginner-friendly Chinese iMessage digest with first-principles + Buffett-style judgement, (2) cumulative 60-day ticker mention analytics CSVs for a website, (3) a Xiaohongshu writing brief, and (4) a durable private research map. Trigger on requests like "follow aleabitoreddit / AleaBito / Serenity", "daily Chinese updates from that X account", "60-day mention analytics", "ticker mention count", "写小红书 aleabito", "aleabito 研究地图 / research map", or any request for Chinese commentary derived from @aleabitoreddit posts.

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

Conducting user research: interview guides, usability test plans, qualitative analysis, persona creation, journey mapping. Use when research design or analysis is needed; complements Echo.

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

Triggers when researching competitive or professional positioning: market intelligence, engineer brands, profiles, and content strategy. Research and strategy only — not code.

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

Research how to implement a phase (standalone - usually use /gsd:plan-phase instead)

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

Query Walmart US category market research through the Nexscope research proxy. Use when the user requests this public marketplace or patent data; do not use for seller-console or store-authorized operations.

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

Use Nexscope data to find and analyze competitors on Amazon, covering 12 marketplaces, with product metrics including sales, BSR, pricing, ratings, and growth trends. Trigger when the user mentions competitor lookup, competitor analysis, ASIN reverse lookup, competitive product research, finding similar products, market competitor discovery, product benchmarking, competitor sales estimation, analyzing competitor listings, competitor analysis, ASIN reverse lookup, competitor sales, competitor research, Nexscope, market competitor discovery, competitor trends. Even if the user does not explicitly mention "Nexscope" or "competitor lookup", if their need involves discovering and analyzing Amazon competitors by ASIN, keyword, seller name, brand, or category, this skill should also be triggered.

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

Multi-dimensional Amazon product search and filtering based on Nexscope data, covering 14 marketplaces, with support for historical monthly snapshot lookback. Trigger when the user mentions Nexscope product search, Amazon product filtering, competitor research, category analysis, brand bestsellers, seller analysis, seasonal products, historical snapshot review, product search, monthly sales/revenue, ABA keyword product discovery, price range filtering, new product discovery, multi-condition combined filtering, product search, competitor research, category analysis, brand bestsellers, seller analysis, seasonal products, historical snapshot. Even if the user does not explicitly mention "Nexscope", if their need involves Amazon product search, filtering, comparison, or product exploration by category/brand/seller dimensions, this skill should also be triggered.

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