3,239 件 ・ 関連度順
概要と使いどころ
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
日本語の概要は準備中です。原文の説明を表示しています。
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
日本語の概要は準備中です。原文の説明を表示しています。
Build a persistent visual brand identity for image generation. Defines how the brand looks visually — aesthetic, lighting, composition, mood — and writes it to brand/creative-kit.md so /image-gen and other creative skills produce consistent on-brand visuals. Three modes: Extract (from website/URL), Build (interview), Reference (mood board/examples). Use when starting any project that needs images, when the user says "visual style", "brand aesthetic", "image style", "visual identity", "how should our images look", "build visual brand", "define our look", or when /image-gen outputs feel generic because no visual style exists yet.
日本語の概要は準備中です。原文の説明を表示しています。
Designs viral referral programs with incentive structures, sharing mechanics, and tracking. Covers one-sided, two-sided, tiered, and milestone models with viral coefficient calculations. Use when someone wants word-of-mouth growth, viral loops, invite programs, or says 'referral', 'viral loop', 'word of mouth', 'invite program', 'refer a friend', 'growth loop', 'referral incentive', 'affiliate program', 'ambassador program', 'get users to invite friends', or 'organic growth'. Even casual mentions like 'how do I get my users to spread the word' or 'can users invite others' should trigger this. Includes anti-fraud measures and copy templates for both referrer and referee. Use this whenever user-driven acquisition or viral mechanics are discussed.
日本語の概要は準備中です。原文の説明を表示しています。
Generate 5 different narrative scripts for visual slideshows from a single positioning angle. Each script uses a different storytelling framework (AIDA, PAS, BAB, Star-Story-Solution, Stat-Flip) producing genuinely different stories, not layout variations. Make sure to use this skill whenever the user wants slideshow scripts, TikTok content scripts, carousel copy, narrative frameworks for visual content, or says anything about writing scripts for slides or social media storytelling. Even 'write me some TikTok content' or 'I need carousel copy' should trigger this. Outputs structured YAML content specs that chain directly to /paper-marketing for visual design.
日本語の概要は準備中です。原文の説明を表示しています。
A senior marketing operator for any project. Orchestrates 76 marketing skills to build brands, generate content, and distribute across channels. Use this skill whenever the user wants to do marketing - brand voice, copy, SEO, email, social, launches, or anything marketing-related. Also triggers on 'help me market', 'write copy', 'launch strategy', 'brand voice', 'SEO', 'content', 'email sequence', 'social posts', 'landing page', 'grow', 'audience', 'competitors', 'what should I do next for marketing', 'I need more users', 'how do I get people to care', or any marketing request. When in doubt about which marketing skill to use, start here - even if the user's request is vague or doesn't explicitly mention marketing.
日本語の概要は準備中です。原文の説明を表示しています。
Cluster keywords by search intent and map each cluster to an existing or proposed page, with cannibalization detection from Search Console. Use this skill when the user has a keyword list (saved set, brand/keyword-plan.md, GSC export, or seed topic) and needs page targets, content briefs, or a site map for SEO pages — especially before seo-content or seo-machine page generation. Triggers: "cluster keywords", "keyword mapping", "map keywords to pages", "keyword cannibalization", "which page should target".
日本語の概要は準備中です。原文の説明を表示しています。
Optimizes multi-step conversion flows including signup, onboarding, upgrade, and checkout. Maps each step, identifies friction and drop-off risks, then recommends specific copy/UX changes with A/B test plans. Use when someone says 'signup flow', 'onboarding optimization', 'checkout conversion', 'paywall optimization', 'activation rate', 'funnel analysis', 'why are users dropping off', 'registration flow', 'trial conversion', 'free to paid', 'upgrade flow', 'user journey', or wants to improve any multi-step user journey. If they mention steps, screens, or a sequence that leads to signup, payment, or activation, this is the skill. Even casual mentions like 'users aren't finishing signup' or 'our onboarding sucks' should trigger this. Use this instead of page-cro when the problem spans multiple screens rather than a single page.
日本語の概要は準備中です。原文の説明を表示しています。
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".
日本語の概要は準備中です。原文の説明を表示しています。
Define or extract a consistent brand voice that other skills can use. Three modes: Extract (analyze existing content), Build (interview-based), Auto-Scrape (from URL). Use when copy sounds generic, when starting any new project, when voice feels inconsistent across channels, when onboarding a new brand, or when any skill needs voice-profile.md but it doesn't exist yet. This is always the first skill to run for a new project. Make sure to use this skill whenever the user mentions tone of voice, brand personality, 'my copy all sounds the same', 'how should I sound', 'analyze my website voice', 'define my tone', or anything about making content sound more human or distinctive. Even if the user just says 'my marketing sounds generic' — that's a voice problem.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to plan a product launch, feature announcement, release strategy, or go-to-market plan. Also use when the user mentions 'launch plan', 'go to market', 'GTM', 'Product Hunt', 'beta launch', 'how do I launch', 'pre-launch', 'launch checklist', 'distribution plan', 'release strategy', 'feature announcement', or is about to ship something and needs a distribution plan. Even vague requests like 'I'm almost done building, what now?' or 'how do I get users?' should trigger this skill. Make sure to use this whenever someone is planning ANY kind of product or feature release, even if they don't say 'launch' explicitly — if they're thinking about getting something in front of users, this is the skill. This is the STRATEGIC planner — for operational platform submissions and directory launches, see /startup-launcher instead.
日本語の概要は準備中です。原文の説明を表示しています。
Build detailed buyer personas and audience profiles from research. Use this skill whenever the user mentions audience, buyer persona, ideal customer, target market, ICP, watering holes, 'who am I selling to', customer research, or audience profile. Also use when content feels unfocused or generic (that's an audience problem), when conversion is low because messaging doesn't resonate, when starting any new project (audience should be first), or when any downstream skill needs audience.md but it doesn't exist yet. Even if the user doesn't explicitly ask for audience research, trigger this if they're writing copy or building a landing page without a clear audience defined. Three approaches: Quick Profile, Persona Build, Community Mining.
日本語の概要は準備中です。原文の説明を表示しています。
Plans free tools, calculators, generators, and interactive widgets that attract target audience through search and social sharing. Engineering as marketing — build something useful, capture leads. Use when someone wants to build a free tool for marketing, says 'free tool', 'calculator', 'generator', 'engineering as marketing', 'side project marketing', 'interactive widget', 'lead generation tool', 'SEO tool', 'growth hack', 'build something to attract users', or wants to attract users through utility rather than content. Also use when someone asks 'how do I get more signups', 'what should I build for marketing', or 'content marketing alternative' — a free tool is often the best answer. Includes search volume validation, UX flow templates, and conversion hook design.
日本語の概要は準備中です。原文の説明を表示しています。
Research companies, competitors, funding, news, leadership, and market context with Exa Agent and advanced search. Use when researching companies, competitor analysis, market research, or building company lists. Writes findings the caller can fold into brand/competitors.md or brand/landscape.md. Prefer this over ad-hoc web search for company deep dives. Distinct from competitive-intel (full brand competitive file methodology) - this skill is the Exa research engine those foundation skills should call.
日本語の概要は準備中です。原文の説明を表示しています。
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when the user wants to stress-test a plan against the project's language and documented decisions. Run BEFORE /claude-setup:build on non-trivial features in repos that have (or should have) a CONTEXT.md.
日本語の概要は準備中です。原文の説明を表示しています。
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when the user wants to stress-test a plan against the project's language and documented decisions. Run BEFORE /build on non-trivial features in repos that have (or should have) a CONTEXT.md.
日本語の概要は準備中です。原文の説明を表示しています。
Do work in an Upstash Box, a sandboxed cloud container driven through the remote Upstash MCP server (mcp.upstash.com), instead of on the local machine. Use when the user asks to run, build, test, clone, or edit something remotely, in a sandbox, in the cloud, or in a box, when the deliverable is a pull request, a public preview URL, or a screenshot of a running app, when the local machine cannot deliver (no GitHub login for gh, no way to expose a port, a dirty or slow local checkout), when several independent tasks should run in parallel on separate machines, a code factory that turns a list of tasks into a list of pull requests, or when the deliverable is a video, screen recording, demo or timelapse of a browser, web app, terminal program or agent run. Applies whenever the session has the box_* and blob_* MCP tools, even when Upstash is not named.
日本語の概要は準備中です。原文の説明を表示しています。
行业调研——researcher CLI + 多 Agent 对抗式研究引擎。输入一个行业/赛道/商业机会的模糊需求， 输出一份有据可依、经过证据校验和红蓝对抗检验的战略调研报告。内置国民经济行业分类映射、 MECE/PESTLE/波特五力等咨询框架、事前验尸法和黑格尔辩证法合题引擎。 支持精简/标准/深度三种报告深度。 触发方式：/industry-research、「行业调研」、「行业分析」、「赛道研究」、「市场调研」 Use when the user asks for industry research, sector analysis, market study, competitive landscape analysis, investment thesis research, or any request involving structured industry investigation. Also trigger when user mentions 调研报告, 行业研究, 赛道分析, 商业机会分析, 投资逻辑梳理, or similar phrases. Even casual requests like "帮我看看 XX行业怎么样" or "XX赛道值不值得做" should trigger this skill.
日本語の概要は準備中です。原文の説明を表示しています。
Design and review autonomous or semi-autonomous agent loops — systems where an agent prompts itself, runs on a schedule or event, and iterates toward a goal without a human at the keyboard. Use this whenever the user wants to build, design, harden, or audit any kind of self-running agent, agentic workflow, control loop, background worker, cron/heartbeat/webhook-driven agent, "Ralph loop", auto-PR-fixer, monitoring agent, or any long-running task that should keep going on its own until done. Trigger this even when the user says "agentic workflow", "automation that runs itself", "an agent that keeps trying until X", or "make my agent stop running away / burning tokens" without using the word "loop". Also use it to review an existing loop's stopping conditions, guardrails, verification, and escalation paths.
日本語の概要は準備中です。原文の説明を表示しています。
OpenSearch provider for obz. Supports log search and trace operations using Lucene-based query syntax. Requires --index flag. This skill should be used when the user mentions "OpenSearch", "obz -p os", or needs to search logs or traces from an OpenSearch cluster.
日本語の概要は準備中です。原文の説明を表示しています。
Grafana Loki provider for obz. Covers log search using LogQL, a label-based query language for log aggregation. This skill should be used when the user mentions "Loki", "Grafana Loki", "LogQL", "obz log search -p loki", or needs to search logs from a Loki instance.
日本語の概要は準備中です。原文の説明を表示しています。
Grafana Mimir provider for obz. Covers all 6 metric commands using standard PromQL. Mimir is a horizontally-scalable Prometheus-compatible TSDB. This skill should be used when the user mentions "Mimir", "Grafana Mimir", "obz metric -p mimir", or needs to query metrics from a Mimir cluster.
日本語の概要は準備中です。原文の説明を表示しています。
Alibaba Cloud SLS (Simple Log Service) provider for obz. Supports metrics (PromQL), logs (SLS Query), and traces across project/store pairs. Requires AccessKey auth and provider-specific flags like --project, --logstore, --metricstore, and --trace-logstore. This skill should be used when the user mentions "SLS", "Alibaba Cloud", "obz -p sls", or needs to configure SLS provider instances.
日本語の概要は準備中です。原文の説明を表示しています。
Datadog provider for obz. Supports metrics (Datadog Query Language), logs (Datadog Log Query), and traces. Requires api-key and app-key configured under auth in config.yaml. Does not support metric labels, label-values, or series commands. This skill should be used when the user mentions "Datadog", "DD", "obz -p dd", Datadog Query Language, or needs to configure Datadog provider instances with regional endpoints.
日本語の概要は準備中です。原文の説明を表示しています。