3,245 件 ・ 関連度順
概要と使いどころ
Identifies missing information required to complete qualification, segmentation, or outreach preparation. Use when the user provides records and a goal and wants prioritized research gaps with sources.
日本語の概要は準備中です。原文の説明を表示しています。
Ranks companies or accounts by strategic relevance and opportunity. Use when the user provides accounts and wants a priority score, tier, rationale, risks, and next action.
日本語の概要は準備中です。原文の説明を表示しています。
Qualifies and scores B2B prospects against a supplied ideal customer profile. Use when the user provides a lead list, company records, prospect data, or qualification criteria and wants prioritization, fit analysis, or disqualification reasons.
日本語の概要は準備中です。原文の説明を表示しています。
Compares a group of companies by products, positioning, market focus, and differentiators. Use when the user provides several company records and wants a structured competitive comparison.
日本語の概要は準備中です。原文の説明を表示しています。
Classifies professional profiles into buyer, influencer, user, decision-maker, founder, recruiter, or other personas. Use when the user provides profiles and wants persona labels with evidence and confidence. Must not infer sensitive personal attributes.
日本語の概要は準備中です。原文の説明を表示しています。
Converts a job description into a structured candidate-sourcing workflow. Use when the user provides a role and wants candidate criteria, search terms, source recommendations, and a screening process. Must avoid sourcing on sensitive personal attributes.
日本語の概要は準備中です。原文の説明を表示しています。
Normalizes and improves the consistency of prospect-list data. Use when the user provides a messy prospect or lead export and wants standardized records, flagged issues, and a cleanup summary.
日本語の概要は準備中です。原文の説明を表示しています。
Divides records into geographic or account-ownership territories. Use when the user provides records with location or account data and wants consistent territory assignments with unresolved locations flagged.
日本語の概要は準備中です。原文の説明を表示しています。
Assesses the quality, composition, and usefulness of a lead list. Use when the user provides a lead list and wants completeness, distribution, quality issues, and recommended next actions.
日本語の概要は準備中です。原文の説明を表示しています。
Identifies likely duplicate profiles or companies using available record evidence. Use when the user provides a list and wants duplicate groups, match confidence, and merge recommendations. Describe records as likely duplicates unless there is an exact deterministic match.
日本語の概要は準備中です。原文の説明を表示しています。
Analyzes a dataset of companies or profiles to identify market patterns. Use when the user provides a larger dataset and wants segments, dominant categories, gaps, and emerging patterns.
日本語の概要は準備中です。原文の説明を表示しています。
Use the Crabbox wrapper for OpenClaw remote validation across Linux, macOS, Windows, and WSL2, including delegated Blacksmith Testbox proof. Report the actual provider and id.
日本語の概要は準備中です。原文の説明を表示しています。
Use when exposing app features to App Intents, Shortcuts, Siri, Spotlight, widgets, controls, or system actions — small safe AppIntents, AppShortcutsProvider, AppEnum/AppEntity, parameters, and open-vs-background behavior.
日本語の概要は準備中です。原文の説明を表示しています。
Re-analyze an existing GitHub Issue using its current title and body as input, refresh the implementation plan against the latest code state, and update the Issue in place. Use this when the user provides an Issue number (numeric, `#`-prefixed, or Issue URL) and wants to regenerate the Explore-based analysis. For reflecting comment-driven updates instead, use update-issue. For creating a brand-new Issue from a natural-language task description, use create-issue.
日本語の概要は準備中です。原文の説明を表示しています。
Create an implementation plan and a GitHub Issue based on the task description provided as an argument. Use this when the user supplies a natural-language task description (not an issue number) and wants a new implementation-ready Issue. If the input is an existing issue number, use create-issue-from-issue-number (re-analyze) or update-issue (reflect comments) instead.
日本語の概要は準備中です。原文の説明を表示しています。
Web search, content extraction, crawling, and deep research via the Tavily CLI. Use this skill whenever the user wants to search the web, find articles, research a topic, look something up online, extract content from a URL, grab text from a webpage, crawl documentation, download a site's pages, discover URLs on a domain, or conduct in-depth research with citations. Also use when they say "fetch this page", "pull the content from", "get the page at https://", "find me articles about", or reference extracting data from external websites. This provides LLM-optimized web search, content extraction, site crawling, URL discovery, and AI-powered deep research — capabilities beyond what agents can do natively. Do NOT trigger for local file operations, git commands, deployments, or code editing tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Integrate authentication and authorization flows with provider-specific setup and RBAC safeguards.
日本語の概要は準備中です。原文の説明を表示しています。
Review a GitHub pull request and provide structured feedback with severity ratings
日本語の概要は準備中です。原文の説明を表示しています。
AI citability scoring and optimization. Analyzes web page content to determine how likely AI systems (ChatGPT, Claude, Perplexity, Gemini) are to cite or quote passages from the page. Provides a citability score (0-100) with specific rewrite suggestions.
日本語の概要は準備中です。原文の説明を表示しています。
AI crawler access analysis. Checks robots.txt, meta tags, and HTTP headers to determine which AI crawlers can access the site. Provides a complete access map and recommendations for maximizing AI visibility while maintaining appropriate control.
日本語の概要は準備中です。原文の説明を表示しています。
Use when editing .vue files, creating Vue 3 components, writing composables, or testing Vue code - provides Composition API patterns, props/emits best practices, VueUse integration, and reactive destructuring guidance
日本語の概要は準備中です。原文の説明を表示しています。
Use when managing Node.js dependencies with pnpm - provides workspace setup, catalogs, CLI commands, overrides, and CI configuration
日本語の概要は準備中です。原文の説明を表示しています。
Symptom → root-cause lookup table for nuxt-crouton's recurring failure modes — exact error strings mapped to their known cause, fix, and evidence issue. Use when you hit an error you don't recognize in this repo, before debugging from first principles. Trigger phrases and symptoms: "Cannot resolve entry module .nuxt/hub/db/schema.entry.ts", "Could not load '@fyit/crouton'", "No migrations present", "No schema files found", "$setup.t is not a function", "does not provide an export named 'Map'", "no such table: translations_ui", "collection pages 500 in production", "the build was green but the app is broken", "is this a known issue?".
日本語の概要は準備中です。原文の説明を表示しています。
Use when writing, editing, debugging, or reviewing dealer language code in btn, dlr, or script files. Provides the complete dealer DSL syntax reference for bridge hand generation constraints.
日本語の概要は準備中です。原文の説明を表示しています。