[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DAZVF76PEN8HVR8XENP7AT":3,"skill-same:01M7DAZVF76PEN8HVR8XENP7AT":101},{"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":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":6,"ownerHtmlUrl":49,"ownerBlogUrl":50,"ownerDescription":51,"updatedAt":52,"install":53,"resources":66},"01M7DAZVF76PEN8HVR8XENP7AT","integrating-dast-with-owasp-zap-in-pipeline",null,"Integrates OWASP ZAP (Zed Attack Proxy) into GitHub Actions and GitLab CI pipelines, covering baseline, full, and API scan configuration against running applications, ZAP finding interpretation, scan policy tuning, and DAST quality gates. Use when testing running web apps or REST\u002FGraphQL APIs for XSS, SQLi, CSRF, and auth\u002Fauthz flaws, or when SAST alone is insufficient and runtime DAST is required for compliance or release gating.","SaiVatsal\u002FSkills-I-Use","SaiVatsal","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F242597752?v=4","01M7D5YM1T4VXW9203M0GFAHZ1","SaiVatsalPolimera","01M7D5YM2D61ST39XVR2V7B7ZJ",3,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002FAnthropic-Cybersecurity-Skills-main\u002Fskills\u002Fintegrating-dast-with-owasp-zap-in-pipeline\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002FAnthropic-Cybersecurity-Skills-main\u002Fskills\u002Fintegrating-dast-with-owasp-zap-in-pipeline\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: integrating-dast-with-owasp-zap-in-pipeline\ndescription: Integrates OWASP ZAP (Zed Attack Proxy) into GitHub Actions and GitLab CI pipelines, covering baseline, full, and API scan configuration against running applications, ZAP finding interpretation, scan policy tuning, and DAST quality gates. Use when testing running web apps or REST\u002FGraphQL APIs for XSS, SQLi, CSRF, and auth\u002Fauthz flaws, or when SAST alone is insufficient and runtime DAST is required for compliance or release gating.\ndomain: cybersecurity\nsubdomain: devsecops\ntags:\n- devsecops\n- cicd\n- dast\n- owasp-zap\n- dynamic-testing\n- secure-sdlc\nversion: 1.0.0\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- PR.PS-01\n- GV.SC-07\n- ID.IM-04\n- PR.PS-04\nmitre_attack:\n- T1195\n- T1554\n- T1059.004\n---\n\n# Integrating DAST with OWASP ZAP in Pipeline\n\n## When to Use\n\n- When testing running web applications for vulnerabilities like XSS, SQLi, CSRF, and misconfigurations\n- When SAST alone is insufficient and runtime behavior testing is required\n- When compliance mandates dynamic security testing of web applications before production\n- When testing APIs (REST\u002FGraphQL) for authentication, authorization, and injection flaws\n- When establishing continuous DAST scanning in staging environments before production deployment\n\n**Do not use** for scanning source code (use SAST), for scanning dependencies (use SCA), or for infrastructure configuration scanning (use IaC scanning tools).\n\n## Prerequisites\n\n- OWASP ZAP Docker image or installed locally (zaproxy\u002Fzap-stable or zaproxy\u002Faction-*)\n- Running target application accessible from the CI\u002FCD runner (staging URL or Docker service)\n- ZAP scan rules configuration (optional, for tuning)\n- OpenAPI\u002FSwagger specification for API scanning (optional)\n\n## Workflow\n\n### Step 1: Configure ZAP Baseline Scan in GitHub Actions\n\n```yaml\n# .github\u002Fworkflows\u002Fdast-scan.yml\nname: DAST Security Scan\n\non:\n  deployment_status:\n  workflow_dispatch:\n    inputs:\n      target_url:\n        description: 'Target URL to scan'\n        required: true\n\njobs:\n  zap-baseline:\n    name: ZAP Baseline Scan\n    runs-on: ubuntu-latest\n    services:\n      webapp:\n        image: ${{ github.repository }}:${{ github.sha }}\n        ports:\n          - 8080:8080\n        options: --health-cmd=\"curl -f http:\u002F\u002Flocalhost:8080\u002Fhealth\" --health-interval=10s --health-timeout=5s --health-retries=5\n\n    steps:\n      - uses: actions\u002Fcheckout@v4\n\n      - name: ZAP Baseline Scan\n        uses: zaproxy\u002Faction-baseline@v0.12.0\n        with:\n          target: 'http:\u002F\u002Fwebapp:8080'\n          rules_file_name: '.zap\u002Frules.tsv'\n          cmd_options: '-a -j'\n          allow_issue_writing: false\n\n      - name: Upload ZAP Report\n        if: always()\n        uses: actions\u002Fupload-artifact@v4\n        with:\n          name: zap-baseline-report\n          path: report_html.html\n```\n\n### Step 2: Configure ZAP Full Scan for Comprehensive Testing\n\n```yaml\n  zap-full-scan:\n    name: ZAP Full Scan\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions\u002Fcheckout@v4\n\n      - name: ZAP Full Scan\n        uses: zaproxy\u002Faction-full-scan@v0.12.0\n        with:\n          target: ${{ github.event.inputs.target_url || 'https:\u002F\u002Fstaging.example.com' }}\n          rules_file_name: '.zap\u002Frules.tsv'\n          cmd_options: '-a -j -T 60'\n\n      - name: Upload Reports\n        if: always()\n        uses: actions\u002Fupload-artifact@v4\n        with:\n          name: zap-full-report\n          path: |\n            report_html.html\n            report_json.json\n```\n\n### Step 3: Configure API Scan with OpenAPI Specification\n\n```yaml\n  zap-api-scan:\n    name: ZAP API Scan\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions\u002Fcheckout@v4\n\n      - name: ZAP API Scan\n        uses: zaproxy\u002Faction-api-scan@v0.12.0\n        with:\n          target: 'https:\u002F\u002Fstaging.example.com\u002Fapi\u002Fopenapi.json'\n          format: openapi\n          rules_file_name: '.zap\u002Fapi-rules.tsv'\n          cmd_options: '-a -j'\n```\n\n### Step 4: Configure ZAP Scan Rules\n\n```tsv\n# .zap\u002Frules.tsv\n# Rule ID\tAction (IGNORE\u002FWARN\u002FFAIL)\tDescription\n10003\tIGNORE\t# Vulnerable JS Library (handled by SCA)\n10015\tWARN\t# Incomplete or No Cache-control Header\n10021\tFAIL\t# X-Content-Type-Options Missing\n10035\tFAIL\t# Strict-Transport-Security Missing\n10038\tFAIL\t# Content Security Policy Missing\n10098\tIGNORE\t# Cross-Domain Misconfiguration (CDN)\n40012\tFAIL\t# Cross Site Scripting (Reflected)\n40014\tFAIL\t# Cross Site Scripting (Persistent)\n40018\tFAIL\t# SQL Injection\n40019\tFAIL\t# SQL Injection (MySQL)\n40032\tFAIL\t# .htaccess Information Leak\n90033\tFAIL\t# Loosely Scoped Cookie\n```\n\n### Step 5: Run ZAP with Docker Compose for Local Testing\n\n```yaml\n# docker-compose.zap.yml\nversion: '3.8'\nservices:\n  webapp:\n    build: .\n    ports:\n      - \"8080:8080\"\n    healthcheck:\n      test: [\"CMD\", \"curl\", \"-f\", \"http:\u002F\u002Flocalhost:8080\u002Fhealth\"]\n      interval: 10s\n      retries: 5\n\n  zap:\n    image: zaproxy\u002Fzap-stable:latest\n    depends_on:\n      webapp:\n        condition: service_healthy\n    command: >\n      zap-baseline.py\n        -t http:\u002F\u002Fwebapp:8080\n        -r \u002Fzap\u002Fwrk\u002Freport.html\n        -J \u002Fzap\u002Fwrk\u002Freport.json\n        -c \u002Fzap\u002Fwrk\u002Frules.tsv\n        -I\n    volumes:\n      - .\u002Fzap-reports:\u002Fzap\u002Fwrk\n      - .\u002F.zap\u002Frules.tsv:\u002Fzap\u002Fwrk\u002Frules.tsv\n```\n\n## Key Concepts\n\n| Term | Definition |\n|------|------------|\n| DAST | Dynamic Application Security Testing — tests running applications by sending requests and analyzing responses |\n| Baseline Scan | Quick passive scan that spiders the application without active attacks, suitable for CI\u002FCD |\n| Full Scan | Active scan including attack payloads for XSS, SQLi, and other injection vulnerabilities |\n| API Scan | Targeted scan using OpenAPI\u002FSwagger specs to test all documented API endpoints |\n| Spider | ZAP's crawler that discovers application pages and endpoints by following links |\n| Active Scan | Phase where ZAP sends attack payloads to discovered endpoints to find exploitable vulnerabilities |\n| Passive Scan | Analysis of HTTP responses for security headers, cookies, and information disclosure without sending attacks |\n| Scan Policy | Configuration defining which attack types to enable and their intensity levels |\n\n## Tools & Systems\n\n- **OWASP ZAP**: Open-source web application security scanner for DAST testing\n- **zaproxy\u002Faction-baseline**: GitHub Action for ZAP passive baseline scanning\n- **zaproxy\u002Faction-full-scan**: GitHub Action for ZAP active full scanning\n- **zaproxy\u002Faction-api-scan**: GitHub Action for API-focused scanning with OpenAPI support\n- **Nuclei**: Alternative vulnerability scanner with template-based detection for CI\u002FCD integration\n\n## Common Scenarios\n\n### Scenario: Integrating DAST into a Staging Deployment Pipeline\n\n**Context**: A team deploys to staging before production and needs automated DAST scanning between stages to catch runtime vulnerabilities.\n\n**Approach**:\n1. Add a DAST job in the pipeline that triggers after successful staging deployment\n2. Run ZAP baseline scan first for quick passive feedback (2-5 minutes)\n3. Follow with a targeted API scan using the application's OpenAPI specification\n4. Configure rules.tsv to FAIL on critical findings (XSS, SQLi) and WARN on headers\u002Fcookies\n5. Upload ZAP reports as pipeline artifacts for review\n6. Block production deployment if any FAIL-level findings are detected\n7. Schedule weekly full scans against staging for deeper coverage\n\n**Pitfalls**: ZAP full scans can take 30+ minutes and may overwhelm staging servers with attack traffic. Use baseline scans in CI and full scans on schedule. Running DAST against production without coordination can trigger WAF blocks and incident alerts.\n\n## Output Format\n\n```\nZAP DAST Scan Report\n======================\nTarget: https:\u002F\u002Fstaging.example.com\nScan Type: Baseline + API\nDate: 2026-02-23\nDuration: 4m 32s\n\nFINDINGS:\n  FAIL: 3\n  WARN: 7\n  INFO: 12\n  PASS: 45\n\nFAILING ALERTS:\n  [HIGH] 40012 - Cross Site Scripting (Reflected)\n    URL: https:\u002F\u002Fstaging.example.com\u002Fsearch?q=\u003Cscript>\n    Method: GET\n    Evidence: \u003Cscript>alert(1)\u003C\u002Fscript>\n\n  [MEDIUM] 10021 - X-Content-Type-Options Missing\n    URL: https:\u002F\u002Fstaging.example.com\u002Fapi\u002Fv1\u002F*\n    Evidence: Response header missing\n\n  [MEDIUM] 10035 - Strict-Transport-Security Missing\n    URL: https:\u002F\u002Fstaging.example.com\u002F\n    Evidence: HSTS header not present\n\nQUALITY GATE: FAILED (1 HIGH, 2 MEDIUM findings)\n```\n","# Integrating DAST with OWASP ZAP in Pipeline\n\n## When to Use\n\n- When testing running web applications for vulnerabilities like XSS, SQLi, CSRF, and misconfigurations\n- When SAST alone is insufficient and runtime behavior testing is required\n- When compliance mandates dynamic security testing of web applications before production\n- When testing APIs (REST\u002FGraphQL) for authentication, authorization, and injection flaws\n- When establishing continuous DAST scanning in staging environments before production deployment\n\n**Do not use** for scanning source code (use SAST), for scanning dependencies (use SCA), or for infrastructure configuration scanning (use IaC scanning tools).\n\n## Prerequisites\n\n- OWASP ZAP Docker image or installed locally (zaproxy\u002Fzap-stable or zaproxy\u002Faction-*)\n- Running target application accessible from the CI\u002FCD runner (staging URL or Docker service)\n- ZAP scan rules configuration (optional, for tuning)\n- OpenAPI\u002FSwagger specification for API scanning (optional)\n\n## Workflow\n\n### Step 1: Configure ZAP Baseline Scan in GitHub Actions\n\n```yaml\n# .github\u002Fworkflows\u002Fdast-scan.yml\nname: DAST Security Scan\n\non:\n  deployment_status:\n  workflow_dispatch:\n    inputs:\n      target_url:\n        description: 'Target URL to scan'\n        required: true\n\njobs:\n  zap-baseline:\n    name: ZAP Baseline Scan\n    runs-on: ubuntu-latest\n    services:\n      webapp:\n        image: ${{ github.repository }}:${{ github.sha }}\n        ports:\n          - 8080:8080\n        options: --health-cmd=\"curl -f http:\u002F\u002Flocalhost:8080\u002Fhealth\" --health-interval=10s --health-timeout=5s --health-retries=5\n\n    steps:\n      - uses: actions\u002Fcheckout@v4\n\n      - name: ZAP Baseline Scan\n        uses: zaproxy\u002Faction-baseline@v0.12.0\n        with:\n          target: 'http:\u002F\u002Fwebapp:8080'\n          rules_file_name: '.zap\u002Frules.tsv'\n          cmd_options: '-a -j'\n          allow_issue_writing: false\n\n      - name: Upload ZAP Report\n        if: always()\n        uses: actions\u002Fupload-artifact@v4\n        with:\n          name: zap-baseline-report\n          path: report_html.html\n```\n\n### Step 2: Configure ZAP Full Scan for Comprehensive Testing\n\n```yaml\n  zap-full-scan:\n    name: ZAP Full Scan\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions\u002Fcheckout@v4\n\n      - name: ZAP Full Scan\n        uses: zaproxy\u002Faction-full-scan@v0.12.0\n        with:\n          target: ${{ github.event.inputs.target_url || 'https:\u002F\u002Fstaging.example.com' }}\n          rules_file_name: '.zap\u002Frules.tsv'\n          cmd_options: '-a -j -T 60'\n\n      - name: Upload Reports\n        if: always()\n        uses: actions\u002Fupload-artifact@v4\n        with:\n          name: zap-full-report\n          path: |\n            report_html.html\n            report_json.json\n```\n\n### Step 3: Configure API Scan with OpenAPI Specification\n\n```yaml\n  zap-api-scan:\n    name: ZAP API Scan\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions\u002Fcheckout@v4\n\n      - name: ZAP API Scan\n        uses: zaproxy\u002Faction-api-scan@v0.12.0\n        with:\n          target: 'https:\u002F\u002Fstaging.example.com\u002Fapi\u002Fopenapi.json'\n          format: openapi\n          rules_file_name: '.zap\u002Fapi-rules.tsv'\n          cmd_options: '-a -j'\n```\n\n### Step 4: Configure ZAP Scan Rules\n\n```tsv\n# .zap\u002Frules.tsv\n# Rule ID\tAction (IGNORE\u002FWARN\u002FFAIL)\tDescription\n10003\tIGNORE\t# Vulnerable JS Library (handled by SCA)\n10015\tWARN\t# Incomplete or No Cache-control Header\n10021\tFAIL\t# X-Content-Type-Options Missing\n10035\tFAIL\t# Strict-Transport-Security Missing\n10038\tFAIL\t# Content Security Policy Missing\n10098\tIGNORE\t# Cross-Domain Misconfiguration (CDN)\n40012\tFAIL\t# Cross Site Scripting (Reflected)\n40014\tFAIL\t# Cross Site Scripting (Persistent)\n40018\tFAIL\t# SQL Injection\n40019\tFAIL\t# SQL Injection (MySQL)\n40032\tFAIL\t# .htaccess Information Leak\n90033\tFAIL\t# Loosely Scoped Cookie\n```\n\n### Step 5: Run ZAP with Docker Compose for Local Testing\n\n```yaml\n# docker-compose.zap.yml\nversion: '3.8'\nservices:\n  webapp:\n    build: .\n    ports:\n      - \"8080:8080\"\n    healthcheck:\n      test: [\"CMD\", \"curl\", \"-f\", \"http:\u002F\u002Flocalhost:8080\u002Fhealth\"]\n      interval: 10s\n      retries: 5\n\n  zap:\n    image: zaproxy\u002Fzap-stable:latest\n    depends_on:\n      webapp:\n        condition: service_healthy\n    command: >\n      zap-baseline.py\n        -t http:\u002F\u002Fwebapp:8080\n        -r \u002Fzap\u002Fwrk\u002Freport.html\n        -J \u002Fzap\u002Fwrk\u002Freport.json\n        -c \u002Fzap\u002Fwrk\u002Frules.tsv\n        -I\n    volumes:\n      - .\u002Fzap-reports:\u002Fzap\u002Fwrk\n      - .\u002F.zap\u002Frules.tsv:\u002Fzap\u002Fwrk\u002Frules.tsv\n```\n\n## Key Concepts\n\n| Term | Definition |\n|------|------------|\n| DAST | Dynamic Application Security Testing — tests running applications by sending requests and analyzing responses |\n| Baseline Scan | Quick passive scan that spiders the application without active attacks, suitable for CI\u002FCD |\n| Full Scan | Active scan including attack payloads for XSS, SQLi, and other injection vulnerabilities |\n| API Scan | Targeted scan using OpenAPI\u002FSwagger specs to test all documented API endpoints |\n| Spider | ZAP's crawler that discovers application pages and endpoints by following links |\n| Active Scan | Phase where ZAP sends attack payloads to discovered endpoints to find exploitable vulnerabilities |\n| Passive Scan | Analysis of HTTP responses for security headers, cookies, and information disclosure without sending attacks |\n| Scan Policy | Configuration defining which attack types to enable and their intensity levels |\n\n## Tools & Systems\n\n- **OWASP ZAP**: Open-source web application security scanner for DAST testing\n- **zaproxy\u002Faction-baseline**: GitHub Action for ZAP passive baseline scanning\n- **zaproxy\u002Faction-full-scan**: GitHub Action for ZAP active full scanning\n- **zaproxy\u002Faction-api-scan**: GitHub Action for API-focused scanning with OpenAPI support\n- **Nuclei**: Alternative vulnerability scanner with template-based detection for CI\u002FCD integration\n\n## Common Scenarios\n\n### Scenario: Integrating DAST into a Staging Deployment Pipeline\n\n**Context**: A team deploys to staging before production and needs automated DAST scanning between stages to catch runtime vulnerabilities.\n\n**Approach**:\n1. Add a DAST job in the pipeline that triggers after successful staging deployment\n2. Run ZAP baseline scan first for quick passive feedback (2-5 minutes)\n3. Follow with a targeted API scan using the application's OpenAPI specification\n4. Configure rules.tsv to FAIL on critical findings (XSS, SQLi) and WARN on headers\u002Fcookies\n5. Upload ZAP reports as pipeline artifacts for review\n6. Block production deployment if any FAIL-level findings are detected\n7. Schedule weekly full scans against staging for deeper coverage\n\n**Pitfalls**: ZAP full scans can take 30+ minutes and may overwhelm staging servers with attack traffic. Use baseline scans in CI and full scans on schedule. Running DAST against production without coordination can trigger WAF blocks and incident alerts.\n\n## Output Format\n\n```\nZAP DAST Scan Report\n======================\nTarget: https:\u002F\u002Fstaging.example.com\nScan Type: Baseline + API\nDate: 2026-02-23\nDuration: 4m 32s\n\nFINDINGS:\n  FAIL: 3\n  WARN: 7\n  INFO: 12\n  PASS: 45\n\nFAILING ALERTS:\n  [HIGH] 40012 - Cross Site Scripting (Reflected)\n    URL: https:\u002F\u002Fstaging.example.com\u002Fsearch?q=\u003Cscript>\n    Method: GET\n    Evidence: \u003Cscript>alert(1)\u003C\u002Fscript>\n\n  [MEDIUM] 10021 - X-Content-Type-Options Missing\n    URL: https:\u002F\u002Fstaging.example.com\u002Fapi\u002Fv1\u002F*\n    Evidence: Response header missing\n\n  [MEDIUM] 10035 - Strict-Transport-Security Missing\n    URL: https:\u002F\u002Fstaging.example.com\u002F\n    Evidence: HSTS header not present\n\nQUALITY GATE: FAILED (1 HIGH, 2 MEDIUM findings)\n```\n",{"name":5,"tags":25,"author":32,"domain":33,"license":15,"version":34,"nist_csf":35,"subdomain":26,"description":7,"mitre_attack":40},[26,27,28,29,30,31],"devsecops","cicd","dast","owasp-zap","dynamic-testing","secure-sdlc","mahipal","cybersecurity","1.0.0",[36,37,38,39],"PR.PS-01","GV.SC-07","ID.IM-04","PR.PS-04",[41,42,43],"T1195","T1554","T1059.004","main","8a3b3de73262a4c4db64523949360f3c599c2fb1","Anthropic-Cybersecurity-Skills-main\u002Fskills\u002Fintegrating-dast-with-owasp-zap-in-pipeline",0,"https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use","https:\u002F\u002Fgithub.com\u002FSaiVatsal","https:\u002F\u002Fsaivatsal.github.io\u002FPortfolio\u002F","The Longer It Takes The Stronger It Becomes ","2026-09-21 22:45:58",{"source":8,"skillName":5,"commands":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add SaiVatsal\u002FSkills-I-Use --skill integrating-dast-with-owasp-zap-in-pipeline",{"tool":59,"command":60},"bunx","bunx skills add SaiVatsal\u002FSkills-I-Use --skill integrating-dast-with-owasp-zap-in-pipeline",{"tool":62,"command":63},"pnpm","pnpm dlx skills add SaiVatsal\u002FSkills-I-Use --skill integrating-dast-with-owasp-zap-in-pipeline","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002FAnthropic-Cybersecurity-Skills-main\u002Fskills\u002Fintegrating-dast-with-owasp-zap-in-pipeline\u002FSKILL.md",true,[67,73,77,83,87,91,97],{"path":68,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":71,"sourceHtmlUrl":72},"assets\u002Ftemplate.md","ASSET","资产文件",2410,"https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002FAnthropic-Cybersecurity-Skills-main\u002Fskills\u002Fintegrating-dast-with-owasp-zap-in-pipeline\u002Fassets\u002Ftemplate.md",{"path":74,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":76,"sourceHtmlUrl":16},"LICENSE","许可证",11255,{"path":78,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":81,"sourceHtmlUrl":82},"references\u002Fapi-reference.md","REFERENCE","参考文档",1496,"https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002FAnthropic-Cybersecurity-Skills-main\u002Fskills\u002Fintegrating-dast-with-owasp-zap-in-pipeline\u002Freferences\u002Fapi-reference.md",{"path":84,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":85,"sourceHtmlUrl":86},"references\u002Fstandards.md",1412,"https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002FAnthropic-Cybersecurity-Skills-main\u002Fskills\u002Fintegrating-dast-with-owasp-zap-in-pipeline\u002Freferences\u002Fstandards.md",{"path":88,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":89,"sourceHtmlUrl":90},"references\u002Fworkflows.md",2443,"https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002FAnthropic-Cybersecurity-Skills-main\u002Fskills\u002Fintegrating-dast-with-owasp-zap-in-pipeline\u002Freferences\u002Fworkflows.md",{"path":92,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":95,"sourceHtmlUrl":96},"scripts\u002Fagent.py","SCRIPT","脚本",6106,"https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002FAnthropic-Cybersecurity-Skills-main\u002Fskills\u002Fintegrating-dast-with-owasp-zap-in-pipeline\u002Fscripts\u002Fagent.py",{"path":98,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":99,"sourceHtmlUrl":100},"scripts\u002Fprocess.py",8058,"https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002FAnthropic-Cybersecurity-Skills-main\u002Fskills\u002Fintegrating-dast-with-owasp-zap-in-pipeline\u002Fscripts\u002Fprocess.py",[102,110,118,127,134,141],{"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":106,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":20},"01M7DJZP6E6KMBQV4CZSDPZEZ8","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002Fwebapp-testing\u002FSKILL.md",[],[],{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":114,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":20},"01M7DJZFTS5TS06K2TV3MDTE67","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002Fweb-artifacts-builder\u002FSKILL.md",[],[],{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":122,"licenseFileUrl":123,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":20},"01M7DJRK4SRQ908F2TJM6EZ7EV","ui-styling","Create beautiful, accessible user interfaces with shadcn\u002Fui components (built on Radix UI + Tailwind), Tailwind CSS utility-first styling, and canvas-based visual designs. Use when building user interfaces, implementing design systems, creating responsive layouts, adding accessible components (dialogs, dropdowns, forms, tables), customizing themes and colors, implementing dark mode, generating visual designs and posters, or establishing consistent styling patterns across applications.","MIT","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002Fui-ux-pro-max-skill-main\u002Fcli\u002Fassets\u002Fskills\u002Fui-styling\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002Fui-ux-pro-max-skill-main\u002Fcli\u002Fassets\u002Fskills\u002Fui-styling\u002FSKILL.md",[],[],{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":122,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":133,"publishedAt":20},"01M7DJR902059VEQP23PVM2WA0","design","Comprehensive design skill: brand identity, design tokens, UI styling, logo generation (55 styles, Gemini AI), corporate identity program (50 deliverables, CIP mockups), HTML presentations (Chart.js), banner design (22 styles, social\u002Fads\u002Fweb\u002Fprint), icon design (15 styles, SVG, Gemini 3.1 Pro), social photos (HTML→screenshot, multi-platform). Actions: design logo, create CIP, generate mockups, build slides, design banner, generate icon, create social photos, social media images, brand identity, design system. Platforms: Facebook, Twitter, LinkedIn, YouTube, Instagram, Pinterest, TikTok, Threads, Google Ads.","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002Fui-ux-pro-max-skill-main\u002Fcli\u002Fassets\u002Fskills\u002Fdesign\u002FSKILL.md",[],[],{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":122,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":140,"publishedAt":20},"01M7DJR56QF5N6XYTCPCFHFMNP","design-system","Token architecture, component specifications, and slide generation. Three-layer tokens (primitive→semantic→component), CSS variables, spacing\u002Ftypography scales, component specs, strategic slide creation. Use for design tokens, systematic design, brand-compliant presentations.","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002Fui-ux-pro-max-skill-main\u002Fcli\u002Fassets\u002Fskills\u002Fdesign-system\u002FSKILL.md",[],[],{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":122,"licenseFileUrl":6,"sourceHtmlUrl":145,"categories":146,"keywords":147,"publishedAt":20},"01M7DJQXB6M0SFF7NX8J5N01AH","banner-design","Design banners for social media, ads, website heroes, creative assets, and print. Multiple art direction options with AI-generated visuals. Actions: design, create, generate banner. Platforms: Facebook, Twitter\u002FX, LinkedIn, YouTube, Instagram, Google Display, website hero, print. Styles: minimalist, gradient, bold typography, photo-based, illustrated, geometric, retro, glassmorphism, 3D, neon, duotone, editorial, collage. Uses ui-ux-pro-max, frontend-design, ai-artist, ai-multimodal skills.","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002Fui-ux-pro-max-skill-main\u002Fcli\u002Fassets\u002Fskills\u002Fbanner-design\u002FSKILL.md",[],[]]