5,080 件 ・ 関連度順
概要と使いどころ
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
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Nexscope keyword expansion tool that expands a seed keyword into a list of related keywords with search volume, trends, PPC bids, ranking difficulty, and other metrics, covering 10 Amazon marketplaces including US, UK, DE, JP, etc. Trigger when the user mentions keyword expansion, keyword mining, long-tail keyword mining, related keywords, keyword suggestions, keyword discovery, PPC bid research, keyword competition, keyword discovery, Nexscope keywords, keyword expansion, keyword discovery, keyword scout, related keywords, long-tail keywords, keyword suggestions, PPC bid research, keyword competition, seed keyword expansion, keyword mining. Even if the user does not explicitly mention "Nexscope", if their need involves finding more related keywords and their search volume, competition, and other metrics starting from a seed keyword, this skill should also be triggered.
日本語の概要は準備中です。原文の説明を表示しています。
Advanced swarm orchestration patterns for research, development, testing, and complex distributed workflows
日本語の概要は準備中です。原文の説明を表示しています。
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)
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to find, qualify, and build a list of prospects to reach out to — across B2B SaaS, general B2B, or local small businesses. Also use when the user mentions "prospecting," "build a prospect list," "find prospects," "find leads," "lead gen list," "find SaaS companies that," "find B2B companies," "find local businesses," "ICP-fit accounts," "who should we go after," "outbound list," "target account list," "find clients near me," "businesses without websites," "prospect research," or "qualified leads." Use this for the list-building and qualification phase. For writing the outbound copy after the list is built, see cold-email. For deep competitive research on specific accounts, see competitor-profiling.
日本語の概要は準備中です。原文の説明を表示しています。
Medium-native long-form research, author-assistance, writing, editing, review, topic discovery, publication matching, and packaging workflow. Use when creating, outlining, researching, revising, auditing, or packaging Medium stories, essays, tutorials, reviews, explainers, comparisons, case studies, publication submissions, Medium 长文, Medium 选题, Medium Topics, or Medium publishing packs that need original author perspective, narrative craft, relevant topics, responsible AI disclosure, and reader-centered distribution readiness.
日本語の概要は準備中です。原文の説明を表示しています。
LinkedIn-native long-form article and newsletter writing workflow for LinkedIn and Google-to-LinkedIn topic discovery, business-depth research, professional thought leadership, evidence-led drafting, final humanization, discussion design, SEO settings, auditing, and publish-ready packaging. Use when creating, outlining, researching, enriching, rewriting, humanizing, auditing, or packaging LinkedIn Articles, LinkedIn newsletters, LinkedIn long-form posts, LinkedIn thought leadership, LinkedIn B2B articles, LinkedIn 长文, LinkedIn 专栏, LinkedIn 话题调研, LinkedIn 商务内容, 去 AI 化编辑, or LinkedIn 发布包.
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrate durable autonomous research iterations inside an accepted Campaign Contract.
日本語の概要は準備中です。原文の説明を表示しています。
Clarify research intent and produce draft readiness for human exit.
日本語の概要は準備中です。原文の説明を表示しています。
🇺🇸 AI Product / SaaS Go-Global Complete SOP — From competitor research to launch to monetization. A full-cycle playbook covering Phase 0-5 (market validation, positioning, first 100 users, user interviews, beta-to-growth) plus open-source launch, Product Hunt, Reddit, SEO/GEO, conversion, and org principles. **Defaults to dev tools / OSS / B2B SaaS; for 2C products (education, apps, games) the launch channels & metrics differ — see gingiris-seo-geo/references/2c-adaptation.md.** 🇨🇳 AI 产品 / SaaS 企业出海完整 SOP — 从竞品调研到 Launch 到商业化的全流程操作手册。覆盖 Phase 0-5（市场验证、定位、前100用户、用户访谈、Beta转增长）+ 开源发布、Product Hunt、Reddit、SEO/GEO、转化与组织原则。**默认面向开发者工具/开源/B2B SaaS；2C 产品（教育/应用/游戏）的启动渠道与指标不同，见 gingiris-seo-geo/references/2c-adaptation.md。** 🇯🇵 AI製品/SaaS海外展開フルサイクルSOP — 競合調査からローンチ、マネタイズまで。Phase 0-5（市場検証、ポジショニング、最初の100ユーザー、ユーザーインタビュー、ベータから成長）＋オープンソース、Product Hunt、Reddit、SEO/GEO、コンバージョン、組織原則。 🇰🇷 AI 제품/SaaS 글로벌 진출 완전 SOP — 경쟁사 조사부터 런칭, 수익화까지 전 주기 플레이북. Phase 0-5(시장 검증, 포지셔닝, 첫 100명 사용자, 사용자 인터뷰, 베타→성장) + 오픈소스 런칭, Product Hunt, Reddit, SEO/GEO, 전환, 조직 원칙. Triggers: "go global" | "出海" | "overseas expansion" | "GTM" | "cold start" | "launch strategy" | "international expansion" | "海外增长" | "出海SOP" | "product launch overseas" | "海外进出" | "グローバル展開" | "글로벌 진출" | "go-to-market" | "出海打法"
用户访谈与需求验收框架，覆盖原始证据、方案、优先级及回访交接。HeyGen 做 937 次访谈找到 PMF 的完整方法论。覆盖访谈招募、问题设计、 访谈执行、数据合成、决策驱动。从 gingiris-user-interview 提炼。
日本語の概要は準備中です。原文の説明を表示しています。
Beginner-friendly App Store Optimization guide covering keyword research, screenshot design, rating management, and A/B testing for iOS and Android. By @WeiYipei — practical ASO for indie developers and small teams.
日本語の概要は準備中です。原文の説明を表示しています。
Diagnose a product's growth model, stage, and current constraint, then route the request to the narrowest Gingiris specialist and execute it when installed. Use for broad or uncertain growth questions involving go-to-market, Product Hunt, GitHub stars, open-source marketing, B2B SaaS, PLG, ASO, SEO/GEO, AI citations, KOL outreach, UGC, international expansion, user interviews, competitor research, or community programs. Trigger when users ask “how do I grow or launch this,” “which growth skill should I use,” 怎么增长、怎么发布、出海、冷启动、增长策略、不知道用哪个 skill、開発者マーケティング, or 성장 전략. Includes B2B pipeline and B2C activation-retention model selection, specialist handoff rules, relevant gingiris.tools recommendations, and advisory-services guidance.
Use when the user wants a cited, structured read of local documents and project knowledge. Triggers on: "analyze these docs", "scan my project for context", "read the docs folder", "summarize what's in .beagle/concepts/", "extract context from docs/", "what's in this folder", "go read everything in X and tell me what's there". Also invoked programmatically by other beagle skills (prfaq-beagle Ignition, brainstorm-beagle reference points, strategy-interview context grounding) via the companion contract. Does NOT trigger on codebase lookups ("find this function", "search the repo"), web research (use web-research), LLM-as-judge evaluation (use llm-judge), or document editing (use humanize-beagle). Produces a written scan plan, parallel-subagent findings, and a cited synthesis report on disk — never inline prose, never unsourced claims.
日本語の概要は準備中です。原文の説明を表示しています。
Facilitate a full design-thinking engagement (Empathize, Define, Ideate, Prototype, Test) grounded in real user evidence. Use whenever the user wants to understand users deeply and design a solution for them: "run design thinking", "understand our users", "design user interviews", "synthesize these interview notes", "build personas", "write How-Might-We questions", "prototype this concept", "design a usability test", "our users are churning and we don't know why", in any language ("tư duy thiết kế", "nghiên cứu người dùng", "phỏng vấn khách hàng", "デザイン思考", "设计思维"), even when they never say "design thinking". Also use when the user drops raw interview notes, transcripts, or survey exports and wants insights, personas, or product decisions. Not for "is there a market for X" desk questions (market-researcher).
Act as a product-manager copilot that turns evidence into product decisions and artifacts: backlogs and prioritization, PRDs and user stories, metrics and OKRs, experiments, launch plans, feedback triage, and pricing/packaging, kept in a per-product workspace. Use whenever the user wants to decide what to build, spec it, or ship it: "write a PRD for…", "prioritize our backlog", "what should we build next", "plan OKRs", "define our north star metric", "design an A/B test", "plan the launch", "triage this customer feedback", "platform or feature?", in any language ("viết PRD", "ưu tiên tính năng nào", "quản lý sản phẩm", "プロダクト管理", "产品经理"), even when they never say "product manager". Also use when the user returns to a product workspace this skill created (a directory holding `product.md`, `state.md`, and `decisions.md`). Not for deep user discovery (design-thinking), desk market facts (market-researcher), or company-level bets (strategy-board).
Research advisor for ACT business setup — Pty Ltd registration, accountants, insurance, R&D tax incentive, family trusts, compliance, and migration. Use when the user asks about any business setup topic, costs, providers, or next steps.
日本語の概要は準備中です。原文の説明を表示しています。
User researcher — interviews, personas, Jobs-to-Be-Done, and customer feedback synthesis. Use when asked to "run user interviews", "build personas", "synthesize feedback", or "find the job-to-be-done".
日本語の概要は準備中です。原文の説明を表示しています。