[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7D8609SWK9Q67DHYC92XT22":3,"skill-same:01M7D8609SWK9Q67DHYC92XT22":73},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M7D8609SWK9Q67DHYC92XT22","senior-secops",null,"Senior SecOps engineer skill for application security, vulnerability management, compliance verification, and secure development practices. Runs SAST\u002FDAST scans, generates CVE remediation plans, checks dependency vulnerabilities, creates security policies, enforces secure coding patterns, and automates compliance checks against SOC2, PCI-DSS, HIPAA, and GDPR. Use when conducting a security review or audit, responding to a CVE or security incident, hardening infrastructure, implementing authentication or secrets management, running penetration test prep, checking OWASP Top 10 exposure, or enforcing security controls in CI\u002FCD pipelines.","Mabbit143\u002FClaude-SKills","Mabbit143","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F192994237?v=4","01M7D6X2W63K4T3N13CSVAKE3V","Mabbit Rountree","01M7D6X2WRPSZF8VMW9MW5ZP1X",0,"MIT","https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fengineering-team\u002Fskills\u002Fsenior-secops\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: \"senior-secops\"\ndescription: Senior SecOps engineer skill for application security, vulnerability management, compliance verification, and secure development practices. Runs SAST\u002FDAST scans, generates CVE remediation plans, checks dependency vulnerabilities, creates security policies, enforces secure coding patterns, and automates compliance checks against SOC2, PCI-DSS, HIPAA, and GDPR. Use when conducting a security review or audit, responding to a CVE or security incident, hardening infrastructure, implementing authentication or secrets management, running penetration test prep, checking OWASP Top 10 exposure, or enforcing security controls in CI\u002FCD pipelines.\n---\n\n# Senior SecOps Engineer\n\nComplete toolkit for Security Operations including vulnerability management, compliance verification, secure coding practices, and security automation.\n\n---\n\n## Table of Contents\n\n- [Core Capabilities](#core-capabilities)\n- [Workflows](#workflows)\n- [Tool Reference](#tool-reference)\n- [Security Standards](#security-standards)\n- [Compliance Frameworks](#compliance-frameworks)\n- [Best Practices](#best-practices)\n\n---\n\n## Core Capabilities\n\n### 1. Security Scanner\n\nScan source code for security vulnerabilities including hardcoded secrets, SQL injection, XSS, command injection, and path traversal.\n\n```bash\n# Scan project for security issues\npython scripts\u002Fsecurity_scanner.py \u002Fpath\u002Fto\u002Fproject\n\n# Filter by severity\npython scripts\u002Fsecurity_scanner.py \u002Fpath\u002Fto\u002Fproject --severity high\n\n# JSON output for CI\u002FCD\npython scripts\u002Fsecurity_scanner.py \u002Fpath\u002Fto\u002Fproject --json --output report.json\n```\n\n**Detects:**\n- Hardcoded secrets (API keys, passwords, AWS credentials, GitHub tokens, private keys)\n- SQL injection patterns (string concatenation, f-strings, template literals)\n- XSS vulnerabilities (innerHTML assignment, unsafe DOM manipulation, React unsafe patterns)\n- Command injection (shell=True, exec, eval with user input)\n- Path traversal (file operations with user input)\n\n### 2. Vulnerability Assessor\n\nScan dependencies for known CVEs across npm, Python, and Go ecosystems.\n\n```bash\n# Assess project dependencies\npython scripts\u002Fvulnerability_assessor.py \u002Fpath\u002Fto\u002Fproject\n\n# Critical\u002Fhigh only\npython scripts\u002Fvulnerability_assessor.py \u002Fpath\u002Fto\u002Fproject --severity high\n\n# Export vulnerability report\npython scripts\u002Fvulnerability_assessor.py \u002Fpath\u002Fto\u002Fproject --json --output vulns.json\n```\n\n**Scans:**\n- `package.json` and `package-lock.json` (npm)\n- `requirements.txt` and `pyproject.toml` (Python)\n- `go.mod` (Go)\n\n**Output:**\n- CVE IDs with CVSS scores\n- Affected package versions\n- Fixed versions for remediation\n- Overall risk score (0-100)\n\n### 3. Compliance Checker\n\nVerify security compliance against SOC 2, PCI-DSS, HIPAA, and GDPR frameworks.\n\n```bash\n# Check all frameworks\npython scripts\u002Fcompliance_checker.py \u002Fpath\u002Fto\u002Fproject\n\n# Specific framework\npython scripts\u002Fcompliance_checker.py \u002Fpath\u002Fto\u002Fproject --framework soc2\npython scripts\u002Fcompliance_checker.py \u002Fpath\u002Fto\u002Fproject --framework pci-dss\npython scripts\u002Fcompliance_checker.py \u002Fpath\u002Fto\u002Fproject --framework hipaa\npython scripts\u002Fcompliance_checker.py \u002Fpath\u002Fto\u002Fproject --framework gdpr\n\n# Export compliance report\npython scripts\u002Fcompliance_checker.py \u002Fpath\u002Fto\u002Fproject --json --output compliance.json\n```\n\n**Verifies:**\n- Access control implementation\n- Encryption at rest and in transit\n- Audit logging\n- Authentication strength (MFA, password hashing)\n- Security documentation\n- CI\u002FCD security controls\n\n---\n\n## Workflows\n\n### Workflow 1: Security Audit\n\nComplete security assessment of a codebase.\n\n```bash\n# Step 1: Scan for code vulnerabilities\npython scripts\u002Fsecurity_scanner.py . --severity medium\n# STOP if exit code 2 — resolve critical findings before continuing\n```\n\n```bash\n# Step 2: Check dependency vulnerabilities\npython scripts\u002Fvulnerability_assessor.py . --severity high\n# STOP if exit code 2 — patch critical CVEs before continuing\n```\n\n```bash\n# Step 3: Verify compliance controls\npython scripts\u002Fcompliance_checker.py . --framework all\n# STOP if exit code 2 — address critical gaps before proceeding\n```\n\n```bash\n# Step 4: Generate combined reports\npython scripts\u002Fsecurity_scanner.py . --json --output security.json\npython scripts\u002Fvulnerability_assessor.py . --json --output vulns.json\npython scripts\u002Fcompliance_checker.py . --json --output compliance.json\n```\n\n### Workflow 2: CI\u002FCD Security Gate\n\nIntegrate security checks into deployment pipeline.\n\n```yaml\n# .github\u002Fworkflows\u002Fsecurity.yml\nname: \"security-scan\"\n\non:\n  pull_request:\n    branches: [main, develop]\n\njobs:\n  security-scan:\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions\u002Fcheckout@v4\n\n      - name: \"set-up-python\"\n        uses: actions\u002Fsetup-python@v5\n        with:\n          python-version: '3.11'\n\n      - name: \"security-scanner\"\n        run: python scripts\u002Fsecurity_scanner.py . --severity high\n\n      - name: \"vulnerability-assessment\"\n        run: python scripts\u002Fvulnerability_assessor.py . --severity critical\n\n      - name: \"compliance-check\"\n        run: python scripts\u002Fcompliance_checker.py . --framework soc2\n```\n\nEach step fails the pipeline on its respective exit code — no deployment proceeds past a critical finding.\n\n### Workflow 3: CVE Triage\n\nRespond to a new CVE affecting your application.\n\n```\n1. ASSESS (0-2 hours)\n   - Identify affected systems using vulnerability_assessor.py\n   - Check if CVE is being actively exploited\n   - Determine CVSS environmental score for your context\n   - STOP if CVSS 9.0+ on internet-facing system — escalate immediately\n\n2. PRIORITIZE\n   - Critical (CVSS 9.0+, internet-facing): 24 hours\n   - High (CVSS 7.0-8.9): 7 days\n   - Medium (CVSS 4.0-6.9): 30 days\n   - Low (CVSS \u003C 4.0): 90 days\n\n3. REMEDIATE\n   - Update affected dependency to fixed version\n   - Run security_scanner.py to verify fix (must return exit code 0)\n   - STOP if scanner still flags the CVE — do not deploy\n   - Test for regressions\n   - Deploy with enhanced monitoring\n\n4. VERIFY\n   - Re-run vulnerability_assessor.py\n   - Confirm CVE no longer reported\n   - Document remediation actions\n```\n\n### Workflow 4: Incident Response\n\nSecurity incident handling procedure.\n\n```\nPHASE 1: DETECT & IDENTIFY (0-15 min)\n- Alert received and acknowledged\n- Initial severity assessment (SEV-1 to SEV-4)\n- Incident commander assigned\n- Communication channel established\n\nPHASE 2: CONTAIN (15-60 min)\n- Affected systems identified\n- Network isolation if needed\n- Credentials rotated if compromised\n- Preserve evidence (logs, memory dumps)\n\nPHASE 3: ERADICATE (1-4 hours)\n- Root cause identified\n- Malware\u002Fbackdoors removed\n- Vulnerabilities patched (run security_scanner.py; must return exit code 0)\n- Systems hardened\n\nPHASE 4: RECOVER (4-24 hours)\n- Systems restored from clean backup\n- Services brought back online\n- Enhanced monitoring enabled\n- User access restored\n\nPHASE 5: POST-INCIDENT (24-72 hours)\n- Incident timeline documented\n- Root cause analysis complete\n- Lessons learned documented\n- Preventive measures implemented\n- Stakeholder report delivered\n```\n\n---\n\n## Tool Reference\n\n### security_scanner.py\n\n| Option | Description |\n|--------|-------------|\n| `target` | Directory or file to scan |\n| `--severity, -s` | Minimum severity: critical, high, medium, low |\n| `--verbose, -v` | Show files as they're scanned |\n| `--json` | Output results as JSON |\n| `--output, -o` | Write results to file |\n\n**Exit Codes:** `0` = no critical\u002Fhigh findings · `1` = high severity findings · `2` = critical severity findings\n\n### vulnerability_assessor.py\n\n| Option | Description |\n|--------|-------------|\n| `target` | Directory containing dependency files |\n| `--severity, -s` | Minimum severity: critical, high, medium, low |\n| `--verbose, -v` | Show files as they're scanned |\n| `--json` | Output results as JSON |\n| `--output, -o` | Write results to file |\n\n**Exit Codes:** `0` = no critical\u002Fhigh vulnerabilities · `1` = high severity vulnerabilities · `2` = critical severity vulnerabilities\n\n### compliance_checker.py\n\n| Option | Description |\n|--------|-------------|\n| `target` | Directory to check |\n| `--framework, -f` | Framework: soc2, pci-dss, hipaa, gdpr, all |\n| `--verbose, -v` | Show checks as they run |\n| `--json` | Output results as JSON |\n| `--output, -o` | Write results to file |\n\n**Exit Codes:** `0` = compliant (90%+ score) · `1` = non-compliant (50-69% score) · `2` = critical gaps (\u003C50% score)\n\n---\n\n## Security Standards\n\nSee `references\u002Fsecurity_standards.md` for OWASP Top 10 full guidance, secure coding standards, authentication requirements, and API security controls.\n\n### Secure Coding Checklist\n\n```markdown\n## Input Validation\n- [ ] Validate all input on server side\n- [ ] Use allowlists over denylists\n- [ ] Sanitize for specific context (HTML, SQL, shell)\n\n## Output Encoding\n- [ ] HTML encode for browser output\n- [ ] URL encode for URLs\n- [ ] JavaScript encode for script contexts\n\n## Authentication\n- [ ] Use bcrypt\u002Fargon2 for passwords\n- [ ] Implement MFA for sensitive operations\n- [ ] Enforce strong password policy\n\n## Session Management\n- [ ] Generate secure random session IDs\n- [ ] Set HttpOnly, Secure, SameSite flags\n- [ ] Implement session timeout (15 min idle)\n\n## Error Handling\n- [ ] Log errors with context (no secrets)\n- [ ] Return generic messages to users\n- [ ] Never expose stack traces in production\n\n## Secrets Management\n- [ ] Use environment variables or secrets manager\n- [ ] Never commit secrets to version control\n- [ ] Rotate credentials regularly\n```\n\n---\n\n## Compliance Frameworks\n\nSee `references\u002Fcompliance_requirements.md` for full control mappings. Run `compliance_checker.py` to verify the controls below:\n\n### SOC 2 Type II\n- **CC6** Logical Access: authentication, authorization, MFA\n- **CC7** System Operations: monitoring, logging, incident response\n- **CC8** Change Management: CI\u002FCD, code review, deployment controls\n\n### PCI-DSS v4.0\n- **Req 3\u002F4**: Encryption at rest and in transit (TLS 1.2+)\n- **Req 6**: Secure development (input validation, secure coding)\n- **Req 8**: Strong authentication (MFA, password policy)\n- **Req 10\u002F11**: Audit logging, SAST\u002FDAST\u002Fpenetration testing\n\n### HIPAA Security Rule\n- Unique user IDs and audit trails for PHI access (164.312(a)(1), 164.312(b))\n- MFA for person\u002Fentity authentication (164.312(d))\n- Transmission encryption via TLS (164.312(e)(1))\n\n### GDPR\n- **Art 25\u002F32**: Privacy by design, encryption, pseudonymization\n- **Art 33**: Breach notification within 72 hours\n- **Art 17\u002F20**: Right to erasure and data portability\n\n---\n\n## Best Practices\n\n### Secrets Management\n\n```python\n# BAD: Hardcoded secret\nAPI_KEY = \"sk-1234567890abcdef\"\n\n# GOOD: Environment variable\nimport os\nAPI_KEY = os.environ.get(\"API_KEY\")\n\n# BETTER: Secrets manager\nfrom your_vault_client import get_secret\nAPI_KEY = get_secret(\"api\u002Fkey\")\n```\n\n### SQL Injection Prevention\n\n```python\n# BAD: String concatenation\nquery = f\"SELECT * FROM users WHERE id = {user_id}\"\n\n# GOOD: Parameterized query\ncursor.execute(\"SELECT * FROM users WHERE id = %s\", (user_id,))\n```\n\n### XSS Prevention\n\n```javascript\n\u002F\u002F BAD: Direct innerHTML assignment is vulnerable\n\u002F\u002F GOOD: Use textContent (auto-escaped)\nelement.textContent = userInput;\n\n\u002F\u002F GOOD: Use sanitization library for HTML\nimport DOMPurify from 'dompurify';\nconst safeHTML = DOMPurify.sanitize(userInput);\n```\n\n### Authentication\n\n```javascript\n\u002F\u002F Password hashing\nconst bcrypt = require('bcrypt');\nconst SALT_ROUNDS = 12;\n\n\u002F\u002F Hash password\nconst hash = await bcrypt.hash(password, SALT_ROUNDS);\n\n\u002F\u002F Verify password\nconst match = await bcrypt.compare(password, hash);\n```\n\n### Security Headers\n\n```javascript\n\u002F\u002F Express.js security headers\nconst helmet = require('helmet');\napp.use(helmet());\n\n\u002F\u002F Or manually set headers:\napp.use((req, res, next) => {\n  res.setHeader('X-Content-Type-Options', 'nosniff');\n  res.setHeader('X-Frame-Options', 'DENY');\n  res.setHeader('X-XSS-Protection', '1; mode=block');\n  res.setHeader('Strict-Transport-Security', 'max-age=31536000; includeSubDomains');\n  res.setHeader('Content-Security-Policy', \"default-src 'self'\");\n  next();\n});\n```\n\n---\n\n## OWASP Top 10 Quick-Check\n\nRapid 15-minute assessment — run through each category and note pass\u002Ffail. For deep-dive testing, hand off to the **security-pen-testing** skill.\n\n| # | Category | One-Line Check |\n|---|----------|----------------|\n| A01 | Broken Access Control | Verify role checks on every endpoint; test horizontal privilege escalation |\n| A02 | Cryptographic Failures | Confirm TLS 1.2+ everywhere; no secrets in logs or source |\n| A03 | Injection | Run parameterized query audit; check ORM raw-query usage |\n| A04 | Insecure Design | Review threat model exists for critical flows |\n| A05 | Security Misconfiguration | Check default credentials removed; error pages generic |\n| A06 | Vulnerable Components | Run `vulnerability_assessor.py`; zero critical\u002Fhigh CVEs |\n| A07 | Auth Failures | Verify MFA on admin; brute-force protection active |\n| A08 | Software & Data Integrity | Confirm CI\u002FCD pipeline signs artifacts; no unsigned deps |\n| A09 | Logging & Monitoring | Validate audit logs capture auth events; alerts configured |\n| A10 | SSRF | Test internal URL filters; block metadata endpoints (169.254.169.254) |\n\n> **Deep dive needed?** Hand off to `security-pen-testing` for full OWASP Testing Guide coverage.\n\n---\n\n## Secret Scanning Tools\n\nChoose the right scanner for each stage of your workflow:\n\n| Tool | Best For | Language | Pre-commit | CI\u002FCD | Custom Rules |\n|------|----------|----------|:----------:|:-----:|:------------:|\n| **gitleaks** | CI pipelines, full-repo scans | Go | Yes | Yes | TOML regexes |\n| **detect-secrets** | Pre-commit hooks, incremental | Python | Yes | Partial | Plugin-based |\n| **truffleHog** | Deep history scans, entropy | Go | No | Yes | Regex + entropy |\n\n**Recommended setup:** Use `detect-secrets` as a pre-commit hook (catches secrets before they enter history) and `gitleaks` in CI (catches anything that slips through).\n\n```bash\n# detect-secrets pre-commit hook (.pre-commit-config.yaml)\n- repo: https:\u002F\u002Fgithub.com\u002FYelp\u002Fdetect-secrets\n  rev: v1.4.0\n  hooks:\n    - id: detect-secrets\n      args: ['--baseline', '.secrets.baseline']\n\n# gitleaks in GitHub Actions\n- name: gitleaks\n  uses: gitleaks\u002Fgitleaks-action@v2\n  env:\n    GITLEAKS_LICENSE: ${{ secrets.GITLEAKS_LICENSE }}\n```\n\n---\n\n## Supply Chain Security\n\nProtect against dependency and artifact tampering with SBOM generation, artifact signing, and SLSA compliance.\n\n**SBOM Generation:**\n- **syft** — generates SBOMs from container images or source dirs (SPDX, CycloneDX formats)\n- **cyclonedx-cli** — CycloneDX-native tooling; merge multiple SBOMs for mono-repos\n\n```bash\n# Generate SBOM from container image\nsyft packages ghcr.io\u002Forg\u002Fapp:latest -o cyclonedx-json > sbom.json\n```\n\n**Artifact Signing (Sigstore\u002Fcosign):**\n```bash\n# Sign a container image (keyless via OIDC)\ncosign sign ghcr.io\u002Forg\u002Fapp:latest\n# Verify signature\ncosign verify ghcr.io\u002Forg\u002Fapp:latest --certificate-identity=ci@org.com --certificate-oidc-issuer=https:\u002F\u002Ftoken.actions.githubusercontent.com\n```\n\n**SLSA Levels Overview:**\n| Level | Requirement | What It Proves |\n|-------|-------------|----------------|\n| 1 | Build process documented | Provenance exists |\n| 2 | Hosted build service, signed provenance | Tamper-resistant provenance |\n| 3 | Hardened build platform, non-falsifiable provenance | Tamper-proof build |\n| 4 | Two-party review, hermetic builds | Maximum supply-chain assurance |\n\n> **Cross-references:** `security-pen-testing` (vulnerability exploitation testing), `dependency-auditor` (license and CVE audit for dependencies).\n\n---\n\n## Reference Documentation\n\n| Document | Description |\n|----------|-------------|\n| `references\u002Fsecurity_standards.md` | OWASP Top 10, secure coding, authentication, API security |\n| `references\u002Fvulnerability_management_guide.md` | CVE triage, CVSS scoring, remediation workflows |\n| `references\u002Fcompliance_requirements.md` | SOC 2, PCI-DSS, HIPAA, GDPR full control mappings |\n","# Senior SecOps Engineer\n\nComplete toolkit for Security Operations including vulnerability management, compliance verification, secure coding practices, and security automation.\n\n---\n\n## Table of Contents\n\n- [Core Capabilities](#core-capabilities)\n- [Workflows](#workflows)\n- [Tool Reference](#tool-reference)\n- [Security Standards](#security-standards)\n- [Compliance Frameworks](#compliance-frameworks)\n- [Best Practices](#best-practices)\n\n---\n\n## Core Capabilities\n\n### 1. Security Scanner\n\nScan source code for security vulnerabilities including hardcoded secrets, SQL injection, XSS, command injection, and path traversal.\n\n```bash\n# Scan project for security issues\npython scripts\u002Fsecurity_scanner.py \u002Fpath\u002Fto\u002Fproject\n\n# Filter by severity\npython scripts\u002Fsecurity_scanner.py \u002Fpath\u002Fto\u002Fproject --severity high\n\n# JSON output for CI\u002FCD\npython scripts\u002Fsecurity_scanner.py \u002Fpath\u002Fto\u002Fproject --json --output report.json\n```\n\n**Detects:**\n- Hardcoded secrets (API keys, passwords, AWS credentials, GitHub tokens, private keys)\n- SQL injection patterns (string concatenation, f-strings, template literals)\n- XSS vulnerabilities (innerHTML assignment, unsafe DOM manipulation, React unsafe patterns)\n- Command injection (shell=True, exec, eval with user input)\n- Path traversal (file operations with user input)\n\n### 2. Vulnerability Assessor\n\nScan dependencies for known CVEs across npm, Python, and Go ecosystems.\n\n```bash\n# Assess project dependencies\npython scripts\u002Fvulnerability_assessor.py \u002Fpath\u002Fto\u002Fproject\n\n# Critical\u002Fhigh only\npython scripts\u002Fvulnerability_assessor.py \u002Fpath\u002Fto\u002Fproject --severity high\n\n# Export vulnerability report\npython scripts\u002Fvulnerability_assessor.py \u002Fpath\u002Fto\u002Fproject --json --output vulns.json\n```\n\n**Scans:**\n- `package.json` and `package-lock.json` (npm)\n- `requirements.txt` and `pyproject.toml` (Python)\n- `go.mod` (Go)\n\n**Output:**\n- CVE IDs with CVSS scores\n- Affected package versions\n- Fixed versions for remediation\n- Overall risk score (0-100)\n\n### 3. Compliance Checker\n\nVerify security compliance against SOC 2, PCI-DSS, HIPAA, and GDPR frameworks.\n\n```bash\n# Check all frameworks\npython scripts\u002Fcompliance_checker.py \u002Fpath\u002Fto\u002Fproject\n\n# Specific framework\npython scripts\u002Fcompliance_checker.py \u002Fpath\u002Fto\u002Fproject --framework soc2\npython scripts\u002Fcompliance_checker.py \u002Fpath\u002Fto\u002Fproject --framework pci-dss\npython scripts\u002Fcompliance_checker.py \u002Fpath\u002Fto\u002Fproject --framework hipaa\npython scripts\u002Fcompliance_checker.py \u002Fpath\u002Fto\u002Fproject --framework gdpr\n\n# Export compliance report\npython scripts\u002Fcompliance_checker.py \u002Fpath\u002Fto\u002Fproject --json --output compliance.json\n```\n\n**Verifies:**\n- Access control implementation\n- Encryption at rest and in transit\n- Audit logging\n- Authentication strength (MFA, password hashing)\n- Security documentation\n- CI\u002FCD security controls\n\n---\n\n## Workflows\n\n### Workflow 1: Security Audit\n\nComplete security assessment of a codebase.\n\n```bash\n# Step 1: Scan for code vulnerabilities\npython scripts\u002Fsecurity_scanner.py . --severity medium\n# STOP if exit code 2 — resolve critical findings before continuing\n```\n\n```bash\n# Step 2: Check dependency vulnerabilities\npython scripts\u002Fvulnerability_assessor.py . --severity high\n# STOP if exit code 2 — patch critical CVEs before continuing\n```\n\n```bash\n# Step 3: Verify compliance controls\npython scripts\u002Fcompliance_checker.py . --framework all\n# STOP if exit code 2 — address critical gaps before proceeding\n```\n\n```bash\n# Step 4: Generate combined reports\npython scripts\u002Fsecurity_scanner.py . --json --output security.json\npython scripts\u002Fvulnerability_assessor.py . --json --output vulns.json\npython scripts\u002Fcompliance_checker.py . --json --output compliance.json\n```\n\n### Workflow 2: CI\u002FCD Security Gate\n\nIntegrate security checks into deployment pipeline.\n\n```yaml\n# .github\u002Fworkflows\u002Fsecurity.yml\nname: \"security-scan\"\n\non:\n  pull_request:\n    branches: [main, develop]\n\njobs:\n  security-scan:\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions\u002Fcheckout@v4\n\n      - name: \"set-up-python\"\n        uses: actions\u002Fsetup-python@v5\n        with:\n          python-version: '3.11'\n\n      - name: \"security-scanner\"\n        run: python scripts\u002Fsecurity_scanner.py . --severity high\n\n      - name: \"vulnerability-assessment\"\n        run: python scripts\u002Fvulnerability_assessor.py . --severity critical\n\n      - name: \"compliance-check\"\n        run: python scripts\u002Fcompliance_checker.py . --framework soc2\n```\n\nEach step fails the pipeline on its respective exit code — no deployment proceeds past a critical finding.\n\n### Workflow 3: CVE Triage\n\nRespond to a new CVE affecting your application.\n\n```\n1. ASSESS (0-2 hours)\n   - Identify affected systems using vulnerability_assessor.py\n   - Check if CVE is being actively exploited\n   - Determine CVSS environmental score for your context\n   - STOP if CVSS 9.0+ on internet-facing system — escalate immediately\n\n2. PRIORITIZE\n   - Critical (CVSS 9.0+, internet-facing): 24 hours\n   - High (CVSS 7.0-8.9): 7 days\n   - Medium (CVSS 4.0-6.9): 30 days\n   - Low (CVSS \u003C 4.0): 90 days\n\n3. REMEDIATE\n   - Update affected dependency to fixed version\n   - Run security_scanner.py to verify fix (must return exit code 0)\n   - STOP if scanner still flags the CVE — do not deploy\n   - Test for regressions\n   - Deploy with enhanced monitoring\n\n4. VERIFY\n   - Re-run vulnerability_assessor.py\n   - Confirm CVE no longer reported\n   - Document remediation actions\n```\n\n### Workflow 4: Incident Response\n\nSecurity incident handling procedure.\n\n```\nPHASE 1: DETECT & IDENTIFY (0-15 min)\n- Alert received and acknowledged\n- Initial severity assessment (SEV-1 to SEV-4)\n- Incident commander assigned\n- Communication channel established\n\nPHASE 2: CONTAIN (15-60 min)\n- Affected systems identified\n- Network isolation if needed\n- Credentials rotated if compromised\n- Preserve evidence (logs, memory dumps)\n\nPHASE 3: ERADICATE (1-4 hours)\n- Root cause identified\n- Malware\u002Fbackdoors removed\n- Vulnerabilities patched (run security_scanner.py; must return exit code 0)\n- Systems hardened\n\nPHASE 4: RECOVER (4-24 hours)\n- Systems restored from clean backup\n- Services brought back online\n- Enhanced monitoring enabled\n- User access restored\n\nPHASE 5: POST-INCIDENT (24-72 hours)\n- Incident timeline documented\n- Root cause analysis complete\n- Lessons learned documented\n- Preventive measures implemented\n- Stakeholder report delivered\n```\n\n---\n\n## Tool Reference\n\n### security_scanner.py\n\n| Option | Description |\n|--------|-------------|\n| `target` | Directory or file to scan |\n| `--severity, -s` | Minimum severity: critical, high, medium, low |\n| `--verbose, -v` | Show files as they're scanned |\n| `--json` | Output results as JSON |\n| `--output, -o` | Write results to file |\n\n**Exit Codes:** `0` = no critical\u002Fhigh findings · `1` = high severity findings · `2` = critical severity findings\n\n### vulnerability_assessor.py\n\n| Option | Description |\n|--------|-------------|\n| `target` | Directory containing dependency files |\n| `--severity, -s` | Minimum severity: critical, high, medium, low |\n| `--verbose, -v` | Show files as they're scanned |\n| `--json` | Output results as JSON |\n| `--output, -o` | Write results to file |\n\n**Exit Codes:** `0` = no critical\u002Fhigh vulnerabilities · `1` = high severity vulnerabilities · `2` = critical severity vulnerabilities\n\n### compliance_checker.py\n\n| Option | Description |\n|--------|-------------|\n| `target` | Directory to check |\n| `--framework, -f` | Framework: soc2, pci-dss, hipaa, gdpr, all |\n| `--verbose, -v` | Show checks as they run |\n| `--json` | Output results as JSON |\n| `--output, -o` | Write results to file |\n\n**Exit Codes:** `0` = compliant (90%+ score) · `1` = non-compliant (50-69% score) · `2` = critical gaps (\u003C50% score)\n\n---\n\n## Security Standards\n\nSee `references\u002Fsecurity_standards.md` for OWASP Top 10 full guidance, secure coding standards, authentication requirements, and API security controls.\n\n### Secure Coding Checklist\n\n```markdown\n## Input Validation\n- [ ] Validate all input on server side\n- [ ] Use allowlists over denylists\n- [ ] Sanitize for specific context (HTML, SQL, shell)\n\n## Output Encoding\n- [ ] HTML encode for browser output\n- [ ] URL encode for URLs\n- [ ] JavaScript encode for script contexts\n\n## Authentication\n- [ ] Use bcrypt\u002Fargon2 for passwords\n- [ ] Implement MFA for sensitive operations\n- [ ] Enforce strong password policy\n\n## Session Management\n- [ ] Generate secure random session IDs\n- [ ] Set HttpOnly, Secure, SameSite flags\n- [ ] Implement session timeout (15 min idle)\n\n## Error Handling\n- [ ] Log errors with context (no secrets)\n- [ ] Return generic messages to users\n- [ ] Never expose stack traces in production\n\n## Secrets Management\n- [ ] Use environment variables or secrets manager\n- [ ] Never commit secrets to version control\n- [ ] Rotate credentials regularly\n```\n\n---\n\n## Compliance Frameworks\n\nSee `references\u002Fcompliance_requirements.md` for full control mappings. Run `compliance_checker.py` to verify the controls below:\n\n### SOC 2 Type II\n- **CC6** Logical Access: authentication, authorization, MFA\n- **CC7** System Operations: monitoring, logging, incident response\n- **CC8** Change Management: CI\u002FCD, code review, deployment controls\n\n### PCI-DSS v4.0\n- **Req 3\u002F4**: Encryption at rest and in transit (TLS 1.2+)\n- **Req 6**: Secure development (input validation, secure coding)\n- **Req 8**: Strong authentication (MFA, password policy)\n- **Req 10\u002F11**: Audit logging, SAST\u002FDAST\u002Fpenetration testing\n\n### HIPAA Security Rule\n- Unique user IDs and audit trails for PHI access (164.312(a)(1), 164.312(b))\n- MFA for person\u002Fentity authentication (164.312(d))\n- Transmission encryption via TLS (164.312(e)(1))\n\n### GDPR\n- **Art 25\u002F32**: Privacy by design, encryption, pseudonymization\n- **Art 33**: Breach notification within 72 hours\n- **Art 17\u002F20**: Right to erasure and data portability\n\n---\n\n## Best Practices\n\n### Secrets Management\n\n```python\n# BAD: Hardcoded secret\nAPI_KEY = \"sk-1234567890abcdef\"\n\n# GOOD: Environment variable\nimport os\nAPI_KEY = os.environ.get(\"API_KEY\")\n\n# BETTER: Secrets manager\nfrom your_vault_client import get_secret\nAPI_KEY = get_secret(\"api\u002Fkey\")\n```\n\n### SQL Injection Prevention\n\n```python\n# BAD: String concatenation\nquery = f\"SELECT * FROM users WHERE id = {user_id}\"\n\n# GOOD: Parameterized query\ncursor.execute(\"SELECT * FROM users WHERE id = %s\", (user_id,))\n```\n\n### XSS Prevention\n\n```javascript\n\u002F\u002F BAD: Direct innerHTML assignment is vulnerable\n\u002F\u002F GOOD: Use textContent (auto-escaped)\nelement.textContent = userInput;\n\n\u002F\u002F GOOD: Use sanitization library for HTML\nimport DOMPurify from 'dompurify';\nconst safeHTML = DOMPurify.sanitize(userInput);\n```\n\n### Authentication\n\n```javascript\n\u002F\u002F Password hashing\nconst bcrypt = require('bcrypt');\nconst SALT_ROUNDS = 12;\n\n\u002F\u002F Hash password\nconst hash = await bcrypt.hash(password, SALT_ROUNDS);\n\n\u002F\u002F Verify password\nconst match = await bcrypt.compare(password, hash);\n```\n\n### Security Headers\n\n```javascript\n\u002F\u002F Express.js security headers\nconst helmet = require('helmet');\napp.use(helmet());\n\n\u002F\u002F Or manually set headers:\napp.use((req, res, next) => {\n  res.setHeader('X-Content-Type-Options', 'nosniff');\n  res.setHeader('X-Frame-Options', 'DENY');\n  res.setHeader('X-XSS-Protection', '1; mode=block');\n  res.setHeader('Strict-Transport-Security', 'max-age=31536000; includeSubDomains');\n  res.setHeader('Content-Security-Policy', \"default-src 'self'\");\n  next();\n});\n```\n\n---\n\n## OWASP Top 10 Quick-Check\n\nRapid 15-minute assessment — run through each category and note pass\u002Ffail. For deep-dive testing, hand off to the **security-pen-testing** skill.\n\n| # | Category | One-Line Check |\n|---|----------|----------------|\n| A01 | Broken Access Control | Verify role checks on every endpoint; test horizontal privilege escalation |\n| A02 | Cryptographic Failures | Confirm TLS 1.2+ everywhere; no secrets in logs or source |\n| A03 | Injection | Run parameterized query audit; check ORM raw-query usage |\n| A04 | Insecure Design | Review threat model exists for critical flows |\n| A05 | Security Misconfiguration | Check default credentials removed; error pages generic |\n| A06 | Vulnerable Components | Run `vulnerability_assessor.py`; zero critical\u002Fhigh CVEs |\n| A07 | Auth Failures | Verify MFA on admin; brute-force protection active |\n| A08 | Software & Data Integrity | Confirm CI\u002FCD pipeline signs artifacts; no unsigned deps |\n| A09 | Logging & Monitoring | Validate audit logs capture auth events; alerts configured |\n| A10 | SSRF | Test internal URL filters; block metadata endpoints (169.254.169.254) |\n\n> **Deep dive needed?** Hand off to `security-pen-testing` for full OWASP Testing Guide coverage.\n\n---\n\n## Secret Scanning Tools\n\nChoose the right scanner for each stage of your workflow:\n\n| Tool | Best For | Language | Pre-commit | CI\u002FCD | Custom Rules |\n|------|----------|----------|:----------:|:-----:|:------------:|\n| **gitleaks** | CI pipelines, full-repo scans | Go | Yes | Yes | TOML regexes |\n| **detect-secrets** | Pre-commit hooks, incremental | Python | Yes | Partial | Plugin-based |\n| **truffleHog** | Deep history scans, entropy | Go | No | Yes | Regex + entropy |\n\n**Recommended setup:** Use `detect-secrets` as a pre-commit hook (catches secrets before they enter history) and `gitleaks` in CI (catches anything that slips through).\n\n```bash\n# detect-secrets pre-commit hook (.pre-commit-config.yaml)\n- repo: https:\u002F\u002Fgithub.com\u002FYelp\u002Fdetect-secrets\n  rev: v1.4.0\n  hooks:\n    - id: detect-secrets\n      args: ['--baseline', '.secrets.baseline']\n\n# gitleaks in GitHub Actions\n- name: gitleaks\n  uses: gitleaks\u002Fgitleaks-action@v2\n  env:\n    GITLEAKS_LICENSE: ${{ secrets.GITLEAKS_LICENSE }}\n```\n\n---\n\n## Supply Chain Security\n\nProtect against dependency and artifact tampering with SBOM generation, artifact signing, and SLSA compliance.\n\n**SBOM Generation:**\n- **syft** — generates SBOMs from container images or source dirs (SPDX, CycloneDX formats)\n- **cyclonedx-cli** — CycloneDX-native tooling; merge multiple SBOMs for mono-repos\n\n```bash\n# Generate SBOM from container image\nsyft packages ghcr.io\u002Forg\u002Fapp:latest -o cyclonedx-json > sbom.json\n```\n\n**Artifact Signing (Sigstore\u002Fcosign):**\n```bash\n# Sign a container image (keyless via OIDC)\ncosign sign ghcr.io\u002Forg\u002Fapp:latest\n# Verify signature\ncosign verify ghcr.io\u002Forg\u002Fapp:latest --certificate-identity=ci@org.com --certificate-oidc-issuer=https:\u002F\u002Ftoken.actions.githubusercontent.com\n```\n\n**SLSA Levels Overview:**\n| Level | Requirement | What It Proves |\n|-------|-------------|----------------|\n| 1 | Build process documented | Provenance exists |\n| 2 | Hosted build service, signed provenance | Tamper-resistant provenance |\n| 3 | Hardened build platform, non-falsifiable provenance | Tamper-proof build |\n| 4 | Two-party review, hermetic builds | Maximum supply-chain assurance |\n\n> **Cross-references:** `security-pen-testing` (vulnerability exploitation testing), `dependency-auditor` (license and CVE audit for dependencies).\n\n---\n\n## Reference Documentation\n\n| Document | Description |\n|----------|-------------|\n| `references\u002Fsecurity_standards.md` | OWASP Top 10, secure coding, authentication, API security |\n| `references\u002Fvulnerability_management_guide.md` | CVE triage, CVSS scoring, remediation workflows |\n| `references\u002Fcompliance_requirements.md` | SOC 2, PCI-DSS, HIPAA, GDPR full control mappings |\n",{"name":5,"description":7},"claude\u002Fregistry-repo-7lRiv","44e1a5b2d387b250bcd0794f7eb5e1228223d1e2","engineering-team\u002Fskills\u002Fsenior-secops","https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills","https:\u002F\u002Fgithub.com\u002FMabbit143","I’m edgy and fun, probably too serious, but I love an adventure.","2026-09-22 07:56:32",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add Mabbit143\u002FClaude-SKills --skill senior-secops",{"tool":37,"command":38},"bunx","bunx skills add Mabbit143\u002FClaude-SKills --skill senior-secops",{"tool":40,"command":41},"pnpm","pnpm dlx skills add Mabbit143\u002FClaude-SKills --skill senior-secops","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fengineering-team\u002Fskills\u002Fsenior-secops\u002FSKILL.md",true,[45,51,55,59,65,69],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"references\u002Fcompliance_requirements.md","REFERENCE","参考文档",23807,"https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fengineering-team\u002Fskills\u002Fsenior-secops\u002Freferences\u002Fcompliance_requirements.md",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"references\u002Fsecurity_standards.md",19246,"https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fengineering-team\u002Fskills\u002Fsenior-secops\u002Freferences\u002Fsecurity_standards.md",{"path":56,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002Fvulnerability_management_guide.md",14297,"https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fengineering-team\u002Fskills\u002Fsenior-secops\u002Freferences\u002Fvulnerability_management_guide.md",{"path":60,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":63,"sourceHtmlUrl":64},"scripts\u002Fcompliance_checker.py","SCRIPT","脚本",38622,"https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fengineering-team\u002Fskills\u002Fsenior-secops\u002Fscripts\u002Fcompliance_checker.py",{"path":66,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":67,"sourceHtmlUrl":68},"scripts\u002Fsecurity_scanner.py",16570,"https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fengineering-team\u002Fskills\u002Fsenior-secops\u002Fscripts\u002Fsecurity_scanner.py",{"path":70,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":71,"sourceHtmlUrl":72},"scripts\u002Fvulnerability_assessor.py",20415,"https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fengineering-team\u002Fskills\u002Fsenior-secops\u002Fscripts\u002Fvulnerability_assessor.py",[74,81,88,95,102,109],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7D99ZA4F916M5CM3K2EQFE8","syllabus","Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Triggers whenever a user uploads a syllabus, course outline, or curriculum document and wants supplementary readings. Also triggers on: 'syllabus reading list', 'find papers for my course', 'create a reading list from this syllabus', 'recent research for my class', 'supplementary readings', 'find journal articles for these topics', 'what recent papers cover this material', 'any new research on these course topics', 'update my syllabus with recent papers'. Even casual mentions when a syllabus is attached should trigger this skill.","https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7D99ND4B38EG1BYQX722F5D","research","Default entry point for any research request — a hybrid router that classifies the question deterministically and either delegates to a specialist research skill (pulse for trends\u002Fsentiment, grants for NIH funding, litreview for academic literature, syllabus for course reading, patent for prior-art + IP landscape, dossier for entity research) or runs its own plan-decompose-multi-source-search-synthesize-cite fallback workflow when no specialist matches. Always surfaces the routing decision so users can override. Triggers — \"research [topic]\", \"look into [topic]\", \"what do we know about [topic]\", \"investigate [topic]\", \"find me information on [topic]\", \"do some research on [topic]\", \"I need to understand [topic]\", or any research request that doesn't obviously match a more-specific specialist skill. Output is a markdown briefing (default) or .docx document (on request) with full citations and an audit log.","https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fresearch\u002Fresearch\u002Fskills\u002Fresearch\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M7D999VS936SV9TX940A98AQ","pulse","Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X\u002FTwitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend\u002Fsentiment\u002Fproblems\u002Fopportunities\u002Fcomparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Triggers: 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]', or any variation requesting multi-source recency intelligence on a topic. Also use for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.","https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":19},"01M7D98XBECS6368GEJNG8C1Z1","patent","Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search \u002F freedom-to-operate \u002F competitive landscape \u002F acquisition diligence \u002F litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Triggers: 'prior art search for [invention]', 'patent search on [topic]', 'freedom to operate analysis', 'FTO for [product]', 'patent landscape for [field]', 'is [invention] novel', 'patents on [topic]', 'competitive patent analysis', 'prior art for litigation', 'patent diligence on [company]'. Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.","https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\u002FSKILL.md",[],[],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":19},"01M7D98N2R7CA7RM00PNP4VV6C","notebooklm","Browser automation skill for controlling Google's NotebookLM. Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio Overview, infographics, slide decks, study guides, briefing docs, mind maps, timelines, FAQs), and creating new notebooks. Triggers on any phrase involving NotebookLM — 'open NotebookLM', 'check my [name] notebook', 'pull info from NotebookLM', 'ask my notebook about X', 'add [source] to NotebookLM', 'create an infographic in NotebookLM', 'use NotebookLM Studio', 'generate a slide deck from my notebook', or any variation where the goal involves NotebookLM. Requires browser automation environment — fails gracefully when unavailable.","https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fresearch\u002Fnotebooklm\u002Fskills\u002Fnotebooklm\u002FSKILL.md",[],[],{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":19},"01M7D98B1SCTS4RAWZFCF9QJ5M","litreview","Academic literature orientation skill that searches papers via Consensus, builds a strategic search plan using PICO (default) or SPIDER \u002F Decomposition \u002F hybrid as fallbacks, and synthesizes findings into a professionally formatted Word document (.docx) research guide. Grill-me intake (research question specificity + framework hint + tentative depth) before the recon search; a second forcing checkpoint after Phase 2 confirms framework + sub-areas + depth before searches consume budget. Configurable depth (5\u002F10\u002F20 queries) controls coverage vs. speed. Output is a 'launching pad' — not a finished review, but an orientation guide that lets a researcher dive in confidently. Triggers: 'litreview on [topic]', 'literature review on [topic]', 'I'm starting a literature review on X', 'I'm writing a paper on X', 'help me research X', 'I'm doing research on X', 'can you help me research X'. Do NOT trigger for single one-off paper searches where the user just wants a quick list — that's a plain Consensus search.","https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fresearch\u002Flitreview\u002Fskills\u002Flitreview\u002FSKILL.md",[],[]]