Defines and manages service levels — setting targets that reflect what customers need, measuring honestly, and handling breaches. Use this to write or negotiate an SLA, decide what to measure and at what threshold, respond to a missed service level, or work out why a service that meets its targets still has unhappy customers.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
A service level is a promise with a number attached. The number is the easy part; choosing what to measure is where these go wrong.
The characteristic failure is a service meeting every target while customers are angry. It happens when the measure is chosen for availability of data rather than relevance:
A target is a spending decision. Each added nine costs disproportionately more than the last, so the question is never "what would be good?" but "what is the gap worth to the customer, and does it exceed what closing it costs?"
Set the internal objective tighter than the external commitment. The gap between them is your warning margin; without it, the first thing you learn about a breach is the breach.
An unmeasurable clause is a future dispute. Every service level needs: what is measured, where it is measured from, how it is calculated, what is excluded, over what window, and what happens when it is missed.
Exclusions are the substance — planned maintenance, force majeure, customer-caused failures,
dependencies outside your control. Vague exclusions get read narrowly when it matters. For anything
with contractual teeth, legal-risk:contract-review owns the remedy language; this skill owns
whether the number is achievable.
Say so before the customer does. A breach reported by the provider with a cause and a fix costs far less trust than one the customer discovers and raises.
Then separate the incident from the pattern. One breach is an incident, handled by
customer-experience:escalation-management. Repeated breaches of the same target mean the target was
never fundable — renegotiate it honestly rather than continuing to miss it.
references/sources.md in this skill lists the outside authorities that settle the questions
here — what each one is authoritative for, and what you may do with it. Check them before
answering on anything they cover, and cite what you used. Most are free to read and not free
to reproduce; the use note on each is binding.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Designs and audits who can reach what — authentication, authorization models, privileged access, service credentials, and joiner-mover-leaver process. Use this to design a permissions model, run an access review, reduce standing privilege, handle offboarding, set up SSO or MFA, manage service and machine credentials, or diagnose why permissions have sprawled.
日本語の概要は準備中です。原文の説明を表示しています。
Concentrates marketing and sales effort on a named set of accounts rather than on volume — qualifying whether the model fits your economics at all, building the account list and the buying group inside each, tiering effort against account value, coordinating so the account experiences one campaign rather than several, and measuring account progression instead of leads. Use this to decide whether to run an account-based program, build one, or work out why an existing one produces activity and no pipeline.
日本語の概要は準備中です。原文の説明を表示しています。
Gets new users from signup to first real value — signup flow, onboarding, time-to-value, and the early experience that determines whether someone becomes a user or a lapsed account. Use this to design or fix signup and onboarding, diagnose why signups do not convert to active use, reduce time-to-value, or decide what a new user must accomplish first.
日本語の概要は準備中です。原文の説明を表示しています。
Designs orchestrator-and-subagent hierarchies for a repository — splitting agents by exclusive write surface, pairing every producer with an independent auditor, and enforcing the split with a script that runs in CI. Use this whenever the user wants to set up, expand, audit, or fix a multi-agent or subagent structure for a codebase; asks how to divide work between agents; wants agent charters, roles, or a surface map written; or is hitting agents that collide on the same files, review their own work, or drift from their remit. Also use when sizing a roster or deciding whether a new agent is justified.
日本語の概要は準備中です。原文の説明を表示しています。
Governs models and AI systems in production — intended use, evaluation, monitoring, human oversight, documentation, and the decision to deploy or retire. Use this before deploying a model or AI feature, when defining evaluation criteria, when a model's behavior has drifted, when assessing AI risk or regulatory exposure, or when deciding whether an AI system is fit for a consequential decision.
日本語の概要は準備中です。原文の説明を表示しています。
Produces executive-level research — market sizing, competitor mapping, trend analysis, and strategic intelligence — grounded in cited sources with the confidence in each claim made explicit. Use this to analyze a market or industry, map competitors, evaluate a market-entry or build-versus-buy decision, produce a research brief, or assemble evidence for a decision. Also use when comparing options that need a structured, evidence-based verdict rather than an opinion.
日本語の概要は準備中です。原文の説明を表示しています。