2,210 件 ・ 関連度順
概要と使いどころ
"Evaluate backlink quality using Domain Authority, Domain Rating, and trust metrics. Use this skill when the user needs to assess link profile health, identify toxic backlinks, or plan link building strategy — even if they say 'check my backlinks', 'link building', or 'domain authority analysis'.".
日本語の概要は準備中です。原文の説明を表示しています。
"Apply BCG Growth-Share Matrix to analyze a product or business unit portfolio for resource allocation decisions. Use this skill when the user needs to prioritize investments across multiple products, decide which products to grow vs harvest vs divest, or evaluate a portfolio's balance — even if they say 'which products should we invest in' or 'portfolio strategy' without naming BCG.".
日本語の概要は準備中です。原文の説明を表示しています。
"Apply the Marketing Mix (4P/7P) framework to design tactical marketing decisions across Product, Price, Place, Promotion — plus People, Process, Physical Evidence for services. Use this skill when the user needs to plan a product launch, design a go-to-market strategy, or audit their marketing mix — even if they say 'how should we price this', 'where should we sell', or 'what's our go-to-market plan'.".
日本語の概要は準備中です。原文の説明を表示しています。
"Develop brand positioning strategy including positioning statements, perceptual maps, and brand personality/archetype analysis. Use this skill when the user needs to define or refine how their brand is perceived relative to competitors, craft a positioning statement, build a brand identity framework, or map competitive positions — even if they say 'what makes us different', 'our brand feels generic', or 'how do customers see us vs competitors'.".
日本語の概要は準備中です。原文の説明を表示しています。
"Analyze supply chain operations using the SCOR model across Plan, Source, Make, Deliver, and Return processes. Use this skill when the user needs to optimize supply chain efficiency, evaluate supplier performance, improve logistics, or design an end-to-end supply chain strategy — even if they say 'our deliveries are slow', 'supply chain costs are too high', or 'we keep running out of stock'.".
日本語の概要は準備中です。原文の説明を表示しています。
"Apply STP (Segmentation, Targeting, Positioning) framework for market strategy. Use this skill when the user needs to define target customer segments, select which segments to pursue, or craft a positioning statement — even if they say 'who is our customer', 'which market should we focus on', or 'how should we position ourselves'.".
日本語の概要は準備中です。原文の説明を表示しています。
"Analyze and design pricing strategies including cost-plus, value-based, competitive, penetration, and skimming approaches with psychological pricing techniques. Use this skill when the user needs to set or change prices, evaluate pricing models, understand price elasticity, or apply psychological pricing — even if they say 'how much should we charge', 'are we priced right', or 'our margins are too low'.".
日本語の概要は準備中です。原文の説明を表示しています。
"Corporate-governance practice playbook: board composition, three lines of defense, audit/compensation/nomination committee operations, independent-director governance, stakeholder communication, IPO governance upgrade, and family-business professionalization. Use for board-structure design, independent-director selection, three-lines implementation, IPO governance preparation, major governance incidents (fraud, scandal, insider trading), or family-business corporatization. Triggers: 『董事會組成』『獨董沒發揮功能』『三道防線』『上櫃治理補強』『家族法人化』『委員會分工』『ESG 治理』『審計委員會』『薪酬委員會』『提名委員會』. For Taiwan EMBA corporate-governance/finance/law/ESG cases. Focuses on listed-company and IPO practice; governance theory: use Asgard `grad-governance`; 9-box/繼任規劃/接班人才盤點: use `ops-talent-strategy`; COSO ERM/風險地圖/風險委員會運作: use `biz-erm`.".
日本語の概要は準備中です。原文の説明を表示しています。
Safely merge GitHub pull requests using comprehensive pre-merge validation. Use this skill when the user asks to merge a PR, complete a PR workflow, or check if a PR is ready to merge. Validates CI/CD status, reviews, and conflicts before merging with the appropriate strategy.
日本語の概要は準備中です。原文の説明を表示しています。
Condense long reports, documents, or data exports into structured summaries with key findings, implications, and recommended actions. Use when the work is distilling dense content for busy readers. Do not use for original analysis, strategy formulation, or when the source material needs expert interpretation beyond summarization.
日本語の概要は準備中です。原文の説明を表示しています。
Write and cascade OKRs (Objectives and Key Results) for company, department, team, or project level. Ensure objectives are inspiring and key results are measurable outcomes. Includes weekly check-in template. Use at the start of each quarter or when aligning strategy to execution. Do not use for KPI performance reviews or daily task tracking.
日本語の概要は準備中です。原文の説明を表示しています。
Turn meeting notes, transcripts, or rough bullets into decisions, action items, owners, due dates, and follow-up queues. Use when the work is repetitive meeting cleanup or recap writing. Do not use for negotiation strategy, legal advice, or executive decision framing.
日本語の概要は準備中です。原文の説明を表示しています。
Build or refine brand positioning with audience, category, differentiators, proof, tone, JTBD signals, and competitive context. Use when marketing, founders, or GTM teams need a positioning canvas, messaging pillars, or campaign foundation. Do not use for isolated ad copy tweaks with no strategy question.
日本語の概要は準備中です。原文の説明を表示しています。
Turn launch dates, campaign inputs, and asset requests into a structured content calendar and workback plan. Use when the work is recurring marketing coordination and schedule packaging. Do not use for brand strategy, positioning design, or deep performance interpretation.
日本語の概要は準備中です。原文の説明を表示しています。
Design rigorous A/B test plans with hypothesis, sample size calculation, Minimum Detectable Effect (MDE), randomization strategy, and decision rules. Includes guardrail metrics and rollout playbook. Use when planning product experiments, conversion optimization, or data-driven feature decisions.
日本語の概要は準備中です。原文の説明を表示しています。
Standardize incoming legal or commercial contract requests into request type, missing information, priority, and review queue. Use when the work is intake routing and request cleanup. Do not use for clause interpretation, negotiation strategy, or legal advice on the agreement itself.
日本語の概要は準備中です。原文の説明を表示しています。
Build a Go-to-Market (GTM) plan for new product launches, market entries, or feature rollouts. Covers market sizing (TAM/SAM/SOM), positioning, messaging, channel strategy, pricing approach, and launch timeline. Use when preparing to bring something new to market. Do not use for ongoing marketing operations or campaign execution.
日本語の概要は準備中です。原文の説明を表示しています。
Review REST and GraphQL API designs for consistency, usability, and best practices. Covers naming conventions, versioning strategy, error format, pagination, authentication patterns, and breaking change detection. Use when reviewing API specs, designing new APIs, or auditing existing endpoints.
日本語の概要は準備中です。原文の説明を表示しています。
Review commercial contracts, NDAs, MSAs, SOWs, and vendor agreements for obligation clarity, risk allocation, termination, data handling, and negotiation red flags. Use when a user needs a structured contract summary, red flag list, fallback positions, or clause-by-clause review. Do not use as jurisdiction-specific legal advice, litigation strategy, or final legal sign-off.
日本語の概要は準備中です。原文の説明を表示しています。
Write one-page executive briefs and decision memos that turn messy inputs into a concise recommendation, options, risks, decision ask, and next steps. Use when leaders need a fast read before approving budget, policy, vendor, headcount, or strategy changes. Do not use for long-form reports, slide design, or generic summarization without a decision.
日本語の概要は準備中です。原文の説明を表示しています。
Malware reverse engineering and suspicious artifact analysis skill for defensive triage, static analysis, dynamic analysis planning, unpacking strategy, indicators of compromise, behavior summaries, YARA/Sigma ideas, and remediation guidance. Use for suspicious binaries, scripts, documents, logs, memory artifacts, sandbox reports, and malware family analysis in isolated environments.
日本語の概要は準備中です。原文の説明を表示しています。
Use when styling with Tailwind CSS v4 - @theme syntax, design token architecture, dark mode strategy, bundle size optimization, component-layer discipline, or migrating from v3
日本語の概要は準備中です。原文の説明を表示しています。
Establish project thesis before first code. Infer product type from domain/folder/README. Identify users, business model, pSEO strategy, AI-native dev approach. Maintain PROJECT_BRIEF.md as source of truth.
日本語の概要は準備中です。原文の説明を表示しています。
SWR data fetching patterns — keys and fetchers, isLoading vs isValidating, revalidation strategy, useSWRMutation, useSWRInfinite, conditional fetching
日本語の概要は準備中です。原文の説明を表示しています。