メニュー
Define an SLA backed by the OLAs and underpinning contracts that make it deliverable, and a service catalog of standard requests. Reach for this when designing service targets or a request catalog.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/mcorbett51090/RavenClaude --skill design-slas-and-catalogコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Route everyday, well-defined work (single-file edits, test-writing, summarization, mechanical refactors, boilerplate) to a cheaper coding agent (Grok or Copilot CLI) instead of doing it in the main Claude session, escalating multi-file/architecture/debugging/security work to Claude. Opt-in via the `cheap_lane:` comfort-posture knob.
Authors, validates and packages a claude.ai Organization Skill — the intake questions, the trigger and scope exercises, then lint, pack and verify against measured platform constraints. Reach for this when someone wants to publish a Skill to their organization, or when an upload was rejected and the reason is unclear.
Drafts a reply to an inbound customer email, grounded in the account record and the published help-centre articles rather than in recall. Use when a customer emails about billing, a renewal or an outage, when a reply must cite current policy, or when a teammate asks for a first draft to edit.
SOC 職業分類に基づく
SKILL.md を表示中
| name | design-slas-and-catalog |
| description | Define an SLA backed by the OLAs and underpinning contracts that make it deliverable, and a service catalog of standard requests. Reach for this when designing service targets or a request catalog. |
A customer-facing SLA is only real if the internal and vendor commitments behind it exist (§2 #4).
What the service is, who consumes it, and what "good" means to them. Targets follow the customer's need, not what's easy to measure.
The customer-facing commitments (availability, response/resolution times by priority). Make them specific, measurable, and deliverable.
For each SLA target, identify the OLAs (commitments between internal IT teams) and underpinning contracts (vendor SLAs) that must hold for the SLA to be met. A gap here is a future breach — surface it now.
Define the standard, pre-approved service requests (access, equipment, common asks) with their fulfillment paths. A service request is not an incident; route repetitive ones to standard-change models.
Add the knowledge/self-service that lets users self-serve the top request types, and instrument the deflection rate (§2 #7). Use the sla-ola-definition template.