1,799 件 ・ 関連度順
概要と使いどころ
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Converts structured prospect research into concise outreach preparation briefs. Use when the user provides prospect or account research and wants a brief with context, angles, and claims to verify. It generates a research brief and must not invent personalization or send outreach.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Converts inconsistent job titles into standardized role, department, and seniority labels. Use when the user provides records with free-text titles and wants consistent role family, department, and seniority fields.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
可变体的 warm editorial 演示设计系统，用于 presentation、case sharing、项目汇报、战略叙事和产品发布。支持横向全屏 HTML deck 与程序化 PPTX，通过 style profile、语义 slide manifest、构图新颖度规划和反重复验证，在保持编辑设计 DNA 的同时避免固定配色、固定卡片和固定 11 页模板。用户要求 Pfizer/Anthropic/warm editorial/编辑设计风格、类似血液科那套，或需要高规格且非模板化的 HTML/PPT 演示时使用。
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Resolve, validate, and audit manuscript integrity and applicable requirements for academic manuscripts and paper artifacts. Use when Codex needs to determine active paper rules from manuscript state, paper type, venue, submission stage, or workflow mode; lint a LaTeX paper project; assess submission readiness; create or update a paper policy profile; explain why a rule is active; or validate the paper-policy registries. Do not use as the primary skill for prose drafting, peer review, rebuttal writing, citation discovery, or figure/table creation.
日本語の概要は準備中です。原文の説明を表示しています。
Control and interact with a live browser session on any scraped page — click buttons, fill forms, navigate flows, and extract data using natural language prompts or code. Use when the user needs to interact with a webpage beyond simple scraping: logging into a site, submitting forms, clicking through pagination, handling infinite scroll, navigating multi-step checkout or wizard flows, or when a regular scrape failed because content is behind JavaScript interaction. Also useful for authenticated scraping via profiles. Triggers on "interact", "click", "fill out the form", "log in to", "sign in", "submit", "paginated", "next page", "infinite scroll", "interact with the page", "navigate to", "open a session", or "scrape failed".
日本語の概要は準備中です。原文の説明を表示しています。
Use at the start of a Codex task to inspect repo readiness, project profile, monorepo shape, role docs, spec status, knowledge index, and recommend the next workflow.
日本語の概要は準備中です。原文の説明を表示しています。
Exasol database interaction via the exapump CLI and Exasol SQL. Covers SQL queries and DML/DDL such as `SELECT`, `INSERT`, `UPDATE`, `DELETE`, `MERGE`, `CREATE TABLE`, `ALTER TABLE`, and `DROP TABLE`, `CREATE CONNECTION` connection objects without import or export intent, schema inspection, table design, `exapump sql` and `exapump profile`, query profiling, analytics, and Exasol-specific SQL behavior outside exasol-import and exasol-export.
日本語の概要は準備中です。原文の説明を表示しています。