[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73C019HCG4QBKPV91CVG4VF":3,"skill-same:01M73C019HCG4QBKPV91CVG4VF":59},{"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":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":37,"commitSha":38,"skillDirectory":39,"forksCount":40,"repositoryHtmlUrl":41,"repositoryHomepageUrl":6,"ownerHtmlUrl":42,"ownerBlogUrl":43,"ownerDescription":6,"updatedAt":44,"install":45,"resources":58},"01M73C019HCG4QBKPV91CVG4VF","security-audit-codebase",null,"Perform a security audit of a codebase checking for exposed secrets, vulnerable dependencies, injection vulnerabilities, insecure configurations, and OWASP Top 10 issues. Use before publishing or deploying a project, for periodic security reviews, after adding authentication or API integration, before open-sourcing a private repository, or when preparing for a security compliance audit.","roohe\u002Fagentic-super-skills","roohe","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F99054084?v=4","01M734WCDFP6RZVT5CNM00QR26","01M734WCE4BD0T4NZS5PCV9V5F",10,"MIT","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fsecurity-audit-codebase\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: security-audit-codebase\nlocale: caveman-lite\nsource_locale: en\nsource_commit: 82c77053\ntranslator: \"Julius Brussee homage — caveman\"\ntranslation_date: \"2026-05-03\"\ndescription: >\n  Perform a security audit of a codebase checking for exposed secrets,\n  vulnerable dependencies, injection vulnerabilities, insecure\n  configurations, and OWASP Top 10 issues. Use before publishing or\n  deploying a project, for periodic security reviews, after adding\n  authentication or API integration, before open-sourcing a private\n  repository, or when preparing for a security compliance audit.\nlicense: MIT\nallowed-tools: Read Write Edit Bash Grep Glob\nmetadata:\n  author: Philipp Thoss\n  version: \"1.0\"\n  domain: general\n  complexity: intermediate\n  language: multi\n  tags: security, audit, owasp, secrets, vulnerability\n---\n\n# Security Audit Codebase\n\nPerform a systematic security review of a codebase to identify vulnerabilities and exposed secrets.\n\n## When to Use\n\n- Before publishing or deploying a project\n- Periodic security review of existing projects\n- After adding authentication, API integration, or user input handling\n- Before open-sourcing a private repository\n- Preparing for a security compliance audit\n\n## Inputs\n\n- **Required**: Codebase to audit\n- **Optional**: Specific focus area (secrets, dependencies, injection, auth)\n- **Optional**: Compliance framework (OWASP, ISO 27001, SOC 2)\n- **Optional**: Previous audit findings for comparison\n\n## Procedure\n\n### Step 1: Scan for Exposed Secrets\n\nSearch for patterns that indicate hardcoded secrets:\n\n```bash\n# API keys and tokens\ngrep -rn \"sk-\\|ghp_\\|gho_\\|github_pat_\\|hf_\\|AKIA\" --include=\"*.{md,js,ts,py,R,json,yml,yaml}\" .\n\n# Generic secret patterns\ngrep -rn \"password\\s*=\\s*['\\\"]\" --include=\"*.{js,ts,py,R,json}\" .\ngrep -rn \"api[_-]key\\s*[=:]\\s*['\\\"]\" --include=\"*.{js,ts,py,R,json}\" .\ngrep -rn \"secret\\s*[=:]\\s*['\\\"]\" --include=\"*.{js,ts,py,R,json}\" .\n\n# Connection strings\ngrep -rn \"postgresql:\u002F\u002F\\|mysql:\u002F\u002F\\|mongodb:\u002F\u002F\" .\n\n# Private keys\ngrep -rn \"BEGIN.*PRIVATE KEY\" .\n```\n\n**Got:** No real secrets found — only placeholders like `YOUR_TOKEN_HERE` or `your.email@example.com`.\n\n**If fail:** If real secrets are found, remove them immediately, rotate the exposed credential, and clean git history with `git filter-branch` or `git-filter-repo`. Treat any exposed secret as compromised.\n\n### Step 2: Check .gitignore Coverage\n\nVerify sensitive files are excluded:\n\n```bash\n# Check that these are git-ignored\ngit check-ignore .env .Renviron credentials.json node_modules\u002F\n\n# Look for tracked sensitive files\ngit ls-files | grep -i \"\\.env\\|\\.renviron\\|credentials\\|secret\"\n```\n\n**Got:** All sensitive files (`.env`, `.Renviron`, `credentials.json`) are listed in `.gitignore`, and `git ls-files` returns no tracked sensitive files.\n\n**If fail:** If sensitive files are tracked, run `git rm --cached \u003Cfile>` to untrack them, add to `.gitignore`, and commit. The file remains on disk but is no longer version-controlled.\n\n### Step 3: Audit Dependencies\n\n**Node.js**:\n\n```bash\nnpm audit\nnpx audit-ci --moderate\n```\n\n**Python**:\n\n```bash\npip-audit\nsafety check\n```\n\n**R**:\n\n```r\n# Check for known vulnerabilities in packages\n# No built-in tool, but verify package sources\nrenv::status()\n```\n\n**Got:** No high or critical vulnerabilities in dependencies. Moderate and low vulnerabilities documented for review.\n\n**If fail:** If critical vulnerabilities are found, update the affected packages immediately with `npm audit fix` or `pip install --upgrade`. If updates introduce breaking changes, document the vulnerability and create a remediation plan.\n\n### Step 4: Check for Injection Vulnerabilities\n\n**SQL Injection**:\n\n```bash\n# Look for string concatenation in queries\ngrep -rn \"paste.*SELECT\\|paste.*INSERT\\|paste.*UPDATE\\|paste.*DELETE\" --include=\"*.R\" .\ngrep -rn \"query.*\\+.*\\|query.*\\$\\{\" --include=\"*.{js,ts}\" .\n```\n\nAll database queries should use parameterized queries, not string concatenation.\n\n**Command Injection**:\n\n```bash\n# Look for shell execution with user input\ngrep -rn \"system\\(.*paste\\|exec(\\|spawn(\" --include=\"*.{R,js,ts,py}\" .\n```\n\n**XSS (Cross-Site Scripting)**:\n\n```bash\n# Look for unescaped user content in HTML\ngrep -rn \"innerHTML\\|dangerouslySetInnerHTML\\|v-html\" --include=\"*.{js,ts,jsx,tsx,vue}\" .\n```\n\n**Got:** No SQL, command, or XSS injection vectors found. All database queries use parameterized statements, shell commands avoid user-controlled input, and HTML output is properly escaped.\n\n**If fail:** If injection vulnerabilities are found, replace string concatenation in queries with parameterized queries, sanitize or escape user input before shell execution, and use framework-safe rendering methods instead of `innerHTML` or `dangerouslySetInnerHTML`.\n\n### Step 5: Review Authentication and Authorization\n\nChecklist:\n- [ ] Passwords hashed with bcrypt\u002Fargon2 (not MD5\u002FSHA1)\n- [ ] Session tokens are random and sufficiently long\n- [ ] Authentication tokens have expiration\n- [ ] API endpoints check authorization\n- [ ] CORS configured restrictively\n- [ ] CSRF protection enabled for state-changing operations\n\n**Got:** All checklist items pass: passwords use strong hashing, tokens are random with expiration, endpoints enforce authorization, CORS is restrictive, and CSRF protection is active.\n\n**If fail:** Prioritize fixes by severity: weak password hashing and missing authorization are critical, while CORS and CSRF issues are high. Document all findings with their severity level.\n\n### Step 6: Check Configuration Security\n\n```bash\n# Debug mode in production configs\ngrep -rn \"debug\\s*[=:]\\s*[Tt]rue\\|DEBUG\\s*=\\s*1\" --include=\"*.{json,yml,yaml,toml,cfg}\" .\n\n# Permissive CORS\ngrep -rn \"Access-Control-Allow-Origin.*\\*\\|cors.*origin.*\\*\" --include=\"*.{js,ts}\" .\n\n# HTTP instead of HTTPS\ngrep -rn \"http:\u002F\u002F\" --include=\"*.{js,ts,py,R}\" . | grep -v \"localhost\\|127.0.0.1\\|http:\u002F\u002F\"\n```\n\n**Got:** Debug mode is disabled in production configurations, CORS does not use wildcard origins in production, and all external URLs use HTTPS.\n\n**If fail:** If debug mode is enabled in production configs, disable it immediately. Replace wildcard CORS origins with explicit allowed domains. Update `http:\u002F\u002F` URLs to `https:\u002F\u002F` where the endpoint supports it.\n\n### Step 7: Document Findings\n\nCreate an audit report:\n\n```markdown\n# Security Audit Report\n\n**Date**: YYYY-MM-DD\n**Auditor**: [Name]\n**Scope**: [Repository\u002FProject]\n**Status**: [PASS\u002FFAIL\u002FCONDITIONAL]\n\n## Findings Summary\n\n| Category | Status | Details |\n|----------|--------|---------|\n| Exposed secrets | PASS | No secrets found |\n| .gitignore | PASS | Sensitive files excluded |\n| Dependencies | WARN | 2 moderate vulnerabilities |\n| Injection | PASS | Parameterized queries used |\n| Auth\u002FAuthZ | N\u002FA | No authentication in scope |\n| Configuration | PASS | Debug mode disabled |\n\n## Detailed Findings\n\n### Finding 1: [Title]\n- **Severity**: Low \u002F Medium \u002F High \u002F Critical\n- **Location**: `path\u002Fto\u002Ffile:line`\n- **Description**: What was found\n- **Recommendation**: How to fix\n- **Status**: Open \u002F Resolved\n\n## Recommendations\n1. Update dependencies to fix moderate vulnerabilities\n2. [Additional recommendations]\n```\n\n**Got:** A complete `SECURITY_AUDIT_REPORT.md` saved in the project root with findings categorized by severity, each with a specific location, description, and recommendation.\n\n**If fail:** With too many findings to document individually, group by category and prioritize critical\u002Fhigh findings. Generate the report regardless of outcome to establish a baseline.\n\n## Validation\n\n- [ ] No hardcoded secrets in source code\n- [ ] .gitignore covers all sensitive files\n- [ ] No high\u002Fcritical dependency vulnerabilities\n- [ ] No injection vulnerabilities\n- [ ] Authentication is properly implemented (if applicable)\n- [ ] Audit report is complete and findings addressed\n\n## Pitfalls\n\n- **Only checking current files**: Secrets in git history are still exposed. Check with `git log -p --all -S 'secret_pattern'`.\n- **Ignoring dev dependencies**: Development dependencies can still introduce supply chain risks.\n- **False sense of security from `.gitignore`**: `.gitignore` only prevents future tracking. Already-committed files need `git rm --cached`.\n- **Overlooking configuration files**: `docker-compose.yml`, CI configs, and deployment scripts often contain secrets.\n- **Not rotating compromised credentials**: Finding and removing a secret is not enough. The credential must be revoked and regenerated.\n\n## Related Skills\n\n- `configure-git-repository` - proper .gitignore setup\n- `write-claude-md` - documenting security requirements\n- `setup-gxp-r-project` - security in regulated environments\n","# Security Audit Codebase\n\nPerform a systematic security review of a codebase to identify vulnerabilities and exposed secrets.\n\n## When to Use\n\n- Before publishing or deploying a project\n- Periodic security review of existing projects\n- After adding authentication, API integration, or user input handling\n- Before open-sourcing a private repository\n- Preparing for a security compliance audit\n\n## Inputs\n\n- **Required**: Codebase to audit\n- **Optional**: Specific focus area (secrets, dependencies, injection, auth)\n- **Optional**: Compliance framework (OWASP, ISO 27001, SOC 2)\n- **Optional**: Previous audit findings for comparison\n\n## Procedure\n\n### Step 1: Scan for Exposed Secrets\n\nSearch for patterns that indicate hardcoded secrets:\n\n```bash\n# API keys and tokens\ngrep -rn \"sk-\\|ghp_\\|gho_\\|github_pat_\\|hf_\\|AKIA\" --include=\"*.{md,js,ts,py,R,json,yml,yaml}\" .\n\n# Generic secret patterns\ngrep -rn \"password\\s*=\\s*['\\\"]\" --include=\"*.{js,ts,py,R,json}\" .\ngrep -rn \"api[_-]key\\s*[=:]\\s*['\\\"]\" --include=\"*.{js,ts,py,R,json}\" .\ngrep -rn \"secret\\s*[=:]\\s*['\\\"]\" --include=\"*.{js,ts,py,R,json}\" .\n\n# Connection strings\ngrep -rn \"postgresql:\u002F\u002F\\|mysql:\u002F\u002F\\|mongodb:\u002F\u002F\" .\n\n# Private keys\ngrep -rn \"BEGIN.*PRIVATE KEY\" .\n```\n\n**Got:** No real secrets found — only placeholders like `YOUR_TOKEN_HERE` or `your.email@example.com`.\n\n**If fail:** If real secrets are found, remove them immediately, rotate the exposed credential, and clean git history with `git filter-branch` or `git-filter-repo`. Treat any exposed secret as compromised.\n\n### Step 2: Check .gitignore Coverage\n\nVerify sensitive files are excluded:\n\n```bash\n# Check that these are git-ignored\ngit check-ignore .env .Renviron credentials.json node_modules\u002F\n\n# Look for tracked sensitive files\ngit ls-files | grep -i \"\\.env\\|\\.renviron\\|credentials\\|secret\"\n```\n\n**Got:** All sensitive files (`.env`, `.Renviron`, `credentials.json`) are listed in `.gitignore`, and `git ls-files` returns no tracked sensitive files.\n\n**If fail:** If sensitive files are tracked, run `git rm --cached \u003Cfile>` to untrack them, add to `.gitignore`, and commit. The file remains on disk but is no longer version-controlled.\n\n### Step 3: Audit Dependencies\n\n**Node.js**:\n\n```bash\nnpm audit\nnpx audit-ci --moderate\n```\n\n**Python**:\n\n```bash\npip-audit\nsafety check\n```\n\n**R**:\n\n```r\n# Check for known vulnerabilities in packages\n# No built-in tool, but verify package sources\nrenv::status()\n```\n\n**Got:** No high or critical vulnerabilities in dependencies. Moderate and low vulnerabilities documented for review.\n\n**If fail:** If critical vulnerabilities are found, update the affected packages immediately with `npm audit fix` or `pip install --upgrade`. If updates introduce breaking changes, document the vulnerability and create a remediation plan.\n\n### Step 4: Check for Injection Vulnerabilities\n\n**SQL Injection**:\n\n```bash\n# Look for string concatenation in queries\ngrep -rn \"paste.*SELECT\\|paste.*INSERT\\|paste.*UPDATE\\|paste.*DELETE\" --include=\"*.R\" .\ngrep -rn \"query.*\\+.*\\|query.*\\$\\{\" --include=\"*.{js,ts}\" .\n```\n\nAll database queries should use parameterized queries, not string concatenation.\n\n**Command Injection**:\n\n```bash\n# Look for shell execution with user input\ngrep -rn \"system\\(.*paste\\|exec(\\|spawn(\" --include=\"*.{R,js,ts,py}\" .\n```\n\n**XSS (Cross-Site Scripting)**:\n\n```bash\n# Look for unescaped user content in HTML\ngrep -rn \"innerHTML\\|dangerouslySetInnerHTML\\|v-html\" --include=\"*.{js,ts,jsx,tsx,vue}\" .\n```\n\n**Got:** No SQL, command, or XSS injection vectors found. All database queries use parameterized statements, shell commands avoid user-controlled input, and HTML output is properly escaped.\n\n**If fail:** If injection vulnerabilities are found, replace string concatenation in queries with parameterized queries, sanitize or escape user input before shell execution, and use framework-safe rendering methods instead of `innerHTML` or `dangerouslySetInnerHTML`.\n\n### Step 5: Review Authentication and Authorization\n\nChecklist:\n- [ ] Passwords hashed with bcrypt\u002Fargon2 (not MD5\u002FSHA1)\n- [ ] Session tokens are random and sufficiently long\n- [ ] Authentication tokens have expiration\n- [ ] API endpoints check authorization\n- [ ] CORS configured restrictively\n- [ ] CSRF protection enabled for state-changing operations\n\n**Got:** All checklist items pass: passwords use strong hashing, tokens are random with expiration, endpoints enforce authorization, CORS is restrictive, and CSRF protection is active.\n\n**If fail:** Prioritize fixes by severity: weak password hashing and missing authorization are critical, while CORS and CSRF issues are high. Document all findings with their severity level.\n\n### Step 6: Check Configuration Security\n\n```bash\n# Debug mode in production configs\ngrep -rn \"debug\\s*[=:]\\s*[Tt]rue\\|DEBUG\\s*=\\s*1\" --include=\"*.{json,yml,yaml,toml,cfg}\" .\n\n# Permissive CORS\ngrep -rn \"Access-Control-Allow-Origin.*\\*\\|cors.*origin.*\\*\" --include=\"*.{js,ts}\" .\n\n# HTTP instead of HTTPS\ngrep -rn \"http:\u002F\u002F\" --include=\"*.{js,ts,py,R}\" . | grep -v \"localhost\\|127.0.0.1\\|http:\u002F\u002F\"\n```\n\n**Got:** Debug mode is disabled in production configurations, CORS does not use wildcard origins in production, and all external URLs use HTTPS.\n\n**If fail:** If debug mode is enabled in production configs, disable it immediately. Replace wildcard CORS origins with explicit allowed domains. Update `http:\u002F\u002F` URLs to `https:\u002F\u002F` where the endpoint supports it.\n\n### Step 7: Document Findings\n\nCreate an audit report:\n\n```markdown\n# Security Audit Report\n\n**Date**: YYYY-MM-DD\n**Auditor**: [Name]\n**Scope**: [Repository\u002FProject]\n**Status**: [PASS\u002FFAIL\u002FCONDITIONAL]\n\n## Findings Summary\n\n| Category | Status | Details |\n|----------|--------|---------|\n| Exposed secrets | PASS | No secrets found |\n| .gitignore | PASS | Sensitive files excluded |\n| Dependencies | WARN | 2 moderate vulnerabilities |\n| Injection | PASS | Parameterized queries used |\n| Auth\u002FAuthZ | N\u002FA | No authentication in scope |\n| Configuration | PASS | Debug mode disabled |\n\n## Detailed Findings\n\n### Finding 1: [Title]\n- **Severity**: Low \u002F Medium \u002F High \u002F Critical\n- **Location**: `path\u002Fto\u002Ffile:line`\n- **Description**: What was found\n- **Recommendation**: How to fix\n- **Status**: Open \u002F Resolved\n\n## Recommendations\n1. Update dependencies to fix moderate vulnerabilities\n2. [Additional recommendations]\n```\n\n**Got:** A complete `SECURITY_AUDIT_REPORT.md` saved in the project root with findings categorized by severity, each with a specific location, description, and recommendation.\n\n**If fail:** With too many findings to document individually, group by category and prioritize critical\u002Fhigh findings. Generate the report regardless of outcome to establish a baseline.\n\n## Validation\n\n- [ ] No hardcoded secrets in source code\n- [ ] .gitignore covers all sensitive files\n- [ ] No high\u002Fcritical dependency vulnerabilities\n- [ ] No injection vulnerabilities\n- [ ] Authentication is properly implemented (if applicable)\n- [ ] Audit report is complete and findings addressed\n\n## Pitfalls\n\n- **Only checking current files**: Secrets in git history are still exposed. Check with `git log -p --all -S 'secret_pattern'`.\n- **Ignoring dev dependencies**: Development dependencies can still introduce supply chain risks.\n- **False sense of security from `.gitignore`**: `.gitignore` only prevents future tracking. Already-committed files need `git rm --cached`.\n- **Overlooking configuration files**: `docker-compose.yml`, CI configs, and deployment scripts often contain secrets.\n- **Not rotating compromised credentials**: Finding and removing a secret is not enough. The credential must be revoked and regenerated.\n\n## Related Skills\n\n- `configure-git-repository` - proper .gitignore setup\n- `write-claude-md` - documenting security requirements\n- `setup-gxp-r-project` - security in regulated environments\n",{"name":5,"locale":23,"license":14,"metadata":24,"translator":31,"description":32,"allowed-tools":33,"source_commit":34,"source_locale":35,"translation_date":36},"caveman-lite",{"tags":25,"author":26,"domain":27,"version":28,"language":29,"complexity":30},"security, audit, owasp, secrets, vulnerability","Philipp Thoss","general","1.0","multi","intermediate","Julius Brussee homage — caveman","Perform a security audit of a codebase checking for exposed secrets, vulnerable dependencies, injection vulnerabilities, insecure configurations, and OWASP Top 10 issues. Use before publishing or deploying a project, for periodic security reviews, after adding authentication or API integration, before open-sourcing a private repository, or when preparing for a security compliance audit.\n","Read Write Edit Bash Grep Glob","82c77053","en","2026-05-03","master","f483e54f3ad5f202a77d45f2e57f8d970b71195f","skills_library\u002Fsecurity-audit-codebase",2,"https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills","https:\u002F\u002Fgithub.com\u002Froohe","yoou.link","2026-05-19 15:56:07",{"source":8,"skillName":5,"commands":46,"prompt":56,"zipAvailable":57},[47,50,53],{"tool":48,"command":49},"npx","npx skills add roohe\u002Fagentic-super-skills --skill security-audit-codebase",{"tool":51,"command":52},"bunx","bunx skills add roohe\u002Fagentic-super-skills --skill security-audit-codebase",{"tool":54,"command":55},"pnpm","pnpm dlx skills add roohe\u002Fagentic-super-skills --skill security-audit-codebase","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fsecurity-audit-codebase\u002FSKILL.md",true,[],[60,67,74,81,88,95],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":18},"01M73D865CZME2FCMKA4PQM348","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\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fzarr-python\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":18},"01M73D7Z64J4ABWZJD7P44XBBF","youtube-downloader","Download and process YouTube content for research. Use when: downloading competitor videos for analysis; extracting audio for podcasts; getting transcripts for content repurposing; archiving webinars; research content curation","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fyoutube-downloader\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":18},"01M73D7K8778TGZV3GJFR3703D","yc-pitch-deck","Create a compelling startup pitch deck that follows the structure proven to raise billions from top investors. Master the YC and Sequoia formats that get founders funded. Use when: **Fundraising** to create investor pitch decks; **YC application** to structure your narrative; **Demo Day prep** to craft your 2-minute pitch; **Angel investors** to communicate your opportunity; **Partnership pitches** to structure compelling asks","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fyc-pitch-deck\u002FSKILL.md",[],[],{"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":87,"publishedAt":18},"01M73D70KJSE0E8Z28YMNNRT04","x-twitter-scraper","Use when the user needs X (Twitter) data or confirmation-gated X actions through Xquik: tweet search, user lookup, follower extraction, media download, monitoring, webhooks, MCP, SDKs, posting, likes, DMs, and profile updates. Requires a Xquik API key. Never ask for X login material.","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fx-twitter-scraper\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":18},"01M73D6ED01GV077R7K4NZNFZJ","write-vignette","Create R package vignettes using R Markdown or Quarto. Covers vignette setup, YAML configuration, code chunk options, building and testing, and CRAN requirements for vignettes. Use when adding a Getting Started tutorial, documenting complex workflows spanning multiple functions, creating domain-specific guides, or when CRAN submission requires user-facing documentation beyond function help pages.","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fwrite-vignette\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":18},"01M73D69YJR0BK3NFHE0CYG3EF","write-validation-documentation","Write IQ\u002FOQ\u002FPQ validation documentation for computerized systems in regulated environments. Covers protocols, reports, test scripts, deviation handling, and approval workflows. Use when validating R or other software for regulated use, preparing for a regulatory audit, documenting qualification of computing environments, or creating and updating validation protocols and reports for new or re-qualified systems.","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fwrite-validation-documentation\u002FSKILL.md",[],[]]