[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75XF57B40THERT6SH1NXVSQ":3,"skill-same:01M75XF57B40THERT6SH1NXVSQ":47},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":29,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M75XF57B40THERT6SH1NXVSQ","project-rotate-secrets",null,"Use when a session starts to apply a pending secret rotation, when `just rotate-secrets` collected new values, or when `bin\u002Frotate-secrets apply` stopped with exit 10 or 11.","loupe-ac\u002Floupe","loupe-ac","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F345019842?v=4","01M75XDH3V7GZDHB5M0J04BFTP","Loupe","01M75XDH4EWXVAMQEHFV5TWBMF",2,"AGPL-3.0","https:\u002F\u002Fgithub.com\u002Floupe-ac\u002Floupe\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fproject-rotate-secrets\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: project-rotate-secrets\ndescription: \"Use when a session starts to apply a pending secret rotation, when `just rotate-secrets` collected new values, or when `bin\u002Frotate-secrets apply` stopped with exit 10 or 11.\"\n---\n\n# Applying a pending secret rotation\n\n`just rotate-secrets` collects the new values and saves them as pending. It changes nothing live. This skill applies them. You never see a secret value, and you must never try to read one. The secret read hook refuses the store, `terraform.tfvars`, saved plans and the `.rotate-secrets.tmp.*` files.\n\nInvoke `project-deploy` as well. It carries the production console command and the checks after a deploy.\n\n## The loop\n\nRun `bin\u002Frotate-secrets apply` from the main checkout. Read its exit code, and act on it:\n\n| Exit | Meaning | Do this |\n|---|---|---|\n| 0 | Every pending value is live. | Go to \"When it finishes\". |\n| 10 | The second encryption key deploy is live. | Go to \"Re-encrypt\". |\n| 11 | A plan changes a resource or an app field beyond the rotated secrets. Nothing was applied. | Go to \"An unexpected plan\". |\n| Other | A plan, an apply, a deployment or a GitHub call failed. | Report the error lines to the owner, and stop. A rerun of `bin\u002Frotate-secrets apply` resumes. |\n\nEach apply saves a plan, checks it, and applies that plan. Terraform asks nothing. The owner trusts the script's plan check, so do not ask the owner before an apply.\n\nA rotation of `github_app_webhook_secret` waits for the new deployment and resends the failed GitHub deliveries. That can take several minutes. Run the command with a timeout of 10 minutes.\n\n## Re-encrypt\n\nRun the re-encrypt in the production `web` console. `doctl apps console` needs a TTY, so give it one with `script`:\n\n```bash\nAPP=$(just tf-output -raw app_id | tail -1)\n(sleep 8; printf 'bin\u002Fconsole doctrine-extra:reencrypt --no-ansi; echo RE_EXIT=$?; exit\\n'; sleep 150) \\\n  | script -q \u002Fdev\u002Fnull doctl apps console \"$APP\" web 2>&1 | tail -40\n```\n\nRead the table. Every `Unreadable` count must be 0, and `RE_EXIT` must be 0. Then run `bin\u002Frotate-secrets apply --reencrypted`, and go back to the loop.\n\nWhen a count is not 0, or the console does not connect, stop. Show the owner the table or the error line. The old key stays in `app_encryption_key_previous`, so nothing is lost. `docs\u002Foperating\u002Frotating-encryption-key.md` says what to do next.\n\n## An unexpected plan\n\nThe script prints each extra resource as `\u003Caddress> \u003Cactions>`, and each extra app field by name, such as `spec.env.ADMIN_EMAIL`. It prints no value. Show the owner the list, and ask whether to accept it. Name the likely cause when you know it, such as a Terraform change on `main` that nobody applied.\n\nWhen the owner accepts, run `bin\u002Frotate-secrets apply --allow \u003Cname>` with one `--allow` for each name. An `--allow` counts for one run only. Repeat it on a later run, such as `apply --reencrypted`, when the same name comes back. Otherwise stop. The pending values stay. `bin\u002Frotate-secrets discard` refuses after an apply starts, because the live store can hold values that production lacks.\n\n## When it finishes\n\n1. Run `just healthz`, and report the version it prints.\n2. Relay the \"Revoke by hand\" list to the owner, item by item. The owner revokes each old credential at its vendor.\n3. When the output asks to end the sessions after an `app_secret` rotation, relay that command to the owner. Do not run it yourself, because it signs the owner out too.\n4. Report what changed: the secrets that rotated, the number of applies, and anything the owner still has to do.\n","# Applying a pending secret rotation\n\n`just rotate-secrets` collects the new values and saves them as pending. It changes nothing live. This skill applies them. You never see a secret value, and you must never try to read one. The secret read hook refuses the store, `terraform.tfvars`, saved plans and the `.rotate-secrets.tmp.*` files.\n\nInvoke `project-deploy` as well. It carries the production console command and the checks after a deploy.\n\n## The loop\n\nRun `bin\u002Frotate-secrets apply` from the main checkout. Read its exit code, and act on it:\n\n| Exit | Meaning | Do this |\n|---|---|---|\n| 0 | Every pending value is live. | Go to \"When it finishes\". |\n| 10 | The second encryption key deploy is live. | Go to \"Re-encrypt\". |\n| 11 | A plan changes a resource or an app field beyond the rotated secrets. Nothing was applied. | Go to \"An unexpected plan\". |\n| Other | A plan, an apply, a deployment or a GitHub call failed. | Report the error lines to the owner, and stop. A rerun of `bin\u002Frotate-secrets apply` resumes. |\n\nEach apply saves a plan, checks it, and applies that plan. Terraform asks nothing. The owner trusts the script's plan check, so do not ask the owner before an apply.\n\nA rotation of `github_app_webhook_secret` waits for the new deployment and resends the failed GitHub deliveries. That can take several minutes. Run the command with a timeout of 10 minutes.\n\n## Re-encrypt\n\nRun the re-encrypt in the production `web` console. `doctl apps console` needs a TTY, so give it one with `script`:\n\n```bash\nAPP=$(just tf-output -raw app_id | tail -1)\n(sleep 8; printf 'bin\u002Fconsole doctrine-extra:reencrypt --no-ansi; echo RE_EXIT=$?; exit\\n'; sleep 150) \\\n  | script -q \u002Fdev\u002Fnull doctl apps console \"$APP\" web 2>&1 | tail -40\n```\n\nRead the table. Every `Unreadable` count must be 0, and `RE_EXIT` must be 0. Then run `bin\u002Frotate-secrets apply --reencrypted`, and go back to the loop.\n\nWhen a count is not 0, or the console does not connect, stop. Show the owner the table or the error line. The old key stays in `app_encryption_key_previous`, so nothing is lost. `docs\u002Foperating\u002Frotating-encryption-key.md` says what to do next.\n\n## An unexpected plan\n\nThe script prints each extra resource as `\u003Caddress> \u003Cactions>`, and each extra app field by name, such as `spec.env.ADMIN_EMAIL`. It prints no value. Show the owner the list, and ask whether to accept it. Name the likely cause when you know it, such as a Terraform change on `main` that nobody applied.\n\nWhen the owner accepts, run `bin\u002Frotate-secrets apply --allow \u003Cname>` with one `--allow` for each name. An `--allow` counts for one run only. Repeat it on a later run, such as `apply --reencrypted`, when the same name comes back. Otherwise stop. The pending values stay. `bin\u002Frotate-secrets discard` refuses after an apply starts, because the live store can hold values that production lacks.\n\n## When it finishes\n\n1. Run `just healthz`, and report the version it prints.\n2. Relay the \"Revoke by hand\" list to the owner, item by item. The owner revokes each old credential at its vendor.\n3. When the output asks to end the sessions after an `app_secret` rotation, relay that command to the owner. Do not run it yourself, because it signs the owner out too.\n4. Report what changed: the secrets that rotated, the number of applies, and anything the owner still has to do.\n",{"name":5,"description":7},"main","b0ae29efd5410c4e5bf9a6ed6aed4b6c1d82e55a",".agents\u002Fskills\u002Fproject-rotate-secrets",0,"https:\u002F\u002Fgithub.com\u002Floupe-ac\u002Floupe","https:\u002F\u002Floupe.ac\u002F","https:\u002F\u002Fgithub.com\u002Floupe-ac","The control plane for your agent loops.","2026-11-15 04:50:14",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add loupe-ac\u002Floupe --skill project-rotate-secrets",{"tool":39,"command":40},"bunx","bunx skills add loupe-ac\u002Floupe --skill project-rotate-secrets",{"tool":42,"command":43},"pnpm","pnpm dlx skills add loupe-ac\u002Floupe --skill project-rotate-secrets","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Floupe-ac\u002Floupe\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fproject-rotate-secrets\u002FSKILL.md",true,[],[48,55,62,69,76,83],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M75XHSK6MYZ0BH7PJHP378QV","loupe-workers","Use when reading worker runs or bridges through the loupe MCP, stopping, resuming or holding workers, cancelling a bridge command, or recovering workers after a usage limit or network outage.","https:\u002F\u002Fgithub.com\u002Floupe-ac\u002Floupe\u002Fblob\u002Fmain\u002Fplugins\u002Floupe\u002Fskills\u002Floupe-workers\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M75XHPW77P75PPWY8Z7Q9XMZ","loupe-site-review","Use when acting on live-review feedback through the loupe MCP: reading the feedback of a card or project, fixing it, or marking it addressed.","https:\u002F\u002Fgithub.com\u002Floupe-ac\u002Floupe\u002Fblob\u002Fmain\u002Fplugins\u002Floupe\u002Fskills\u002Floupe-site-review\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M75XHK6EZP2FZRQ1B4PS4CGH","loupe-inbox","Use when an agent needs a decision, answer or review from the project owner through the loupe MCP, hands a question or to-do to a person, resumes after an ask closed, or needs its session id.","https:\u002F\u002Fgithub.com\u002Floupe-ac\u002Floupe\u002Fblob\u002Fmain\u002Fplugins\u002Floupe\u002Fskills\u002Floupe-inbox\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M75XHDN9XG71R4T248BZ540A","loupe-documents","Use when writing or revising a document for the Loupe app through the loupe MCP, such as a plan, spec, RFC, audit report or retrospective.","https:\u002F\u002Fgithub.com\u002Floupe-ac\u002Floupe\u002Fblob\u002Fmain\u002Fplugins\u002Floupe\u002Fskills\u002Floupe-documents\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M75XHBERM2SWJ7SJ1EB5M4SB","loupe-discovery","Use when a bridge runs a discovery run of a Loupe project, when a prompt names loupe-discovery, or when writing a readiness report.","https:\u002F\u002Fgithub.com\u002Floupe-ac\u002Floupe\u002Fblob\u002Fmain\u002Fplugins\u002Floupe\u002Fskills\u002Floupe-discovery\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M75XH7X2KCFWPVMQJJAMPYJN","loupe-board","Use when working a Loupe project board through the loupe MCP: reading or writing a card, moving a card, changing the columns, or linking a document or a pull request to a card.","https:\u002F\u002Fgithub.com\u002Floupe-ac\u002Floupe\u002Fblob\u002Fmain\u002Fplugins\u002Floupe\u002Fskills\u002Floupe-board\u002FSKILL.md",[],[]]