1.9万 件 ・ 関連度順
"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.".
日本語の概要は準備中です。原文の説明を表示しています。
"SME and family-business management for Taiwan's industrial structure (98% SME, 70%+ family-controlled listed). Integrates four pillars: resource-constrained decision-making, family governance (Tagiuri-Davis three circles), four-layer succession, and professionalization. Use for sub-200-employee strategy, capital-constrained prioritization, family-vs-professional-manager conflict, founder handover, family-constitution design, or SME financing limits. Triggers: 『二代接班』『家族企業』『中小企業』『家族憲章』『家族辦公室』『傳承規劃』『小公司策略』『資源有限』『家族跟專業經理人』『三圓模型』『隱形冠軍』. For 成大 EMBA SME strategy, 政大 EMBA family-business succession, 逢甲 EMBA SME management cases. Fills Asgard gaps in resource-constrained strategy and Chinese-family governance.".
日本語の概要は準備中です。原文の説明を表示しています。
"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'.".
日本語の概要は準備中です。原文の説明を表示しています。
Design API and module boundaries with clear contracts, error semantics, pagination, and additive compatibility. Use before implementing REST/GraphQL endpoints, SDKs, or public module APIs.
日本語の概要は準備中です。原文の説明を表示しています。
"Conduct SWOT analysis with TOWS matrix for strategic planning. Use this skill when the user needs to evaluate a company, product, or project by identifying strengths, weaknesses, opportunities, and threats, or wants to generate strategic options from internal and external factors. Also use when the user mentions competitive positioning, strategic assessment, or asks 'what are our advantages and risks', even without naming SWOT explicitly.".
日本語の概要は準備中です。原文の説明を表示しています。
"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'.".
日本語の概要は準備中です。原文の説明を表示しています。
"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'.".
日本語の概要は準備中です。原文の説明を表示しています。
"Apply Theory of Constraints (TOC) to identify and manage system bottlenecks. Use this skill when the user needs to find what limits throughput, optimize a constrained process, apply the Five Focusing Steps, or implement Drum-Buffer-Rope scheduling — even if they say 'our output is stuck', 'what's the bottleneck', or 'why can't we produce more'.".
日本語の概要は準備中です。原文の説明を表示しています。
"Implement VCG mechanism for incentive-compatible ad slot allocation with truthful bidding. Use this skill when the user needs to design a truthful auction mechanism, compute externality-based payments, or understand why platforms may prefer GSP over VCG — even if they say 'truthful auction design', 'VCG payments', or 'incentive-compatible mechanism'.".
日本語の概要は準備中です。原文の説明を表示しています。
"Build credit scoring models to predict default probability from borrower characteristics. Use this skill when the user needs to assess creditworthiness, build a credit scorecard, or evaluate lending risk — even if they say 'predict default risk', 'credit scoring', or 'loan approval model'.".
日本語の概要は準備中です。原文の説明を表示しています。
"Apply Bayesian averaging to rank items by combining observed ratings with prior expectations. Use this skill when the user needs to rank items with varying review counts, build a 'top rated' list that handles low-sample items fairly, or implement IMDB-style weighted rating — even if they say 'weighted average rating', 'IMDB formula', or 'ranking with prior'.".
日本語の概要は準備中です。原文の説明を表示しています。
"Calculate Altman Z-Score to predict corporate bankruptcy probability from financial ratios. Use this skill when the user needs to assess a company's financial distress risk, screen for bankruptcy-prone firms, or evaluate credit worthiness — even if they say 'bankruptcy prediction', 'financial distress score', or 'Z-score analysis'.".
日本語の概要は準備中です。原文の説明を表示しています。
"Implement Statistical Process Control charts to monitor production process stability. Use this skill when the user needs to detect process shifts, set control limits, or distinguish common cause from special cause variation — even if they say 'process monitoring', 'control chart', or 'is our process in control'.".
日本語の概要は準備中です。原文の説明を表示しています。
"Implement Generalized Second Price auction for ad slot allocation and pricing. Use this skill when the user needs to understand search ad auctions, compute ad positions and costs-per-click, or analyze bidding dynamics — even if they say 'how does Google Ads auction work', 'ad rank calculation', or 'second price auction for ads'.".
日本語の概要は準備中です。原文の説明を表示しています。
"Build CTR prediction models for estimating ad click-through rates from features. Use this skill when the user needs to predict click probability, build an ad ranking model, or evaluate ad creative performance — even if they say 'predict click rate', 'ad relevance scoring', or 'which ad will get more clicks'.".
日本語の概要は準備中です。原文の説明を表示しています。
Design agent tools and CLI surfaces—schemas, naming, errors, idempotency, and discoverability for LLM callers. Use when defining tools for agents, SDKs, or AI-native CLIs.
日本語の概要は準備中です。原文の説明を表示しています。
"Design multi-objective e-commerce product ranking combining relevance, conversion, and business metrics. Use this skill when the user needs to build a product ranking system beyond text relevance, balance relevance with commercial objectives, or implement learning-to-rank — even if they say 'product sorting', 'search result ranking', or 'how to rank products'.".
日本語の概要は準備中です。原文の説明を表示しています。
Begeleidt het opnemen, nabewerken en publiceren van de opgenomen rondleiding door de demo (/rondleiding) met de `just walkthrough`-commando's. Gebruik dit bij "ik heb een opname gemaakt", "neem hoofdstuk X opnieuw op", "zet de rondleiding op de preview", vragen over knippen, ondertitels, diateksten, de stemkloon of FAQ-antwoorden, en wanneer de replay iets niet goed nadoet (een klik, een scroll).
日本語の概要は準備中です。原文の説明を表示しています。
Analyze project dependencies, build dependency trees, detect conflicts, and check compatibility
日本語の概要は準備中です。原文の説明を表示しています。
Scan codebase for security vulnerabilities including secrets, insecure dependencies, and unsafe code patterns. Use when performing automated security scans.
日本語の概要は準備中です。原文の説明を表示しています。
Auto-activates during requirements analysis to evaluate technical stack compatibility, recommend appropriate technologies, and assess performance implications.
日本語の概要は準備中です。原文の説明を表示しています。
Fix bugs and technical debt with minimal ceremony. Issue GitHub optional — provide one for traceability or work free-form. Replaces /issue-fix.
日本語の概要は準備中です。原文の説明を表示しています。
Phase 0 validation gate — problem framing, competitive analysis, feasibility, and a go/no-go checkpoint before committing to a feature. Use when evaluating whether an idea is worth building, before /story or /design. Trigger on "is this worth building", "validate this idea", "discovery", "should we build".
日本語の概要は準備中です。原文の説明を表示しています。
Zero-ceremony atomic task execution. Use for tiny fixes or enhancements (minutes, not hours) that don't warrant SDLC ceremony. Flags: --discuss (disambiguate first), --full (delegate to /pre-commit after execution), --issue N (link commit to GitHub issue).
日本語の概要は準備中です。原文の説明を表示しています。