canary-watch
Use this skill to monitor and verify a deployed URL or public OSS launch surface after releases — checks HTTP endpoints, SSE streams, static assets, console errors, performance regressions, PR queue health, maintainer feedback, and listing-review blockers after deploys, merges, submissions, or dependency upgrades. Smoke / canary / post-deploy / PR-watch verification.
npx skills add mturac/everything-openai-codex --skill canary-watch --agent codex
Same command for any agent — swap --agent for claude-code, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Canary Watch — Post-Deploy Monitoring ## When to Use - After deploying to production or staging - After merging a risky PR - When you want to verify a fix actually fixed it - Continuous monitoring during a launch window - After dependency upgrades - After submitting EOC or a related OSS project to awesome lists, marketplaces, plugin directories, or community catalogs ## How It Works Monitors a deployed URL or public launch surface for regressions. Runs in a loop until stopped or until the watch window expires. ## Responsibility Contract Act as the release or launch canary owner for the monitored surface. Owned surface: - deployed URLs and their stated health checks - public listing PRs and their review state - the evidence report that explains whether action is needed Non-goals: - do not merge PRs - do not close PRs - do not argue with maintainers - do not post public comments from this skill - do not open new listing PRs from this skill Required verification: - cite the exact URL, PR, check, comment, or command output used as evidence - separate `healthy`, `needs fix`, `needs response`, and `watch only` - return changed files only when the watch action edited local docs, tests,
- When to Use
- How It Works
- Responsibility Contract
- Rule Precedence
- Listing Target Decision Context
- Technical Risk Contract
- What It Watches
- Watch Modes
- Alert Thresholds
- Notifications
- OSS PR Queue Workflow
- 1. Read the Current Queue
- 2. Classify the PR
- 3. Anti-Spam Rule
gh search prs "everything-openai-codex" --author mturac --state open --json url,repository,title,updatedAt --limit 100 gh search prs "everything-openai-codex" --author mturac --state closed --json url,repository,title,updatedAt --limit 100 gh pr view <number> --repo <owner/repo> --json mergeable,statusCheckRollup,comments,reviews,body,title,url
What does the canary-watch skill do?
Use this skill to monitor and verify a deployed URL or public OSS launch surface after releases — checks HTTP endpoints, SSE streams, static assets, console errors, performance regressions, PR queue health, maintainer feedback, and listing-review blockers after deploys, merges, submissions, or dependency upgrades. Smoke / canary / post-deploy / PR-watch verification.
How do I install it?
Run `npx skills add mturac/everything-openai-codex --skill canary-watch --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mturac/everything-openai-codex, a repository with 84 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.