[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DM2AGRJ822B3C8NQCDK3JG":3,"skill-same:01M7DM2AGRJ822B3C8NQCDK3JG":45},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":44},"01M7DM2AGRJ822B3C8NQCDK3JG","routines",null,"Put the project's recurring rituals on a schedule, with the owner's consent. Weekly north-star report, monthly market watch, dependency triage, Supabase advisor sweep, reflect and harness-optimize. Uses Claude Code Routines (cloud cron) where they fit, and documents the Codex \u002F local cron equivalent. Use when asked to automate, schedule or \"keep the project moving on its own\", or after setup finishes.","foxinthehenhouse\u002Fapp-in-a-box","foxinthehenhouse","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F144333692?v=4","01M7DKXRK1CCGY9F45FYGWVD29","Kyle Fox","01M7DKXRKNG8A1ADJFXVH15RXT",0,"MIT","https:\u002F\u002Fgithub.com\u002Ffoxinthehenhouse\u002Fapp-in-a-box\u002Fblob\u002Fmain\u002Fplugins\u002Fapp-in-a-box\u002Ftemplate\u002F.agents\u002Fskills\u002Froutines\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: routines\ndescription: Put the project's recurring rituals on a schedule, with the owner's consent. Weekly north-star report, monthly market watch, dependency triage, Supabase advisor sweep, reflect and harness-optimize. Uses Claude Code Routines (cloud cron) where they fit, and documents the Codex \u002F local cron equivalent. Use when asked to automate, schedule or \"keep the project moving on its own\", or after setup finishes.\ndisable-model-invocation: true\n---\n\n# Routines\n\nWithout a schedule, the rituals only run when the session-start line nags. This\nskill sets them up to run on their own. **It creates nothing without an explicit yes\nfor each routine**, because every run spends tokens and can open PRs\u002Fissues.\n\n## 1. Offer the menu (ask, structured, multi-select)\n\n| Ritual | Cadence | What a run produces | Where it can run |\n|---|---|---|---|\n| `north-star-report` | Mon 08:xx | Report file + proposed tickets (issue comment; files nothing unapproved) | Cloud (needs the PostHog connector on the Routine) |\n| `dependency-triage` | Mon 08:xx | `triage` pass over open dependency PRs + `npm audit` \u002F `pip-audit`; one summary issue | Cloud |\n| `market-watch` | 1st Tue of the month, 09:xx | Re-checks competitors and complaint themes against `docs\u002Fproduct\u002FVALIDATION.md`; one issue only if something changed | Cloud |\n| `supabase-advisor` | Wed 08:xx | Security\u002Fperformance advisors → one issue per new finding | Cloud (needs the Supabase connector) |\n| `harness-optimize` | Fri 16:xx | Harness-change PR from the week's session signal | **Local**: it reads session transcripts on the machine where you work |\n| `reflect` | Fri 16:xx | Memory notes PR | **Local**, same reason |\n\nEstimated cost: each cloud run is one agent session, roughly a normal working\nsession's tokens. Say that in the question. Recommend the first two by default.\n\n## 2. Create the ones they picked\n\nEach ritual's procedure lives in `.agents\u002Froutines\u002F\u003Critual>.md` (cadence, where it\nruns, connectors, steps). The Routine's prompt just points there, so the procedure is\nversioned and reviewed with the code.\n\n**Claude Code (cloud Routines).** Run `\u002Fschedule` (alias `\u002Froutines`) and create one\nroutine per pick against this GitHub repo, with a prompt that stands alone because\neach run starts fresh:\n\n```\nIn \u003Cowner>\u002F\u003Crepo>: follow .agents\u002Froutines\u002F\u003Critual>.md end to end.\nNever merge, never push to main, never file a ticket the procedure says needs\napproval: put proposals in one issue titled \"\u003Critual>: \u003Cdate>\" instead.\n```\n\nAdd only the connectors that ritual needs (PostHog, Supabase, Linear). Use a minute\nthat isn't :00 to avoid the top-of-hour rush. Manage or delete them later at\nclaude.ai\u002Fcode\u002Froutines.\n\n**Codex \u002F any agent (local cron).** Codex has no cloud scheduler; use the machine's:\n\n```cron\n# crontab -e   (runs in the repo; logs to ~\u002F.local\u002Fstate\u002F\u003Cslug>-rituals.log)\n13 8 * * 1  codex exec -C \u002Fpath\u002Fto\u002Frepo --approve-for-me -c sandbox_workspace_write.network_access=true \"Follow .agents\u002Froutines\u002Fnorth-star-report.md.\" >> ~\u002F.local\u002Fstate\u002F\u003Cslug>-rituals.log 2>&1\n47 16 * * 5 codex exec -C \u002Fpath\u002Fto\u002Frepo --approve-for-me -c sandbox_workspace_write.network_access=true \"Follow .agents\u002Froutines\u002Freflect.md, then .agents\u002Froutines\u002Fharness-optimize.md.\" >> ~\u002F.local\u002Fstate\u002F\u003Cslug>-rituals.log 2>&1\n```\n\nFor Claude Code the local equivalent is\n`cd \u002Fpath\u002Fto\u002Frepo && claude -p \"\u002Fharness-optimize\" --permission-mode auto`. Cron\nruns can't answer an approval prompt, so pick a mode that won't stop to ask. On macOS, prefer a\n`launchd` agent (cron may lack disk access). These flags were checked against\n`codex-cli 0.159.3` (`-C`, `--approve-for-me`, `-c`); confirm with `codex exec --help` \u002F\n`claude --help` first, since CLIs drift.\n\n## 3. Record it\n\nAdd each scheduled ritual's name to `.claude\u002Fharness\u002Fmanifest.json` →\n`cadence.scheduled` (e.g. `[\"north-star-report\", \"dependency-triage\"]`), so the\nsession-start nudge stops asking you to run by hand what a routine already runs.\nCommit that on a branch with a PR (`chore: schedule rituals`), and log it in\n`docs\u002Fdecision-log.md` (who agreed, what runs, where).\n\nReply with a table: ritual → where it runs → first run time → how to stop it.\n\n## Ask the owner\n\nFollow `.agents\u002Frules\u002Fproduct-judgement.md`: ask with a structured question (recommended option first), never decide these silently. In this skill that means: Which rituals run unattended and on what schedule, since each run spends tokens and can open issues or PRs. One yes per routine.\n","# Routines\n\nWithout a schedule, the rituals only run when the session-start line nags. This\nskill sets them up to run on their own. **It creates nothing without an explicit yes\nfor each routine**, because every run spends tokens and can open PRs\u002Fissues.\n\n## 1. Offer the menu (ask, structured, multi-select)\n\n| Ritual | Cadence | What a run produces | Where it can run |\n|---|---|---|---|\n| `north-star-report` | Mon 08:xx | Report file + proposed tickets (issue comment; files nothing unapproved) | Cloud (needs the PostHog connector on the Routine) |\n| `dependency-triage` | Mon 08:xx | `triage` pass over open dependency PRs + `npm audit` \u002F `pip-audit`; one summary issue | Cloud |\n| `market-watch` | 1st Tue of the month, 09:xx | Re-checks competitors and complaint themes against `docs\u002Fproduct\u002FVALIDATION.md`; one issue only if something changed | Cloud |\n| `supabase-advisor` | Wed 08:xx | Security\u002Fperformance advisors → one issue per new finding | Cloud (needs the Supabase connector) |\n| `harness-optimize` | Fri 16:xx | Harness-change PR from the week's session signal | **Local**: it reads session transcripts on the machine where you work |\n| `reflect` | Fri 16:xx | Memory notes PR | **Local**, same reason |\n\nEstimated cost: each cloud run is one agent session, roughly a normal working\nsession's tokens. Say that in the question. Recommend the first two by default.\n\n## 2. Create the ones they picked\n\nEach ritual's procedure lives in `.agents\u002Froutines\u002F\u003Critual>.md` (cadence, where it\nruns, connectors, steps). The Routine's prompt just points there, so the procedure is\nversioned and reviewed with the code.\n\n**Claude Code (cloud Routines).** Run `\u002Fschedule` (alias `\u002Froutines`) and create one\nroutine per pick against this GitHub repo, with a prompt that stands alone because\neach run starts fresh:\n\n```\nIn \u003Cowner>\u002F\u003Crepo>: follow .agents\u002Froutines\u002F\u003Critual>.md end to end.\nNever merge, never push to main, never file a ticket the procedure says needs\napproval: put proposals in one issue titled \"\u003Critual>: \u003Cdate>\" instead.\n```\n\nAdd only the connectors that ritual needs (PostHog, Supabase, Linear). Use a minute\nthat isn't :00 to avoid the top-of-hour rush. Manage or delete them later at\nclaude.ai\u002Fcode\u002Froutines.\n\n**Codex \u002F any agent (local cron).** Codex has no cloud scheduler; use the machine's:\n\n```cron\n# crontab -e   (runs in the repo; logs to ~\u002F.local\u002Fstate\u002F\u003Cslug>-rituals.log)\n13 8 * * 1  codex exec -C \u002Fpath\u002Fto\u002Frepo --approve-for-me -c sandbox_workspace_write.network_access=true \"Follow .agents\u002Froutines\u002Fnorth-star-report.md.\" >> ~\u002F.local\u002Fstate\u002F\u003Cslug>-rituals.log 2>&1\n47 16 * * 5 codex exec -C \u002Fpath\u002Fto\u002Frepo --approve-for-me -c sandbox_workspace_write.network_access=true \"Follow .agents\u002Froutines\u002Freflect.md, then .agents\u002Froutines\u002Fharness-optimize.md.\" >> ~\u002F.local\u002Fstate\u002F\u003Cslug>-rituals.log 2>&1\n```\n\nFor Claude Code the local equivalent is\n`cd \u002Fpath\u002Fto\u002Frepo && claude -p \"\u002Fharness-optimize\" --permission-mode auto`. Cron\nruns can't answer an approval prompt, so pick a mode that won't stop to ask. On macOS, prefer a\n`launchd` agent (cron may lack disk access). These flags were checked against\n`codex-cli 0.159.3` (`-C`, `--approve-for-me`, `-c`); confirm with `codex exec --help` \u002F\n`claude --help` first, since CLIs drift.\n\n## 3. Record it\n\nAdd each scheduled ritual's name to `.claude\u002Fharness\u002Fmanifest.json` →\n`cadence.scheduled` (e.g. `[\"north-star-report\", \"dependency-triage\"]`), so the\nsession-start nudge stops asking you to run by hand what a routine already runs.\nCommit that on a branch with a PR (`chore: schedule rituals`), and log it in\n`docs\u002Fdecision-log.md` (who agreed, what runs, where).\n\nReply with a table: ritual → where it runs → first run time → how to stop it.\n\n## Ask the owner\n\nFollow `.agents\u002Frules\u002Fproduct-judgement.md`: ask with a structured question (recommended option first), never decide these silently. In this skill that means: Which rituals run unattended and on what schedule, since each run spends tokens and can open issues or PRs. One yes per routine.\n",{"name":5,"description":7,"disable-model-invocation":24},true,"main","82b5819f074e18b5d31db7a122e1f0ae5f5abbf7","plugins\u002Fapp-in-a-box\u002Ftemplate\u002F.agents\u002Fskills\u002Froutines","https:\u002F\u002Fgithub.com\u002Ffoxinthehenhouse\u002Fapp-in-a-box","https:\u002F\u002Fgithub.com\u002Ffoxinthehenhouse","Not a developer","2026-10-06 17:24:46",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":24},[34,37,40],{"tool":35,"command":36},"npx","npx skills add foxinthehenhouse\u002Fapp-in-a-box --skill routines",{"tool":38,"command":39},"bunx","bunx skills add foxinthehenhouse\u002Fapp-in-a-box --skill routines",{"tool":41,"command":42},"pnpm","pnpm dlx skills add foxinthehenhouse\u002Fapp-in-a-box --skill routines","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ffoxinthehenhouse\u002Fapp-in-a-box\u002Fblob\u002Fmain\u002Fplugins\u002Fapp-in-a-box\u002Ftemplate\u002F.agents\u002Fskills\u002Froutines\u002FSKILL.md",[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M7DM2EPAFBTFNV5EW5GHKD5Q","ship","Release checklist for getting a build to testers or the stores. Runs the risk gate first (refuses while a risk item is open) and walks the owner through the compliance checklist. Covers the version bump, EAS build and submit, OTA updates and when they're safe, changelog, store listing, privacy nutrition label \u002F data safety form, the Accessibility Nutrition Labels, and the account-deletion requirement. Guidance-level; it never handles signing secrets. Use when asked to ship, release, submit to TestFlight \u002F App Store \u002F Play, or push an OTA update.","https:\u002F\u002Fgithub.com\u002Ffoxinthehenhouse\u002Fapp-in-a-box\u002Fblob\u002Fmain\u002Fplugins\u002Fapp-in-a-box\u002Ftemplate\u002F.agents\u002Fskills\u002Fship\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M7DM27C3K1Y7FM0NZSBRSVEN","reflect","Consolidate what recent sessions learned into the project's long-term memory (.agents\u002Fmemory). Use at the end of a substantial session, after a correction from the user, after a painful debugging session, when the session-start healthcheck says reflect is overdue or a pending-reflection seed is waiting, or when MEMORY.md exceeds its budget.","https:\u002F\u002Fgithub.com\u002Ffoxinthehenhouse\u002Fapp-in-a-box\u002Fblob\u002Fmain\u002Fplugins\u002Fapp-in-a-box\u002Ftemplate\u002F.agents\u002Fskills\u002Freflect\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7DM2146TCNYXVVS2QXF08GS","pr-review","Review a pull request on the owner's behalf and fix what's safe to fix. Runs the deterministic gates first, then correctness\u002Fsecurity, design-system, accessibility and analytics review passes, verifies each blocking finding, applies safe fixes, re-checks, and ends with a plain-English verdict. Use when a PR is opened, when asked to review a PR, a branch or a pasted diff, or before merging anything.","https:\u002F\u002Fgithub.com\u002Ffoxinthehenhouse\u002Fapp-in-a-box\u002Fblob\u002Fmain\u002Fplugins\u002Fapp-in-a-box\u002Ftemplate\u002F.agents\u002Fskills\u002Fpr-review\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7DM1X6QP3QAT47ET852S0P8","north-star-report","Weekly product-analytics and reliability readout. Pulls the funnel of the brief's 5 north-star events from PostHog, finds the biggest drop-offs and errors, checks each SLO in docs\u002Fslo.yaml against its error budget, compares with last week, and proposes (then, with a yes, files) tickets that target them. Use weekly, when the session-start line says it's overdue, when the backlog is empty, or when asked \"how is the app doing?\".","https:\u002F\u002Fgithub.com\u002Ffoxinthehenhouse\u002Fapp-in-a-box\u002Fblob\u002Fmain\u002Fplugins\u002Fapp-in-a-box\u002Ftemplate\u002F.agents\u002Fskills\u002Fnorth-star-report\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7DM1QX8F3D95JSTEHC0P9QA","next","Decide the single next best thing to work on, with two alternates. Reads setup progress, work in progress, open PRs and failing CI, the backlog (GitHub Issues or Linear), overdue harness rituals, product decisions parked until now, and north-star analytics if PostHog is connected. Use when someone asks \"what next?\", \"what should I work on?\", at the start of a session, or after a PR merges.","https:\u002F\u002Fgithub.com\u002Ffoxinthehenhouse\u002Fapp-in-a-box\u002Fblob\u002Fmain\u002Fplugins\u002Fapp-in-a-box\u002Ftemplate\u002F.agents\u002Fskills\u002Fnext\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7DM1NGHSRAY1NJVDWE1TG9Q","new-worktree","Create an isolated git worktree + branch off origin\u002Fmain for one unit of work, so parallel agents or sessions never share a checkout. Use when starting any ticket, or when another session may be working in the main checkout.","https:\u002F\u002Fgithub.com\u002Ffoxinthehenhouse\u002Fapp-in-a-box\u002Fblob\u002Fmain\u002Fplugins\u002Fapp-in-a-box\u002Ftemplate\u002F.agents\u002Fskills\u002Fnew-worktree\u002FSKILL.md",[],[]]