5,686 件 ・ 関連度順
概要と使いどころ
Turns an ICP or research goal into a plan for finding and scraping suitable directories. Use when the user has a target audience but is unsure where to find them, and wants source categories, queries, and an extraction workflow.
日本語の概要は準備中です。原文の説明を表示しています。
Assesses potential suppliers against defined commercial, operational, and compliance requirements. Use when the user provides supplier records plus sourcing requirements and wants a consistent shortlist with strengths and risks.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Designs an end-to-end process for finding, extracting, enriching, qualifying, and exporting leads. Use when the user wants a repeatable lead workflow plan rather than a single source plan.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Turns company records into structured company research summaries. Use when the user provides company names or records and wants a consistent overview, market position, and relevance assessment.
日本語の概要は準備中です。原文の説明を表示しています。
Divides a lead list into useful commercial segments. Use when the user provides a combined lead list and wants segments with criteria, sizes, recommended treatment, and priority.
日本語の概要は準備中です。原文の説明を表示しています。
Creates a repeatable process for researching and comparing companies. Use when the user wants a structured, reusable company-research workflow with objectives, sources, fields, and validation.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Groups companies by industry, business model, size, maturity, market, or strategic fit. Use when the user provides company records and wants consistent segment assignments with definitions and confidence.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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 company names, industries, domains, locations, and descriptions. Use when the user provides company records and wants consistent canonical fields with confidence and unresolved items flagged.
日本語の概要は準備中です。原文の説明を表示しています。
Use after PROJECT_GUIDE.md exists, when the user asks if a project is worth their time, should they build vs buy, or invokes project-worth-my-time. Follow-up to explain-new-project—weighs project context (files, git history, chat) to recommend whether to invest in a repo, cherry-pick a feature, park the idea, pass, or use an existing polished product instead. Optionally enriched by a personal-memory MCP (e.g. Pieces) when one is available.
日本語の概要は準備中です。原文の説明を表示しています。
Crawl websites and extract content from multiple pages via the Tavily CLI. Use this skill when the user wants to crawl a site, download documentation, extract an entire docs section, bulk-extract pages, save a site as local markdown files, or says "crawl", "get all the pages", "download the docs", "extract everything under /docs", "bulk extract", or needs content from many pages on the same domain. Supports depth/breadth control, path filtering, semantic instructions, and saving each page as a local markdown file.
日本語の概要は準備中です。原文の説明を表示しています。
Route ordinary public-web information tasks to the correct Tavily CLI operation. Use when the task concerns publicly accessible webpages and needs web discovery, clean extraction, URL mapping, same-site crawling, or public-web-only research, but the exact Tavily operation is not yet clear or several operations must be sequenced. Prefer the specific leaf skill when intent is clear: tavily-search for discovery without a URL, tavily-extract for known URLs, tavily-map for URL/site-structure discovery, tavily-crawl for content from many pages on one site, tavily-research for cited multi-source synthesis, and tavily-dynamic-search for programmatic filtering with context isolation. Do not use for named social/community/media/career/code platforms, login or cookie-dependent content, platform-native discussions, or cross-platform collection; use Agent Reach there. Do not use for local files, Git operations, deployments, or ordinary code editing.
日本語の概要は準備中です。原文の説明を表示しています。
Formats plain text or markdown files with frontmatter, titles, summaries, headings, bold, lists, and code blocks. Use when user asks to "format markdown", "beautify article", "add formatting", or improve article layout. Outputs to {filename}-formatted.md.
日本語の概要は準備中です。原文の説明を表示しています。
AI image generation with OpenAI GPT Image 2, Azure OpenAI, Google, OpenRouter, DashScope, Z.AI GLM-Image, MiniMax, Jimeng, Seedream, Replicate and Agnes APIs. Supports text-to-image, reference images, aspect ratios, and batch generation from saved prompt files. Sequential by default; use batch parallel generation when the user already has multiple prompts or wants stable multi-image throughput. Use when user asks to generate, create, or draw images.
日本語の概要は準備中です。原文の説明を表示しています。
UI/UX design intelligence for web, mobile, and desktop. This skill should be used when designing, building, reviewing, or fixing interfaces, including pages, components, design systems, accessibility, interaction, responsive layout, typography, color, charts, and stack-specific UI implementation. Searchable local data: 79 searchable styles (50 active), 192 product palettes and reasoning profiles, 74 font pairings, 119 UX guidelines, 105 icons, 17 GSAP presets, 25 chart types, and 22 stacks.
日本語の概要は準備中です。原文の説明を表示しています。
Use when tasks involve reading, creating, or reviewing PDF files where rendering and layout matter; prefer visual checks by rendering pages (Poppler) and use Python tools such as `reportlab`, `pdfplumber`, and `pypdf` for generation and extraction.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates (.potx), layouts, speaker notes, or comments. Trigger whenever the user mentions "deck," "slides," "presentation," or references a .pptx or .potx filename, regardless of what they plan to do with the content afterward. If a .pptx or .potx file needs to be opened, created, or touched, use this skill.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.
日本語の概要は準備中です。原文の説明を表示しています。
Design, audit, harden, review, or upgrade MCP servers and MCP Apps with revision-aware protocol profiles, explicit HTTP/deployment boundaries, capability-centered validation, bilingual reporting, and reproducible evidence. Use for MCP server architecture, JSON-RPC or Streamable HTTP bugs, security hardening, protocol-version migration, MCP Apps widget boundaries, review reconciliation, test planning, and public engineering evidence.
日本語の概要は準備中です。原文の説明を表示しています。
Pull the latest GEO-SEO skill updates from the upstream repository. Compares installed files against the latest release, shows what changed, and updates all skills, agents, scripts, and schema templates in place.
日本語の概要は準備中です。原文の説明を表示しています。