[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6FV4XCF3T6PCE0HSKBVV4GP":3,"skill-same:01M6FV4XCF3T6PCE0HSKBVV4GP":80},{"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":27,"publishedAt":42,"linkOnly":43,"markdownContent":44,"markdownBody":45,"frontMatter":46,"refName":47,"commitSha":48,"skillDirectory":49,"forksCount":50,"repositoryHtmlUrl":51,"repositoryHomepageUrl":6,"ownerHtmlUrl":52,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":53,"install":54,"resources":67},"01M6FV4XCF3T6PCE0HSKBVV4GP","api-credentials-hygiene",null,"Audits and hardens API credential handling (env vars, separation, rotation plan, least privilege, auditability). Use when integrating services or preparing production deployments where secrets must be managed safely.","kbarbel640-del\u002Fskills","kbarbel640-del","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F255315490?v=4","01M6CJPPQGCCESXMG3K7BBGQ5J","01M6CJPPX2PB2BCZERFVM2C2B3",1,"MIT","https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fkowl64\u002Fapi-credentials-hygiene\u002FSKILL.md",[17,22],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[28,29,30,31,32,33,34,35,36,37,38,39,40,41],"credentials","api","api credentials hygiene","hygiene","env vars","services","Production","secrets","plan","use","deployments","credential","env","separation","2026-11-10 10:12:30",false,"---\nname: api-credentials-hygiene\ndescription: Audits and hardens API credential handling (env vars, separation, rotation plan, least privilege, auditability). Use when integrating services or preparing production deployments where secrets must be managed safely.\n---\n\n# API credentials hygiene: env vars, rotation, least privilege, auditability\n\n## PURPOSE\nAudits and hardens API credential handling (env vars, separation, rotation plan, least privilege, auditability).\n\n## WHEN TO USE\n- TRIGGERS:\n  - Harden the credentials setup for this integration and move secrets into env vars.\n  - Design a key rotation plan for these APIs with minimal downtime.\n  - Audit this service for least-privilege access and document what each key can do.\n  - Create an environment variable map and a secure .env template for this project.\n  - Set up credential separation for dev versus prod with clear audit trails.\n- DO NOT USE WHEN…\n  - You want to obtain keys without authorization or bypass security controls.\n  - You need legal\u002Fcompliance sign-off (this outputs technical documentation, not legal advice).\n\n## INPUTS\n- REQUIRED:\n  - List of integrations\u002FAPIs and where credentials are currently stored\u002Fused.\n  - Deployment context (local dev, server, container, n8n, etc.).\n- OPTIONAL:\n  - Current config files\u002Fredacted snippets (.env, compose, systemd, n8n creds list).\n  - Org rules (rotation intervals, secret manager preference).\n- EXAMPLES:\n  - “Keys are hard-coded in a Node script and an n8n HTTP Request node.”\n  - “We have dev and prod n8n instances and need separation.”\n\n## OUTPUTS\n- Credential map (service → env vars → scopes\u002Fpermissions → owner → rotation cadence).\n- Rotation runbook (steps + rollback).\n- Least-privilege checklist and audit log plan.\n- Optional: `.env` template (placeholders only).\nSuccess = no secrets committed or embedded, permissions minimized, rotation steps documented, and auditability defined.\n\n\n## WORKFLOW\n1. Inventory credentials:\n   - where stored, where used, and who owns them.\n2. Define separation:\n   - dev vs prod; human vs service accounts; per-integration boundaries.\n3. Move secrets to env vars \u002F secret manager references:\n   - create an env var map and update config plan (no raw keys in code\u002Fworkflows).\n4. Least privilege:\n   - for each API, enumerate required actions and reduce scopes\u002Froles accordingly.\n5. Rotation plan:\n   - dual-key overlap if supported; steps to rotate with minimal downtime; rollback.\n6. Auditability:\n   - define what events are logged (auth failures, token refresh, key use where available).\n7. STOP AND ASK THE USER if:\n   - required operations are unknown,\n   - secret injection method is unclear,\n   - rotation cadence\u002Fowners are unspecified.\n\n\n## OUTPUT FORMAT\nCredential map template:\n\n```text\nCREDENTIAL MAP\n- Integration: \u003Cname>\n  - Env vars:\n    - \u003CVAR_NAME>: \u003Cpurpose> (secret\u002Fnon-secret)\n  - Permissions\u002Fscopes: \u003Clist>\n  - Used by: \u003Cservice\u002Fworkflow>\n  - Storage: \u003Csecret manager\u002Fenv var>\n  - Rotation: \u003Ccadence> | \u003Cowner> | \u003Cprocedure>\n  - Audit: \u003Cwhat is logged and where>\n```\n\nIf providing a template, output `assets\u002Fdotenv-template.example` with placeholders only.\n\n\n## SAFETY & EDGE CASES\n- Never output real secrets, tokens, or private keys. Use placeholders.\n- Read-only by default; propose changes as a plan unless explicitly asked to modify files.\n- Avoid over-broad scopes\u002Froles unless justified by a documented requirement.\n\n\n## EXAMPLES\n- Input: “n8n HTTP nodes contain API keys.”  \n  Output: Env var map + plan to move to n8n credentials\u002Fenv vars + rotation runbook.\n\n- Input: “Need dev vs prod separation.”  \n  Output: Two env maps + naming scheme + access boundary checklist.\n\n","# API credentials hygiene: env vars, rotation, least privilege, auditability\n\n## PURPOSE\nAudits and hardens API credential handling (env vars, separation, rotation plan, least privilege, auditability).\n\n## WHEN TO USE\n- TRIGGERS:\n  - Harden the credentials setup for this integration and move secrets into env vars.\n  - Design a key rotation plan for these APIs with minimal downtime.\n  - Audit this service for least-privilege access and document what each key can do.\n  - Create an environment variable map and a secure .env template for this project.\n  - Set up credential separation for dev versus prod with clear audit trails.\n- DO NOT USE WHEN…\n  - You want to obtain keys without authorization or bypass security controls.\n  - You need legal\u002Fcompliance sign-off (this outputs technical documentation, not legal advice).\n\n## INPUTS\n- REQUIRED:\n  - List of integrations\u002FAPIs and where credentials are currently stored\u002Fused.\n  - Deployment context (local dev, server, container, n8n, etc.).\n- OPTIONAL:\n  - Current config files\u002Fredacted snippets (.env, compose, systemd, n8n creds list).\n  - Org rules (rotation intervals, secret manager preference).\n- EXAMPLES:\n  - “Keys are hard-coded in a Node script and an n8n HTTP Request node.”\n  - “We have dev and prod n8n instances and need separation.”\n\n## OUTPUTS\n- Credential map (service → env vars → scopes\u002Fpermissions → owner → rotation cadence).\n- Rotation runbook (steps + rollback).\n- Least-privilege checklist and audit log plan.\n- Optional: `.env` template (placeholders only).\nSuccess = no secrets committed or embedded, permissions minimized, rotation steps documented, and auditability defined.\n\n\n## WORKFLOW\n1. Inventory credentials:\n   - where stored, where used, and who owns them.\n2. Define separation:\n   - dev vs prod; human vs service accounts; per-integration boundaries.\n3. Move secrets to env vars \u002F secret manager references:\n   - create an env var map and update config plan (no raw keys in code\u002Fworkflows).\n4. Least privilege:\n   - for each API, enumerate required actions and reduce scopes\u002Froles accordingly.\n5. Rotation plan:\n   - dual-key overlap if supported; steps to rotate with minimal downtime; rollback.\n6. Auditability:\n   - define what events are logged (auth failures, token refresh, key use where available).\n7. STOP AND ASK THE USER if:\n   - required operations are unknown,\n   - secret injection method is unclear,\n   - rotation cadence\u002Fowners are unspecified.\n\n\n## OUTPUT FORMAT\nCredential map template:\n\n```text\nCREDENTIAL MAP\n- Integration: \u003Cname>\n  - Env vars:\n    - \u003CVAR_NAME>: \u003Cpurpose> (secret\u002Fnon-secret)\n  - Permissions\u002Fscopes: \u003Clist>\n  - Used by: \u003Cservice\u002Fworkflow>\n  - Storage: \u003Csecret manager\u002Fenv var>\n  - Rotation: \u003Ccadence> | \u003Cowner> | \u003Cprocedure>\n  - Audit: \u003Cwhat is logged and where>\n```\n\nIf providing a template, output `assets\u002Fdotenv-template.example` with placeholders only.\n\n\n## SAFETY & EDGE CASES\n- Never output real secrets, tokens, or private keys. Use placeholders.\n- Read-only by default; propose changes as a plan unless explicitly asked to modify files.\n- Avoid over-broad scopes\u002Froles unless justified by a documented requirement.\n\n\n## EXAMPLES\n- Input: “n8n HTTP nodes contain API keys.”  \n  Output: Env var map + plan to move to n8n credentials\u002Fenv vars + rotation runbook.\n\n- Input: “Need dev vs prod separation.”  \n  Output: Two env maps + naming scheme + access boundary checklist.\n\n",{"name":5,"description":7},"main","e7e336ac628c3e3bd771aff1aaa469c93778f94a","skills\u002Fkowl64\u002Fapi-credentials-hygiene",0,"https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills","https:\u002F\u002Fgithub.com\u002Fkbarbel640-del","2026-08-23 22:39:37",{"source":8,"skillName":5,"commands":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add kbarbel640-del\u002Fskills --skill api-credentials-hygiene",{"tool":60,"command":61},"bunx","bunx skills add kbarbel640-del\u002Fskills --skill api-credentials-hygiene",{"tool":63,"command":64},"pnpm","pnpm dlx skills add kbarbel640-del\u002Fskills --skill api-credentials-hygiene","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fkowl64\u002Fapi-credentials-hygiene\u002FSKILL.md",true,[68,74],{"path":69,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":73},"_meta.json","REFERENCE","参考文档",298,"https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fkowl64\u002Fapi-credentials-hygiene\u002F_meta.json",{"path":75,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":78,"sourceHtmlUrl":79},"assets\u002Fdotenv-template.example.md","ASSET","资产文件",341,"https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fkowl64\u002Fapi-credentials-hygiene\u002Fassets\u002Fdotenv-template.example.md",[81,109,135,156,162,182],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":90,"publishedAt":42},"01M6G8J55967D6281ACMKAKTEQ","crowd-prompting","A marketplace where AI agents improve prompts, system instructions, tool descriptions, and other text-based content with domain expertise from real-world operations — and earn tokens for valuable contributions.","https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fzzadrian\u002Fcrowd-prompting\u002FSKILL.md",[87],{"categoryNo":88,"categoryName":89,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000036","内容创作者",[91,92,29,93,94,95,96,97,98,99,100,101,102,103,104,105,106,107,108],"crowd prompting","prompting","with","tokens","domain","world","prompts","operations","instructions","text","tool","system","improve","productivity","marketplace","https","content","ai agents",{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":118,"publishedAt":42},"01M6G8J0PKPAYVET6BWE8W4C26","dilemm-ai","Compete in DilemmAI, the prisoner's dilemma AI arena at dilemm.ai. Use when an OpenClaw agent wants to create an account, design and submit strategy prompts for their bot, enter matchmaking, analyze historical matches and leaderboards, and iterate on bot strategy. Requires headless browser automation (no API available yet).","https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fzyori\u002Fdilemm-ai\u002FSKILL.md",[115],{"categoryNo":116,"categoryName":117,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",[119,29,120,121,122,123,124,125,126,127,128,129,130,131,132,133,134,97,37],"dilemm ai","arena","analyze","browser","openclaw agent","create","automation","browser automation","bot","openclaw","design","strategy","headless","compete","submit","matchmaking",{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":139,"categories":140,"keywords":144,"publishedAt":42},"01M6G8HWAF3K9SW7NP3Z83CPJ6","arxiv-paper-reviews","Interact with arXiv Crawler API to fetch papers, read reviews, and submit comments. Use when working with arXiv papers, fetching paper lists by date\u002Fcategory\u002Finterest, viewing paper details with comments, or submitting paper reviews via API at http:\u002F\u002F150.158.152.82:8000.","https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fzxrys\u002Fweak-accept\u002FSKILL.md",[141],{"categoryNo":142,"categoryName":143,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000021","资料检索与研究",[145,146,147,148,149,150,151,93,152,133,37,153,29,154,155],"arxiv paper reviews","reviews","arxiv","paper","crawler","papers","comments","fetch","read","http","via",{"skillNo":157,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":161,"publishedAt":42},"01M6G8HQJ7N7WMY6YV7D7SSJ16","https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fzxrys\u002Farxiv-paper-reviews\u002FSKILL.md",[160],{"categoryNo":142,"categoryName":143,"taxonomyType":20,"taxonomyTypeDesc":21},[148,147,146,145,155,150,151,93,149,133,37,152,153,29,154],{"skillNo":163,"name":164,"nameZh":6,"description":165,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":166,"categories":167,"keywords":168,"publishedAt":42},"01M6G8HM95Y64JNVFC2HN4E2BG","git-summary","Get a quick summary of the current Git repository including status, recent commits, branches, and contributors.","https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fzweack\u002Fgit-summary\u002FSKILL.md",[],[169,170,171,172,173,174,175,176,177,178,179,180,181],"git","summary","git summary","commits","repository","win32","status","linux","contributors","true","quick","get","branches",{"skillNo":183,"name":184,"nameZh":6,"description":185,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":186,"categories":187,"keywords":192,"publishedAt":42},"01M6G8HGEGF05CNEJCGVYFSC4R","agent-constitution","Interact with AgentConstitution governance contracts on Base Sepolia. Check compliance, read rules, log actions, query governance state.","https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fztsalexey\u002Fagent-constitution\u002FSKILL.md",[188,189],{"categoryNo":116,"categoryName":117,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":190,"categoryName":191,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000037","律师与法务",[193,194,195,196,93,197,198,47,199,153,200,201,202,203,204,106,205,206,207],"agent constitution","constitution","contracts","tree","query","base","log","check","Rules","projects","compliance","actions","state","governance","github"]