[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M751WB87H0CPAFP9J365NHG7":3,"skill-same:01M751WB87H0CPAFP9J365NHG7":90},{"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":36,"commitSha":37,"skillDirectory":5,"forksCount":14,"repositoryHtmlUrl":38,"repositoryHomepageUrl":6,"ownerHtmlUrl":39,"ownerBlogUrl":40,"ownerDescription":6,"updatedAt":41,"install":42,"resources":55},"01M751WB87H0CPAFP9J365NHG7","integrating-dast-with-owasp-zap-in-pipeline",null,"This skill covers integrating OWASP ZAP (Zed Attack Proxy) for Dynamic Application Security Testing in CI\u002FCD pipelines. It addresses configuring baseline, full, and API scans against running applications, interpreting ZAP findings, tuning scan policies, and establishing DAST quality gates in GitHub Actions and GitLab CI.","SamuelChien\u002Fmega-skills-collection","SamuelChien","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F4652114?v=4","01M74KK34WVHA0P5ZYSJRDDFMG","Samuel Chien","01M74KK35FQN1N9VZ9EPTH3P2S",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fintegrating-dast-with-owasp-zap-in-pipeline\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fintegrating-dast-with-owasp-zap-in-pipeline\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: integrating-dast-with-owasp-zap-in-pipeline\ndescription: >\n  This skill covers integrating OWASP ZAP (Zed Attack Proxy) for Dynamic Application\n  Security Testing in CI\u002FCD pipelines. It addresses configuring baseline, full, and API\n  scans against running applications, interpreting ZAP findings, tuning scan policies,\n  and establishing DAST quality gates in GitHub Actions and GitLab CI.\ndomain: cybersecurity\nsubdomain: devsecops\ntags: [devsecops, cicd, dast, owasp-zap, dynamic-testing, secure-sdlc]\nversion: 1.0.0\nauthor: mahipal\nlicense: Apache-2.0\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,"subdomain":26,"description":35},[26,27,28,29,30,31],"devsecops","cicd","dast","owasp-zap","dynamic-testing","secure-sdlc","mahipal","cybersecurity","1.0.0","This skill covers integrating OWASP ZAP (Zed Attack Proxy) for Dynamic Application Security Testing in CI\u002FCD pipelines. It addresses configuring baseline, full, and API scans against running applications, interpreting ZAP findings, tuning scan policies, and establishing DAST quality gates in GitHub Actions and GitLab CI.\n","main","c2b1fdccc779e99ac814e55fb69ca8d71215dd0f","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection","https:\u002F\u002Fgithub.com\u002FSamuelChien","http:\u002F\u002Fsamuelchien.com\u002F","2026-05-26 08:27:14",{"source":8,"skillName":5,"commands":43,"prompt":53,"zipAvailable":54},[44,47,50],{"tool":45,"command":46},"npx","npx skills add SamuelChien\u002Fmega-skills-collection --skill integrating-dast-with-owasp-zap-in-pipeline",{"tool":48,"command":49},"bunx","bunx skills add SamuelChien\u002Fmega-skills-collection --skill integrating-dast-with-owasp-zap-in-pipeline",{"tool":51,"command":52},"pnpm","pnpm dlx skills add SamuelChien\u002Fmega-skills-collection --skill integrating-dast-with-owasp-zap-in-pipeline","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fintegrating-dast-with-owasp-zap-in-pipeline\u002FSKILL.md",true,[56,62,66,72,76,80,86],{"path":57,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":60,"sourceHtmlUrl":61},"assets\u002Ftemplate.md","ASSET","资产文件",2410,"https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fintegrating-dast-with-owasp-zap-in-pipeline\u002Fassets\u002Ftemplate.md",{"path":63,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":65,"sourceHtmlUrl":16},"LICENSE","许可证",11255,{"path":67,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":70,"sourceHtmlUrl":71},"references\u002Fapi-reference.md","REFERENCE","参考文档",1496,"https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fintegrating-dast-with-owasp-zap-in-pipeline\u002Freferences\u002Fapi-reference.md",{"path":73,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":74,"sourceHtmlUrl":75},"references\u002Fstandards.md",1412,"https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fintegrating-dast-with-owasp-zap-in-pipeline\u002Freferences\u002Fstandards.md",{"path":77,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Fworkflows.md",2443,"https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fintegrating-dast-with-owasp-zap-in-pipeline\u002Freferences\u002Fworkflows.md",{"path":81,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":84,"sourceHtmlUrl":85},"scripts\u002Fagent.py","SCRIPT","脚本",6106,"https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fintegrating-dast-with-owasp-zap-in-pipeline\u002Fscripts\u002Fagent.py",{"path":87,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":88,"sourceHtmlUrl":89},"scripts\u002Fprocess.py",8058,"https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fintegrating-dast-with-owasp-zap-in-pipeline\u002Fscripts\u002Fprocess.py",[91,99,106,113,120,127],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":95,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":20},"01M76R4WZQZAXGGXMQCA0FZ716","zustand-store-ts","Create Zustand stores with TypeScript, subscribeWithSelector middleware, and proper state\u002Faction separation. Use when building React state management, creating global stores, or implementing reactive state patterns with Zustand.","MIT","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fzustand-store-ts\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":95,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":20},"01M76R4T9KENDH7FENGZQHBW4G","zustand-store-creator","Zustand Store Creator - Auto-activating skill for Frontend Development.\nTriggers on: zustand store creator, zustand store creator\nPart of the Frontend Development skill category.","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fzustand-store-creator\u002FSKILL.md",[],[],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":95,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":20},"01M76R3YWN84B7SANJ52X799ZE","zero-trust-config-helper","Zero Trust Config Helper - Auto-activating skill for Security Advanced.\nTriggers on: zero trust config helper, zero trust config helper\nPart of the Security Advanced skill category.","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fzero-trust-config-helper\u002FSKILL.md",[],[],{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":95,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":20},"01M76R3HNSV2AEYSKHM915GJ58","zapier-integration-helper","Zapier Integration Helper - Auto-activating skill for Business Automation.\nTriggers on: zapier integration helper, zapier integration helper\nPart of the Business Automation skill category.","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fzapier-integration-helper\u002FSKILL.md",[],[],{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":20},"01M76R3DJSKAT4FA7DV4BF3GCE","zai-cli","Execute z.AI CLI providing vision, search, reader, and GitHub exploration via CLI and MCP.\nUse when user needs image\u002Fvideo analysis, OCR, UI-to-code conversion, error diagnosis,\nreal-time web search, web page to markdown extraction, or GitHub code exploration.\nTrigger with phrases like \"analyze this image\", \"search the web for\", \"read this page\",\n\"explore this repo\", or \"use zai\". Requires Z_AI_API_KEY.","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fzai-cli\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":95,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":133,"publishedAt":20},"01M76R2KAM699XE9AJVAWE4H2E","yt-research","Research competitor YouTube channels, niches, and trending topics for your content strategy.\nUse this skill whenever the user says \"research channels\", \"analyze competitors\", \"find trending topics\",\n\"niche analysis\", \"competitive research\", \"what are other creators doing\", \"scrape YouTube channels\",\nor wants to understand the competitive landscape for a specific tool or topic area. Use when working with yt research. Trigger with 'yt', 'research'.","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fyt-research\u002FSKILL.md",[],[]]