[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M743APWHYHATR6N4QKTDBVEM":3,"skill-same:01M743APWHYHATR6N4QKTDBVEM":48},{"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":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M743APWHYHATR6N4QKTDBVEM","convex-deploy-guard",null,"Classify + announce the target Convex deployment before any deployment-affecting command; fresh explicit consent for prod actions; session read-only mode.","krake747\u002Fnext-bite","krake747","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F41166160?v=4","01M6C7NZHDDRQH3NNDXXY1WMDS","Kevin Kraemer","01M6C7NZNM7ZQ1XMT6ZSSFZ3CY",0,"AGPL-3.0","https:\u002F\u002Fgithub.com\u002Fkrake747\u002Fnext-bite\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fconvex-deploy-guard\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: convex-deploy-guard\ndescription: \"Classify + announce the target Convex deployment before any deployment-affecting command; fresh explicit consent for prod actions; session read-only mode.\"\n---\n\n\u003C!-- GENERATED from convex-agents content\u002Fcapabilities\u002Fdeploy-guard.json — do not edit by hand. -->\n\n# Deployment target guard\n\nDeployments are not interchangeable, and most incidents start with a command aimed at the wrong one. Every Convex project has several (personal dev, preview, prod — often across multiple projects on one machine). This guard is the standing discipline: identify, announce, then act — and treat prod as consent-gated, per action, per session.\n\n## Workflow\n\n1. IDENTIFY before you act: read `CONVEX_DEPLOYMENT` in .env.local, `convex.json`, and whether `CONVEX_DEPLOY_KEY` is set; or call the official Convex MCP `status` tool. Classify the target: local-anonymous | dev | preview | prod. If two sources disagree, resolve before proceeding.\n2. ANNOUNCE in one line before any deployment-affecting command: `target: dev (joyful-capybara-123, personal dev)`. Never run the command in the same breath as discovering the target — announce first.\n3. PROD needs a FRESH explicit yes: before `npx convex deploy` (when it resolves to prod), `npx convex run --prod`, `env set` on prod, snapshot `import`\u002F`export` on prod, or starting the MCP with prod access — state exactly what will change on which deployment and get an explicit yes in THIS session. A yes given earlier, or for a different target, does not carry.\n4. MCP safety defaults: start the official MCP scoped non-prod (`--deployment dev`). The two prod flags are DIFFERENT risk levels — keep them split: a read-only prod audit (advisor\u002Finsights reading data\u002Flogs\u002Finsights) passes ONLY `--cautiously-allow-production-pii` (read tools); `--dangerously-enable-production-deployments` (which enables MUTATING prod tools) stays OFF unless the user explicitly asked to CHANGE prod this session. Never pair them by default — 'look at prod' must not silently grant 'mutate prod'.\n5. READ-ONLY session mode: when the user says 'read-only' \u002F 'don't change anything', honor it absolutely for the rest of the session — no deploy, no env set\u002Fremove, no mutations via `run`, no imports; start the MCP with `--disable-tools run,envSet,envRemove`.\n6. Wrong-deployment diagnosis: when a deploy 'didn't change anything', do NOT re-deploy harder. Re-run step 1 — the deploy almost certainly landed on a different deployment than the one being observed.\n7. Ambiguity = stop: if you cannot determine which deployment a command will hit, find out (status tool) — never guess.\n\n## Rules\n\n- Classify and announce the target BEFORE every deployment-affecting command — identification and action are two separate steps.\n- Prod consent is per-action, per-target, per-session: state what changes where, get a fresh explicit yes.\n- Keep the two prod MCP flags split by risk: --cautiously-allow-production-pii (read-only) for an audit; --dangerously-enable-production-deployments (mutating) only when the user explicitly asks to change prod. Both are user-spoken-only; default every MCP start to a non-prod deployment selector.\n- Read-only mode, once requested, is absolute for the session — including 'harmless' mutations.\n- A deploy that seemed to do nothing means the WRONG deployment changed — diagnose the target, don't re-run.\n- This guard composes: ship, env, migrate, and seed run it as their step 0; it is not itself a deploy tool.\n","\u003C!-- GENERATED from convex-agents content\u002Fcapabilities\u002Fdeploy-guard.json — do not edit by hand. -->\n\n# Deployment target guard\n\nDeployments are not interchangeable, and most incidents start with a command aimed at the wrong one. Every Convex project has several (personal dev, preview, prod — often across multiple projects on one machine). This guard is the standing discipline: identify, announce, then act — and treat prod as consent-gated, per action, per session.\n\n## Workflow\n\n1. IDENTIFY before you act: read `CONVEX_DEPLOYMENT` in .env.local, `convex.json`, and whether `CONVEX_DEPLOY_KEY` is set; or call the official Convex MCP `status` tool. Classify the target: local-anonymous | dev | preview | prod. If two sources disagree, resolve before proceeding.\n2. ANNOUNCE in one line before any deployment-affecting command: `target: dev (joyful-capybara-123, personal dev)`. Never run the command in the same breath as discovering the target — announce first.\n3. PROD needs a FRESH explicit yes: before `npx convex deploy` (when it resolves to prod), `npx convex run --prod`, `env set` on prod, snapshot `import`\u002F`export` on prod, or starting the MCP with prod access — state exactly what will change on which deployment and get an explicit yes in THIS session. A yes given earlier, or for a different target, does not carry.\n4. MCP safety defaults: start the official MCP scoped non-prod (`--deployment dev`). The two prod flags are DIFFERENT risk levels — keep them split: a read-only prod audit (advisor\u002Finsights reading data\u002Flogs\u002Finsights) passes ONLY `--cautiously-allow-production-pii` (read tools); `--dangerously-enable-production-deployments` (which enables MUTATING prod tools) stays OFF unless the user explicitly asked to CHANGE prod this session. Never pair them by default — 'look at prod' must not silently grant 'mutate prod'.\n5. READ-ONLY session mode: when the user says 'read-only' \u002F 'don't change anything', honor it absolutely for the rest of the session — no deploy, no env set\u002Fremove, no mutations via `run`, no imports; start the MCP with `--disable-tools run,envSet,envRemove`.\n6. Wrong-deployment diagnosis: when a deploy 'didn't change anything', do NOT re-deploy harder. Re-run step 1 — the deploy almost certainly landed on a different deployment than the one being observed.\n7. Ambiguity = stop: if you cannot determine which deployment a command will hit, find out (status tool) — never guess.\n\n## Rules\n\n- Classify and announce the target BEFORE every deployment-affecting command — identification and action are two separate steps.\n- Prod consent is per-action, per-target, per-session: state what changes where, get a fresh explicit yes.\n- Keep the two prod MCP flags split by risk: --cautiously-allow-production-pii (read-only) for an audit; --dangerously-enable-production-deployments (mutating) only when the user explicitly asks to change prod. Both are user-spoken-only; default every MCP start to a non-prod deployment selector.\n- Read-only mode, once requested, is absolute for the session — including 'harmless' mutations.\n- A deploy that seemed to do nothing means the WRONG deployment changed — diagnose the target, don't re-run.\n- This guard composes: ship, env, migrate, and seed run it as their step 0; it is not itself a deploy tool.\n",{"name":5,"description":7},"main","3c970b39d008db97116163d98fcac34ddbfa6d3a",".agents\u002Fskills\u002Fconvex-deploy-guard",1,"https:\u002F\u002Fgithub.com\u002Fkrake747\u002Fnext-bite","https:\u002F\u002Fnextbite.kevinkraemer.com","https:\u002F\u002Fgithub.com\u002Fkrake747","https:\u002F\u002Fwww.kevinkraemer.com","Full-stack dev into functional programming. Curious, easy-going, and always up for a ride on road or gravel.","2026-11-15 03:33:16",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add krake747\u002Fnext-bite --skill convex-deploy-guard",{"tool":40,"command":41},"bunx","bunx skills add krake747\u002Fnext-bite --skill convex-deploy-guard",{"tool":43,"command":44},"pnpm","pnpm dlx skills add krake747\u002Fnext-bite --skill convex-deploy-guard","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkrake747\u002Fnext-bite\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fconvex-deploy-guard\u002FSKILL.md",true,[],[49,57,64,71,78,85],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":56},"01M7DS27FA8C6TBS02DHT6R6D2","react-review","Use when reviewing React components, hooks, or route files for idiomatic React, when the user asks for refactor targets or a React cleanup pass, or types \u002Freact-review. Reports composition, colocation, state ownership, and repo-idiom findings ranked by hurt. It reports, it does not fix. External scanner counterpart is react-doctor.","https:\u002F\u002Fgithub.com\u002Fkrake747\u002Fnext-bite\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Freact-review\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M743DFMPGZYXA36R160AE5GQ","writing-for-agents","Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.","https:\u002F\u002Fgithub.com\u002Fkrake747\u002Fnext-bite\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwriting-for-agents\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M743DD5BX30Q0369WKWK16ZZ","wizard","Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.","https:\u002F\u002Fgithub.com\u002Fkrake747\u002Fnext-bite\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwizard\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M743D9JSP6KD0YRZ96AXB4DN","wait-what","Stop. That last message did not land: re-pitch it.","https:\u002F\u002Fgithub.com\u002Fkrake747\u002Fnext-bite\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwait-what\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M743D26PT5F1DTZKKAAXNQHH","to-questionnaire","Turn a decision you can't fully answer into a questionnaire for someone else to fill in.","https:\u002F\u002Fgithub.com\u002Fkrake747\u002Fnext-bite\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fto-questionnaire\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M743CTKH749CZ429C9XWF2GJ","retro","Conduct a retrospective on a coding session.","https:\u002F\u002Fgithub.com\u002Fkrake747\u002Fnext-bite\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fretro\u002FSKILL.md",[],[]]