[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78XPDFQAPX9XZ06EEYV1W06":3,"skill-same:01M78XPDFQAPX9XZ06EEYV1W06":57},{"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":34,"commitSha":35,"skillDirectory":36,"forksCount":37,"repositoryHtmlUrl":38,"repositoryHomepageUrl":6,"ownerHtmlUrl":39,"ownerBlogUrl":40,"ownerDescription":41,"updatedAt":42,"install":43,"resources":56},"01M78XPDFQAPX9XZ06EEYV1W06","bamboohr-upgrade-migration",null,"Plan and execute BambooHR API migration with breaking change detection.\nUse when BambooHR announces API changes, adapting to deprecated endpoints,\nor migrating from legacy API patterns to current best practices.\nTrigger with phrases like \"upgrade bamboohr\", \"bamboohr migration\",\n\"bamboohr breaking changes\", \"bamboohr API update\", \"bamboohr deprecated\".","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--bamboohr-pack--bamboohr-upgrade-migration\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: bamboohr-upgrade-migration\ndescription: |\n  Plan and execute BambooHR API migration with breaking change detection.\n  Use when BambooHR announces API changes, adapting to deprecated endpoints,\n  or migrating from legacy API patterns to current best practices.\n  Trigger with phrases like \"upgrade bamboohr\", \"bamboohr migration\",\n  \"bamboohr breaking changes\", \"bamboohr API update\", \"bamboohr deprecated\".\nallowed-tools: Read, Write, Edit, Bash(npm:*), Bash(git:*)\nversion: 1.0.0\nlicense: MIT\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\ntags: [saas, hr, bamboohr, migration]\ncompatible-with: claude-code\n---\n\n# BambooHR Upgrade & Migration\n\n## Overview\n\nGuide for handling BambooHR API changes, migrating from legacy patterns, and proactively detecting deprecations. BambooHR's API is versioned at v1 — breaking changes are announced on their changelog rather than through version bumps.\n\n## Prerequisites\n\n- Current BambooHR integration working\n- Access to BambooHR API changelog\n- Git for version control\n- Test suite available\n\n## Instructions\n\n### Step 1: Check for Announced Changes\n\n```bash\n# Monitor BambooHR's official changelog pages\necho \"Check these URLs before any migration work:\"\necho \"  Past changes:    https:\u002F\u002Fdocumentation.bamboohr.com\u002Fdocs\u002Fpast-changes-to-the-api\"\necho \"  Planned changes: https:\u002F\u002Fdocumentation.bamboohr.com\u002Fdocs\u002Fplanned-changes-to-the-api\"\necho \"  Status page:     https:\u002F\u002Fstatus.bamboohr.com\"\n```\n\n### Step 2: Common Migration Patterns\n\n#### URL Format Migration\n\nBambooHR has used two base URL formats historically:\n\n```typescript\n\u002F\u002F Legacy format (still works)\nconst LEGACY = `https:\u002F\u002Fapi.bamboohr.com\u002Fapi\u002Fgateway.php\u002F${domain}\u002Fv1`;\n\n\u002F\u002F Modern format (equivalent)\nconst MODERN = `https:\u002F\u002F${domain}.bamboohr.com\u002Fapi\u002Fv1`;\n\n\u002F\u002F Migration: both work, but use the gateway.php format for API key auth\n\u002F\u002F The modern format is used for browser-based OAuth flows\n```\n\n#### XML to JSON Migration\n\n```typescript\n\u002F\u002F Legacy: XML responses (default if no Accept header)\nconst xmlRes = await fetch(`${BASE}\u002Femployees\u002Fdirectory`, {\n  headers: { Authorization: AUTH },\n  \u002F\u002F No Accept header — returns XML\n});\n\n\u002F\u002F Current: JSON responses (always set Accept header)\nconst jsonRes = await fetch(`${BASE}\u002Femployees\u002Fdirectory`, {\n  headers: { Authorization: AUTH, Accept: 'application\u002Fjson' },\n});\n\n\u002F\u002F Migration checklist:\n\u002F\u002F - Add 'Accept: application\u002Fjson' to ALL requests\n\u002F\u002F - Replace XML parsing with JSON.parse\n\u002F\u002F - Update response type definitions\n```\n\n#### Employee Endpoint Changes\n\n```typescript\n\u002F\u002F Legacy: using employee ID 0 for \"current user\"\n\u002F\u002F GET \u002Femployees\u002F0\u002F?fields=firstName,lastName\n\u002F\u002F This returns the employee record for the API key's user\n\n\u002F\u002F Current: still works, but prefer explicit employee IDs from directory\nconst dir = await client.getDirectory();\nconst currentUser = dir.employees.find(e => e.workEmail === knownEmail);\n```\n\n### Step 3: Detect Deprecated Field Usage\n\n```typescript\n\u002F\u002F Scan your codebase for BambooHR field references\nconst DEPRECATED_FIELDS = [\n  \u002F\u002F As of 2025, these field aliases may change:\n  'bestEmail',       \u002F\u002F Use 'workEmail' or 'homeEmail' explicitly\n  'fullName1',       \u002F\u002F Use 'displayName' instead\n  'fullName2',       \u002F\u002F Use firstName + lastName\n  'fullName3',       \u002F\u002F Removed\n  'fullName4',       \u002F\u002F Removed\n  'fullName5',       \u002F\u002F Removed\n];\n\nconst CURRENT_FIELD_MAPPING: Record\u003Cstring, string> = {\n  'bestEmail': 'workEmail',\n  'fullName1': 'displayName',\n  'fullName2': 'displayName',  \u002F\u002F Or construct from firstName + lastName\n};\n\nfunction migrateFieldName(oldField: string): string {\n  if (DEPRECATED_FIELDS.includes(oldField)) {\n    const replacement = CURRENT_FIELD_MAPPING[oldField];\n    console.warn(`Deprecated field '${oldField}' — use '${replacement}' instead`);\n    return replacement || oldField;\n  }\n  return oldField;\n}\n```\n\n### Step 4: Migration Testing Strategy\n\n```typescript\n\u002F\u002F tests\u002Fmigration\u002Fbamboohr-compat.test.ts\nimport { describe, it, expect } from 'vitest';\n\ndescribe('BambooHR API Compatibility', () => {\n  it('should handle both old and new field names', async () => {\n    const emp = await client.getEmployee(testId, [\n      'displayName', 'firstName', 'lastName', 'workEmail',\n    ]);\n\n    \u002F\u002F Verify current fields work\n    expect(emp.displayName).toBeTruthy();\n    expect(emp.workEmail).toBeTruthy();\n  });\n\n  it('should handle null fields gracefully', async () => {\n    \u002F\u002F BambooHR may return null for newly added fields\n    const emp = await client.getEmployee(testId, [\n      'firstName', 'lastName', 'supervisor', 'division',\n    ]);\n\n    \u002F\u002F These may be null\u002Fempty for some employees\n    expect(emp.firstName).toBeTruthy();\n    expect(emp.supervisor).toBeDefined(); \u002F\u002F null is valid\n  });\n\n  it('should handle table schema changes', async () => {\n    const jobInfo = await client.getTableRows(testId, 'jobInfo');\n\n    \u002F\u002F Verify required columns still present\n    if (jobInfo.length > 0) {\n      const row = jobInfo[0];\n      expect(row).toHaveProperty('date');\n      expect(row).toHaveProperty('jobTitle');\n    }\n  });\n});\n```\n\n### Step 5: Gradual Migration with Feature Flags\n\n```typescript\ninterface MigrationConfig {\n  useNewEndpoint: boolean;\n  useNewFieldNames: boolean;\n  enableNewWebhookFormat: boolean;\n}\n\nconst MIGRATION_FLAGS: MigrationConfig = {\n  useNewEndpoint: process.env.BAMBOOHR_USE_NEW_ENDPOINT === 'true',\n  useNewFieldNames: true,       \u002F\u002F Already migrated\n  enableNewWebhookFormat: false, \u002F\u002F Testing in staging\n};\n\nasync function getEmployeeData(id: string): Promise\u003CRecord\u003Cstring, string>> {\n  const fields = MIGRATION_FLAGS.useNewFieldNames\n    ? ['displayName', 'workEmail', 'jobTitle']\n    : ['bestEmail', 'fullName1', 'jobTitle']; \u002F\u002F Legacy\n\n  return client.getEmployee(id, fields);\n}\n```\n\n### Step 6: Rollback Procedure\n\n```bash\n#!\u002Fbin\u002Fbash\n# If migration causes issues:\n\n# 1. Revert to previous code\ngit revert HEAD --no-edit\n\n# 2. Deploy previous version\n# (use your deployment tool)\n\n# 3. Verify old API patterns still work\ncurl -s -u \"${BAMBOOHR_API_KEY}:x\" \\\n  -H \"Accept: application\u002Fjson\" \\\n  \"${BASE}\u002Femployees\u002Fdirectory\" | jq '.employees | length'\n\necho \"Rollback complete. Document what failed for next attempt.\"\n```\n\n## Output\n\n- Identified deprecated fields and endpoints\n- Migration code with backward compatibility\n- Compatibility test suite\n- Feature-flagged gradual migration\n- Documented rollback procedure\n\n## Error Handling\n\n| Migration Issue | Detection | Solution |\n|----------------|-----------|----------|\n| Deprecated field returns null | Runtime null checks | Map to replacement field |\n| Endpoint returns 404 | HTTP status monitoring | Check BambooHR changelog |\n| Response schema changed | Zod validation failure | Update schema definitions |\n| New required fields | 400 on create\u002Fupdate | Add required fields to payload |\n\n## Resources\n\n- [BambooHR Past API Changes](https:\u002F\u002Fdocumentation.bamboohr.com\u002Fdocs\u002Fpast-changes-to-the-api)\n- [BambooHR Planned API Changes](https:\u002F\u002Fdocumentation.bamboohr.com\u002Fdocs\u002Fplanned-changes-to-the-api)\n- [BambooHR Field Names](https:\u002F\u002Fdocumentation.bamboohr.com\u002Fdocs\u002Flist-of-field-names)\n\n## Next Steps\n\nFor CI integration during upgrades, see `bamboohr-ci-integration`.\n","# BambooHR Upgrade & Migration\n\n## Overview\n\nGuide for handling BambooHR API changes, migrating from legacy patterns, and proactively detecting deprecations. BambooHR's API is versioned at v1 — breaking changes are announced on their changelog rather than through version bumps.\n\n## Prerequisites\n\n- Current BambooHR integration working\n- Access to BambooHR API changelog\n- Git for version control\n- Test suite available\n\n## Instructions\n\n### Step 1: Check for Announced Changes\n\n```bash\n# Monitor BambooHR's official changelog pages\necho \"Check these URLs before any migration work:\"\necho \"  Past changes:    https:\u002F\u002Fdocumentation.bamboohr.com\u002Fdocs\u002Fpast-changes-to-the-api\"\necho \"  Planned changes: https:\u002F\u002Fdocumentation.bamboohr.com\u002Fdocs\u002Fplanned-changes-to-the-api\"\necho \"  Status page:     https:\u002F\u002Fstatus.bamboohr.com\"\n```\n\n### Step 2: Common Migration Patterns\n\n#### URL Format Migration\n\nBambooHR has used two base URL formats historically:\n\n```typescript\n\u002F\u002F Legacy format (still works)\nconst LEGACY = `https:\u002F\u002Fapi.bamboohr.com\u002Fapi\u002Fgateway.php\u002F${domain}\u002Fv1`;\n\n\u002F\u002F Modern format (equivalent)\nconst MODERN = `https:\u002F\u002F${domain}.bamboohr.com\u002Fapi\u002Fv1`;\n\n\u002F\u002F Migration: both work, but use the gateway.php format for API key auth\n\u002F\u002F The modern format is used for browser-based OAuth flows\n```\n\n#### XML to JSON Migration\n\n```typescript\n\u002F\u002F Legacy: XML responses (default if no Accept header)\nconst xmlRes = await fetch(`${BASE}\u002Femployees\u002Fdirectory`, {\n  headers: { Authorization: AUTH },\n  \u002F\u002F No Accept header — returns XML\n});\n\n\u002F\u002F Current: JSON responses (always set Accept header)\nconst jsonRes = await fetch(`${BASE}\u002Femployees\u002Fdirectory`, {\n  headers: { Authorization: AUTH, Accept: 'application\u002Fjson' },\n});\n\n\u002F\u002F Migration checklist:\n\u002F\u002F - Add 'Accept: application\u002Fjson' to ALL requests\n\u002F\u002F - Replace XML parsing with JSON.parse\n\u002F\u002F - Update response type definitions\n```\n\n#### Employee Endpoint Changes\n\n```typescript\n\u002F\u002F Legacy: using employee ID 0 for \"current user\"\n\u002F\u002F GET \u002Femployees\u002F0\u002F?fields=firstName,lastName\n\u002F\u002F This returns the employee record for the API key's user\n\n\u002F\u002F Current: still works, but prefer explicit employee IDs from directory\nconst dir = await client.getDirectory();\nconst currentUser = dir.employees.find(e => e.workEmail === knownEmail);\n```\n\n### Step 3: Detect Deprecated Field Usage\n\n```typescript\n\u002F\u002F Scan your codebase for BambooHR field references\nconst DEPRECATED_FIELDS = [\n  \u002F\u002F As of 2025, these field aliases may change:\n  'bestEmail',       \u002F\u002F Use 'workEmail' or 'homeEmail' explicitly\n  'fullName1',       \u002F\u002F Use 'displayName' instead\n  'fullName2',       \u002F\u002F Use firstName + lastName\n  'fullName3',       \u002F\u002F Removed\n  'fullName4',       \u002F\u002F Removed\n  'fullName5',       \u002F\u002F Removed\n];\n\nconst CURRENT_FIELD_MAPPING: Record\u003Cstring, string> = {\n  'bestEmail': 'workEmail',\n  'fullName1': 'displayName',\n  'fullName2': 'displayName',  \u002F\u002F Or construct from firstName + lastName\n};\n\nfunction migrateFieldName(oldField: string): string {\n  if (DEPRECATED_FIELDS.includes(oldField)) {\n    const replacement = CURRENT_FIELD_MAPPING[oldField];\n    console.warn(`Deprecated field '${oldField}' — use '${replacement}' instead`);\n    return replacement || oldField;\n  }\n  return oldField;\n}\n```\n\n### Step 4: Migration Testing Strategy\n\n```typescript\n\u002F\u002F tests\u002Fmigration\u002Fbamboohr-compat.test.ts\nimport { describe, it, expect } from 'vitest';\n\ndescribe('BambooHR API Compatibility', () => {\n  it('should handle both old and new field names', async () => {\n    const emp = await client.getEmployee(testId, [\n      'displayName', 'firstName', 'lastName', 'workEmail',\n    ]);\n\n    \u002F\u002F Verify current fields work\n    expect(emp.displayName).toBeTruthy();\n    expect(emp.workEmail).toBeTruthy();\n  });\n\n  it('should handle null fields gracefully', async () => {\n    \u002F\u002F BambooHR may return null for newly added fields\n    const emp = await client.getEmployee(testId, [\n      'firstName', 'lastName', 'supervisor', 'division',\n    ]);\n\n    \u002F\u002F These may be null\u002Fempty for some employees\n    expect(emp.firstName).toBeTruthy();\n    expect(emp.supervisor).toBeDefined(); \u002F\u002F null is valid\n  });\n\n  it('should handle table schema changes', async () => {\n    const jobInfo = await client.getTableRows(testId, 'jobInfo');\n\n    \u002F\u002F Verify required columns still present\n    if (jobInfo.length > 0) {\n      const row = jobInfo[0];\n      expect(row).toHaveProperty('date');\n      expect(row).toHaveProperty('jobTitle');\n    }\n  });\n});\n```\n\n### Step 5: Gradual Migration with Feature Flags\n\n```typescript\ninterface MigrationConfig {\n  useNewEndpoint: boolean;\n  useNewFieldNames: boolean;\n  enableNewWebhookFormat: boolean;\n}\n\nconst MIGRATION_FLAGS: MigrationConfig = {\n  useNewEndpoint: process.env.BAMBOOHR_USE_NEW_ENDPOINT === 'true',\n  useNewFieldNames: true,       \u002F\u002F Already migrated\n  enableNewWebhookFormat: false, \u002F\u002F Testing in staging\n};\n\nasync function getEmployeeData(id: string): Promise\u003CRecord\u003Cstring, string>> {\n  const fields = MIGRATION_FLAGS.useNewFieldNames\n    ? ['displayName', 'workEmail', 'jobTitle']\n    : ['bestEmail', 'fullName1', 'jobTitle']; \u002F\u002F Legacy\n\n  return client.getEmployee(id, fields);\n}\n```\n\n### Step 6: Rollback Procedure\n\n```bash\n#!\u002Fbin\u002Fbash\n# If migration causes issues:\n\n# 1. Revert to previous code\ngit revert HEAD --no-edit\n\n# 2. Deploy previous version\n# (use your deployment tool)\n\n# 3. Verify old API patterns still work\ncurl -s -u \"${BAMBOOHR_API_KEY}:x\" \\\n  -H \"Accept: application\u002Fjson\" \\\n  \"${BASE}\u002Femployees\u002Fdirectory\" | jq '.employees | length'\n\necho \"Rollback complete. Document what failed for next attempt.\"\n```\n\n## Output\n\n- Identified deprecated fields and endpoints\n- Migration code with backward compatibility\n- Compatibility test suite\n- Feature-flagged gradual migration\n- Documented rollback procedure\n\n## Error Handling\n\n| Migration Issue | Detection | Solution |\n|----------------|-----------|----------|\n| Deprecated field returns null | Runtime null checks | Map to replacement field |\n| Endpoint returns 404 | HTTP status monitoring | Check BambooHR changelog |\n| Response schema changed | Zod validation failure | Update schema definitions |\n| New required fields | 400 on create\u002Fupdate | Add required fields to payload |\n\n## Resources\n\n- [BambooHR Past API Changes](https:\u002F\u002Fdocumentation.bamboohr.com\u002Fdocs\u002Fpast-changes-to-the-api)\n- [BambooHR Planned API Changes](https:\u002F\u002Fdocumentation.bamboohr.com\u002Fdocs\u002Fplanned-changes-to-the-api)\n- [BambooHR Field Names](https:\u002F\u002Fdocumentation.bamboohr.com\u002Fdocs\u002Flist-of-field-names)\n\n## Next Steps\n\nFor CI integration during upgrades, see `bamboohr-ci-integration`.\n",{"name":5,"tags":24,"author":29,"license":15,"version":30,"description":31,"allowed-tools":32,"compatible-with":33},[25,26,27,28],"saas","hr","bamboohr","migration","Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Plan and execute BambooHR API migration with breaking change detection.\nUse when BambooHR announces API changes, adapting to deprecated endpoints,\nor migrating from legacy API patterns to current best practices.\nTrigger with phrases like \"upgrade bamboohr\", \"bamboohr migration\",\n\"bamboohr breaking changes\", \"bamboohr API update\", \"bamboohr deprecated\".\n","Read, Write, Edit, Bash(npm:*), Bash(git:*)","claude-code","main","99825ad3f3bcc6597ddcc7294a14e6e922f2b67b","skills\u002Fsaas-packs--bamboohr-pack--bamboohr-upgrade-migration",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":44,"prompt":54,"zipAvailable":55},[45,48,51],{"tool":46,"command":47},"npx","npx skills add jukeyman\u002Fjukeyman-skills --skill bamboohr-upgrade-migration",{"tool":49,"command":50},"bunx","bunx skills add jukeyman\u002Fjukeyman-skills --skill bamboohr-upgrade-migration",{"tool":52,"command":53},"pnpm","pnpm dlx skills add jukeyman\u002Fjukeyman-skills --skill bamboohr-upgrade-migration","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsaas-packs--bamboohr-pack--bamboohr-upgrade-migration\u002FSKILL.md",true,[],[58,65,72,79,86,94],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"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":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"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":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"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":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"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":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":90,"sourceHtmlUrl":91,"categories":92,"keywords":93,"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":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"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",[],[]]