[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EVVTSPPFCFSAN5Q6Y3R16A":3,"skill-same:01M7EVVTSPPFCFSAN5Q6Y3R16A":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":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M7EVVTSPPFCFSAN5Q6Y3R16A","secrets-manager",null,"Design secrets management — vaulting, rotation, least-privilege access, and eliminating hardcoded credentials.","TanNhatCMS\u002Fjarvis","TanNhatCMS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F113796420?v=4","01M753MV17KG5CD3152G3WQEQY","KietNT","01M7EKEDYVYQ6PWVJJMZ911VMX",0,"MIT","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-secrets-manager\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: secrets-manager\ndescription: Design secrets management — vaulting, rotation, least-privilege access, and eliminating hardcoded credentials.\ncategory: security\n---\n\n## Overview\n\nSecrets — API keys, passwords, tokens, certificates, connection strings — are the keys to the kingdom, and they leak constantly: hardcoded in repos, pasted in chat, baked into images. A secrets-management program gives every secret a safe home (a vault), a defined lifetime (rotation), and minimal exposure (least-privilege access with audit trails).\n\nThis skill covers selecting and operating secrets management: vault architecture, rotation, application integration patterns, and cleaning up the hardcoded-secret debt most orgs carry.\n\nSecrets management fails most often not on technology but on developer experience: if the vault is harder than hardcoding, developers will hardcode. The winning pattern makes the secure path the easy path — SDKs, sidecar injectors, and CI integrations that fetch secrets with less effort than copying them into config files.\n\n## When to use\n\n- Replacing hardcoded credentials and config-file secrets with a vault.\n- Designing secret rotation for databases, API keys, and service accounts.\n- Responding to a leaked secret (revoke, rotate, investigate exposure).\n- Auditing who can access which secrets and whether access is still needed.\n\n## Core concepts\n\n- **Vault as the system of record:** HashiCorp Vault, cloud KMS\u002Fsecrets services, or equivalent — secrets live encrypted at rest, with access control, versioning, and audit logging. Spreadsheets, wikis, and chat are not vaults.\n- **Dynamic vs static secrets:** dynamic (generated on demand, short-lived, e.g., per-request DB credentials) beats static (long-lived passwords) — stolen dynamic secrets expire before they can be used.\n- **Rotation:** scheduled (e.g., 30–90 days) plus event-driven (employee departure, suspected leak, incident). Automated rotation beats manual; manual rotation gets skipped.\n- **Least privilege + audit:** applications and humans get exactly the secrets they need, via short-lived tokens, with every access logged. Regular access reviews prune stale grants.\n- **No secrets in code, ever:** repos, CI logs, container images, and client-side bundles must be secret-free. Pre-commit hooks and secret scanning enforce it.\n- **Break-glass:** emergency access procedures for when the vault is down — sealed, logged, tested, and rotated after use.\n\n- **Secret zero problem.** The credential used to authenticate to the vault is itself a secret — bootstrap it from platform identity (instance roles, workload identity) rather than another static token.\n- **Rotation without downtime.** Versioned secrets plus graceful reload (or dual-support windows) let applications pick up rotated values without restarts or outages.\n- **Ephemeral credentials.** The best secret is one that barely exists: dynamic, short-lived credentials issued per workload session minimize the value of any leak.\n\n## Practical workflow\n\n1. **Inventory secrets:** scan repos, CI configs, wikis, and chat exports for hardcoded secrets (automated secret scanning). Classify by blast radius: production DB creds and cloud root keys first.\n2. **Stand up the vault:** choose the platform; configure encryption at rest, authentication (OIDC\u002FIAM-based, not long-lived tokens), audit logging to the SIEM, and backup\u002Frestore tested.\n3. **Migrate applications:** switch apps to vault APIs or injectors (sidecar\u002Fenv at deploy time, never baked into images). Prefer dynamic secrets for databases and cloud access.\n4. **Automate rotation:** scheduled rotation for static secrets; event-driven rotation runbooks for leaks and offboarding. Verify apps pick up rotated secrets without downtime (versioned secrets, graceful reload).\n5. **Enforce prevention:** pre-commit secret scanning, CI pipeline secret detection (block on high-confidence finds), and container-image scanning. Treat a blocked commit as coaching, not punishment.\n6. **Respond to leaks:** when a secret leaks — revoke\u002Frotate immediately, search for where else it was used, check access logs for misuse during the exposure window, then fix the process that allowed the leak.\n\n### Leak response checklist\n\n- [ ] Secret revoked\u002Frotated at the source (old value dead)\n- [ ] All copies removed (repo history rewritten or repo rotated, chat deleted, images rebuilt)\n- [ ] Access logs reviewed for the exposure window\n- [ ] Root cause fixed (why was it hardcoded \u002F over-exposed?)\n- [ ] Detection improved (scanning rule, alert)\n\n### Sustaining the practice\n\n- Scan for hardcoded secrets on every commit and in every image build\n- Review vault access grants quarterly against current team membership\n- Test vault backup\u002Frestore and break-glass procedures annually\n- Track mean-time-to-rotate after a suspected leak as a readiness metric\n\n### Metrics that prove it works\n\n- % of applications migrated from hardcoded\u002Fconfig secrets to the vault\n- Rotation compliance % (secrets rotated within policy window)\n- Hardcoded-secret scanner finds per quarter (trending down)\n- Secret access review completion and stale-grant removal counts\n\n## Common pitfalls\n\n- **Vault with weak auth.** A vault fronted by a shared static token is a single point of compromise. Use short-lived, identity-based auth.\n- **No rotation.** \"Vaulted but never rotated\" just centralizes stale secrets. Automate rotation or it will not happen.\n- **Secrets in CI logs and images.** Mask secrets in pipeline output; never bake them into container layers (each layer persists even if a later layer deletes the file).\n- **Over-broad access.** \"The whole team can read prod secrets\" defeats the purpose. Scope by environment and role; review quarterly.\n- **Break-glass never tested.** An untested emergency procedure fails during the actual emergency. Test restores and break-glass annually.\n- **Scanning without remediation.** Finding 500 hardcoded secrets with no rotation-and-removal program is just a list. Pair scanning with a cleanup backlog and SLA.\n- **A vault nobody backs up.** Losing the vault means losing every secret at once. Test backup and restore, including the unseal\u002Frecovery procedure.\n- **Long-lived vault tokens.** Static tokens for automation defeat the purpose. Use short-lived, identity-bound auth for workloads.\n- **Vault sprawl.** Three teams running three different vaults means three audit trails and three backup stories. Standardize on one platform with proper multi-tenancy.\n- **Secrets in backups and logs.** Encrypted vault backups are still sensitive; CI logs echo secrets without masking. Protect the copies, not just the vault.\n","## Overview\n\nSecrets — API keys, passwords, tokens, certificates, connection strings — are the keys to the kingdom, and they leak constantly: hardcoded in repos, pasted in chat, baked into images. A secrets-management program gives every secret a safe home (a vault), a defined lifetime (rotation), and minimal exposure (least-privilege access with audit trails).\n\nThis skill covers selecting and operating secrets management: vault architecture, rotation, application integration patterns, and cleaning up the hardcoded-secret debt most orgs carry.\n\nSecrets management fails most often not on technology but on developer experience: if the vault is harder than hardcoding, developers will hardcode. The winning pattern makes the secure path the easy path — SDKs, sidecar injectors, and CI integrations that fetch secrets with less effort than copying them into config files.\n\n## When to use\n\n- Replacing hardcoded credentials and config-file secrets with a vault.\n- Designing secret rotation for databases, API keys, and service accounts.\n- Responding to a leaked secret (revoke, rotate, investigate exposure).\n- Auditing who can access which secrets and whether access is still needed.\n\n## Core concepts\n\n- **Vault as the system of record:** HashiCorp Vault, cloud KMS\u002Fsecrets services, or equivalent — secrets live encrypted at rest, with access control, versioning, and audit logging. Spreadsheets, wikis, and chat are not vaults.\n- **Dynamic vs static secrets:** dynamic (generated on demand, short-lived, e.g., per-request DB credentials) beats static (long-lived passwords) — stolen dynamic secrets expire before they can be used.\n- **Rotation:** scheduled (e.g., 30–90 days) plus event-driven (employee departure, suspected leak, incident). Automated rotation beats manual; manual rotation gets skipped.\n- **Least privilege + audit:** applications and humans get exactly the secrets they need, via short-lived tokens, with every access logged. Regular access reviews prune stale grants.\n- **No secrets in code, ever:** repos, CI logs, container images, and client-side bundles must be secret-free. Pre-commit hooks and secret scanning enforce it.\n- **Break-glass:** emergency access procedures for when the vault is down — sealed, logged, tested, and rotated after use.\n\n- **Secret zero problem.** The credential used to authenticate to the vault is itself a secret — bootstrap it from platform identity (instance roles, workload identity) rather than another static token.\n- **Rotation without downtime.** Versioned secrets plus graceful reload (or dual-support windows) let applications pick up rotated values without restarts or outages.\n- **Ephemeral credentials.** The best secret is one that barely exists: dynamic, short-lived credentials issued per workload session minimize the value of any leak.\n\n## Practical workflow\n\n1. **Inventory secrets:** scan repos, CI configs, wikis, and chat exports for hardcoded secrets (automated secret scanning). Classify by blast radius: production DB creds and cloud root keys first.\n2. **Stand up the vault:** choose the platform; configure encryption at rest, authentication (OIDC\u002FIAM-based, not long-lived tokens), audit logging to the SIEM, and backup\u002Frestore tested.\n3. **Migrate applications:** switch apps to vault APIs or injectors (sidecar\u002Fenv at deploy time, never baked into images). Prefer dynamic secrets for databases and cloud access.\n4. **Automate rotation:** scheduled rotation for static secrets; event-driven rotation runbooks for leaks and offboarding. Verify apps pick up rotated secrets without downtime (versioned secrets, graceful reload).\n5. **Enforce prevention:** pre-commit secret scanning, CI pipeline secret detection (block on high-confidence finds), and container-image scanning. Treat a blocked commit as coaching, not punishment.\n6. **Respond to leaks:** when a secret leaks — revoke\u002Frotate immediately, search for where else it was used, check access logs for misuse during the exposure window, then fix the process that allowed the leak.\n\n### Leak response checklist\n\n- [ ] Secret revoked\u002Frotated at the source (old value dead)\n- [ ] All copies removed (repo history rewritten or repo rotated, chat deleted, images rebuilt)\n- [ ] Access logs reviewed for the exposure window\n- [ ] Root cause fixed (why was it hardcoded \u002F over-exposed?)\n- [ ] Detection improved (scanning rule, alert)\n\n### Sustaining the practice\n\n- Scan for hardcoded secrets on every commit and in every image build\n- Review vault access grants quarterly against current team membership\n- Test vault backup\u002Frestore and break-glass procedures annually\n- Track mean-time-to-rotate after a suspected leak as a readiness metric\n\n### Metrics that prove it works\n\n- % of applications migrated from hardcoded\u002Fconfig secrets to the vault\n- Rotation compliance % (secrets rotated within policy window)\n- Hardcoded-secret scanner finds per quarter (trending down)\n- Secret access review completion and stale-grant removal counts\n\n## Common pitfalls\n\n- **Vault with weak auth.** A vault fronted by a shared static token is a single point of compromise. Use short-lived, identity-based auth.\n- **No rotation.** \"Vaulted but never rotated\" just centralizes stale secrets. Automate rotation or it will not happen.\n- **Secrets in CI logs and images.** Mask secrets in pipeline output; never bake them into container layers (each layer persists even if a later layer deletes the file).\n- **Over-broad access.** \"The whole team can read prod secrets\" defeats the purpose. Scope by environment and role; review quarterly.\n- **Break-glass never tested.** An untested emergency procedure fails during the actual emergency. Test restores and break-glass annually.\n- **Scanning without remediation.** Finding 500 hardcoded secrets with no rotation-and-removal program is just a list. Pair scanning with a cleanup backlog and SLA.\n- **A vault nobody backs up.** Losing the vault means losing every secret at once. Test backup and restore, including the unseal\u002Frecovery procedure.\n- **Long-lived vault tokens.** Static tokens for automation defeat the purpose. Use short-lived, identity-bound auth for workloads.\n- **Vault sprawl.** Three teams running three different vaults means three audit trails and three backup stories. Standardize on one platform with proper multi-tenancy.\n- **Secrets in backups and logs.** Encrypted vault backups are still sensitive; CI logs echo secrets without masking. Protect the copies, not just the vault.\n",{"name":5,"category":24,"description":7},"security","main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-secrets-manager",1,"https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis","https:\u002F\u002Fgithub.com\u002FTanNhatCMS","https:\u002F\u002Fmrkiet.name.vn","2026-11-07 14:23:08",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add TanNhatCMS\u002Fjarvis --skill secrets-manager",{"tool":39,"command":40},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill secrets-manager",{"tool":42,"command":43},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill secrets-manager","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-secrets-manager\u002FSKILL.md",true,[],[48,55,63,70,77,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},"01M7EWYJR0J8DARY7E59Z6Y9MV","web-scrape","Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open\u002Ffetch fails on JS-heavy pages, or when you need clean markdown\u002Fstructured extraction from a site. Requires FIRECRAWL_API_KEY.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fweb-scrape\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":59,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7EWYBN5P6F2AJG3FR24T9BP","design-taste-frontend","tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML\u002FCSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, \"AI-made\", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7EWY8FQFNQ2GB7NZZWGSSDX","test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-tdd\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7EWY5SHBFRH1HDHVWM9K7TV","systematic-debugging","Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-debugging\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7EWY3NM0Z0JAKS7HDZ24K66","requesting-code-review","Use when completing tasks, implementing major features, or before merging to verify work meets requirements","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-code-review\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},"01M7EWY0WRMWX4M9ZFY0WKC593","brainstorming","You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-brainstorming\u002FSKILL.md",[],[]]