スキルを探す

Developer relations playbook builder — produces a DevRel program design covering community platform, contributor program tiers, ambassador criteria, event strategy, and success metrics. Use when asked to "build a DevRel program", "design our developer community", "create a contributor program", "start a developer advocacy program", or "how do we grow our dev community".

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

Map AI cost topology — billing attribution, team-level spend, forecast vs actuals, alert gaps. Use when asked to "map our AI spend", "who is spending on LLMs", or "set up AI cost attribution".

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

Design cost reduction strategies — model tiering, prompt compression, caching, batch inference. Use when asked to "reduce our AI costs", "set up model tiering", or "cut LLM spend".

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

Survey the project's existing contracts and policy docs. Use when asked "what contracts do we have", "survey our policy docs", or "inventory our agreements".

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

Support operations reconnaissance -- audit current ticket volume, SLA compliance, knowledge base coverage, escalation paths, and CSAT to understand where support is the constraint. Use when asked to "audit our support", "why is our response time bad", "how healthy is our support operation", or "before designing a support system".

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

Write a hardening playbook for a system or service — CIS benchmark mapping and implementation steps. Use when asked to "harden this server", "apply the CIS benchmark", or "write a hardening playbook".

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

Design detection rules for a threat — SIEM queries, alert logic, and MITRE ATT&CK mapping. Use when asked to "write a detection rule", "how do we detect this attack", or "build a SIEM query for this TTP".

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

Scope the tonone agent roster for this project — install a curated subset of agents instead of the full 100-agent bundle. Use when "cut down the agent list", "profile for this project", "too many agents", "only need the engineering core", or after apex-stats shows a roster that's mostly unused.

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

Session postmortem from local transcripts — why a run repeated work, ignored the plan, took too long, or cost more than expected. Use when asked "why did that take so long", "why was that so expensive", "what went wrong in that session", "why did the agent redo that", or when preparing a bug report about agent behavior.

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

Engineering lead — hand Apex any task and it routes internally. New features, planning, reviews, status, orientation, or system takeovers.

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

Draft compliance policies required by a framework (access control, incident response, data retention). Use when asked to "write an access control policy", "draft our incident response policy", or "we need a data retention policy".

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

Compare API performance across versions — regression detection and root cause analysis. Use when asked "did performance regress", "compare API latency across versions", or "why is this slower".

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