[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78GYKXZ86Z9ESS7F319CWJW":3,"skill-same:01M78GYKXZ86Z9ESS7F319CWJW":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},"01M78GYKXZ86Z9ESS7F319CWJW","validating-api-schemas",null,"Validate API schemas against OpenAPI, JSON Schema, and GraphQL specifications.\nUse when validating API schemas and contracts.\nTrigger with phrases like \"validate API schema\", \"check OpenAPI spec\", or \"verify schema\".","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\u002Fapi-development--api-schema-validator--validating-api-schemas\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: validating-api-schemas\ndescription: |\n  Validate API schemas against OpenAPI, JSON Schema, and GraphQL specifications.\n  Use when validating API schemas and contracts.\n  Trigger with phrases like \"validate API schema\", \"check OpenAPI spec\", or \"verify schema\".\n  \nallowed-tools: Read, Write, Edit, Grep, Glob, Bash(api:schema-*)\nversion: 1.0.0\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\nlicense: MIT\ncompatible-with: claude-code, codex, openclaw\ntags: [api, graphql, validating-api]\n---\n# Validating API Schemas\n\n## Overview\n\nValidate API specifications against OpenAPI 3.0\u002F3.1, JSON Schema Draft 2020-12, and GraphQL SDL standards using linting rules, structural analysis, and best-practice enforcement. Detect incomplete schemas, undocumented endpoints, inconsistent naming conventions, and breaking changes before they reach consumers.\n\n## Prerequisites\n\n- OpenAPI specification files (YAML or JSON) or GraphQL SDL schema files\n- Schema linting tool: Spectral (OpenAPI), `graphql-schema-linter` (GraphQL), or `ajv-cli` (JSON Schema)\n- Version control for schema files to enable diff-based breaking change detection\n- CI pipeline for automated schema validation on every pull request\n- `oasdiff` or `openapi-diff` for breaking change detection between versions\n\n## Instructions\n\n1. Locate all API specification files using Glob, identifying OpenAPI specs, JSON Schema definitions, and GraphQL SDL files across the project.\n2. Run structural validation to verify the specification conforms to the declared standard (OpenAPI 3.0, 3.1, or JSON Schema Draft 2020-12) and is syntactically valid.\n3. Apply Spectral linting rules to enforce naming conventions (camelCase properties, kebab-case paths), required descriptions on all operations, and example values for request\u002Fresponse schemas.\n4. Verify schema completeness: every endpoint has documented request schemas, all response status codes have schemas (including 400, 401, 404, 500), and all `$ref` references resolve.\n5. Check for security scheme coverage: every endpoint either declares a security requirement or is explicitly marked as public with rationale.\n6. Detect breaking changes by comparing the current schema against the previous released version: removed endpoints, removed required fields, type changes, and narrowed enum values.\n7. Validate consistency across endpoints: pagination parameters use the same naming (`page`\u002F`limit` vs `offset`\u002F`count`), error response envelopes follow a single standard, and date formats are consistent.\n8. Generate a validation report with severity levels (error, warning, info) and specific file:line references for each finding.\n\nSee `${CLAUDE_SKILL_DIR}\u002Freferences\u002Fimplementation.md` for the full implementation guide.\n\n## Output\n\n- `${CLAUDE_SKILL_DIR}\u002Freports\u002Fschema-validation.json` - Machine-readable validation findings with severity\n- `${CLAUDE_SKILL_DIR}\u002Freports\u002Fschema-validation.md` - Human-readable report with fix recommendations\n- `${CLAUDE_SKILL_DIR}\u002Freports\u002Fbreaking-changes.md` - Breaking change analysis between schema versions\n- `${CLAUDE_SKILL_DIR}\u002F.spectral.yaml` - Custom Spectral linting rule configuration\n- `${CLAUDE_SKILL_DIR}\u002Fscripts\u002Fvalidate-schema.sh` - CI-ready schema validation script\n- `${CLAUDE_SKILL_DIR}\u002Freports\u002Fschema-coverage.md` - Endpoint documentation completeness matrix\n\n## Error Handling\n\n| Error | Cause | Solution |\n|-------|-------|----------|\n| Unresolved $ref | Schema references a component that does not exist or has a typo | List all `$ref` targets and verify each resolves; check for circular references |\n| Missing response schema | Endpoint returns undocumented status codes | Add schemas for all observed response codes; use `default` response as fallback |\n| Inconsistent naming | Mix of camelCase and snake_case property names across endpoints | Define naming convention in Spectral ruleset; apply auto-fix where possible |\n| Breaking change detected | Required field added to existing request schema | Make new field optional with default value; or create new API version for breaking changes |\n| Schema too permissive | Use of `additionalProperties: true` or missing type constraints | Set `additionalProperties: false` by default; require explicit type and format on all properties |\n\nRefer to `${CLAUDE_SKILL_DIR}\u002Freferences\u002Ferrors.md` for comprehensive error patterns.\n\n## Examples\n\n**Pre-commit schema lint**: Git pre-commit hook runs Spectral against all modified OpenAPI files, blocking commits that introduce undocumented endpoints, missing descriptions, or inconsistent naming.\n\n**Breaking change CI gate**: On pull requests modifying API specs, `oasdiff` compares against the main branch version, failing the build if backward-incompatible changes are detected without a version bump.\n\n**Schema completeness audit**: Generate a matrix showing every endpoint vs. documentation status (description, request schema, response schemas for 200\u002F400\u002F401\u002F404\u002F500, examples), highlighting gaps with coverage percentage.\n\nSee `${CLAUDE_SKILL_DIR}\u002Freferences\u002Fexamples.md` for additional examples.\n\n## Resources\n\n- Spectral OpenAPI linter: https:\u002F\u002Fstoplight.io\u002Fopen-source\u002Fspectral\n- OpenAPI Specification: https:\u002F\u002Fspec.openapis.org\u002Foas\u002Fv3.1.0\n- JSON Schema specification: https:\u002F\u002Fjson-schema.org\u002F\n- oasdiff breaking change detection: https:\u002F\u002Fgithub.com\u002FTufin\u002Foasdiff","# Validating API Schemas\n\n## Overview\n\nValidate API specifications against OpenAPI 3.0\u002F3.1, JSON Schema Draft 2020-12, and GraphQL SDL standards using linting rules, structural analysis, and best-practice enforcement. Detect incomplete schemas, undocumented endpoints, inconsistent naming conventions, and breaking changes before they reach consumers.\n\n## Prerequisites\n\n- OpenAPI specification files (YAML or JSON) or GraphQL SDL schema files\n- Schema linting tool: Spectral (OpenAPI), `graphql-schema-linter` (GraphQL), or `ajv-cli` (JSON Schema)\n- Version control for schema files to enable diff-based breaking change detection\n- CI pipeline for automated schema validation on every pull request\n- `oasdiff` or `openapi-diff` for breaking change detection between versions\n\n## Instructions\n\n1. Locate all API specification files using Glob, identifying OpenAPI specs, JSON Schema definitions, and GraphQL SDL files across the project.\n2. Run structural validation to verify the specification conforms to the declared standard (OpenAPI 3.0, 3.1, or JSON Schema Draft 2020-12) and is syntactically valid.\n3. Apply Spectral linting rules to enforce naming conventions (camelCase properties, kebab-case paths), required descriptions on all operations, and example values for request\u002Fresponse schemas.\n4. Verify schema completeness: every endpoint has documented request schemas, all response status codes have schemas (including 400, 401, 404, 500), and all `$ref` references resolve.\n5. Check for security scheme coverage: every endpoint either declares a security requirement or is explicitly marked as public with rationale.\n6. Detect breaking changes by comparing the current schema against the previous released version: removed endpoints, removed required fields, type changes, and narrowed enum values.\n7. Validate consistency across endpoints: pagination parameters use the same naming (`page`\u002F`limit` vs `offset`\u002F`count`), error response envelopes follow a single standard, and date formats are consistent.\n8. Generate a validation report with severity levels (error, warning, info) and specific file:line references for each finding.\n\nSee `${CLAUDE_SKILL_DIR}\u002Freferences\u002Fimplementation.md` for the full implementation guide.\n\n## Output\n\n- `${CLAUDE_SKILL_DIR}\u002Freports\u002Fschema-validation.json` - Machine-readable validation findings with severity\n- `${CLAUDE_SKILL_DIR}\u002Freports\u002Fschema-validation.md` - Human-readable report with fix recommendations\n- `${CLAUDE_SKILL_DIR}\u002Freports\u002Fbreaking-changes.md` - Breaking change analysis between schema versions\n- `${CLAUDE_SKILL_DIR}\u002F.spectral.yaml` - Custom Spectral linting rule configuration\n- `${CLAUDE_SKILL_DIR}\u002Fscripts\u002Fvalidate-schema.sh` - CI-ready schema validation script\n- `${CLAUDE_SKILL_DIR}\u002Freports\u002Fschema-coverage.md` - Endpoint documentation completeness matrix\n\n## Error Handling\n\n| Error | Cause | Solution |\n|-------|-------|----------|\n| Unresolved $ref | Schema references a component that does not exist or has a typo | List all `$ref` targets and verify each resolves; check for circular references |\n| Missing response schema | Endpoint returns undocumented status codes | Add schemas for all observed response codes; use `default` response as fallback |\n| Inconsistent naming | Mix of camelCase and snake_case property names across endpoints | Define naming convention in Spectral ruleset; apply auto-fix where possible |\n| Breaking change detected | Required field added to existing request schema | Make new field optional with default value; or create new API version for breaking changes |\n| Schema too permissive | Use of `additionalProperties: true` or missing type constraints | Set `additionalProperties: false` by default; require explicit type and format on all properties |\n\nRefer to `${CLAUDE_SKILL_DIR}\u002Freferences\u002Ferrors.md` for comprehensive error patterns.\n\n## Examples\n\n**Pre-commit schema lint**: Git pre-commit hook runs Spectral against all modified OpenAPI files, blocking commits that introduce undocumented endpoints, missing descriptions, or inconsistent naming.\n\n**Breaking change CI gate**: On pull requests modifying API specs, `oasdiff` compares against the main branch version, failing the build if backward-incompatible changes are detected without a version bump.\n\n**Schema completeness audit**: Generate a matrix showing every endpoint vs. documentation status (description, request schema, response schemas for 200\u002F400\u002F401\u002F404\u002F500, examples), highlighting gaps with coverage percentage.\n\nSee `${CLAUDE_SKILL_DIR}\u002Freferences\u002Fexamples.md` for additional examples.\n\n## Resources\n\n- Spectral OpenAPI linter: https:\u002F\u002Fstoplight.io\u002Fopen-source\u002Fspectral\n- OpenAPI Specification: https:\u002F\u002Fspec.openapis.org\u002Foas\u002Fv3.1.0\n- JSON Schema specification: https:\u002F\u002Fjson-schema.org\u002F\n- oasdiff breaking change detection: https:\u002F\u002Fgithub.com\u002FTufin\u002Foasdiff",{"name":5,"tags":24,"author":28,"license":15,"version":29,"description":30,"allowed-tools":31,"compatible-with":32},[25,26,27],"api","graphql","validating-api","Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Validate API schemas against OpenAPI, JSON Schema, and GraphQL specifications.\nUse when validating API schemas and contracts.\nTrigger with phrases like \"validate API schema\", \"check OpenAPI spec\", or \"verify schema\".\n","Read, Write, Edit, Grep, Glob, Bash(api:schema-*)","claude-code, codex, openclaw","main","99825ad3f3bcc6597ddcc7294a14e6e922f2b67b","skills\u002Fapi-development--api-schema-validator--validating-api-schemas",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 validating-api-schemas",{"tool":48,"command":49},"bunx","bunx skills add jukeyman\u002Fjukeyman-skills --skill validating-api-schemas",{"tool":51,"command":52},"pnpm","pnpm dlx skills add jukeyman\u002Fjukeyman-skills --skill validating-api-schemas","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fapi-development--api-schema-validator--validating-api-schemas\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",[],[]]