スキルを探す

Build or audit a financial model — 3-statement model (P&L, cash flow, balance sheet), scenario analysis, and sensitivity tables. Use when asked to "build a financial model", "model our growth scenarios", or "what happens to runway if we hire 5 people".

日本語の概要は準備中です。原文の説明を表示しています。

Prepare fundraising financial materials — investor model, data room financial docs, cap table, and use-of-funds narrative. Use when asked to "prepare for Series A", "build our investor model", or "what financials do investors want".

日本語の概要は準備中です。原文の説明を表示しています。

Assess and improve cloud portability — identify lock-in, prioritize abstraction, and design migration paths. Use when asked "how locked in are we", "reduce vendor lock-in", or "plan a cloud migration".

日本語の概要は準備中です。原文の説明を表示しています。

Write a developer quickstart — minimal steps from zero to first successful API call. Use when asked to "write a quickstart", "get users from zero to first API call", or "write a getting started guide".

日本語の概要は準備中です。原文の説明を表示しています。

Audit existing vulnerability management — find SLA gaps, missing tiers, and process failures. Use when asked to "audit our vulnerability management", "find patch SLA gaps", or "are we patching fast enough".

日本語の概要は準備中です。原文の説明を表示しています。

Design a vulnerability management program — SLAs, asset tiers, escalation, and metrics. Use when asked to "design a patching program", "set vulnerability SLAs", or "define our patch cadence".

日本語の概要は準備中です。原文の説明を表示しています。

Design a mock server for an API — tooling selection, response fixtures, and error scenarios. Use when asked to "build a mock server", "mock this API for development", or "create response fixtures".

日本語の概要は準備中です。原文の説明を表示しています。

Customer Success engineer — onboarding optimization, health scoring, expansion revenue, churn prevention, and NRR growth. Use when asked to "improve onboarding", "score account health", "prevent churn", or "grow NRR".

日本語の概要は準備中です。原文の説明を表示しています。

Design or audit Kubernetes RBAC — roles, bindings, service accounts, and least-privilege model. Use when asked to "audit Kubernetes RBAC", "apply least privilege in K8s", or "review service account permissions".

日本語の概要は準備中です。原文の説明を表示しています。

Audit an existing Kubernetes cluster — find misconfigurations, security gaps, and resource issues. Use when asked to "audit our Kubernetes cluster", "find K8s misconfigurations", or "check cluster security gaps".

日本語の概要は準備中です。原文の説明を表示しています。

Customer success reconnaissance — audit current onboarding completion, health signals, NRR, churn patterns, and CS motion. Use when asked to "audit our customer success", "why are customers churning", "what's our NRR", or before designing any CS playbook.

日本語の概要は準備中です。原文の説明を表示しています。

Metrics architecture — produce a complete metrics plan given a product description. North Star, input metrics tree, instrumentation spec, action triggers, and counter-metrics. Use when asked to "design a metrics framework", "what should we measure", "build a metrics system", "define our KPIs", "what are our success metrics", "metrics strategy", or "what do we track".

日本語の概要は準備中です。原文の説明を表示しています。

Generate financial reports — monthly close package, variance analysis, and management reporting. Use when asked to "generate monthly financials", "close the books", or "write variance commentary".

日本語の概要は準備中です。原文の説明を表示しています。

Audit existing mocks and test doubles — find contract drift, missing error cases, and stale fixtures. Use when asked to "audit our mocks", "find stale test fixtures", or "check for contract drift".

日本語の概要は準備中です。原文の説明を表示しています。

Design a Kubernetes cluster architecture — node pools, RBAC, networking, and workload config. Use when asked to "design a Kubernetes cluster", "plan our node pools", or "design K8s architecture for this workload".

日本語の概要は準備中です。原文の説明を表示しています。

Design a service mesh deployment — technology selection, mTLS policy, and traffic management config. Use when asked "should we use a service mesh", "Istio or Linkerd", or "design our mTLS policy".

日本語の概要は準備中です。原文の説明を表示しています。

Analytics reconnaissance for takeover — find all analytics tools, inventory what's tracked and dashboarded, assess data freshness and metric definitions, and present a coverage map. Use when asked "what analytics exist", "BI assessment", or "what do we track".

日本語の概要は準備中です。原文の説明を表示しています。

Review existing analytics — find all dashboards and reports, check who uses them, whether metrics are defined, and whether they drive decisions. Recommend what to keep, kill, or add. Use when asked "are our dashboards useful", "analytics review", or "metrics audit".

日本語の概要は準備中です。原文の説明を表示しています。

Design service mesh observability — distributed tracing, service-level metrics, and dashboards. Use when asked to "add service mesh observability", "set up distributed tracing in the mesh", or "build service-level dashboards".

日本語の概要は準備中です。原文の説明を表示しています。

Audit and improve unit economics — LTV, CAC, payback period, gross margin, contribution margin. Use when asked to "are our unit economics good", "what is our LTV/CAC", or "how do we improve gross margin".

日本語の概要は準備中です。原文の説明を表示しています。

Design or review annual operating budget — headcount plan, departmental spending, revenue targets, and variance tracking. Use when asked to "build our budget", "plan headcount for next year", or "review our spending".

日本語の概要は準備中です。原文の説明を表示しています。

Audit existing service mesh configuration — find mTLS gaps, traffic policy issues, and observability holes. Use when asked to "audit our service mesh", "find mTLS gaps", or "review traffic policy issues".

日本語の概要は準備中です。原文の説明を表示しています。

Survey existing onboarding docs and developer portal — find gaps and structural issues. Use when asked to "survey our onboarding docs", "find developer portal gaps", or "review our onboarding structure".

日本語の概要は準備中です。原文の説明を表示しています。

Use when asked to select chart types for analytics dashboards, choose BI visualizations, or design data displays. Examples: "best chart for sales data", "dashboard visualization for metrics", "analytics chart selection"

日本語の概要は準備中です。原文の説明を表示しています。