القائمة
Daily meta-routine — watches every other routine for error rates, drift, and runaway cost; surfaces routine_health findings into the Inbox. Routine-only.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Evaluate multiple choices side-by-side based on relevant criteria, then present a comparison the user can act on. Use when the user asks to compare options, choose between alternatives, or weigh up X vs Y.
Day-of-week rotating proactive sweep — Mon=connections / Tue=routines / Wed=skills / Thu=memories / Fri=findings / Sat=cross-cutting / Sun=weekly summary. Forces outward scan instead of inward thrash. Routine-only; load this skill into a daily routine that fires AssistantAgent. Adapted from goanna's caretaker.
Use when an agent has had N consecutive quiet runs with nothing to do. Pivots to bounded inward consolidation (promote findings, refresh memory, audit asks) anchored in own data — NOT generic news summarisation. Adapted from goanna's reverie cycle. Routine-only; loaded by the routine that detects the quiet condition.
Use to track open questions you owe the user (asks) and time-bounded commitments you owe yourself (tasks). Write OPEN entries when you commit; promote to CLOSED when answered/done. Survives session compaction. Adapted from goanna's asks.md/tasks.md pattern.
Reviewer criteria for AI-generated code via with_review. Checks for security issues (injection, auth bypass, secret leakage), correctness, and project conventions. Use as criteria.skill when generating code that touches data, auth, or external systems.
Reviewer criteria for outbound email drafts via with_review. Checks tone-recipient match, professionalism, no AI tells, no placeholder leakage. Use as criteria.skill argument when reviewing email drafts before send.
| name | routine-health-check |
| description | Daily meta-routine — watches every other routine for error rates, drift, and runaway cost; surfaces routine_health findings into the Inbox. Routine-only. |
| disable_model_invocation | true |
Routines run unattended. When one of them starts erroring or running away on cost, the user needs to know — but only via the same channels they already check (the Inbox), not a separate alerting layer.
This skill turns "watch the other routines" into a routine itself. It loads into a daily fire of AssistantAgent and produces findings.
For each routine the user owns:
routine_runs.outcome IN ('error', 'budget_exceeded') in the last 24h vs total runs in 24h. > 30% = high importance.routine_runs.cost_usd over 24h vs the routine's daily cap. ≥ 80% = high importance.For each issue, call inbox_add with:
{
"kind": "routine_health",
"summary": "<routine name> — <one-line issue + action>",
"importance": "<calibrate via score-importance skill>",
"reasoning": "<the numbers backing the claim>",
"suggestedAction": {
"label": "Open routine",
"link": "/dashboard/routines/<id>"
},
"tags": ["routine-health"],
"relatedItemIds": ["<routineId>"]
}
Findings are read while the user is doing other things. Lead with the routine name + the actionable bit, never with technical detail. Detail goes in reasoning.
Examples:
Stuck-tickets sweeper — 4 of 6 fires errored (Gmail token expired). Reconnect Gmail.routine_runs WHERE outcome='error' returned 4 rows for routine_id=abc...Don't emit anything. The Inbox already shows zero new items as "all clear". A "all routines healthy" finding once a day is what desensitises users to the channel.