[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DARFCNQV3ED76AR72ZBVRJ":3,"skill-same:01M6DARFCNQV3ED76AR72ZBVRJ":75},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":22,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":13,"repositoryHtmlUrl":52,"repositoryHomepageUrl":6,"ownerHtmlUrl":53,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":54,"install":55,"resources":68},"01M6DARFCNQV3ED76AR72ZBVRJ","bws-cli-skill",null,"Use when working with Bitwarden Secrets Manager CLI (bws) to run commands with injected secrets, manage secret-manager environment variables, or explain bws usage. Essential for wrapping processes with `bws run --project-id ${BWS_TZEHOUSE_ID_PROD or BWS_TZEHOUSE_ID_DEV} -- {command}`.","tzeusy-org\u002Fai-bootstrap","tzeusy-org","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F141543652?v=4","01M6DAM1AP09H27BYGFY9QCNPB","01M6DAM1F4R187EK11XDN9JZKH",0,"MIT","https:\u002F\u002Fgithub.com\u002Ftzeusy-org\u002Fai-bootstrap\u002Fblob\u002Fmain\u002Fskills\u002Fbws-cli-skill\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"cli","bws cli skill","run","dev","secrets","explain","command","environment","use","manage","bitwarden","active","project","commands","essential","id","2026-11-10 10:12:30",false,"---\nname: bws-cli-skill\ndescription: Use when working with Bitwarden Secrets Manager CLI (bws) to run commands with injected secrets, manage secret-manager environment variables, or explain bws usage. Essential for wrapping processes with `bws run --project-id ${BWS_TZEHOUSE_ID_PROD or BWS_TZEHOUSE_ID_DEV} -- {command}`.\nmetadata:\n  owner: tze\n  authors:\n    - tze\n    - Claude Fable 5.1\n  status: active\n  last_reviewed: \"2026-09-02\"\n---\n\n# bws CLI skill\n\n## Overview\n\nUse this skill to guide LLM behavior for the Bitwarden Secrets Manager CLI. Prioritize safe, idempotent usage and emphasize running commands through `bws run` so secrets are injected into the process environment without being written to disk.\n\n## Quick start\n\n1. Confirm `bws` is installed and available in `PATH`.\n2. Ensure a valid Bitwarden Secrets Manager access token is present (per official docs).\n3. If `\u002Fsecrets\u002F.env` exists, load it into the current process before running `bws`:\n   - `set -a; source \u002Fsecrets\u002F.env; set +a`\n3. Wrap any process that needs secrets with:\n   - `bws run --project-id ${BWS_TZEHOUSE_ID_PROD} -- {command}`\n   - `bws run --project-id ${BWS_TZEHOUSE_ID_DEV} -- {command}`\n\n## Core guidance\n\n- Prefer `bws run` for any command that requires secrets so values stay in memory only.\n- Use explicit project IDs from `BWS_TZEHOUSE_ID_PROD` or `BWS_TZEHOUSE_ID_DEV`; do not hardcode IDs.\n- If `\u002Fsecrets\u002F.env` is the source of project IDs or tokens, load it into the current shell process (avoid printing env values).\n- Keep secrets out of logs, files, and repo history.\n- If a task requires other bws commands, consult [references\u002Fsecrets-manager-cli.md](references\u002Fsecrets-manager-cli.md) and the official docs.\n\n## Usage examples\n\n- Load env vars then run a production command:\n  - `set -a; source \u002Fsecrets\u002F.env; set +a`\n  - `bws run --project-id ${BWS_TZEHOUSE_ID_PROD} -- {command}`\n- Run a production command with secrets:\n  - `bws run --project-id ${BWS_TZEHOUSE_ID_PROD} -- {command}`\n- Run a development command with secrets:\n  - `bws run --project-id ${BWS_TZEHOUSE_ID_DEV} -- {command}`\n\n## Reference\n\nFor detailed CLI subcommands and authentication setup, read [references\u002Fsecrets-manager-cli.md](references\u002Fsecrets-manager-cli.md) and the official docs at https:\u002F\u002Fbitwarden.com\u002Fhelp\u002Fsecrets-manager-cli\u002F.\n","# bws CLI skill\n\n## Overview\n\nUse this skill to guide LLM behavior for the Bitwarden Secrets Manager CLI. Prioritize safe, idempotent usage and emphasize running commands through `bws run` so secrets are injected into the process environment without being written to disk.\n\n## Quick start\n\n1. Confirm `bws` is installed and available in `PATH`.\n2. Ensure a valid Bitwarden Secrets Manager access token is present (per official docs).\n3. If `\u002Fsecrets\u002F.env` exists, load it into the current process before running `bws`:\n   - `set -a; source \u002Fsecrets\u002F.env; set +a`\n3. Wrap any process that needs secrets with:\n   - `bws run --project-id ${BWS_TZEHOUSE_ID_PROD} -- {command}`\n   - `bws run --project-id ${BWS_TZEHOUSE_ID_DEV} -- {command}`\n\n## Core guidance\n\n- Prefer `bws run` for any command that requires secrets so values stay in memory only.\n- Use explicit project IDs from `BWS_TZEHOUSE_ID_PROD` or `BWS_TZEHOUSE_ID_DEV`; do not hardcode IDs.\n- If `\u002Fsecrets\u002F.env` is the source of project IDs or tokens, load it into the current shell process (avoid printing env values).\n- Keep secrets out of logs, files, and repo history.\n- If a task requires other bws commands, consult [references\u002Fsecrets-manager-cli.md](references\u002Fsecrets-manager-cli.md) and the official docs.\n\n## Usage examples\n\n- Load env vars then run a production command:\n  - `set -a; source \u002Fsecrets\u002F.env; set +a`\n  - `bws run --project-id ${BWS_TZEHOUSE_ID_PROD} -- {command}`\n- Run a production command with secrets:\n  - `bws run --project-id ${BWS_TZEHOUSE_ID_PROD} -- {command}`\n- Run a development command with secrets:\n  - `bws run --project-id ${BWS_TZEHOUSE_ID_DEV} -- {command}`\n\n## Reference\n\nFor detailed CLI subcommands and authentication setup, read [references\u002Fsecrets-manager-cli.md](references\u002Fsecrets-manager-cli.md) and the official docs at https:\u002F\u002Fbitwarden.com\u002Fhelp\u002Fsecrets-manager-cli\u002F.\n",{"name":5,"metadata":44,"description":7},{"owner":45,"status":34,"authors":46,"last_reviewed":48},"tze",[45,47],"Claude Fable 5.1","2026-09-02","main","c907d6f0bf96bd61b936e8972e0f1c66ebb8148c","skills\u002Fbws-cli-skill","https:\u002F\u002Fgithub.com\u002Ftzeusy-org\u002Fai-bootstrap","https:\u002F\u002Fgithub.com\u002Ftzeusy-org","2026-11-10 23:17:25",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add tzeusy-org\u002Fai-bootstrap --skill bws-cli-skill",{"tool":61,"command":62},"bunx","bunx skills add tzeusy-org\u002Fai-bootstrap --skill bws-cli-skill",{"tool":64,"command":65},"pnpm","pnpm dlx skills add tzeusy-org\u002Fai-bootstrap --skill bws-cli-skill","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ftzeusy-org\u002Fai-bootstrap\u002Fblob\u002Fmain\u002Fskills\u002Fbws-cli-skill\u002FSKILL.md",true,[69],{"path":70,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":73,"sourceHtmlUrl":74},"references\u002Fsecrets-manager-cli.md","REFERENCE","参考文档",673,"https:\u002F\u002Fgithub.com\u002Ftzeusy-org\u002Fai-bootstrap\u002Fblob\u002Fmain\u002Fskills\u002Fbws-cli-skill\u002Freferences\u002Fsecrets-manager-cli.md",[76,99,124,139,158,169],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":39},"01M6DAZD21TWH2ET70V9FF75CQ","user-run","Use when a step needs privileges this session lacks (docker, sudo, another user's checkout or secrets, host access) and the owner must run it as tze. Writes a reviewable \u002Fhome\u002Forca\u002F.tmp\u002F\u003Cslug>\u002Frun.sh that impersonates tze (USER_TO_IMPERSONATE overrides), tees timestamped logs plus latest.log and collects artifacts there; Claude presents it with a risk and time brief, then continues from the logs. Triggers: \"I'll run it for you\", \"permission denied on docker.sock\", \"needs sudo\", \"sudo: a password is required\", \"run as tze\", \"\u002Fuser-run\".","https:\u002F\u002Fgithub.com\u002Ftzeusy-org\u002Fai-bootstrap\u002Fblob\u002Fmain\u002Fskills\u002Fpersonal\u002Fuser-run\u002FSKILL.md",[],[83,84,25,85,86,31,87,88,89,90,34,91,92,93,94,95,96,27,97,98],"user run","user","docker","logs","host","as","triggers","permission","time","log","artifacts","session","password","access","risk","brief",{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":113,"publishedAt":39},"01M6DAZAHTCBAD2WF0GAHWPST8","requesting-code-review","Use when completing tasks, implementing major features, or before merging to verify work meets requirements","https:\u002F\u002Fgithub.com\u002Ftzeusy-org\u002Fai-bootstrap\u002Fblob\u002Fmain\u002Fskills\u002Fpersonal\u002Fth-workflow\u002Fsubskills\u002Frequesting-code-review\u002FSKILL.md",[105,108],{"categoryNo":106,"categoryName":107,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":109,"categoryName":110,"taxonomyType":111,"taxonomyTypeDesc":112},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[114,115,116,117,118,119,34,120,121,31,122,123],"requesting code review","code","review","code review","work","requirements","upstream","superpowers","verify","tasks",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":132,"publishedAt":39},"01M6DAZ7CJ82D81XZB2YHVVY48","receiving-code-review","Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation","https:\u002F\u002Fgithub.com\u002Ftzeusy-org\u002Fai-bootstrap\u002Fblob\u002Fmain\u002Fskills\u002Fpersonal\u002Fth-workflow\u002Fsubskills\u002Freceiving-code-review\u002FSKILL.md",[130,131],{"categoryNo":106,"categoryName":107,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":109,"categoryName":110,"taxonomyType":111,"taxonomyTypeDesc":112},[133,115,116,117,34,120,134,121,31,135,136,137,138],"receiving code review","implementation","code review feedback","technical","feedback","verification",{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":143,"categories":144,"keywords":145,"publishedAt":39},"01M6DAZ4ER76ADXJ9KRFP7V3Q9","finishing-a-development-branch","Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup","https:\u002F\u002Fgithub.com\u002Ftzeusy-org\u002Fai-bootstrap\u002Fblob\u002Fmain\u002Fskills\u002Fpersonal\u002Fth-workflow\u002Fsubskills\u002Ffinishing-a-development-branch\u002FSKILL.md",[],[146,147,148,149,31,150,118,151,152,153,121,154,155,156,34,120,157,134],"branch","development","finishing a development branch","integrate","decide","how","cleanup","pr","merge","tests","structured","options",{"skillNo":159,"name":160,"nameZh":6,"description":161,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":162,"categories":163,"keywords":164,"publishedAt":39},"01M6DAYZFWWW2YPKP89QNQR96H","executing-plans","Use when you have a written implementation plan to execute in a separate session with review checkpoints","https:\u002F\u002Fgithub.com\u002Ftzeusy-org\u002Fai-bootstrap\u002Fblob\u002Fmain\u002Fskills\u002Fpersonal\u002Fth-workflow\u002Fsubskills\u002Fexecuting-plans\u002FSKILL.md",[],[165,166,167,116,168,34,120,134,121,31,94],"plans","executing plans","plan","execute",{"skillNo":170,"name":171,"nameZh":6,"description":172,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":173,"categories":174,"keywords":175,"publishedAt":39},"01M6DAYWM2YQHYCK7C35K1D29J","dispatching-parallel-agents","Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies","https:\u002F\u002Fgithub.com\u002Ftzeusy-org\u002Fai-bootstrap\u002Fblob\u002Fmain\u002Fskills\u002Fpersonal\u002Fth-workflow\u002Fsubskills\u002Fdispatching-parallel-agents\u002FSKILL.md",[],[176,177,178,31,121,120,179,34,180,123,181],"parallel agents","parallel","dispatching parallel agents","state","dependencies","shared"]