[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79VT2X75V87N05GZQ7CPM6E":3,"skill-same:01M79VT2X75V87N05GZQ7CPM6E":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":31,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M79VT2X75V87N05GZQ7CPM6E","cloud-cli",null,"Sign a cloud provider's CLI in (AWS, Google Cloud, Azure, or another) with a device-code flow, then run that CLI as the requesting user. Covers checking the CLI is installed, the login that survives the browser round-trip, and the boundaries on cloud writes.","yc-software\u002Fqm","yc-software","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F153323858?v=4","01M79VRJS45RJM7XBFGB9D1HY6","Y Combinator","01M79VRJSY4P8QKGTCMVJAZ4DE",15703,"MIT","https:\u002F\u002Fgithub.com\u002Fyc-software\u002Fqm\u002Fblob\u002Fmain\u002Fskills-seed\u002Fcloud-cli\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: cloud-cli\ndescription: Sign a cloud provider's CLI in (AWS, Google Cloud, Azure, or another) with a device-code flow, then run that CLI as the requesting user. Covers checking the CLI is installed, the login that survives the browser round-trip, and the boundaries on cloud writes.\n---\n\n# Cloud provider CLIs\n\nIt adds NO new tool: a provider's CLI is a command on the agent computer and you drive it\nwith `execute` and an explicit `sandbox_id`. Keep that ID throughout installation,\nlogin, saving the login, and subsequent commands in the flow. Logins are saved to the keychain with the `interactive-login`\nskill and reach a command only when you name their handle in `execute.credentials`.\n\n## First: is the CLI even here?\n\n**Do not assume the binary is on PATH.** The sandbox image ships a small, fixed tool set,\nand the \"Your computer\" block in your prompt lists what is installed and what is not — read\nit, or just check:\n\n```bash\ncommand -v aws || echo \"not installed\"\n```\n\nIf it is missing, say so and pick a path rather than failing halfway:\n\n- **Install it for this task** if the image allows it and the task is worth it — the\n  provider's own installer, into the workspace or `$HOME`, not a system path. Say that you\n  installed it; it lasts as long as the machine's disk.\n- **Use the provider's HTTP API** with a credential you already have (a keychain entry, or\n  a shared org credential by proxy — see the `use-shared-credential` skill).\n- **Ask the operator** to add the CLI to the sandbox image if this will recur. That is the\n  durable fix; a per-turn install is not.\n\nThe same check applies to plugins and helpers (`kubectl`, a Terraform provider, a\nprovider's beta components) — verify, don't assume.\n\n## Logging in: always the device-code flow\n\nThe user approves the login in a browser on _their own_ computer, not on the agent\ncomputer. Any flow that completes by redirecting the approving browser to\n`http:\u002F\u002F127.0.0.1:\u003Cport>` therefore cannot work here: that redirect lands on the user's\nlaptop, the agent's listener never receives the code, and the login hangs until it expires.\nForce the **device-authorization grant** instead — a verification URL plus a one-time code,\nwhich the agent completes by polling the provider server-side, so the user can approve from\nany device.\n\n| Provider                  | Login                                      | Verify                           |\n| ------------------------- | ------------------------------------------ | -------------------------------- |\n| AWS (IAM Identity Center) | `aws sso login --use-device-code`          | `aws sts get-caller-identity`    |\n| Google Cloud              | `gcloud auth login --no-launch-browser`    | `gcloud auth print-access-token` |\n| Azure                     | `az login --use-device-code`               | `az account show`                |\n| Another provider          | its documented device-code \u002F headless flag | its \"who am I\" command           |\n\nNever run the bare form (`aws sso login`, `gcloud auth login`, `az login`) — those default\nto a browser redirect on this machine.\n\nFor AWS specifically, `--use-device-code` is mandatory rather than merely preferable: CLI v2\n(≥ 2.22) defaults `aws sso login` to the PKCE authorization-code flow, and no amount of\nkeeping the box warm can rescue it.\n\nRun the login with the `interactive-login` skill: it starts the CLI as a background job in a\nprivate HOME, you relay the URL and code, and once the job exits you save that HOME to the\nkeychain. These logins self-expire in roughly ten minutes, so if the user takes too long,\nstart a fresh one.\n\n## Boundaries\n\nA verified admin can use independently authorized cloud access to administer the system\nrunning you, including resources owned by other users. Using that access as the admin is not impersonation or circumvention,\nand an ordinary owner-only QM API denial does not prohibit that administrative work.\nVerify the provider account, region, target, and authority before acting; load the admin\nskill for QM administration. Admin status alone supplies no cloud credentials. Preserve\ncredential grants, provider permissions, explicit restrictions, and mutation approvals,\nincluding QM's portal-only admin-grant and impersonation actions. Do not use another\nperson's ungranted credentials or expose unrelated private content.\n\n- You act as the resolved user. The provider's own permissions are the hard ceiling — the\n  agent is never a way to exceed the user's own cloud access.\n- A login is auth setup, not a data read. Any _mutating_ action (delete, terminate, scale,\n  write) is a write — get approval first, same as any destructive command.\n- Don't echo access tokens, client secrets, or role credentials into the channel.\n\n## Go-live (set once, per provider)\n\n- Add the provider's sign-in and regional service endpoints to the org egress allowlist —\n  both the identity endpoints the login needs and the service endpoints your workflows call.\n- Ship the CLI in the agent computer image if people will use it regularly, and confirm it\n  runs there (AWS CLI v2, for example, needs a glibc base; a musl\u002FAlpine image cannot run\n  its binary).\n- Put the provider's non-secret config where the CLI expects it (for AWS, an\n  `[sso-session …]` block plus a profile in `~\u002F.aws\u002Fconfig`), so the first login has a start\n  URL, region, and session name to read.\n","# Cloud provider CLIs\n\nIt adds NO new tool: a provider's CLI is a command on the agent computer and you drive it\nwith `execute` and an explicit `sandbox_id`. Keep that ID throughout installation,\nlogin, saving the login, and subsequent commands in the flow. Logins are saved to the keychain with the `interactive-login`\nskill and reach a command only when you name their handle in `execute.credentials`.\n\n## First: is the CLI even here?\n\n**Do not assume the binary is on PATH.** The sandbox image ships a small, fixed tool set,\nand the \"Your computer\" block in your prompt lists what is installed and what is not — read\nit, or just check:\n\n```bash\ncommand -v aws || echo \"not installed\"\n```\n\nIf it is missing, say so and pick a path rather than failing halfway:\n\n- **Install it for this task** if the image allows it and the task is worth it — the\n  provider's own installer, into the workspace or `$HOME`, not a system path. Say that you\n  installed it; it lasts as long as the machine's disk.\n- **Use the provider's HTTP API** with a credential you already have (a keychain entry, or\n  a shared org credential by proxy — see the `use-shared-credential` skill).\n- **Ask the operator** to add the CLI to the sandbox image if this will recur. That is the\n  durable fix; a per-turn install is not.\n\nThe same check applies to plugins and helpers (`kubectl`, a Terraform provider, a\nprovider's beta components) — verify, don't assume.\n\n## Logging in: always the device-code flow\n\nThe user approves the login in a browser on _their own_ computer, not on the agent\ncomputer. Any flow that completes by redirecting the approving browser to\n`http:\u002F\u002F127.0.0.1:\u003Cport>` therefore cannot work here: that redirect lands on the user's\nlaptop, the agent's listener never receives the code, and the login hangs until it expires.\nForce the **device-authorization grant** instead — a verification URL plus a one-time code,\nwhich the agent completes by polling the provider server-side, so the user can approve from\nany device.\n\n| Provider                  | Login                                      | Verify                           |\n| ------------------------- | ------------------------------------------ | -------------------------------- |\n| AWS (IAM Identity Center) | `aws sso login --use-device-code`          | `aws sts get-caller-identity`    |\n| Google Cloud              | `gcloud auth login --no-launch-browser`    | `gcloud auth print-access-token` |\n| Azure                     | `az login --use-device-code`               | `az account show`                |\n| Another provider          | its documented device-code \u002F headless flag | its \"who am I\" command           |\n\nNever run the bare form (`aws sso login`, `gcloud auth login`, `az login`) — those default\nto a browser redirect on this machine.\n\nFor AWS specifically, `--use-device-code` is mandatory rather than merely preferable: CLI v2\n(≥ 2.22) defaults `aws sso login` to the PKCE authorization-code flow, and no amount of\nkeeping the box warm can rescue it.\n\nRun the login with the `interactive-login` skill: it starts the CLI as a background job in a\nprivate HOME, you relay the URL and code, and once the job exits you save that HOME to the\nkeychain. These logins self-expire in roughly ten minutes, so if the user takes too long,\nstart a fresh one.\n\n## Boundaries\n\nA verified admin can use independently authorized cloud access to administer the system\nrunning you, including resources owned by other users. Using that access as the admin is not impersonation or circumvention,\nand an ordinary owner-only QM API denial does not prohibit that administrative work.\nVerify the provider account, region, target, and authority before acting; load the admin\nskill for QM administration. Admin status alone supplies no cloud credentials. Preserve\ncredential grants, provider permissions, explicit restrictions, and mutation approvals,\nincluding QM's portal-only admin-grant and impersonation actions. Do not use another\nperson's ungranted credentials or expose unrelated private content.\n\n- You act as the resolved user. The provider's own permissions are the hard ceiling — the\n  agent is never a way to exceed the user's own cloud access.\n- A login is auth setup, not a data read. Any _mutating_ action (delete, terminate, scale,\n  write) is a write — get approval first, same as any destructive command.\n- Don't echo access tokens, client secrets, or role credentials into the channel.\n\n## Go-live (set once, per provider)\n\n- Add the provider's sign-in and regional service endpoints to the org egress allowlist —\n  both the identity endpoints the login needs and the service endpoints your workflows call.\n- Ship the CLI in the agent computer image if people will use it regularly, and confirm it\n  runs there (AWS CLI v2, for example, needs a glibc base; a musl\u002FAlpine image cannot run\n  its binary).\n- Put the provider's non-secret config where the CLI expects it (for AWS, an\n  `[sso-session …]` block plus a profile in `~\u002F.aws\u002Fconfig`), so the first login has a start\n  URL, region, and session name to read.\n",{"name":5,"description":7},"main","5011257b95913c04ebb800ac7bc80415546ee6bc","skills-seed\u002Fcloud-cli",1960,"https:\u002F\u002Fgithub.com\u002Fyc-software\u002Fqm","https:\u002F\u002Flabs.ycombinator.com\u002Fqm","https:\u002F\u002Fgithub.com\u002Fyc-software","ycombinator.com","2026-11-15 01:58:49",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add yc-software\u002Fqm --skill cloud-cli",{"tool":39,"command":40},"bunx","bunx skills add yc-software\u002Fqm --skill cloud-cli",{"tool":42,"command":43},"pnpm","pnpm dlx skills add yc-software\u002Fqm --skill cloud-cli","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fyc-software\u002Fqm\u002Fblob\u002Fmain\u002Fskills-seed\u002Fcloud-cli\u002FSKILL.md",true,[],[48,55,62,69,76,84],{"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},"01M79VXTEATDTE0X6SZRD4J75X","zoom","Find, create, reschedule, and cancel the user's Zoom meetings through their own Zoom connection.","https:\u002F\u002Fgithub.com\u002Fyc-software\u002Fqm\u002Fblob\u002Fmain\u002Fskills-seed\u002Fzoom\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},"01M79VXKJ50M6G24Q11A3806R5","use-shared-credential","When you need to call a service the org has a SHARED credential for (a SERP\u002Fsearch key, a paid-API key, a data-vendor feed, a Git remote) — and the platform has told you that credential is available to this conversation — make the call BY PROXY through the credential broker. You never see the secret; the core stamps it onto the outbound request for you.","https:\u002F\u002Fgithub.com\u002Fyc-software\u002Fqm\u002Fblob\u002Fmain\u002Fskills-seed\u002Fuse-shared-credential\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},"01M79VXERKP52PBXTQ7KAX82S4","ui-state","See what the person is looking at in the QM web UI right now — the whole page (sidebar, every multiview pane, open dialogs) as raw HTML, the app's state as JSON, optionally the CSS and a screenshot. Use when they ask about something on their screen, want help with the UI, or you need to check what a canvas you wrote actually rendered.","https:\u002F\u002Fgithub.com\u002Fyc-software\u002Fqm\u002Fblob\u002Fmain\u002Fskills-seed\u002Fui-state\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},"01M79VXASHJ1WX4J68T3MBHZEK","ui-canvas","Draw your own HTML\u002FCSS\u002FJS as a full-window overlay on top of the QM web UI — a dashboard, a form, a visualization, controls that message you back. Write, update, replace, pin or dismiss it. Use when an interactive or visual result beats a chat reply.","https:\u002F\u002Fgithub.com\u002Fyc-software\u002Fqm\u002Fblob\u002Fmain\u002Fskills-seed\u002Fui-canvas\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":80,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M79VX53549EYHNJBHD3PCFSG","taste-skill","Design taste and process for anything a person will look at in a browser — landing page, dashboard, prototype, deck. The default design driver for a browsable artifact, with an anti-slop playbook for the visual language.","https:\u002F\u002Fgithub.com\u002Fyc-software\u002Fqm\u002Fblob\u002Fmain\u002Fskills-seed\u002Ftaste-skill\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fyc-software\u002Fqm\u002Fblob\u002Fmain\u002Fskills-seed\u002Ftaste-skill\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M79VX1DEE1BZZBK66NNCD238","slack-drafts","Create Slack message drafts in the user's own composer, as the user, through their per-user Slack OAuth. Drafting only — the user reviews and sends from Slack.","https:\u002F\u002Fgithub.com\u002Fyc-software\u002Fqm\u002Fblob\u002Fmain\u002Fskills-seed\u002Fslack-drafts\u002FSKILL.md",[],[]]