docs(skills): realtime-maintenance no longer needs an incident.io API key

Pull Requests/phaseo/Phaseo/#2923

docs(skills): realtime-maintenance no longer needs an incident.io API key

Open

DanielButler1wants to merge intofrom

1 commit2 files changed+62-114

https://entire.com/gh/phaseoteam/-/trails/155/changes/Phaseo/155

What changed

The realtime-maintenance skill no longer uses an incident.io API key. For each status page step (announce, in progress, complete), it drafts the post with every field ready to paste, and asks the user to publish it in the incident.io dashboard.
It waits for the user to confirm the announcement before starting the window. If the user decides not to announce, it carries on.

Why

The user said incident.io API keys need a much more expensive plan, which they won't buy. incident.io's hosted MCP server and its inc CLI can't publish status page maintenance either, so publishing by hand is the only option that's left.

How

Only SKILL.md changed, plus its generated copy in .claude/skills. The maintenance switch, the deploy guards and the checks are unchanged. API callers still learn about a window from the 503 realtime_maintenance response, which carries maintenance_until and Retry-After.

Before and after

Step	Before	After
Announce, in progress, complete	`curl` to incident.io with `INCIDENT_IO_API_KEY`	A drafted post for the user to publish in the dashboard
What it needs	An incident.io API key on a paid plan	Nothing new

Verification

pnpm skills:validate: 27 skills valid.
pnpm skills:sync: .claude/skills is in sync.
No runtime code changed.

Model: Claude Opus 5.5 (effort unknown) · Harness: Claude Code in T3 Code

🤖 Generated with Claude Code

Summary by CodeRabbit

Documentation
- Updated the realtime maintenance workflow to use the incident.io dashboard for drafting and publishing status-page posts and for starting, updating, and completing maintenance windows.
- Confirm publication before starting a window. You can proceed without an announcement, and the in-progress status update does not block continuing.

Activity

docs(skills): realtime-maintenance drafts status page posts for the user to publish, with no incident.io API key

913fa89Oct 29

vercel[bot]1d ago

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
phaseo	Ready	Preview	Oct 29, 2026 3:24pm UTC

chatgpt-codex-connector[bot]1d ago

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	🔄 Running since 2026-10-29T15:13:40.099035Z	`913fa89`	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

github-actions[bot]1d ago

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

coderabbitai[bot]1d ago

No actionable comments were generated in the recent review.

Recent review info

Run configuration

Source mode: Auto
Repository: Unavailable
Branch: Unavailable
File: No configuration file from this repository applied
Commit: Unavailable
Layers: defaults
Review profile: CHILL
Plan: Advanced
Run ID: 824131a3-b120-4ba9-93b5-3bbbf61315be

Commits

Reviewing files that changed from the base of the PR and between 401dbdf6b9b4cacad6be56f9adcb305a9f45081d and 913fa89da25833cc46fe9c0b58b596b59d6bbbb4.

Files selected for processing: 2

.agents/skills/realtime-maintenance/SKILL.md
.claude/skills/realtime-maintenance/SKILL.md

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

Walkthrough

The two realtime-maintenance skill documents replace incident.io API instructions with manual dashboard steps for publishing and updating maintenance status.

Changes: Realtime maintenance workflow

Layer / File(s)	Summary
Draft and publish announcement `.agents/skills/realtime-maintenance/SKILL.md`, `.claude/skills/realtime-maintenance/SKILL.md`	Both skills describe drafting a status-page post and publishing it in the incident.io dashboard. They request publication confirmation before Step 2 and allow proceeding without an announcement.
Update in-progress status `.agents/skills/realtime-maintenance/SKILL.md`, `.claude/skills/realtime-maintenance/SKILL.md`	Both skills instruct the user to mark the component as under maintenance in the dashboard. Continuing does not depend on confirmation of the update.
Complete maintenance `.agents/skills/realtime-maintenance/SKILL.md`, `.claude/skills/realtime-maintenance/SKILL.md`	Both skills direct the user to complete maintenance in the dashboard and return the component to operational. The “Never” list no longer specifically names the incident.io key.

Priority: Low

Estimated code review effort: 2 (Simple) | ~8 minutes

Change: Other

Suggested labels: Impact: Low Risk

Merge Risk: Minimal · up to 913fa

No concrete merge-blocking risk remains in the reviewed change.

Pre-merge checks: 5

Check name	Status	Explanation
Description Check		Check skipped - CodeRabbit’s high-level summary is enabled.
Title check		The title clearly and concisely identifies the main change: the realtime-maintenance skill no longer requires an incident.io API key.
Docstring Coverage		No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentat…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

Full details: Docstring Coverage

Explanation

No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 0 files. (2 skipped: 2 unsupported.)

Finishing Touches

🧪 Generate unit tests (beta)

Commit to this branch
Create a new PR

Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands.}