6,477 件 ・ 関連度順
概要と使いどころ
Run a full Section 508 + WCAG 2.2 Level AA accessibility audit on a federal / .gov / public-sector website or ICT product. Triggers: "Section 508", "508 audit", "WCAG", "VPAT", "ACR".
日本語の概要は準備中です。原文の説明を表示しています。
Analyzes apparel demand prediction systems for trend forecasting, size curve optimization, color and style analytics, sell-through rate tracking, and markdown optimization following CPFR collaborative planning and GTIN product identification standards..
日本語の概要は準備中です。原文の説明を表示しています。
Analyze pharmaceutical batch production records for yield optimization, process parameter tuning, deviation trending, and cycle time reduction under cGMP compliance. Triggers: phrases: "optimize batch yield", "analyze batch records", "pharma manufacturing analysis".
日本語の概要は準備中です。原文の説明を表示しています。
Write press releases for product launches, funding announcements, partnerships, executive hires, and milestones using the Inverted Pyramid (AP journalism) and Ogilvy on Headlines (David Ogilvy, Ogilvy on Advertising). The lede answers Who/What/When/Where/Why in 40 words or fewer. The headline selects the right audience and promises a specific benefit. Use when the user asks for a press release, media release, news announcement, PR for X, launch announcement, funding announcement, or "write a press release". Reads brand voice and positioning from knowledge/. For pitching it to a journalist, see pr-pitch-writer. For the customer story behind it, see case-study-writer.
日本語の概要は準備中です。原文の説明を表示しています。
Design product experiments to test hypotheses. Use when the user says "run an experiment", "A/B test this", "build-measure-learn", "validate this assumption", "test this hypothesis", "we don't know if this will work", "minimum viable test", "lean experiment", or wants to reduce risk before fully building a feature - even if they don't explicitly say "experiment".
日本語の概要は準備中です。原文の説明を表示しています。
Build Opportunity Solution Trees using Teresa Torres' framework for structured product discovery. Use this skill when: - You need to map a desired outcome to opportunities, solutions, and experiments - You want to decide WHAT to build next based on user research and discovery data - You have workshop findings, pilot feedback, or user research to structure into actionable options - You need a visual tree diagram showing the path from outcome to testable experiments
日本語の概要は準備中です。原文の説明を表示しています。
Capture learnings from a campaign, launch, sprint, or initiative using Five Whys (Taiichi Ohno, Toyota Production System) for root cause analysis and Start-Stop-Continue for action planning. Append reusable insights to knowledge/learnings.md so future runs of the OS get smarter. Use when the user asks for a retro, retrospective, post-mortem, "what did we learn", "campaign wrap-up", "lessons learned", or after a campaign or launch ends. Critical feedback loop that makes the OS compound over time. For the numbers review itself, see kpi-review. For planning the next campaign, see campaign-brief.
日本語の概要は準備中です。原文の説明を表示しています。
Conduct a competitive analysis. Use when the user says "competitive analysis", "how do competitors handle X", "market landscape", "blue ocean", "strategy canvas", "what does [competitor] do", "compare us to X", "positioning analysis", "value curve", or wants to understand how a product or feature compares to alternatives - even if they don't explicitly say "competitive analysis".
日本語の概要は準備中です。原文の説明を表示しています。
Quality gate for product specifications before stakeholder review. Use this skill when: - A spec draft is ready and you want to validate it before sending to Engineering, Design, and QA - You want to check a spec against your template's completeness rules - You need to catch vague language, missing sections, or gaps before review - You want a pass/fail scorecard with specific fix suggestions
日本語の概要は準備中です。原文の説明を表示しています。
Extract UX tasks from a product spec and save as ux-tasks.md in the same spec folder. Use this skill when: - The user wants to generate UX work items from a spec - The user says "UX tasks", "what does UX need to do", "extract UX work", "UX deliverables" - The user wants to hand off a spec to the UX/design team - The user asks "what screens need designing" or "what UX decisions are open"
日本語の概要は準備中です。原文の説明を表示しています。
Plan a marketing campaign end-to-end using Allan Dib's Before/During/After framework (The 1-Page Marketing Plan). Produces a phase-specific campaign brief with goal, audience, message, channels, assets, timeline, budget, and success metrics. Use when the user asks to plan a campaign, brief a campaign, "we need a campaign for X", launch plan, GTM plan, marketing plan for <product>, demand gen plan, or any multi-channel marketing initiative. Reads ICP, services, and KPIs from knowledge/. For a full quarterly strategy rather than one campaign, see marketing-plan scope in positioning-doc and kpi-review. For the content schedule inside the campaign, see social-calendar. For the post-campaign review, see retro.
日本語の概要は準備中です。原文の説明を表示しています。
Write a blameless postmortem after an incident. Use when the user says "postmortem", "post-incident review", "PIR", "what happened in that incident", "incident review", "blameless postmortem", "5 whys", "how do we prevent this again", or needs to document learnings from a production incident - even if they don't explicitly say "postmortem".
日本語の概要は準備中です。原文の説明を表示しています。
Design statistically rigorous experiments to test data science hypotheses. Use when the user says "design an A/B test", "run an experiment", "test this hypothesis", "is this difference significant", "how many samples do I need", "randomized controlled trial", "causal inference", "uplift test", "holdout group", "significance test", "power calculation", "avoid p-hacking", or needs to determine whether an observed effect is real before making a product or model decision.
日本語の概要は準備中です。原文の説明を表示しています。
Document a machine learning model in a structured, transparent format for stakeholders, reviewers, and future maintainers. Use when the user says "document this model", "write a model card", "model documentation", "how should I document my ML model", "bias and fairness report", "model transparency", "what does this model do", "model handoff", "production model documentation", or needs to communicate what a model does, how it was built, where it works, and where it fails.
日本語の概要は準備中です。原文の説明を表示しています。
ハンズオンの「課題・解決策の一言」から、時間枠内で作れる実装スコープ（scope.md）を対話形式で固めていくスキル。projects/<name>/ に input.md → idea.md → scope.md を順に書き出す。/scope-design で明示起動。
projects/<プロジェクト名>/ 配下のファイルをまとめて ZIP にして、成果物として持ち帰れるようにするスキル。node_modules / .venv / __pycache__ など再生成可能なビルド成果物は自動で除外する。/archive-project で明示起動。
ハンズオンで作った動くアプリを「商品として売り出す」視点で見直し、ペライチのランディングページ（LP）を作る対話スキル。動くアプリを実際に触りながらコピーを練り、最後に frontend-design スキルを自動で呼び出して HTML 実物まで一気に着地させる。標準構成では /verify-project の後に本線として実施する（30〜50分）。/landing-page-design で明示起動。
scope.md をもとに Next.js アプリを projects/<name>/apps/ に実装する対話スキル。MVP を一括生成したあと「完了」で終わらず、想定ユーザー1人になりきって触る → 1サイクル1改善のチューニングを回し続けて体験を磨く。/scope-design の後、/verify-project の前に実行する。/build-app で明示起動。
ハンズオンで実装したプロダクトを「もし実際にデリバリーするなら」の観点で棚卸しし、足りない知識を学習計画（study-plan.md）に落とすスキル。ローカルで動作確認できる範囲で実装した前提。`/verify-project` 後・ピッチ前に実行してメタ認知してから登壇する。/study-plan で明示起動。
ハンズオンで実装したプロダクトを「作ったものを評価する」観点で検証し、その結果をピッチ発表の骨子（verification.md）としてまとめる対話スキル。検証と発表準備を同じ流れで進める。ペアフィードバックのリハーサル素材にもなる。/verify-project で明示起動。
Comprehensive guide for discovering, understanding, and installing Claude Code skills from skills.sh marketplace. Use this skill when users want to (1) browse or search skills.sh for recommendations, (2) get skill recommendations by role (developer, marketer, designer, product manager), (3) understand how a specific installed skill works by reading and explaining its SKILL.md, (4) learn the anatomy and structure of skills, or (5) find and install skills that match their specific workflow needs. This is NOT for creating new skills (use skill-creator instead).
日本語の概要は準備中です。原文の説明を表示しています。
Cluster keywords by SERP overlap and design hub-and-spoke content architecture with internal links. Use for planning only; use the blog-cluster command to execute article production.
日本語の概要は準備中です。原文の説明を表示しています。
Generate JSON-LD for ONE blog post (BlogPosting with Person, Organization, BreadcrumbList, ImageObject, VideoObject; FAQPage only as optional entity markup) in a single @graph, and check it against Google's current structured data support. Use when the user says "generate schema", "json-ld for this post", "blog schema". Not for auditing schema across a whole site or other schema types (claude-seo seo-schema), not for product pages, and not a promise of rich results: FAQ rich results ended 2026-05-07.
日本語の概要は準備中です。原文の説明を表示しています。
Audit paid-ad copy, images, video, hooks, concepts, format coverage, platform-native fit, message match, creative fatigue, accessibility, and policy across supported platforms. Use for creative audit, ad creative, creative fatigue, creative diversity, ad copy review, video review, image review, or production priorities.
日本語の概要は準備中です。原文の説明を表示しています。