eng-runbook
An engineering runbook — service overview, alerts table, dashboards links, common procedures with copy-pasteable commands, on-call rotation, and an incident-response checklist. Use when the brief mentions "runbook", "ops doc", "on-call guide", or "SRE doc".
معلومات المصدر
- المستودع
- sanghyunna/readable-studio
- آخر نشاط في المصدر
- ٦ أكتوبر ٢٠٢٦ في ٠٧:٥٩
- لغة SKILL.md المكتشفة
- الإنجليزية
- النجوم
- ٠
- التفرعات
- ٠
خيارات التثبيت
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
مراجعة ملفات المصدر
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
مستكشف الملفات
3 ملفاتعرض SKILL.md
SKILL.md
تعليمات المصدر · معاينة للقراءة فقط- name
- eng-runbook
- description
- An engineering runbook — service overview, alerts table, dashboards links, common procedures with copy-pasteable commands, on-call rotation, and an incident-response checklist. Use when the brief mentions "runbook", "ops doc", "on-call guide", or "SRE doc".
- triggers
- ["runbook","ops doc","on-call","sre doc","service runbook","operations manual"]
- readable
- {"mode":"prototype","platform":"desktop","scenario":"engineering","preview":{"type":"html","entry":"index.html"},"design_system":{"requires":true,"sections":["color","typography","layout","components"]},"example_prompt":"Write a runbook for our auth service — alerts, dashboards, common procedures, on-call rotation."}
# Engineering Runbook Skill
Produce a single-page engineering runbook.
## Workflow
1. Read DESIGN.md.
2. Identify the service from the brief.
3. Layout:
- Header: service name, owner team, severity tier, version.
- Service summary paragraph + dependency list.
- Alerts table: alert name / severity / what it means / first response.
- Dashboards & links list.
- Common procedures block (3–4) with code blocks (deploy, rollback, rotate keys).
- On-call rotation table (week / primary / secondary / backup).
- Incident response checklist (5 numbered steps).
4. One inline `<style>`, semantic HTML, monospace for code blocks.
## Output contract
With file tools, save or edit `index.html`; the saved file is the deliverable. Finish with a brief reference to that file and a summary of the change. Keep the user's topic in the document title.
<readable-delivery channel="no-file-tools">
Only without file tools, use this chat delivery channel with the stable identifier `index` and the user's topic in `title`:
```
<artifact identifier="index" type="text/html" title="Service Runbook">
<!doctype html>...</artifact>
```
</readable-delivery>
عرض على GitHub