[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M793DCXP4G5G26K5XSWGSWJM":3,"skill-same:01M793DCXP4G5G26K5XSWGSWJM":56},{"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":33,"commitSha":34,"skillDirectory":35,"forksCount":36,"repositoryHtmlUrl":37,"repositoryHomepageUrl":6,"ownerHtmlUrl":38,"ownerBlogUrl":39,"ownerDescription":40,"updatedAt":41,"install":42,"resources":55},"01M793DCXP4G5G26K5XSWGSWJM","navan-ci-integration",null,"Use when setting up CI\u002FCD pipelines that validate Navan API integrations, run booking data health checks, or generate automated compliance reports.\nTrigger with \"navan ci integration\" or \"navan pipeline\" or \"navan github actions\".","jukeyman\u002Fjukeyman-skills","jukeyman","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F142960420?v=4","01M78FR4Y3DHMMCBCC0GXXNB3F","RICK JEFFERSON","01M78FR4Z8RVQRAD31Y5J7V6EB",1,"MIT","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsaas-packs--navan-pack--navan-ci-integration\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: navan-ci-integration\ndescription: |\n  Use when setting up CI\u002FCD pipelines that validate Navan API integrations, run booking data health checks, or generate automated compliance reports.\n  Trigger with \"navan ci integration\" or \"navan pipeline\" or \"navan github actions\".\nallowed-tools: Read, Write, Edit, Bash(git:*), Bash(gh:*), Grep, Glob\nversion: 1.0.0\nlicense: MIT\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\ntags: [saas, navan, travel]\ncompatible-with: claude-code\n---\n\n# Navan CI Integration\n\n## Overview\n\nNavan has no SDK — all CI integration uses raw REST calls against `https:\u002F\u002Fapi.navan.com` with OAuth 2.0 client_credentials authentication. This skill generates GitHub Actions workflows that validate your Navan integration on every push: token health checks, booking data schema validation, and travel policy compliance reports. Secrets (client_id, client_secret) are stored in GitHub Actions secrets, never in code.\n\n## Prerequisites\n\n- **Navan Admin access** to create OAuth 2.0 application credentials (Admin > API Settings)\n- **GitHub repo** with Actions enabled\n- **GitHub Secrets** configured: `NAVAN_CLIENT_ID`, `NAVAN_CLIENT_SECRET`\n- Navan API base URL: `https:\u002F\u002Fapi.navan.com`\n\n## Instructions\n\n### Step 1 — Store OAuth Credentials in GitHub Secrets\n\nNavigate to your GitHub repo > Settings > Secrets and variables > Actions. Add:\n\n- `NAVAN_CLIENT_ID` — from Navan Admin > API Settings\n- `NAVAN_CLIENT_SECRET` — from Navan Admin > API Settings\n\n### Step 2 — Create the CI Workflow\n\n```yaml\n# .github\u002Fworkflows\u002Fnavan-integration-check.yml\nname: Navan Integration Health Check\non:\n  push:\n    branches: [main]\n  pull_request:\n  schedule:\n    - cron: '0 6 * * 1'  # Weekly Monday 6am UTC\n\njobs:\n  navan-health:\n    runs-on: ubuntu-latest\n    env:\n      NAVAN_BASE_URL: https:\u002F\u002Fapi.navan.com\n    steps:\n      - uses: actions\u002Fcheckout@v4\n\n      - name: Authenticate with Navan OAuth 2.0\n        id: auth\n        run: |\n          TOKEN_RESPONSE=$(curl -s -X POST \\\n            https:\u002F\u002Fapi.navan.com\u002Fta-auth\u002Foauth\u002Ftoken \\\n            -H \"Content-Type: application\u002Fx-www-form-urlencoded\" \\\n            -d \"grant_type=client_credentials\" \\\n            -d \"client_id=${{ secrets.NAVAN_CLIENT_ID }}\" \\\n            -d \"client_secret=${{ secrets.NAVAN_CLIENT_SECRET }}\")\n\n          ACCESS_TOKEN=$(echo \"$TOKEN_RESPONSE\" | jq -r '.access_token')\n          if [ \"$ACCESS_TOKEN\" = \"null\" ] || [ -z \"$ACCESS_TOKEN\" ]; then\n            echo \"::error::OAuth authentication failed\"\n            echo \"$TOKEN_RESPONSE\" | jq .\n            exit 1\n          fi\n          echo \"::add-mask::$ACCESS_TOKEN\"\n          echo \"token=$ACCESS_TOKEN\" >> \"$GITHUB_OUTPUT\"\n\n      - name: API Health Check — Fetch Bookings\n        run: |\n          HTTP_CODE=$(curl -s -o \u002Ftmp\u002Fbookings.json -w \"%{http_code}\" \\\n            \"$NAVAN_BASE_URL\u002Fv1\u002Fbookings?page=0&size=5\" \\\n            -H \"Authorization: Bearer ${{ steps.auth.outputs.token }}\")\n          echo \"Health check status: $HTTP_CODE\"\n          if [ \"$HTTP_CODE\" != \"200\" ]; then\n            echo \"::error::API health check failed with HTTP $HTTP_CODE\"\n            cat \u002Ftmp\u002Fbookings.json\n            exit 1\n          fi\n\n      - name: Validate Booking Data Schema\n        run: |\n          # Response structure: records in .data array, primary key uuid\n          REQUIRED_FIELDS='[\"uuid\",\"traveler\",\"status\",\"created_at\"]'\n          echo \"$REQUIRED_FIELDS\" | jq -r '.[]' | while read field; do\n            if ! jq -e \".data[0].$field\" \u002Ftmp\u002Fbookings.json > \u002Fdev\u002Fnull 2>&1; then\n              echo \"::warning::Missing expected field: $field\"\n            fi\n          done\n\n      - name: Generate Compliance Report\n        run: |\n          curl -s \"$NAVAN_BASE_URL\u002Fv1\u002Fbookings?page=0&size=50\" \\\n            -H \"Authorization: Bearer ${{ steps.auth.outputs.token }}\" \\\n            -o \u002Ftmp\u002Fcompliance.json\n          echo \"## Navan Compliance Report\" >> \"$GITHUB_STEP_SUMMARY\"\n          jq -r '\"| Metric | Value |\\n|--------|-------|\\n| Total Bookings | \\(.total_bookings) |\\n| In Policy | \\(.in_policy) |\\n| Out of Policy | \\(.out_of_policy) |\"' \\\n            \u002Ftmp\u002Fcompliance.json >> \"$GITHUB_STEP_SUMMARY\" 2>\u002Fdev\u002Fnull || echo \"Report data unavailable\" >> \"$GITHUB_STEP_SUMMARY\"\n```\n\n### Step 3 — Add Integration Test Script\n\n```bash\n#!\u002Fusr\u002Fbin\u002Fenv bash\n# scripts\u002Fnavan-smoke-test.sh — Run locally or in CI\nset -euo pipefail\n\nBASE_URL=\"${NAVAN_BASE_URL:-https:\u002F\u002Fapi.navan.com}\"\n\n# Obtain token\nTOKEN=$(curl -sf -X POST https:\u002F\u002Fapi.navan.com\u002Fta-auth\u002Foauth\u002Ftoken \\\n  -H \"Content-Type: application\u002Fx-www-form-urlencoded\" \\\n  -d \"grant_type=client_credentials&client_id=${NAVAN_CLIENT_ID}&client_secret=${NAVAN_CLIENT_SECRET}\" \\\n  | jq -r '.access_token')\n\n# Test endpoints (records returned in .data array)\nENDPOINTS=(\"v1\u002Fbookings?page=0&size=1\")\nFAILED=0\nfor ep in \"${ENDPOINTS[@]}\"; do\n  CODE=$(curl -s -o \u002Fdev\u002Fnull -w \"%{http_code}\" \\\n    \"$BASE_URL\u002F$ep\" -H \"Authorization: Bearer $TOKEN\")\n  if [ \"$CODE\" = \"200\" ]; then\n    echo \"PASS: $ep ($CODE)\"\n  else\n    echo \"FAIL: $ep ($CODE)\"\n    FAILED=$((FAILED + 1))\n  fi\ndone\n\nexit $FAILED\n```\n\n## Output\n\nThe CI workflow produces:\n- **Pass\u002Ffail status** on each PR for Navan API connectivity\n- **GitHub Step Summary** with a compliance report table\n- **Annotations** warning about missing booking data fields\n- **Weekly scheduled runs** catching credential expiration before it causes outages\n\n## Error Handling\n\n| HTTP Code | Meaning | CI Action |\n|-----------|---------|-----------|\n| `200` | Success | Continue |\n| `401` | Invalid or expired OAuth token | Fail build, alert on credential rotation |\n| `403` | Insufficient API scopes | Fail build, check OAuth app permissions |\n| `404` | Endpoint not found (API version change) | Fail build, review API changelog |\n| `429` | Rate limit exceeded | Retry with exponential backoff (max 3 attempts) |\n| `500-503` | Navan server error | Warn but do not fail (transient) |\n\n## Examples\n\n**Parallel endpoint validation with matrix strategy:**\n\n```yaml\njobs:\n  validate-endpoints:\n    runs-on: ubuntu-latest\n    strategy:\n      matrix:\n        endpoint: [bookings, expenses, users, invoices]\n    steps:\n      - name: Check ${{ matrix.endpoint }}\n        run: |\n          CODE=$(curl -s -o \u002Fdev\u002Fnull -w \"%{http_code}\" \\\n            \"https:\u002F\u002Fapi.navan.com\u002Fv1\u002F${{ matrix.endpoint }}?page=0&size=1\" \\\n            -H \"Authorization: Bearer $TOKEN\")\n          [ \"$CODE\" = \"200\" ] || exit 1\n```\n\n## Resources\n\n- [Navan Help Center](https:\u002F\u002Fapp.navan.com\u002Fapp\u002Fhelpcenter) — API documentation and guides\n- [Navan Integrations](https:\u002F\u002Fnavan.com\u002Fintegrations) — Supported third-party connectors\n- [GitHub Actions Encrypted Secrets](https:\u002F\u002Fdocs.github.com\u002Fen\u002Factions\u002Fsecurity-for-github-actions\u002Fsecurity-guides\u002Fusing-secrets-in-github-actions)\n\n## Next Steps\n\n- Add `navan-deploy-integration` for production deployment patterns\n- Add `navan-observability` for runtime monitoring of the endpoints validated here\n- See `navan-rate-limits` to configure retry policies in CI\n","# Navan CI Integration\n\n## Overview\n\nNavan has no SDK — all CI integration uses raw REST calls against `https:\u002F\u002Fapi.navan.com` with OAuth 2.0 client_credentials authentication. This skill generates GitHub Actions workflows that validate your Navan integration on every push: token health checks, booking data schema validation, and travel policy compliance reports. Secrets (client_id, client_secret) are stored in GitHub Actions secrets, never in code.\n\n## Prerequisites\n\n- **Navan Admin access** to create OAuth 2.0 application credentials (Admin > API Settings)\n- **GitHub repo** with Actions enabled\n- **GitHub Secrets** configured: `NAVAN_CLIENT_ID`, `NAVAN_CLIENT_SECRET`\n- Navan API base URL: `https:\u002F\u002Fapi.navan.com`\n\n## Instructions\n\n### Step 1 — Store OAuth Credentials in GitHub Secrets\n\nNavigate to your GitHub repo > Settings > Secrets and variables > Actions. Add:\n\n- `NAVAN_CLIENT_ID` — from Navan Admin > API Settings\n- `NAVAN_CLIENT_SECRET` — from Navan Admin > API Settings\n\n### Step 2 — Create the CI Workflow\n\n```yaml\n# .github\u002Fworkflows\u002Fnavan-integration-check.yml\nname: Navan Integration Health Check\non:\n  push:\n    branches: [main]\n  pull_request:\n  schedule:\n    - cron: '0 6 * * 1'  # Weekly Monday 6am UTC\n\njobs:\n  navan-health:\n    runs-on: ubuntu-latest\n    env:\n      NAVAN_BASE_URL: https:\u002F\u002Fapi.navan.com\n    steps:\n      - uses: actions\u002Fcheckout@v4\n\n      - name: Authenticate with Navan OAuth 2.0\n        id: auth\n        run: |\n          TOKEN_RESPONSE=$(curl -s -X POST \\\n            https:\u002F\u002Fapi.navan.com\u002Fta-auth\u002Foauth\u002Ftoken \\\n            -H \"Content-Type: application\u002Fx-www-form-urlencoded\" \\\n            -d \"grant_type=client_credentials\" \\\n            -d \"client_id=${{ secrets.NAVAN_CLIENT_ID }}\" \\\n            -d \"client_secret=${{ secrets.NAVAN_CLIENT_SECRET }}\")\n\n          ACCESS_TOKEN=$(echo \"$TOKEN_RESPONSE\" | jq -r '.access_token')\n          if [ \"$ACCESS_TOKEN\" = \"null\" ] || [ -z \"$ACCESS_TOKEN\" ]; then\n            echo \"::error::OAuth authentication failed\"\n            echo \"$TOKEN_RESPONSE\" | jq .\n            exit 1\n          fi\n          echo \"::add-mask::$ACCESS_TOKEN\"\n          echo \"token=$ACCESS_TOKEN\" >> \"$GITHUB_OUTPUT\"\n\n      - name: API Health Check — Fetch Bookings\n        run: |\n          HTTP_CODE=$(curl -s -o \u002Ftmp\u002Fbookings.json -w \"%{http_code}\" \\\n            \"$NAVAN_BASE_URL\u002Fv1\u002Fbookings?page=0&size=5\" \\\n            -H \"Authorization: Bearer ${{ steps.auth.outputs.token }}\")\n          echo \"Health check status: $HTTP_CODE\"\n          if [ \"$HTTP_CODE\" != \"200\" ]; then\n            echo \"::error::API health check failed with HTTP $HTTP_CODE\"\n            cat \u002Ftmp\u002Fbookings.json\n            exit 1\n          fi\n\n      - name: Validate Booking Data Schema\n        run: |\n          # Response structure: records in .data array, primary key uuid\n          REQUIRED_FIELDS='[\"uuid\",\"traveler\",\"status\",\"created_at\"]'\n          echo \"$REQUIRED_FIELDS\" | jq -r '.[]' | while read field; do\n            if ! jq -e \".data[0].$field\" \u002Ftmp\u002Fbookings.json > \u002Fdev\u002Fnull 2>&1; then\n              echo \"::warning::Missing expected field: $field\"\n            fi\n          done\n\n      - name: Generate Compliance Report\n        run: |\n          curl -s \"$NAVAN_BASE_URL\u002Fv1\u002Fbookings?page=0&size=50\" \\\n            -H \"Authorization: Bearer ${{ steps.auth.outputs.token }}\" \\\n            -o \u002Ftmp\u002Fcompliance.json\n          echo \"## Navan Compliance Report\" >> \"$GITHUB_STEP_SUMMARY\"\n          jq -r '\"| Metric | Value |\\n|--------|-------|\\n| Total Bookings | \\(.total_bookings) |\\n| In Policy | \\(.in_policy) |\\n| Out of Policy | \\(.out_of_policy) |\"' \\\n            \u002Ftmp\u002Fcompliance.json >> \"$GITHUB_STEP_SUMMARY\" 2>\u002Fdev\u002Fnull || echo \"Report data unavailable\" >> \"$GITHUB_STEP_SUMMARY\"\n```\n\n### Step 3 — Add Integration Test Script\n\n```bash\n#!\u002Fusr\u002Fbin\u002Fenv bash\n# scripts\u002Fnavan-smoke-test.sh — Run locally or in CI\nset -euo pipefail\n\nBASE_URL=\"${NAVAN_BASE_URL:-https:\u002F\u002Fapi.navan.com}\"\n\n# Obtain token\nTOKEN=$(curl -sf -X POST https:\u002F\u002Fapi.navan.com\u002Fta-auth\u002Foauth\u002Ftoken \\\n  -H \"Content-Type: application\u002Fx-www-form-urlencoded\" \\\n  -d \"grant_type=client_credentials&client_id=${NAVAN_CLIENT_ID}&client_secret=${NAVAN_CLIENT_SECRET}\" \\\n  | jq -r '.access_token')\n\n# Test endpoints (records returned in .data array)\nENDPOINTS=(\"v1\u002Fbookings?page=0&size=1\")\nFAILED=0\nfor ep in \"${ENDPOINTS[@]}\"; do\n  CODE=$(curl -s -o \u002Fdev\u002Fnull -w \"%{http_code}\" \\\n    \"$BASE_URL\u002F$ep\" -H \"Authorization: Bearer $TOKEN\")\n  if [ \"$CODE\" = \"200\" ]; then\n    echo \"PASS: $ep ($CODE)\"\n  else\n    echo \"FAIL: $ep ($CODE)\"\n    FAILED=$((FAILED + 1))\n  fi\ndone\n\nexit $FAILED\n```\n\n## Output\n\nThe CI workflow produces:\n- **Pass\u002Ffail status** on each PR for Navan API connectivity\n- **GitHub Step Summary** with a compliance report table\n- **Annotations** warning about missing booking data fields\n- **Weekly scheduled runs** catching credential expiration before it causes outages\n\n## Error Handling\n\n| HTTP Code | Meaning | CI Action |\n|-----------|---------|-----------|\n| `200` | Success | Continue |\n| `401` | Invalid or expired OAuth token | Fail build, alert on credential rotation |\n| `403` | Insufficient API scopes | Fail build, check OAuth app permissions |\n| `404` | Endpoint not found (API version change) | Fail build, review API changelog |\n| `429` | Rate limit exceeded | Retry with exponential backoff (max 3 attempts) |\n| `500-503` | Navan server error | Warn but do not fail (transient) |\n\n## Examples\n\n**Parallel endpoint validation with matrix strategy:**\n\n```yaml\njobs:\n  validate-endpoints:\n    runs-on: ubuntu-latest\n    strategy:\n      matrix:\n        endpoint: [bookings, expenses, users, invoices]\n    steps:\n      - name: Check ${{ matrix.endpoint }}\n        run: |\n          CODE=$(curl -s -o \u002Fdev\u002Fnull -w \"%{http_code}\" \\\n            \"https:\u002F\u002Fapi.navan.com\u002Fv1\u002F${{ matrix.endpoint }}?page=0&size=1\" \\\n            -H \"Authorization: Bearer $TOKEN\")\n          [ \"$CODE\" = \"200\" ] || exit 1\n```\n\n## Resources\n\n- [Navan Help Center](https:\u002F\u002Fapp.navan.com\u002Fapp\u002Fhelpcenter) — API documentation and guides\n- [Navan Integrations](https:\u002F\u002Fnavan.com\u002Fintegrations) — Supported third-party connectors\n- [GitHub Actions Encrypted Secrets](https:\u002F\u002Fdocs.github.com\u002Fen\u002Factions\u002Fsecurity-for-github-actions\u002Fsecurity-guides\u002Fusing-secrets-in-github-actions)\n\n## Next Steps\n\n- Add `navan-deploy-integration` for production deployment patterns\n- Add `navan-observability` for runtime monitoring of the endpoints validated here\n- See `navan-rate-limits` to configure retry policies in CI\n",{"name":5,"tags":24,"author":28,"license":15,"version":29,"description":30,"allowed-tools":31,"compatible-with":32},[25,26,27],"saas","navan","travel","Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Use when setting up CI\u002FCD pipelines that validate Navan API integrations, run booking data health checks, or generate automated compliance reports.\nTrigger with \"navan ci integration\" or \"navan pipeline\" or \"navan github actions\".\n","Read, Write, Edit, Bash(git:*), Bash(gh:*), Grep, Glob","claude-code","main","99825ad3f3bcc6597ddcc7294a14e6e922f2b67b","skills\u002Fsaas-packs--navan-pack--navan-ci-integration",0,"https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills","https:\u002F\u002Fgithub.com\u002Fjukeyman","https:\u002F\u002FRJBUSINESSSOLUTIONS.ORG","Credit and Finance Expert | Developer\r\n\r\nI'm Rick Jefferson, a seasoned credit and finance expert with over a decade of experience in financial literacy,","2026-07-13 07:03:29",{"source":8,"skillName":5,"commands":43,"prompt":53,"zipAvailable":54},[44,47,50],{"tool":45,"command":46},"npx","npx skills add jukeyman\u002Fjukeyman-skills --skill navan-ci-integration",{"tool":48,"command":49},"bunx","bunx skills add jukeyman\u002Fjukeyman-skills --skill navan-ci-integration",{"tool":51,"command":52},"pnpm","pnpm dlx skills add jukeyman\u002Fjukeyman-skills --skill navan-ci-integration","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsaas-packs--navan-pack--navan-ci-integration\u002FSKILL.md",true,[],[57,64,71,78,85,93],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M79ANS2SM329NEP5ZCX106RR","zustand-store-creator","Create zustand store creator operations. Auto-activating skill for Frontend Development.\nTriggers on: zustand store creator, zustand store creator\nPart of the Frontend Development skill category. Use when working with zustand store creator functionality. Trigger with phrases like \"zustand store creator\", \"zustand creator\", \"zustand\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzustand-store-creator\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M79AMZKP4YDEZ7EHG1Y7PP74","zero-trust-config-helper","Configure with zero trust config helper operations. Auto-activating skill for Security Advanced.\nTriggers on: zero trust config helper, zero trust config helper\nPart of the Security Advanced skill category. Use when configuring systems or services. Trigger with phrases like \"zero trust config helper\", \"zero helper\", \"zero\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzero-trust-config-helper\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M79AMJSBCEJQNBTYNAHYN5HM","zapier-integration-helper","Assist with zapier integration helper operations. Auto-activating skill for Business Automation.\nTriggers on: zapier integration helper, zapier integration helper\nPart of the Business Automation skill category. Use when working with APIs or building integrations. Trigger with phrases like \"zapier integration helper\", \"zapier helper\", \"zapier\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzapier-integration-helper\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M79AHJZGVMARS13VFQYRR1MP","yaml-config-validator","Validate yaml config validator operations. Auto-activating skill for DevOps Basics.\nTriggers on: yaml config validator, yaml config validator\nPart of the DevOps Basics skill category. Use when configuring systems or services. Trigger with phrases like \"yaml config validator\", \"yaml validator\", \"yaml\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fyaml-config-validator\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":89,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M79AHGDZRN0020RDQSQDPAM8","xvary-stock-research","Thesis-driven equity analysis from public SEC EDGAR and market data; \u002Fanalyze, \u002Fscore, \u002Fcompare workflows with bundled Python tools (Claude Code, Cursor, Codex).","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxvary-stock-research\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxvary-stock-research\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M79AHCYJ9FV9RMHQ24HDRN33","xss-vulnerability-scanner","Scan xss vulnerability scanner operations. Auto-activating skill for Security Fundamentals.\nTriggers on: xss vulnerability scanner, xss vulnerability scanner\nPart of the Security Fundamentals skill category. Use when working with xss vulnerability scanner functionality. Trigger with phrases like \"xss vulnerability scanner\", \"xss scanner\", \"xss\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxss-vulnerability-scanner\u002FSKILL.md",[],[]]