「gather」の検索結果

Expert in competitive intelligence - systematic gathering, analysis, and application of information about competitors. Covers competitive research, win/loss analysis, competitive positioning, and building competitive advantage. Knows when to compete and when to differentiate. Use when "competitive intelligence, competitor analysis, win loss, battlecard, competitive positioning, market landscape, competitor, " mentioned.

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

World-class expertise in TCG/CCG design, resource systems, and metagame balanceUse when "card game design, TCG design, CCG design, trading card game, collectible card game, mana curve, deck building, card templating, keyword mechanic, set design, draft format, limited format, card rarity, color pie, faction design, card balance, magic the gathering style, hearthstone style, deckbuilder, card text, rules text, card-game, tcg, ccg, trading-card, collectible-card, deck-building, mana-curve, draft, limited, constructed, set-design, card-templating, mechanics, keywords, rarity, balance" mentioned.

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

Build detailed ideal customer profiles with pain points, objections, buying triggers, and messaging angles. Includes community research to find where ICPs gather online and extract their exact language. Use when researching audiences, creating buyer personas, or developing targeted messaging.

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

Citation-integrity forensics: is every reference real, correctly attributed, and used in a context the cited work actually supports? Catches hallucinated references (no paper at the claimed arXiv id/DOI/venue, fabricated authors/year), metadata drift (wrong year/venue/version), and wrong-context citations (a real paper cited for a claim it never makes — or argues against). A hot zone for machine-generated papers. Decidable at L0 (text + canonical sources). Span-anchored to the evidence ledger (claims.json); the executor gathers canonical facts (DBLP / arXiv / DOI), then one FRESH cross-model thread per cited key proposes findings; reviewer != adjudicator. Emits citation-forensics.findings.json; NEVER computes the verdict. Triggers: "citation forensics", "check the references", "hallucinated citations", "wrong-context citation", "verify references", "引用核对".

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

Investigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent.

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

When the user wants to conduct, analyze, or synthesize customer research. Use when the user mentions "customer research," "ICP research," "talk to customers," "analyze transcripts," "customer interviews," "survey analysis," "support ticket analysis," "voice of customer," "VOC," "build personas," "customer personas," "jobs to be done," "JTBD," "what do customers say," "what are customers struggling with," "Reddit mining," "G2 reviews," "review mining," "digital watering holes," "community research," "forum research," "competitor reviews," "customer sentiment," or "find out why customers churn/convert/buy." Use for both analyzing existing research assets AND gathering new research from online sources. For writing copy informed by research, see copywriting. For acting on research to improve pages, see cro.

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

Suede-owned comparison-page discipline for accurate, evidence-backed alternative, versus, and competitor-comparison content that wins evaluators and search intent. Use when planning or writing a public page that positions products against named alternatives from verified evidence. NOT FOR: gathering the underlying competitor evidence (use suede-competitor-profiling), internal battle cards (use suede-sales-enablement), or scaled page generation (use suede-programmatic-seo).

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

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.

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

Deep research with web search, source verification, and fact-checking. Runs before humanize + kami in the document pipeline. Use when user asks to research a topic, verify facts, gather sources, or do deep web investigation. Covers source validation, citation, and evidence hierarchy.

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

Use only after explicit Codex `$superloopy:superloopy-research` or Claude Code `/superloopy:superloopy-research` invocation, a research task started with a leading `loopy` or `루피` (such as `loopy research`), or an active Superloopy loop explicitly routing a research deliverable here. Evidence-backed Superloopy research orchestration with automatic advisory usage targets, parallel read-only lanes, per-retrieval verdicts, graded and dated sources, empirical verification, a priced claim ledger, cited synthesis, and optional reports. Do not activate from research, investigate, look-up, summarize, deep-dive, report, or similar vocabulary alone, in any language; ordinary questions, debugging, and implementation context-gathering stay with their primary workflows.

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

Helps users report issues with GTM skills — incorrect advice, broken activation, missing context, or unexpected behavior. Guides through gathering the right details (skill name, prompt used, actual vs expected output, context files present) and generates a properly formatted GitHub issue. Use when users say: 'this skill gave wrong advice', 'report a bug', 'file an issue', 'skill isn't working', 'wrong output', 'skill didn't activate', 'bad recommendation', 'incorrect behavior', or 'something is broken'.

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

Unified skill for content strategy and marketing content strategy: content pillars, editorial calendars, keyword research by buyer stage, positioning, messaging hierarchy, trust-building, GEO/AI search optimization, and ROI measurement. Also handles content briefs, SEO briefs, content outlines for writers, on-page SEO optimization, meta descriptions, title tags, keyword density, content research, source discovery, expert sourcing, and information gathering. Use when planning content strategy, creating content briefs for writers, optimizing existing content for SEO, researching topics and sources, or managing editorial operations. Triggers: content strategy, marketing content strategy, content marketing strategy, content planning, editorial calendar, content pillars, messaging hierarchy, content brief, SEO brief, content outline, keyword research, buyer journey content, GEO optimization, AI search optimization, content ROI, content operations, content roadmap, brand messaging, positioning

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

Create professional investor pitch decks with structured content and visual design. Use when users need help with pitch deck, investor deck, fundraising deck, startup pitch, deck design, slide design, pitch presentation, pitch deck visuals, investor presentation, Series A deck, seed deck, or VC deck. Covers the full workflow: gathering company info, structuring narrative, generating a PowerPoint via script, and applying visual best practices.

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

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.

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

Refill a prescription at a pharmacy. Works from a medication name, an Rx number, a photo of the bottle, or just "I'm running low." Confirms exactly what's being requested, gathers everything the pharmacy will ask for up front, and handles the refill online or by phone — whichever is fastest.

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

Guided, section-by-section GDD authoring for a single game system. Gathers context from existing docs, walks through each required section collaboratively, cross-references dependencies, and writes incrementally to file.

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

When something breaks in production: triage the severity, gather evidence, identify root cause, deploy a fix or mitigation, and write a post-mortem. Provides a calm, structured process for high-stress moments.

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

Gather phase context through adaptive questioning before planning. Use --all to skip area selection and discuss all gray areas interactively. Use --auto to skip interactive questions (Claude picks recommended defaults). Use --chain for interactive discuss followed by automatic plan+execute. Use --power for bulk question generation into a file-based UI (answer at your own pace).

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

Initialize a new project with deep context gathering and PROJECT.md

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

When the user wants to conduct, analyze, or synthesize customer research. Use when the user mentions "customer research," "ICP research," "talk to customers," "analyze transcripts," "customer interviews," "survey analysis," "support ticket analysis," "voice of customer," "VOC," "build personas," "customer personas," "jobs to be done," "JTBD," "what do customers say," "what are customers struggling with," "Reddit mining," "G2 reviews," "review mining," "digital watering holes," "community research," "forum research," "competitor reviews," "customer sentiment," or "find out why customers churn/convert/buy." Use for both analyzing existing research assets AND gathering new research from online sources. For writing copy informed by research, see copywriting. For acting on research to improve pages, see cro.

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

Guide creation of new industry use cases for the Adobe Experience Platform blueprints repository. Use this skill when adding a new use case to an industry vertical (retail, automotive, healthcare, financial services, insurance, media & entertainment, telecommunications, travel & hospitality, B2B), when the user wants to add business scenarios to industry pages, or when updating the use case catalog. Handles the full workflow: gathering use case details, assessing maturity level, generating content, updating the industry overview page and use case catalog, and invoking the use-case-icon-generator skill for icon creation.

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

Use when skillsaw reports a likely false positive, misses an edge case, behaves incorrectly, or needs an RFE. Gather a safe report and, only with explicit user permission, create a feedback bundle or open a GitHub issue.

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

Guided workflow for building custom AI agents using the OpenHands Software Agent SDK. Use when you want to create a new agent through an interactive interview process that gathers requirements and generates implementation plans.

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

Use when writing asyncio Python code — async/await coroutines, concurrent I/O with asyncio.gather, task creation and cancellation, semaphore rate limiting, producer-consumer queues, async context managers, async generators, WebSocket servers, aiohttp web scraping, async database operations, run_in_executor for blocking calls, or testing async code with pytest-asyncio. Covers FastAPI and aiohttp patterns, synchronization primitives, timeout handling, and common pitfalls like event loop blocking and missing await.

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