1,120 件 ・ 関連度順
概要と使いどころ
Post-close value creation plans for China-focused portfolio companies. Adapted from the original value-creation-plan skill for Chinese business context, management practices, and market dynamics. Triggers on "A股投后增值", "价值提升计划", "value creation plan China", "100-day plan China", "portfolio value creation", or "value creation [company]".
日本語の概要は準備中です。原文の説明を表示しています。
Structure post-acquisition value creation plans with revenue, cost, and operational levers mapped to an EBITDA bridge. Includes 100-day priorities, KPI targets, and accountability frameworks. Use when planning post-close execution, preparing operating partner materials, or building a board-ready value creation roadmap. Triggers on "value creation plan", "100-day plan", "post-close plan", "EBITDA bridge", "operating plan", or "value creation levers".
日本語の概要は準備中です。原文の説明を表示しています。
"Apply Service-Dominant Logic (Vargo and Lusch, 2004) and value co-creation principles to reframe exchange and value creation. Use this skill when the user needs to redesign value propositions around service exchange, analyze co-creation dynamics between firms and customers, shift from goods-dominant to service-dominant thinking, or when they ask 'how is value created with customers', 'what is our service logic', or 'how do we enable co-creation'.".
日本語の概要は準備中です。原文の説明を表示しています。
Continuously monitor a GitHub PR for merge conflicts, CI failures, and CodeRabbit review comments, then automatically fix any issues found. Polls every 5 minutes and loops until every check is green. Use this skill whenever a PR has just been created or code has been pushed to a PR branch — it should be the default follow-up action after any PR creation or push. Also trigger on: "watch this PR", "guard this PR", "monitor CI", "keep fixing until green", "PRを監視して", "CIが通るまで 直して", /pr-guardian. When a PostToolUse hook reports that a push or PR creation just happened, proactively invoke this skill to start monitoring without waiting for the user to ask.
ECC ToolsのGitHub Appで起きるPRの過剰作成や利用上限の抜け、高額モデルの意図しない使用をコードから追い、費用増加の原因と修正を検証するスキル。
When the user wants to optimize signup, registration, account creation, or trial activation flows. Also use when the user mentions "signup conversions," "registration friction," "signup form optimization," "free trial signup," "reduce signup dropoff," "account creation flow," "people aren't signing up," "signup abandonment," "trial conversion rate," "nobody completes registration," "too many steps to sign up," or "simplify our signup." Use this whenever the user has a signup or registration flow that isn't performing. For post-signup onboarding, see onboarding. For lead capture forms (not account creation), see cro.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to optimize signup, registration, account creation, or trial activation flows. Also use when the user mentions "signup conversions," "registration friction," "signup form optimization," "free trial signup," "reduce signup dropoff," or "account creation flow." For post-signup onboarding, see onboarding-cro. For lead capture forms (not account creation), see form-cro.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to optimize signup, registration, account creation, or trial activation flows. Also use when the user mentions "signup conversions," "registration friction," "signup form optimization," "free trial signup," "reduce signup dropoff," or "account creation flow." For post-signup onboarding, see onboarding-cro. For lead capture forms (not account creation), see form-cro.
日本語の概要は準備中です。原文の説明を表示しています。
Creates Cloud Storage on Google Cloud (also known colloquially as GCS) buckets. Analyzes the workload (sensitive data, media hosting, ingestion, web hosting, archiving, backup, logging, analytics, AI/ML, or general-purpose), validates project-level security settings, and designs a secure-by-default, cost-effective configuration (location, storage class, uniform bucket-level access, public access prevention, soft delete, lifecycle) before creating it. Use whenever a user wants to create, make, set up, provision, or spin up a bucket, or needs object storage for an app, service, pipeline, or dataset — even a "simple" or "default" bucket, or when bucket creation is one step in a larger workflow. Outputs or executes the creation via gcloud, the JSON/REST API, Terraform, or SDK client libraries (C++, Java, Python, Go). Don't use for anything other than creating new buckets — for uploads, downloads, access changes, or reconfiguring existing buckets, use google-cloud-storage-basics.
日本語の概要は準備中です。原文の説明を表示しています。
Discovers golden base images for creating GKE custom node images based on technical specifications or context clues. Use when finding the golden base image for custom GKE node creation, mapping cluster configuration parameters (GKE version, OS, architecture, accelerators, gVisor, cgroups) to image names, or querying GKE base image maps. Don't use for general GKE cluster creation (use gke-cluster-creation) or standard node pool management (use gke-basics).
日本語の概要は準備中です。原文の説明を表示しています。
Scaffold and operate Claude Blog Brain, a source-cited Obsidian brain for blog content creation, optimization, and management dual-optimized for Google rankings (E-E-A-T, the 2026 core updates) and AI citations (GEO/AEO), spanning writing, rewriting and freshness, SERP-informed briefs and outlines, editorial calendars and strategy, semantic topic clusters, schema and internal linking, multilingual publishing, the FLOW framework, factchecking, personas, distribution, and the blog delivery contract, grounded in the claude-blog skill. Use when the user says "claude-blog-brain", "Claude Blog Brain", "create a blog content creation, optimization, and management dual-optimized for Google rankings (E-E-A-T, the 2026 core updates) and AI citations (GEO/AEO), spanning writing, rewriting and freshness, SERP-informed briefs and outlines, editorial calendars and strategy, semantic topic clusters, schema and internal linking, multilingual publishing, the FLOW framework, factchecking, personas, distribution, and the blog delivery contract, grounded in the claude-blog skill brain", "import sources", "synthesize plan", "render report", or wants a persistent vault-backed operating system for blog content creation, optimization, and management dual-optimized for Google rankings (E-E-A-T, the 2026 core updates) and AI citations (GEO/AEO), spanning writing, rewriting and freshness, SERP-informed briefs and outlines, editorial calendars and strategy, semantic topic clusters, schema and internal linking, multilingual publishing, the FLOW framework, factchecking, personas, distribution, and the blog delivery contract, grounded in the claude-blog skill.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to optimize signup, registration, account creation, or trial activation flows. Also use when the user mentions "signup conversions," "registration friction," "signup form optimization," "free trial signup," "reduce signup dropoff," or "account creation flow." For post-signup onboarding, see onboarding-cro. For lead capture forms (not account creation), see form-cro.
日本語の概要は準備中です。原文の説明を表示しています。
调香师与香水 (调香师 / 香水 (Perfumery & Fragrance) — 香水创作与香气调配的职业认知操作系统，从业者/调香师/评香师/学习者视角。覆盖: (a) 第一性张力 — codifiable 理论层 (原料知识/香料化学/嗅觉家族分类/accord 和弦/配方结构 %/挥发度金字塔/IFRA 法规) ⇄ tacit 校准层 (嗅觉记忆/闻香训练/「the nose」/创作直觉/盲嗅识别)，这行的核心矛盾是「可背诵的原料与公式」与「不可言传的嗅觉记忆与品味」之间，嗅觉记忆是极致 tacit 技能; (b) 法系传统 vs 分子/合成派 — 法国 Grasse 天然香料 + haute parfumerie 艺术传统 (天然精油/原精/学徒制) vs 现代分子派 (aroma chemicals 香基/captives 专利分子/headspace 顶空捕香/功能香精)，两套对「香水是什么」的世界观; (c) 培养/传承 — ISIPCA (凡尔赛香水学校) + 四大香精公司内部调香学校 (Givaudan/Firmenich(DSM-Firmenich)/IFF/Symrise) + 学徒制 + 「鼻子」tacit 校准; 角色分工: perfumer(parfumeur 调香师) vs evaluator(评香师) vs flavorist(食用香精师); (d) 行业结构 — 四大香精公司寡头 (Givaudan/DSM-Firmenich/IFF/Symrise) + Mane/Robertet/Takasago，为品牌做 B2B 命题创作 (the brief → creation → mods 模型); vs niche/indie 小众独立香水 (artisanal/直营); 天然 (Grasse/精油) vs 合成 (香基/captives) 的成本与可持续之争; (e) 创作层 — 香调金字塔 (top/heart/base notes 前中后调)、accord 和弦、配方 (酒精中 % 浓度)、浓度分级 (parfum/EDP/EDT/EDC)、调香师的「香风琴」orgue、trials/mods 试样迭代、weighing 称量精度; (f) 法规与安全 — IFRA standards (原料限用)、EU 致敏原标签 (26→80+ allergens)、REACH、橡苔/atranol 限用、经典香水 (Mitsouko/Chanel No.5) 因法规被迫重配 (reformulation) 与创作自由之张力; (g) 评价/批评 — Luca Turin & Tania Sanchez (《Perfumes: The Guide》《The Secret of Scent》气味的科学)、香评人、Fragrantica/Basenotes 社区、vintage vs reformulation 之争、niche vs designer 之争。学派分歧: 法系天然传统派 vs 分子合成派、天然纯粹派 vs 合成实用派、haute parfumerie/niche 艺术派 vs mass designer 商业派、「鼻子=艺术家」vs「调香师=香气工程师/技师」、嗅觉科学之争 (Luca Turin 振动理论 vs 主流形状/受体理论)。不含: 香薰蜡烛/家居香氛纯生产营销、芳香疗法健康宣称 (aromatherapy)、纯化妆品配方学 (超出香精范畴)、DIY 家用香氛套件、精油传销/MLM。) Master OS — automated mastery of 调香师 / 香水 (Perfumery & Fragrance) — 香水创作与香气调配的职业认知操作系统，从业者/调香师/评香师/学习者视角。覆盖: (a) 第一性张力 — codifiable 理论层 (原料知识/香料化学/嗅觉家族分类/accord 和弦/配方结构 %/挥发度金字塔/IFRA 法规) ⇄ tacit 校准层 (嗅觉记忆/闻香训练/「the nose」/创作直觉/盲嗅识别)，这行的核心矛盾是「可背诵的原料与公式」与「不可言传的嗅觉记忆与品味」之间，嗅觉记忆是极致 tacit 技能; (b) 法系传统 vs 分子/合成派 — 法国 Grasse 天然香料 + haute parfumerie 艺术传统 (天然精油/原精/学徒制) vs 现代分子派 (aroma chemicals 香基/captives 专利分子/headspace 顶空捕香/功能香精)，两套对「香水是什么」的世界观; (c) 培养/传承 — ISIPCA (凡尔赛香水学校) + 四大香精公司内部调香学校 (Givaudan/Firmenich(DSM-Firmenich)/IFF/Symrise) + 学徒制 + 「鼻子」tacit 校准; 角色分工: perfumer(parfumeur 调香师) vs evaluator(评香师) vs flavorist(食用香精师); (d) 行业结构 — 四大香精公司寡头 (Givaudan/DSM-Firmenich/IFF/Symrise) + Mane/Robertet/Takasago，为品牌做 B2B 命题创作 (the brief → creation → mods 模型); vs niche/indie 小众独立香水 (artisanal/直营); 天然 (Grasse/精油) vs 合成 (香基/captives) 的成本与可持续之争; (e) 创作层 — 香调金字塔 (top/heart/base notes 前中后调)、accord 和弦、配方 (酒精中 % 浓度)、浓度分级 (parfum/EDP/EDT/EDC)、调香师的「香风琴」orgue、trials/mods 试样迭代、weighing 称量精度; (f) 法规与安全 — IFRA standards (原料限用)、EU 致敏原标签 (26→80+ allergens)、REACH、橡苔/atranol 限用、经典香水 (Mitsouko/Chanel No.5) 因法规被迫重配 (reformulation) 与创作自由之张力; (g) 评价/批评 — Luca Turin & Tania Sanchez (《Perfumes: The Guide》《The Secret of Scent》气味的科学)、香评人、Fragrantica/Basenotes 社区、vintage vs reformulation 之争、niche vs designer 之争。学派分歧: 法系天然传统派 vs 分子合成派、天然纯粹派 vs 合成实用派、haute parfumerie/niche 艺术派 vs mass designer 商业派、「鼻子=艺术家」vs「调香师=香气工程师/技师」、嗅觉科学之争 (Luca Turin 振动理论 vs 主流形状/受体理论)。不含: 香薰蜡烛/家居香氛纯生产营销、芳香疗法健康宣称 (aromatherapy)、纯化妆品配方学 (超出香精范畴)、DIY 家用香氛套件、精油传销/MLM。: top builders' mental models, tool stack, current workflows, jargon, and where to keep up. Trigger this skill when the user works on 调香师 / 香水 (Perfumery & Fragrance) — 香水创作与香气调配的职业认知操作系统，从业者/调香师/评香师/学习者视角。覆盖: (a) 第一性张力 — codifiable 理论层 (原料知识/香料化学/嗅觉家族分类/accord 和弦/配方结构 %/挥发度金字塔/IFRA 法规) ⇄ tacit 校准层 (嗅觉记忆/闻香训练/「the nose」/创作直觉/盲嗅识别)，这行的核心矛盾是「可背诵的原料与公式」与「不可言传的嗅觉记忆与品味」之间，嗅觉记忆是极致 tacit 技能; (b) 法系传统 vs 分子/合成派 — 法国 Grasse 天然香料 + haute parfumerie 艺术传统 (天然精油/原精/学徒制) vs 现代分子派 (aroma chemicals 香基/captives 专利分子/headspace 顶空捕香/功能香精)，两套对「香水是什么」的世界观; (c) 培养/传承 — ISIPCA (凡尔赛香水学校) + 四大香精公司内部调香学校 (Givaudan/Firmenich(DSM-Firmenich)/IFF/Symrise) + 学徒制 + 「鼻子」tacit 校准; 角色分工: perfumer(parfumeur 调香师) vs evaluator(评香师) vs flavorist(食用香精师); (d) 行业结构 — 四大香精公司寡头 (Givaudan/DSM-Firmenich/IFF/Symrise) + Mane/Robertet/Takasago，为品牌做 B2B 命题创作 (the brief → creation → mods 模型); vs niche/indie 小众独立香水 (artisanal/直营); 天然 (Grasse/精油) vs 合成 (香基/captives) 的成本与可持续之争; (e) 创作层 — 香调金字塔 (top/heart/base notes 前中后调)、ac
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to optimize signup, registration, account creation, or trial activation flows. Also use when the user mentions "signup conversions," "registration friction," "signup form optimization," "free trial signup," "reduce signup dropoff," "account creation flow," "people aren't signing up," "signup abandonment," "trial conversion rate," "nobody completes registration," "too many steps to sign up," or "simplify our signup." Use this whenever the user has a signup or registration flow that isn't performing. For post-signup onboarding, see onboarding. For lead capture forms (not account creation), see cro.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to optimize signup, registration, account creation, or trial activation flows. Also use when the user mentions "signup conversions," "registration friction," "signup form optimization," "free trial signup," "reduce signup dropoff," or "account creation flow." For post-signup onboarding, see onboarding-cro. For lead capture forms (not account creation), see form-cro.
日本語の概要は準備中です。原文の説明を表示しています。
Structures 100-day and long-term value creation plans with revenue growth, margin improvement, and capital efficiency initiatives. Use when building value creation plans, tracking improvement initiatives, or preparing operating partner reviews.
日本語の概要は準備中です。原文の説明を表示しています。
Evaluates ETF market mechanics with premium/discount analysis, authorized participant activity, and creation unit arbitrage. Use when analyzing ETF trading, evaluating NAV premiums, or understanding creation/redemption flows.
日本語の概要は準備中です。原文の説明を表示しています。
Automate a professional LinkedIn presence end-to-end using Claude: daily posting with pillar calendar, engagement with anti-detection rules, DM triage, reporting, and growth tracking. Use when the user wants to automate LinkedIn, manage a profile with AI, create a content strategy, or set up engagement automation. Triggers on: "automate my LinkedIn", "LinkedIn automation", "automated LinkedIn", "LinkedIn bot", "LinkedIn scheduling", "LinkedIn AI management", "LinkedIn content calendar", "LinkedIn engagement strategy", "build a LinkedIn presence", "can Claude manage my LinkedIn", "how do I automate my LinkedIn", or any request involving systematic LinkedIn content creation, audience growth, or profile management. Covers: identity/TOV setup, pillar calendar, post creation, engagement rules, anti-detection, scheduled task creation, and weekly reporting.
日本語の概要は準備中です。原文の説明を表示しています。
Hunts for lateral movement via remote service creation, admin share writes, and remote WMI process creation by correlating Windows logon, service install, and process-creation events. Activates for requests to hunt lateral movement, detect PsExec/WMIexec activity, or find remote execution over SMB and WMI.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of an Entertainment and Recreation Manager (theme park, arena, recreation facility, tour operation) — planning attraction/facility capacity against attendance forecasts, evaluating a guest safety or ride-operations decision, pricing admission/season-pass programs, or managing seasonal staffing and weather-driven demand swings.
日本語の概要は準備中です。原文の説明を表示しています。
Scaffold and operate Claude Blog Brain, a source-cited Obsidian brain for blog content creation, optimization, and management dual-optimized for Google rankings (E-E-A-T, the 2026 core updates) and AI citations (GEO/AEO), spanning writing, rewriting and freshness, SERP-informed briefs and outlines, editorial calendars and strategy, semantic topic clusters, schema and internal linking, multilingual publishing, the FLOW framework, factchecking, personas, distribution, and the blog delivery contract, grounded in the claude-blog skill. Use when the user says "claude-blog-brain", "Claude Blog Brain", "create a blog content creation, optimization, and management dual-optimized for Google rankings (E-E-A-T, the 2026 core updates) and AI citations (GEO/AEO), spanning writing, rewriting and freshness, SERP-informed briefs and outlines, editorial calendars and strategy, semantic topic clusters, schema and internal linking, multilingual publishing, the FLOW framework, factchecking, personas, distribution, and the blog delivery contract, grounded in the claude-blog skill brain", "import sources", "synthesize plan", "render report", or wants a persistent vault-backed operating system for blog content creation, optimization, and management dual-optimized for Google rankings (E-E-A-T, the 2026 core updates) and AI citations (GEO/AEO), spanning writing, rewriting and freshness, SERP-informed briefs and outlines, editorial calendars and strategy, semantic topic clusters, schema and internal linking, multilingual publishing, the FLOW framework, factchecking, personas, distribution, and the blog delivery contract, grounded in the claude-blog skill.
日本語の概要は準備中です。原文の説明を表示しています。
Creates Cloud Storage (Google Cloud Storage, or GCS) buckets. Analyzes the workload (sensitive data, media hosting, ingestion, web hosting, archiving, backup, logging, analytics, AI/ML, or general-purpose), validates project-level security settings, and designs a secure-by-default, cost-effective configuration (location, storage class, uniform bucket-level access, public access prevention, soft delete, lifecycle) before creating it. Use whenever a user wants to create, make, set up, provision, or spin up a bucket, or needs object storage for an app, service, pipeline, or dataset — even a "simple" or "default" bucket, or when bucket creation is one step in a larger workflow. Outputs or executes the creation via gcloud, the JSON/REST API, Terraform, or SDK client libraries (C++, Java, Python, Go). Don't use for anything other than creating new buckets — for uploads, downloads, access changes, or reconfiguring existing buckets, use google-cloud-storage-basics.
日本語の概要は準備中です。原文の説明を表示しています。
Discovers golden base images for creating GKE custom node images based on technical specifications or context clues. Use when finding the golden base image for custom GKE node creation, mapping cluster configuration parameters (GKE version, OS, architecture, accelerators, gVisor, cgroups) to image names, or querying GKE base image maps. Don't use for general GKE cluster creation (use gke-cluster-creation) or standard node pool management (use gke-basics).
日本語の概要は準備中です。原文の説明を表示しています。
Use when creating a new custom field on any Salesforce object: choosing field type, setting API name, configuring Field-Level Security, adding to page layouts, and deploying. Triggers: 'add a field', 'new custom field', 'what field type should I use', 'FLS not working', 'field not showing on page layout'. NOT for creating the object itself - use admin/object-creation-and-design. NOT for formula field logic - use admin/formula-fields. NOT for picklist value set management - use admin/picklist-and-value-sets. Also covers: field-meta.xml, CustomField metadata, deleteConstraint, externalId, unique, precision and scale, relationshipOrder, writeRequiresMasterRead, fieldPermissions, package.xml for fields.
日本語の概要は準備中です。原文の説明を表示しています。