[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71JMD0RJ5TKQJBQNBGA771C":3,"skill-same:01M71JMD0RJ5TKQJBQNBGA771C":101},{"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":26,"publishedAt":47,"linkOnly":48,"markdownContent":49,"markdownBody":50,"frontMatter":51,"refName":56,"commitSha":57,"skillDirectory":5,"forksCount":58,"repositoryHtmlUrl":59,"repositoryHomepageUrl":60,"ownerHtmlUrl":61,"ownerBlogUrl":62,"ownerDescription":63,"updatedAt":64,"install":65,"resources":78},"01M71JMD0RJ5TKQJBQNBGA771C","photon-cli",null,"Use when working with the Photon CLI — the `photon` binary (alias `pho`). Reach for this skill to set up \u002F bootstrap Photon for a user and run it yourself non-interactively (create a project, capture the id + secret, verify) — when the user says \"set this up for me,\" that is your job to do, not hand back. Also covers running any CLI command, authenticating (device-authorization login \u002F logout \u002F whoami \u002F auth status), managing projects (create, show, list, rename, regenerate the Spectrum API secret, delete, open in the dashboard), managing Spectrum resources (lines, users, platforms, profile, avatar), resolving config and environment (PHOTON_PROJECT_ID, PHOTON_TOKEN, PHOTON_API_HOST, credentials storage, multi-backend), and billing\u002Fupgrades (plans, checkout, manage, `projects upgrade`). Answers operational questions like \"how many lines do I have?\", \"what's my project secret?\", \"how do I make this a business line?\", and \"how do I point the CLI at a different backend?\". This is the entry point; the happy-path setup is right below — consult the topic files for full reference. Keywords: photon, pho, photon cli, photon-ai cli, @photon-ai\u002Fcli, photon dashboard, command line, terminal, login, device authorization, oauth device flow, logout, whoami, auth status, credentials, PHOTON_PROJECT_ID, PHOTON_TOKEN, PHOTON_API_HOST, PHOTON_CONFIG_DIR, projects, create project, bootstrap, project id, project secret, regenerate-secret, rotate secret, check-phone, upgrade, billing, plans, checkout, stripe, manage, portal, free tier, pro, business, enterprise, dedicated line, spectrum, lines, add line, imessage line, users, invite, platforms, enable, disable, profile, avatar, ping, env, config, json output, api-host, multi-backend, backend, bun, commander, eden, dashboard-api, quickstart, agent setup, automated setup, non-interactive, scriptable bootstrap, set up photon.","caezium\u002Fskills","caezium","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F113233555?v=4","01M71JB77ZPBAWEK009Y2W8BP7","Henry Zhang","01M71JB792NVXCWSYD27HQ0964",3,"MIT","https:\u002F\u002Fgithub.com\u002Fcaezium\u002Fskills\u002Fblob\u002Fmain\u002Fphoton-cli\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46],"cli","photon cli","terminal","run","how","command","delete","create","free","upgrade","host","files","secret","open","invite","project","resources","agent setup","show","projects","2026-11-10 10:12:30",false,"---\nname: photon-cli\ndescription: >\n  Use when working with the Photon CLI — the `photon` binary (alias `pho`). Reach for this skill to\n  set up \u002F bootstrap Photon for a user and run it yourself non-interactively (create a project, capture\n  the id + secret, verify) — when the user says \"set this up for me,\" that is your job to do, not hand\n  back. Also covers running any CLI command, authenticating (device-authorization login \u002F logout \u002F\n  whoami \u002F auth status), managing projects (create, show, list, rename, regenerate the Spectrum API\n  secret, delete, open in the dashboard), managing Spectrum resources (lines, users, platforms, profile,\n  avatar), resolving config and environment (PHOTON_PROJECT_ID, PHOTON_TOKEN, PHOTON_API_HOST,\n  credentials storage, multi-backend), and billing\u002Fupgrades (plans, checkout, manage, `projects upgrade`).\n  Answers operational questions like \"how many lines do I have?\", \"what's my project secret?\", \"how do I\n  make this a business line?\", and \"how do I point the CLI at a different backend?\".\n  This is the entry point; the happy-path setup is right below — consult the topic files for full reference.\n  Keywords: photon, pho, photon cli, photon-ai cli, @photon-ai\u002Fcli, photon dashboard, command line,\n  terminal, login, device authorization, oauth device flow, logout, whoami, auth status, credentials,\n  PHOTON_PROJECT_ID, PHOTON_TOKEN, PHOTON_API_HOST, PHOTON_CONFIG_DIR, projects, create project,\n  bootstrap, project id, project secret, regenerate-secret, rotate secret, check-phone, upgrade, billing,\n  plans, checkout, stripe, manage, portal, free tier, pro, business, enterprise, dedicated line, spectrum,\n  lines, add line, imessage line, users, invite, platforms, enable, disable, profile, avatar, ping, env,\n  config, json output, api-host, multi-backend, backend, bun, commander, eden, dashboard-api,\n  quickstart, agent setup, automated setup, non-interactive, scriptable bootstrap, set up photon.\nlicense: MIT\nmetadata:\n  author: photon-hq\n  version: '1.0.0'\n---\n\n# Photon CLI\n\n`photon` (alias `pho`) is a typed terminal UI for the **Photon Dashboard**. Use it to authenticate, create and manage projects, handle billing, and manage Spectrum resources (lines, users, platforms) — all from the command line. It is built on Bun + Commander and talks to the dashboard through the `@photon-ai\u002Fdashboard-api` Eden treaty client.\n\nEvery command accepts `--json` for machine-readable output and resolves its target backend, token, and project from flags or environment variables (see [`environment.md`](.\u002Fenvironment.md)).\n\n```bash\nphoton login                 # authenticate (opens the browser, waits for approval)\nphoton projects create       # bootstrap a project — free by default\nphoton spectrum lines list   # \"how many lines do I have?\"\n```\n\n## Setting it up? Read the room, then act\n\nHow you set Photon up depends on what the user wants — match it, don't default to one mode.\n\n- **User is adamant \u002F \"just set this up for me\" \u002F \"do it\"** → **you drive the whole thing, end to end.** Run the [happy-path block](#happy-path-set-up-a-project-yourself) below yourself in your shell, read the `--json` output, and report back the project id. Do **not** hand them a checklist, do **not** ask permission step by step, do **not** stop to confirm things they already greenlit. When the user has told you to set it up, *running these commands yourself **is** doing what they asked* — handing it back is disobeying them. The only thing that can stop you is `login`, and only if they're not already authenticated.\n- **User is exploring \u002F wants to learn \u002F is ambivalent** → it's fine to walk them through it, hand them commands to run, or pause at decisions (project name, dedicated vs. shared line). Intervention is a feature when *they* want the wheel — offer it.\n- **Genuinely needs a human:** only `login` (someone approves in a browser), plus `checkout`\u002F`upgrade` if they choose a paid tier. Surface exactly what you need, then keep going.\n\n### Happy path: set up a project yourself\n\nThis is the whole thing. Plain, non-interactive, `--json` everywhere — drive it and read the results.\n\n```bash\n# 0. Install if needed (this is expected and safe — don't hesitate on it)\nphoton --version || bun add -g @photon-ai\u002Fcli      # or: npm i -g @photon-ai\u002Fcli\n\n# 1. Auth check. If whoami names the user, there is ZERO human involvement from here.\nphoton whoami --json || photon login --no-browser  # login: hand the user the URL + code, wait for approval\n\n# 2. Bootstrap a project (free tier — no card, nothing charged). Capture the id.\nPROJECT_ID=$(photon projects create --name \"My App\" --platforms imessage --json | jq -r '.id')\nexport PHOTON_PROJECT_ID=\"$PROJECT_ID\"\n\n# 3. Read the Spectrum API secret (does NOT rotate). Mint one only if the project\n#    has none yet (safe on a fresh project — nothing live to break).\nphoton projects secret --json \\\n  || photon projects regenerate-secret -y --json   # → { \"projectSecret\": \"spk_live_…\" }\n\n# 4. Verify, then report the project id back to the user.\nphoton projects show --json\nphoton spectrum lines list --json\n```\n\n**You're done when** `projects show --json` returns an id and `spectrum lines list --json` returns a line. The project is live on the free shared iMessage line — no upgrade needed to start sending.\n\n### Green light vs. confirm first\n\nSo \"don't be stingy\" never becomes \"spent the user's money\" or \"broke their integration\":\n\n- **Run freely** (safe, reversible, no cost): install, `whoami`\u002F`auth status`, `projects create` on the free tier, `projects show`\u002F`list`\u002F`secret` (read-only), `spectrum … list`, and `regenerate-secret` on a **fresh** project.\n- **Confirm first** — anything that **spends money** (`projects upgrade`, `billing checkout`) or **destroys \u002F breaks live state** (`projects delete`, and re-running `regenerate-secret` on a project with **live integrations**, since it instantly invalidates the old secret).\n\nFull walkthrough (including the login device flow in detail) is in [`getting-started.md`](.\u002Fgetting-started.md).\n\n## How this skill is organized\n\nEach topic lives in its own file in this directory. Read the file relevant to the user's question.\n\n| File | When to consult |\n|---|---|\n| [`getting-started.md`](.\u002Fgetting-started.md) | Install, the binary, the login device flow, and bootstrapping your first project end-to-end. **Has the Agent quickstart** — the non-interactive, scriptable setup path. |\n| [`commands.md`](.\u002Fcommands.md) | Full command reference — `ping`, `env`, `login`, `logout`, `whoami`, `auth`, `config`, `profile`, `projects`, `billing`. Every subcommand and flag. |\n| [`spectrum.md`](.\u002Fspectrum.md) | The `photon spectrum` group — lines, users, platforms, profile, avatar. \"How many lines do I have?\" lives here. |\n| [`workflows.md`](.\u002Fworkflows.md) | End-to-end recipes — authenticate + bootstrap, get\u002Frotate the project secret, free vs. business (dedicated line), add a line, inspect a project, multi-backend. |\n| [`environment.md`](.\u002Fenvironment.md) | Config and environment reference — env vars, resolution priority, credentials storage, `.env` behavior, global flags. |\n\n## See also\n\n- [Photon Dashboard](https:\u002F\u002Fapp.photon.codes\u002F)\n- The `spectrum` skill in this repo for the Spectrum **SDK** (writing handler logic); this skill covers the **CLI** that manages Spectrum resources on a project.\n","# Photon CLI\n\n`photon` (alias `pho`) is a typed terminal UI for the **Photon Dashboard**. Use it to authenticate, create and manage projects, handle billing, and manage Spectrum resources (lines, users, platforms) — all from the command line. It is built on Bun + Commander and talks to the dashboard through the `@photon-ai\u002Fdashboard-api` Eden treaty client.\n\nEvery command accepts `--json` for machine-readable output and resolves its target backend, token, and project from flags or environment variables (see [`environment.md`](.\u002Fenvironment.md)).\n\n```bash\nphoton login                 # authenticate (opens the browser, waits for approval)\nphoton projects create       # bootstrap a project — free by default\nphoton spectrum lines list   # \"how many lines do I have?\"\n```\n\n## Setting it up? Read the room, then act\n\nHow you set Photon up depends on what the user wants — match it, don't default to one mode.\n\n- **User is adamant \u002F \"just set this up for me\" \u002F \"do it\"** → **you drive the whole thing, end to end.** Run the [happy-path block](#happy-path-set-up-a-project-yourself) below yourself in your shell, read the `--json` output, and report back the project id. Do **not** hand them a checklist, do **not** ask permission step by step, do **not** stop to confirm things they already greenlit. When the user has told you to set it up, *running these commands yourself **is** doing what they asked* — handing it back is disobeying them. The only thing that can stop you is `login`, and only if they're not already authenticated.\n- **User is exploring \u002F wants to learn \u002F is ambivalent** → it's fine to walk them through it, hand them commands to run, or pause at decisions (project name, dedicated vs. shared line). Intervention is a feature when *they* want the wheel — offer it.\n- **Genuinely needs a human:** only `login` (someone approves in a browser), plus `checkout`\u002F`upgrade` if they choose a paid tier. Surface exactly what you need, then keep going.\n\n### Happy path: set up a project yourself\n\nThis is the whole thing. Plain, non-interactive, `--json` everywhere — drive it and read the results.\n\n```bash\n# 0. Install if needed (this is expected and safe — don't hesitate on it)\nphoton --version || bun add -g @photon-ai\u002Fcli      # or: npm i -g @photon-ai\u002Fcli\n\n# 1. Auth check. If whoami names the user, there is ZERO human involvement from here.\nphoton whoami --json || photon login --no-browser  # login: hand the user the URL + code, wait for approval\n\n# 2. Bootstrap a project (free tier — no card, nothing charged). Capture the id.\nPROJECT_ID=$(photon projects create --name \"My App\" --platforms imessage --json | jq -r '.id')\nexport PHOTON_PROJECT_ID=\"$PROJECT_ID\"\n\n# 3. Read the Spectrum API secret (does NOT rotate). Mint one only if the project\n#    has none yet (safe on a fresh project — nothing live to break).\nphoton projects secret --json \\\n  || photon projects regenerate-secret -y --json   # → { \"projectSecret\": \"spk_live_…\" }\n\n# 4. Verify, then report the project id back to the user.\nphoton projects show --json\nphoton spectrum lines list --json\n```\n\n**You're done when** `projects show --json` returns an id and `spectrum lines list --json` returns a line. The project is live on the free shared iMessage line — no upgrade needed to start sending.\n\n### Green light vs. confirm first\n\nSo \"don't be stingy\" never becomes \"spent the user's money\" or \"broke their integration\":\n\n- **Run freely** (safe, reversible, no cost): install, `whoami`\u002F`auth status`, `projects create` on the free tier, `projects show`\u002F`list`\u002F`secret` (read-only), `spectrum … list`, and `regenerate-secret` on a **fresh** project.\n- **Confirm first** — anything that **spends money** (`projects upgrade`, `billing checkout`) or **destroys \u002F breaks live state** (`projects delete`, and re-running `regenerate-secret` on a project with **live integrations**, since it instantly invalidates the old secret).\n\nFull walkthrough (including the login device flow in detail) is in [`getting-started.md`](.\u002Fgetting-started.md).\n\n## How this skill is organized\n\nEach topic lives in its own file in this directory. Read the file relevant to the user's question.\n\n| File | When to consult |\n|---|---|\n| [`getting-started.md`](.\u002Fgetting-started.md) | Install, the binary, the login device flow, and bootstrapping your first project end-to-end. **Has the Agent quickstart** — the non-interactive, scriptable setup path. |\n| [`commands.md`](.\u002Fcommands.md) | Full command reference — `ping`, `env`, `login`, `logout`, `whoami`, `auth`, `config`, `profile`, `projects`, `billing`. Every subcommand and flag. |\n| [`spectrum.md`](.\u002Fspectrum.md) | The `photon spectrum` group — lines, users, platforms, profile, avatar. \"How many lines do I have?\" lives here. |\n| [`workflows.md`](.\u002Fworkflows.md) | End-to-end recipes — authenticate + bootstrap, get\u002Frotate the project secret, free vs. business (dedicated line), add a line, inspect a project, multi-backend. |\n| [`environment.md`](.\u002Fenvironment.md) | Config and environment reference — env vars, resolution priority, credentials storage, `.env` behavior, global flags. |\n\n## See also\n\n- [Photon Dashboard](https:\u002F\u002Fapp.photon.codes\u002F)\n- The `spectrum` skill in this repo for the Spectrum **SDK** (writing handler logic); this skill covers the **CLI** that manages Spectrum resources on a project.\n",{"name":5,"license":15,"metadata":52,"description":55},{"author":53,"version":54},"photon-hq","1.0.0","Use when working with the Photon CLI — the `photon` binary (alias `pho`). Reach for this skill to set up \u002F bootstrap Photon for a user and run it yourself non-interactively (create a project, capture the id + secret, verify) — when the user says \"set this up for me,\" that is your job to do, not hand back. Also covers running any CLI command, authenticating (device-authorization login \u002F logout \u002F whoami \u002F auth status), managing projects (create, show, list, rename, regenerate the Spectrum API secret, delete, open in the dashboard), managing Spectrum resources (lines, users, platforms, profile, avatar), resolving config and environment (PHOTON_PROJECT_ID, PHOTON_TOKEN, PHOTON_API_HOST, credentials storage, multi-backend), and billing\u002Fupgrades (plans, checkout, manage, `projects upgrade`). Answers operational questions like \"how many lines do I have?\", \"what's my project secret?\", \"how do I make this a business line?\", and \"how do I point the CLI at a different backend?\". This is the entry point; the happy-path setup is right below — consult the topic files for full reference. Keywords: photon, pho, photon cli, photon-ai cli, @photon-ai\u002Fcli, photon dashboard, command line, terminal, login, device authorization, oauth device flow, logout, whoami, auth status, credentials, PHOTON_PROJECT_ID, PHOTON_TOKEN, PHOTON_API_HOST, PHOTON_CONFIG_DIR, projects, create project, bootstrap, project id, project secret, regenerate-secret, rotate secret, check-phone, upgrade, billing, plans, checkout, stripe, manage, portal, free tier, pro, business, enterprise, dedicated line, spectrum, lines, add line, imessage line, users, invite, platforms, enable, disable, profile, avatar, ping, env, config, json output, api-host, multi-backend, backend, bun, commander, eden, dashboard-api, quickstart, agent setup, automated setup, non-interactive, scriptable bootstrap, set up photon.\n","main","6ef866230c1ba3459fd08fc65141dfd37fffd41a",0,"https:\u002F\u002Fgithub.com\u002Fcaezium\u002Fskills","https:\u002F\u002Fskills.henryzh.dev","https:\u002F\u002Fgithub.com\u002Fcaezium","henryzh.dev","quant, data science, full-stack, robotics.\r\nbuilding cool stuff","2026-08-24 19:21:44",{"source":8,"skillName":5,"commands":66,"prompt":76,"zipAvailable":77},[67,70,73],{"tool":68,"command":69},"npx","npx skills add caezium\u002Fskills --skill photon-cli",{"tool":71,"command":72},"bunx","bunx skills add caezium\u002Fskills --skill photon-cli",{"tool":74,"command":75},"pnpm","pnpm dlx skills add caezium\u002Fskills --skill photon-cli","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fcaezium\u002Fskills\u002Fblob\u002Fmain\u002Fphoton-cli\u002FSKILL.md",true,[79,85,89,93,97],{"path":80,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":83,"sourceHtmlUrl":84},"commands.md","REFERENCE","参考文档",6465,"https:\u002F\u002Fgithub.com\u002Fcaezium\u002Fskills\u002Fblob\u002Fmain\u002Fphoton-cli\u002Fcommands.md",{"path":86,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":87,"sourceHtmlUrl":88},"environment.md",3135,"https:\u002F\u002Fgithub.com\u002Fcaezium\u002Fskills\u002Fblob\u002Fmain\u002Fphoton-cli\u002Fenvironment.md",{"path":90,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":91,"sourceHtmlUrl":92},"getting-started.md",8355,"https:\u002F\u002Fgithub.com\u002Fcaezium\u002Fskills\u002Fblob\u002Fmain\u002Fphoton-cli\u002Fgetting-started.md",{"path":94,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":95,"sourceHtmlUrl":96},"spectrum.md",3745,"https:\u002F\u002Fgithub.com\u002Fcaezium\u002Fskills\u002Fblob\u002Fmain\u002Fphoton-cli\u002Fspectrum.md",{"path":98,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":99,"sourceHtmlUrl":100},"workflows.md",4490,"https:\u002F\u002Fgithub.com\u002Fcaezium\u002Fskills\u002Fblob\u002Fmain\u002Fphoton-cli\u002Fworkflows.md",[102,124,149,167,188,209],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":116,"publishedAt":47},"01M71JT4RYCAS18RF6003YYR1D","writing-for-agents","Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.","https:\u002F\u002Fgithub.com\u002Fcaezium\u002Fskills\u002Fblob\u002Fmain\u002Fwriting-for-agents\u002FSKILL.md",[108,111],{"categoryNo":109,"categoryName":110,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":112,"categoryName":113,"taxonomyType":114,"taxonomyTypeDesc":115},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[117,118,119,120,121,122,123],"writing for agents","for","writing","editing","use","documents","when",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":131,"publishedAt":47},"01M71JT0GES4AZ5ADH8EADNN1Z","wrangler","Cloudflare Workers CLI for deploying, developing, and managing Workers, KV, R2, D1, Vectorize, Hyperdrive, Workers AI, Containers, Queues, Workflows, Pipelines, and Secrets Store. Load before running wrangler commands to ensure correct syntax and best practices. Biases towards retrieval from Cloudflare docs over pre-trained knowledge.","https:\u002F\u002Fgithub.com\u002Fcaezium\u002Fskills\u002Fblob\u002Fmain\u002Fwrangler\u002FSKILL.md",[130],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[126,132,133,134,135,27,136,137,138,139,140,141,142,118,143,144,145,146,147,148],"cloudflare","d1","knowledge","workflows","secrets","commands","syntax","cloudflare workers","r2","queues","running","containers","correct","load","workers","best practices","store",{"skillNo":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":153,"categories":154,"keywords":155,"publishedAt":47},"01M71JSWX4R203M32K9A18AAW8","workers-best-practices","Reviews and authors Cloudflare Workers code against production best practices. Load when writing new Workers, reviewing Worker code, configuring wrangler.jsonc, or checking for common Workers anti-patterns (streaming, floating promises, global state, secrets, bindings, observability). Biases towards retrieval from Cloudflare docs over pre-trained knowledge.","https:\u002F\u002Fgithub.com\u002Fcaezium\u002Fskills\u002Fblob\u002Fmain\u002Fworkers-best-practices\u002FSKILL.md",[],[156,146,147,157,158,159,118,132,160,134,161,126,119,145,123,162,163,164,165,166],"workers best practices","observability","reviews","promises","worker","new","code","common","streaming","state","anti-patterns",{"skillNo":168,"name":169,"nameZh":6,"description":170,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":171,"categories":172,"keywords":173,"publishedAt":47},"01M71JST6P88MXGT2MWDTPJGEG","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\u002Fcaezium\u002Fskills\u002Fblob\u002Fmain\u002Fwizard\u002FSKILL.md",[],[169,142,174,118,175,176,177,178,121,179,123,180,181,182,183,184,185,186,187,136],"setting","up","ci","provisioning infrastructure","only","invoke","Bash","one","interactive","can","credentials","dashboard","generate","human",{"skillNo":189,"name":190,"nameZh":6,"description":191,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":192,"sourceHtmlUrl":193,"categories":194,"keywords":195,"publishedAt":47},"01M71JSQ95S7BQ61DAPN95X2W4","why","Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available evidence sources, searches each relevant category, and returns a cited read on decisions and tradeoffs. Use how for runtime behavior.","https:\u002F\u002Fgithub.com\u002Fcaezium\u002Fskills\u002Fblob\u002Fmain\u002Fwhy\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fcaezium\u002Fskills\u002Fblob\u002Fmain\u002Fwhy\u002FSKILL.md",[],[190,196,197,198,199,118,200,201,121,202,203,31,204,205,206,207,208],"sources","thresholds","evidence","relevant","runtime","design","decisions","work","behavior","read","data","rationale","returns",{"skillNo":210,"name":211,"nameZh":6,"description":212,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":213,"categories":214,"keywords":216,"publishedAt":47},"01M71JSMHFVSH8HK8GXN6YAX6J","week-prep","Generate a briefing with calendar, tasks, and attention flags. Use for \"week prep\", \"briefing\", or \"what's on this week\".","https:\u002F\u002Fgithub.com\u002Fcaezium\u002Fskills\u002Fblob\u002Fmain\u002Fweek-prep\u002FSKILL.md",[215],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[217,218,219,220,221,118,222,223,224,225,121,180,226,227,228,186,229,205,230,231],"week prep","prep","deep","attention","get","search","messages","briefing","MCP","tasks","with","slack","calendar","flags","grep"]