5,727 件 ・ 関連度順
概要と使いどころ
Find company & contact data. Turn your agent into a prospecting platform. Get contact information, roles, tech stack, business events, website changes, intent data. Build lead lists, research prospects, identify talent. 150M+ companies, 800M+ professionals, 50+ data sources.
日本語の概要は準備中です。原文の説明を表示しています。
Azure Cosmos DB performance optimization and best practices guidelines for NoSQL, partitioning, queries, SDK usage, and vector search. Use when writing, reviewing, or refactoring code that interacts with Azure Cosmos DB, designing data models, optimizing queries, or implementing high-performance database operations.
日本語の概要は準備中です。原文の説明を表示しています。
Perform actions in Linear (read, create, update, search issues, projects, comments, teams, cycles, labels, etc.) by writing and running small Node scripts against the official @linear/sdk TypeScript SDK with a personal API key. Use this when the user wants to do Linear work from the terminal without the Linear MCP server, or asks to list/open/create/update/close Linear issues, leave comments, or query teams, projects, users, or workflow states.
日本語の概要は準備中です。原文の説明を表示しています。
Apply the Minimum Sufficient Work (MSW) principle through the MSW Kernel to scope, execute, verify, and stop agent work. State the requested outcome and smallest proof, admit a claim only when deleting it would leave the contract unmet or unproven, do and prove each necessary claim, and halt at the fixed point. Use for implementation, debugging, review, research, planning, documentation, or any task where scope control, proportional evidence, or avoiding overwork matters. Also use when the user says MSW, Minimum Sufficient Work, do only what is necessary, avoid over-engineering, or stop when the result is proven.
日本語の概要は準備中です。原文の説明を表示しています。
Create or evolve an implementation-agnostic website design system from existing-site evidence, verified brand inputs, and an optional Visual Reference Brief. Use to establish visual and restrained-motion baselines, extract an existing site's rendered system for style-preserving extensions, validate one selected baseline with a compact Design Board, or update shared rules before page/module design. Do not conduct cross-industry reference research, map Elementor settings, create page layouts, design modules, or implement production code.
日本語の概要は準備中です。原文の説明を表示しています。
Coordinate the custom Elementor Widget site workflow for kickoff, lightweight company intake, conditional reference research, new-versus-existing site style routing, uncertain next steps, project resumption, or continuous work across content, Design Systems, UI, HTML, and Widget implementation. Do not use for release, old-Widget troubleshooting, theme development, or remote WordPress management.
日本語の概要は準備中です。原文の説明を表示しています。
Bind this repo to an OpenSEO project and prepare the local SEO state directories. Use this skill when starting SEO work on a fresh project, when `.seo/openseo.json` does not exist yet, when the OpenSEO project id is unknown, or when Google Search Console needs connecting before keyword or rank work can start. Triggers: "set up openseo", "link seo project", "connect gsc", "start seo for this site", "openseo project id".
日本語の概要は準備中です。原文の説明を表示しています。
Build an organic-traffic operating system for any site or app: a multi-phase, resumable engine that plans and ships a BATCH ROADMAP of landing pages (use-cases, playbooks, /for/ pages, roundups) on top of real keyword research, with a persistent phase tracker. Use when the user says 'SEO machine', 'build organic traffic', 'rank on Google', 'we need traffic', 'SEO roadmap', 'batch of pages', 'pages roadmap', or 'build an SEO engine'. Distinct from `seo-audit` (one-off diagnostic) and `seo-content` (single-article writer): this skill owns the multi-page roadmap, run sequencing, page generation, internal linking, and the persistent phase tracker across the whole run. For a single alternatives or vs/comparison page, see /competitor-alternatives; for programmatic SEO templates and content at scale, see /seo-content; for off-page link building, see /off-page-seo. Resumable — every invocation continues the last run.
日本語の概要は準備中です。原文の説明を表示しています。
Find the angle that makes something sell. Use this skill whenever the user mentions positioning, angles, differentiation, unique selling proposition, 'how do I stand out', 'what makes us different', value proposition, messaging framework, or 'find the hook'. Also trigger when copy isn't converting (often a positioning problem), when marketing feels generic, when launching a product, creating a lead magnet, writing a landing page, or entering a crowded market. Even if the user is about to write copy without established positioning, run this first — the angle informs everything downstream. Generates 3-5 positioning angles with competitive web research and validation.
日本語の概要は準備中です。原文の説明を表示しています。
Friendly SEO coach mode for the mktg + OpenSEO stack. Use this skill when the user is new to SEO, unsure which SEO workflow to run, asks "what does OpenSEO do", wants strategy explained in plain language, or needs help choosing between keyword research, clustering, competitive analysis, and link prospecting. Triggers: "seo coach", "new to seo", "explain openseo", "what seo should i do", "seo strategy help".
日本語の概要は準備中です。原文の説明を表示しています。
Trigger when: (1) User wants to create an educational/explainer video, (2) User has a vague concept they want visualized, (3) User mentions "3b1b style" or "explain like 3Blue1Brown", (4) User wants to plan a Manim video or animation sequence, (5) User asks to "compose" or "plan" a math/science visualization. Transforms vague video ideas into detailed scene-by-scene plans (scenes.md). Conducts research, asks clarifying questions about audience/scope/focus, and outputs comprehensive scene specifications ready for implementation with ManimCE or ManimGL. Use this BEFORE writing any Manim code. This skill plans the video; use manimce-best-practices or manimgl-best-practices for implementation.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a user needs SCI/SCIE/ESCI/SSCI journal-submission help: evidence-backed candidate-journal discovery from a title, abstract, keywords, or manuscript text; public-metric and risk lookup for a known journal; or a pre-submission compliance check of a draft against a chosen journal's Author Guidelines and same-journal conventions. Also for Chinese requests such as 选刊、投稿期刊推荐、期刊查询、中科院分区、投稿前检查、期刊要求核对. This skill produces candidates, evidence, checks, and uncertainty; it does not judge research quality, predict acceptance, choose a uniquely best journal, draft prose, or simulate peer review.
日本語の概要は準備中です。原文の説明を表示しています。
Use for every coding task. Enforce strict TDD workflow: activate Serena, investigate first, clarify+confirm requirements, write per-task REQUIREMENTS.md in .requirements/<datetime>_<feature_name>/, verify APIs via web search, then implement in tiny test-verified steps.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when the user wants local Obsidian note or metadata work done primarily through documented official desktop `obsidian` CLI commands, with limited local vault filesystem support when needed for parent folders, path checks, ambiguity resolution, verification, or safe vault structure operations. Best for local vault search, note reads, exact-path note updates, backlinks, tasks, properties, templates, and local history. Do not use it for runtime admin, devtools diagnostics, workspace/navigation administration, community tools, `obsidian://` launcher tasks, Headless Sync or Publish workflows, or plugin-specific APIs.
日本語の概要は準備中です。原文の説明を表示しています。
Delegate implementation (or, when explicitly requested, research) to GPT-6.1 Sol (high reasoning; xhigh on request) via Codex CLI. Claude plans, orchestrates, and reviews; Sol writes the code.
日本語の概要は準備中です。原文の説明を表示しています。
中国法条、案例、法规、企业风险与引用核验检索工具。当企业法务专家需要当前中国法律条文、案例、法规、企业风险数据或引用核验时使用。需要用户配置 YD_API_KEY；付费 API 调用消耗额度。
日本語の概要は準備中です。原文の説明を表示しています。
专业技术选型与方案调研顾问。当用户需要做技术选型决策、调研某项技术方向、评估候选方案、寻找最优解时使用。支持：学术论文检索（ArXiv/Google Scholar）、大厂工程博客分析、竞品/开源方案对比、跨行业类比迁移、多维评估打分矩阵、结合业务约束给出可落地的双方案推荐。触发词：技术选型、技术调研、方案调研、技术评估、调研一下、研究一下技术方案、怎么做比较好、业界怎么做、有哪些方案、选哪个好。
日本語の概要は準備中です。原文の説明を表示しています。
搜索微信公众号文章技能。通过微信搜索获取文章列表，覆盖科技/AI、社会热点、财经、教育、职场等各类中文资讯；可按关键词检索并返回标题、概要、发布时间、来源公众号与链接。当用户需要查找微信公众号文章、整理参考资料或快速获取文章信息时使用此技能。
日本語の概要は準備中です。原文の説明を表示しています。
关键词研究与主题聚类策略工具集。提供搜索意图分析、竞品 SERP 分析、主题聚类设计、 内容优先级排序和关键词蚕食防护功能。 触发词：关键词研究、竞品分析、主题聚类、搜索意图、长尾词、关键词难度
日本語の概要は準備中です。原文の説明を表示しています。
International journal scout — searches candidate SCI/SSCI/EI/Scopus journals via Wanfang foreign journal API, performs L1 deterministic rejection screening, and L2 citation fingerprint analysis.
日本語の概要は準備中です。原文の説明を表示しています。
智数分析专家团主理人（诺亚 Nova · 首席数据编排师）。协调 5 位专业成员（sql-analyst、data-scientist、knowledge-researcher、dashboard-designer、report-composer）按预设 Workflow 完成端到端数据分析交付。 触发词："分析数据"、"生成报告"、"数据画像"、"查数据库"、"数据分析"、"帮我分析"、"数据可视化"、"仪表盘"。 路由逻辑：单一维度任务走单 agent 直调；综合性任务走对应 Workflow。
日本語の概要は準備中です。原文の説明を表示しています。
知识检索专家（瑞卡 Rika）。使用 RAG 技术处理多格式文档（PDF/Word/Excel/Markdown/HTML），构建向量知识库，进行语义检索并为问答提供带来源引用的上下文增强回答。 触发词：由 copilot-team-lead 主理人调度执行，不直接面向用户。当主理人下发文档检索、知识提取或 Phase 4 知识增强任务时激活。
日本語の概要は準備中です。原文の説明を表示しています。
深度研究团队主理人（顾全之 · 研究主编）。带领 6 位专业成员按 5 阶段工作流（初调→规划→逐章深研→报告组装→发布输出）完成系统性深度研究，输出带多源引用的专业研究报告。 触发词：深度研究、行业研究、竞品分析、市场调研、学术综述、出一份研究报告、专题研究、趋势分析、技术综述。
日本語の概要は準備中です。原文の説明を表示しています。
On-demand journal peer review simulation expert — supports 7 research paradigms (experimental/computational/empirical_survey/interpretive/mixed_methods/systematic_review/interdisciplinary) with 6-step review workflow, outputting targeted revision suggestions based on journal-specific review standards.
日本語の概要は準備中です。原文の説明を表示しています。