[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6EGN1DJYAED3V65VMJ8MK3X":3,"skill-same:01M6EGN1DJYAED3V65VMJ8MK3X":72},{"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":30,"linkOnly":31,"markdownContent":32,"markdownBody":33,"frontMatter":34,"refName":35,"commitSha":36,"skillDirectory":37,"forksCount":38,"repositoryHtmlUrl":39,"repositoryHomepageUrl":6,"ownerHtmlUrl":40,"ownerBlogUrl":41,"ownerDescription":42,"updatedAt":43,"install":44,"resources":57},"01M6EGN1DJYAED3V65VMJ8MK3X","ln-761-secret-scanner",null,"Scans codebase for hardcoded secrets. Returns normalized findings with severity and remediation guidance. Pre-commit hook integration.","levalencia\u002Fagent-god-mode","levalencia","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6962857?v=4","01M6EB0FZZ4BPQPC4HET4QY6NM","Luis Valencia ","01M6EB0G4HWHPWW0H9X7QKSAHP",3,"MIT","https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fln-761-secret-scanner\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29],"scanner","secret scanner","ln 761 secret scanner","commit","integration","severity","remediation","pre-commit","secrets","returns","guidance","2026-11-10 10:12:30",false,"---\nname: ln-761-secret-scanner\ndescription: Scans codebase for hardcoded secrets. Returns normalized findings with severity and remediation guidance. Pre-commit hook integration.\nlicense: MIT\n---\n\n> **Paths:** File paths (`shared\u002F`, `references\u002F`, `..\u002Fln-*`) are relative to skills repo root. If not found at CWD, locate this SKILL.md directory and go up one level for repo root.\n\n# Secret Scanner\n\nScans codebase for hardcoded secrets and credentials, returning structured findings for remediation.\n\n## Purpose & Scope\n\n- Detect hardcoded secrets using available tools (gitleaks, trufflehog) or manual patterns\n- Classify findings by severity (Critical\u002FHigh\u002FMedium\u002FLow)\n- Filter false positives via baseline and allowlists\n- Provide remediation guidance per finding type\n- Return normalized report to parent orchestrator (ln-760)\n\n## When to Use\n\n- During project bootstrap (via ln-760-security-setup)\n- Pre-commit hook validation\n- CI\u002FCD security pipeline\n- Manual security audit\n\n---\n\n## Workflow\n\n### Phase 1: Tool Detection\n\n**Step 1: Check Available Scanners**\n- Check if gitleaks is installed (preferred)\n- Check if trufflehog is installed (alternative)\n- If neither available: use manual pattern matching as fallback\n\n**Step 2: Load Configuration**\n- Load project `.gitleaks.toml` if exists (custom rules)\n- Load `.gitleaksbaseline` if exists (known false positives)\n- If no config: use default patterns from `references\u002Fdetection_patterns.md`\n\n### Phase 2: Scan Execution\n\n**Step 1: Run Available Scanner**\n- Execute scanner against project root\n- Capture output in structured format (JSON\u002FSARIF preferred)\n- If tool unavailable: run manual grep patterns for high-confidence secrets\n\n**Step 2: Parse Results**\n- Normalize output to common format: file, line, pattern, raw_match\n- Preserve original severity if provided by tool\n\n### Phase 3: Report Generation\n\n**Step 1: Severity Classification**\n- Map findings to severity levels per `references\u002Fdetection_patterns.md`\n- Critical: AWS keys, private keys, JWT secrets\n- High: Generic passwords, connection strings\n- Medium: API keys (may be test data)\n- Low: Potential secrets requiring manual review\n\n**Step 2: False Positive Filtering**\n- Apply baseline exclusions\n- Apply allowlist patterns (placeholders, test data, docs)\n- Mark filtered items as \"excluded\" with reason\n\n**Step 3: Build Report**\n- Group findings by severity\n- Include file path, line number, pattern matched\n- Do NOT include actual secret values in report\n\n### Phase 4: Remediation Guidance\n\n**Step 1: Attach Remediation Actions**\n- For each finding, attach remediation steps from `references\u002Fremediation_guide.md`\n- For Critical findings: emphasize immediate rotation requirement\n\n**Step 2: Return Results**\n- Return structured findings list to orchestrator\n- Include summary: total scanned, total found, by severity\n\n---\n\n## Critical Rules\n\n1. **Never log actual secret values** - redact in all outputs\n2. **Treat any found secret as compromised** - rotation required for Critical\n3. **Preserve baseline** - do not remove existing baseline entries\n4. **Pre-commit priority** - recommend pre-commit hook if not configured\n5. **Git history awareness** - warn if secret may exist in history (requires git-filter-repo)\n\n---\n\n## Definition of Done\n\n- [ ] Scan completed using available tool or manual patterns\n- [ ] Findings classified by severity\n- [ ] False positives filtered via baseline\u002Fallowlist\n- [ ] Remediation guidance attached to each finding\n- [ ] Report returned in normalized format (no raw secret values)\n- [ ] Critical findings flagged with rotation requirement\n\n---\n\n## Reference Files\n\n| File | Purpose |\n|------|---------|\n| `references\u002Fdetection_patterns.md` | Secret patterns by confidence level |\n| `references\u002Fgitleaks_config_template.toml` | Template for project gitleaks config |\n| `references\u002Fremediation_guide.md` | Rotation procedures by secret type |\n\n---\n\n**Version:** 2.0.0\n**Last Updated:** 2026-01-10\n","> **Paths:** File paths (`shared\u002F`, `references\u002F`, `..\u002Fln-*`) are relative to skills repo root. If not found at CWD, locate this SKILL.md directory and go up one level for repo root.\n\n# Secret Scanner\n\nScans codebase for hardcoded secrets and credentials, returning structured findings for remediation.\n\n## Purpose & Scope\n\n- Detect hardcoded secrets using available tools (gitleaks, trufflehog) or manual patterns\n- Classify findings by severity (Critical\u002FHigh\u002FMedium\u002FLow)\n- Filter false positives via baseline and allowlists\n- Provide remediation guidance per finding type\n- Return normalized report to parent orchestrator (ln-760)\n\n## When to Use\n\n- During project bootstrap (via ln-760-security-setup)\n- Pre-commit hook validation\n- CI\u002FCD security pipeline\n- Manual security audit\n\n---\n\n## Workflow\n\n### Phase 1: Tool Detection\n\n**Step 1: Check Available Scanners**\n- Check if gitleaks is installed (preferred)\n- Check if trufflehog is installed (alternative)\n- If neither available: use manual pattern matching as fallback\n\n**Step 2: Load Configuration**\n- Load project `.gitleaks.toml` if exists (custom rules)\n- Load `.gitleaksbaseline` if exists (known false positives)\n- If no config: use default patterns from `references\u002Fdetection_patterns.md`\n\n### Phase 2: Scan Execution\n\n**Step 1: Run Available Scanner**\n- Execute scanner against project root\n- Capture output in structured format (JSON\u002FSARIF preferred)\n- If tool unavailable: run manual grep patterns for high-confidence secrets\n\n**Step 2: Parse Results**\n- Normalize output to common format: file, line, pattern, raw_match\n- Preserve original severity if provided by tool\n\n### Phase 3: Report Generation\n\n**Step 1: Severity Classification**\n- Map findings to severity levels per `references\u002Fdetection_patterns.md`\n- Critical: AWS keys, private keys, JWT secrets\n- High: Generic passwords, connection strings\n- Medium: API keys (may be test data)\n- Low: Potential secrets requiring manual review\n\n**Step 2: False Positive Filtering**\n- Apply baseline exclusions\n- Apply allowlist patterns (placeholders, test data, docs)\n- Mark filtered items as \"excluded\" with reason\n\n**Step 3: Build Report**\n- Group findings by severity\n- Include file path, line number, pattern matched\n- Do NOT include actual secret values in report\n\n### Phase 4: Remediation Guidance\n\n**Step 1: Attach Remediation Actions**\n- For each finding, attach remediation steps from `references\u002Fremediation_guide.md`\n- For Critical findings: emphasize immediate rotation requirement\n\n**Step 2: Return Results**\n- Return structured findings list to orchestrator\n- Include summary: total scanned, total found, by severity\n\n---\n\n## Critical Rules\n\n1. **Never log actual secret values** - redact in all outputs\n2. **Treat any found secret as compromised** - rotation required for Critical\n3. **Preserve baseline** - do not remove existing baseline entries\n4. **Pre-commit priority** - recommend pre-commit hook if not configured\n5. **Git history awareness** - warn if secret may exist in history (requires git-filter-repo)\n\n---\n\n## Definition of Done\n\n- [ ] Scan completed using available tool or manual patterns\n- [ ] Findings classified by severity\n- [ ] False positives filtered via baseline\u002Fallowlist\n- [ ] Remediation guidance attached to each finding\n- [ ] Report returned in normalized format (no raw secret values)\n- [ ] Critical findings flagged with rotation requirement\n\n---\n\n## Reference Files\n\n| File | Purpose |\n|------|---------|\n| `references\u002Fdetection_patterns.md` | Secret patterns by confidence level |\n| `references\u002Fgitleaks_config_template.toml` | Template for project gitleaks config |\n| `references\u002Fremediation_guide.md` | Rotation procedures by secret type |\n\n---\n\n**Version:** 2.0.0\n**Last Updated:** 2026-01-10\n",{"name":5,"license":15,"description":7},"main","fa638b97a18ff6d9f26cf0eaf3dfa123531bcc87","organized-skills\u002Fln-761-secret-scanner",1,"https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode","https:\u002F\u002Fgithub.com\u002Flevalencia","https:\u002F\u002Fmedium.com\u002F@luisevalencia","Microsoft MVP - Artificial Intelligence\r\nMachine Learning Enthusiast\r\n","2026-05-02 06:55:36",{"source":8,"skillName":5,"commands":45,"prompt":55,"zipAvailable":56},[46,49,52],{"tool":47,"command":48},"npx","npx skills add levalencia\u002Fagent-god-mode --skill ln-761-secret-scanner",{"tool":50,"command":51},"bunx","bunx skills add levalencia\u002Fagent-god-mode --skill ln-761-secret-scanner",{"tool":53,"command":54},"pnpm","pnpm dlx skills add levalencia\u002Fagent-god-mode --skill ln-761-secret-scanner","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fln-761-secret-scanner\u002FSKILL.md",true,[58,64,68],{"path":59,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":62,"sourceHtmlUrl":63},"references\u002Fdetection_patterns.md","REFERENCE","参考文档",2913,"https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fln-761-secret-scanner\u002Freferences\u002Fdetection_patterns.md",{"path":65,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":66,"sourceHtmlUrl":67},"references\u002Fgitleaks_config_template.toml",1410,"https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fln-761-secret-scanner\u002Freferences\u002Fgitleaks_config_template.toml",{"path":69,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":70,"sourceHtmlUrl":71},"references\u002Fremediation_guide.md",3485,"https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fln-761-secret-scanner\u002Freferences\u002Fremediation_guide.md",[73,94,132,159,185,213],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":30},"01M6EM8ES5M9J4S8N78NJST0YC","zarr-python","Chunked N-D arrays for cloud storage. Compressed arrays, parallel I\u002FO, S3\u002FGCS integration, NumPy\u002FDask\u002FXarray compatible, for large-scale scientific computing pipelines.","https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fzarr-python\u002FSKILL.md",[],[80,81,82,23,83,84,85,86,87,88,89,90,91,92,93],"python","zarr python","storage","s3","gcs","cloud","dask","parallel","pipelines","arrays","numpy","scientific computing","scale","scientific",{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":113,"publishedAt":30},"01M6EM8AR6ZFKZ9YVW8TTG850Z","zabbix","Zabbix monitoring system automation via API and Python. Use when: (1) Managing hosts, templates, items, triggers, or host groups, (2) Automating monitoring configuration, (3) Sending data via Zabbix trapper\u002Fsender, (4) Querying historical data or events, (5) Bulk operations on Zabbix objects, (6) Maintenance window management, (7) User\u002Fpermission management","https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fzabbix-api-skill\u002FSKILL.md",[100,105,108],{"categoryNo":101,"categoryName":102,"taxonomyType":103,"taxonomyTypeDesc":104},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":106,"categoryName":107,"taxonomyType":103,"taxonomyTypeDesc":104},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":109,"categoryName":110,"taxonomyType":111,"taxonomyTypeDesc":112},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[96,80,114,115,116,117,118,119,120,121,122,123,124,125,126,127,128,129,130,131],"automation","window management","monitoring","data","templates","api","system","operations","use","maintenance","objects","permission","bulk operations","triggers","host","events","via","bulk",{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":138,"publishedAt":30},"01M6EM6Q9JG846ECQY9A210A26","x-twitter-growth","X\u002FTwitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X\u002FTwitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.","https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fx-twitter-growth\u002FSKILL.md",[],[139,140,141,142,143,144,145,146,147,148,149,150,151,152,153,154,155,156,157,158],"twitter","x twitter growth","growth","competitive intelligence","search","analyzing","plan","marketing","web search","competitors","analyze","write","optimize","social","intelligence","viral","growth engine","mechanics","grow","competitive",{"skillNo":160,"name":161,"nameZh":6,"description":162,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":163,"categories":164,"keywords":165,"publishedAt":30},"01M6EM3FQNPYNKPC4CV9TCVNGD","what-if-oracle","Run structured What-If scenario analysis with multi-branch possibility exploration. Use this skill when the user asks speculative questions like \"what if...\", \"what would happen if...\", \"what are the possibilities\", \"explore scenarios\", \"scenario analysis\", \"possibility space\", \"what could go wrong\", \"best case \u002F worst case\", \"risk analysis\", \"contingency planning\", \"strategic options\", or any question about uncertain futures. Also trigger when the user faces a fork-in-the-road decision, wants to stress-test an idea, or needs to think through consequences before committing.","https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fwhat-if-oracle\u002FSKILL.md",[],[166,167,168,169,170,171,172,173,174,175,176,177,122,178,179,180,181,182,183,184],"oracle","what if oracle","test","planning","ux","futures","risk","analysis","explore","decision","branch","question","exploration","options","stress-test","strategies","trigger","case","multi",{"skillNo":186,"name":187,"nameZh":6,"description":188,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":189,"categories":190,"keywords":194,"publishedAt":30},"01M6EM08C06RGDYCJ86HAPK0FF","vercel-react-best-practices","React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React\u002FNext.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.","https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fvercel-react-best-practices\u002FSKILL.md",[191],{"categoryNo":192,"categoryName":193,"taxonomyType":103,"taxonomyTypeDesc":104},"01JBSEEDCAT000000000000009","前端开发",[195,196,197,198,199,200,201,202,203,204,205,206,207,117,208,209,210,211,212,127],"react","vercel react best practices","best practices","react best practices","vercel","writing","performance","components","react components","guidelines","tasks","code","Optimization","Next.js","refactoring","performance optimization","next","pages",{"skillNo":214,"name":215,"nameZh":6,"description":216,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":217,"categories":218,"keywords":229,"publishedAt":30},"01M6EM00S13326QM08DTM94J6Z","venue-templates","Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.","https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fvenue-templates\u002FSKILL.md",[219,222,225,226],{"categoryNo":220,"categoryName":221,"taxonomyType":103,"taxonomyTypeDesc":104},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":223,"categoryName":224,"taxonomyType":103,"taxonomyTypeDesc":104},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":106,"categoryName":107,"taxonomyType":103,"taxonomyTypeDesc":104},{"categoryNo":227,"categoryName":228,"taxonomyType":111,"taxonomyTypeDesc":112},"01JBSEEDCAT000000000000036","内容创作者",[118,230,231,204,232,233,234,235,236,237,238,150,239,240,241,242,243,244,93,245],"venue templates","research","NeurIPS","ICML","LaTeX","science","Bash","access","read","edit","proposals","Academic","requirements","formatting","journal","chi"]