[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78ZGS4F2HPK12Z5285XWH6P":3,"skill-same:01M78ZGS4F2HPK12Z5285XWH6P":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},"01M78ZGS4F2HPK12Z5285XWH6P","documenso-migration-deep-dive",null,"Execute comprehensive Documenso migration strategies for platform switches.\nUse when migrating from other signing platforms, re-platforming to Documenso,\nor performing major infrastructure changes.\nTrigger with phrases like \"migrate to documenso\", \"documenso migration\",\n\"switch to documenso\", \"documenso replatform\", \"replace docusign\".","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--documenso-pack--documenso-migration-deep-dive\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: documenso-migration-deep-dive\ndescription: |\n  Execute comprehensive Documenso migration strategies for platform switches.\n  Use when migrating from other signing platforms, re-platforming to Documenso,\n  or performing major infrastructure changes.\n  Trigger with phrases like \"migrate to documenso\", \"documenso migration\",\n  \"switch to documenso\", \"documenso replatform\", \"replace docusign\".\nallowed-tools: Read, Write, Edit, Bash(npm:*), Bash(node:*)\nversion: 1.0.0\nlicense: MIT\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\ncompatible-with: claude-code, codex, openclaw\ntags: [saas, documenso, migration]\n---\n# Documenso Migration Deep Dive\n\n## Current State\n!`npm list 2>\u002Fdev\u002Fnull | head -10`\n\n## Overview\n\nComprehensive guide for migrating to Documenso from other e-signature platforms (DocuSign, HelloSign, PandaDoc, Adobe Sign). Uses the Strangler Fig pattern for zero-downtime migration with feature flags and rollback support.\n\n## Prerequisites\n\n- Current signing platform documented (APIs, templates, webhooks)\n- Documenso account configured (see `documenso-install-auth`)\n- Feature flag infrastructure (LaunchDarkly, environment variables, etc.)\n- Parallel run capability (both platforms active during migration)\n\n## Migration Strategy: Strangler Fig Pattern\n\n```\nPhase 1: Parallel Systems (Week 1-2)\n┌──────────┐     ┌─────────────┐\n│ Your App │────▶│ Old Platform │  (100% traffic)\n│          │     └─────────────┘\n│          │────▶│  Documenso   │  (shadow: log only, don't send)\n└──────────┘     └─────────────┘\n\nPhase 2: Gradual Cutover (Week 3-4)\n┌──────────┐     ┌─────────────┐\n│ Your App │────▶│ Old Platform │  (50% traffic via feature flag)\n│          │     └─────────────┘\n│          │────▶│  Documenso   │  (50% traffic)\n└──────────┘     └─────────────┘\n\nPhase 3: Full Migration (Week 5+)\n┌──────────┐     ┌─────────────┐\n│ Your App │────▶│  Documenso   │  (100% traffic)\n└──────────┘     └─────────────┘\n                 Old platform decommissioned\n```\n\n## Instructions\n\n### Step 1: Pre-Migration Assessment\n\n```typescript\n\u002F\u002F scripts\u002Fassess-current-system.ts\n\u002F\u002F Inventory your current signing platform usage\n\ninterface MigrationAssessment {\n  platform: string;\n  activeTemplates: number;\n  documentsPerMonth: number;\n  webhookEndpoints: string[];\n  recipientRoles: string[];\n  fieldTypes: string[];\n  integrations: string[];  \u002F\u002F CRM, database, etc.\n}\n\nasync function assessCurrentSystem(): Promise\u003CMigrationAssessment> {\n  \u002F\u002F Example for DocuSign\n  return {\n    platform: \"DocuSign\",\n    activeTemplates: 15,\n    documentsPerMonth: 200,\n    webhookEndpoints: [\n      \"https:\u002F\u002Fapi.yourapp.com\u002Fwebhooks\u002Fdocusign\",\n    ],\n    recipientRoles: [\"Signer\", \"CC\", \"In Person Signer\"],\n    fieldTypes: [\"Signature\", \"Date\", \"Text\", \"Checkbox\", \"Initial\"],\n    integrations: [\"Salesforce\", \"PostgreSQL\"],\n  };\n}\n```\n\n### Step 2: Feature Mapping\n\n| DocuSign | HelloSign | Documenso | Notes |\n|----------|-----------|-----------|-------|\n| Envelope | Signature Request | Document | Documenso v2 also has Envelopes |\n| Template | Template | Template | Create via UI, use via API |\n| Signer | Signer | SIGNER role | Same concept |\n| CC | CC | CC role | Same concept |\n| In Person | N\u002FA | Direct Link | Use embedded signing |\n| Tabs\u002FFields | Form Fields | Fields | SIGNATURE, TEXT, DATE, etc. |\n| Connect (webhooks) | Callbacks | Webhooks | document.completed, etc. |\n| PowerForms | N\u002FA | Direct Links | Public signing URLs |\n\n### Step 3: Template Migration\n\n```typescript\n\u002F\u002F Templates can't be migrated via API — recreate in Documenso\n\u002F\u002F Keep template definitions in code for reproducibility\n\ninterface TemplateDef {\n  name: string;\n  description: string;\n  recipientRoles: Array\u003C{ role: string; placeholder: string }>;\n  fields: Array\u003C{\n    recipientIndex: number;\n    type: string;\n    page: number;\n    x: number;\n    y: number;\n    width: number;\n    height: number;\n  }>;\n}\n\nconst TEMPLATES: TemplateDef[] = [\n  {\n    name: \"NDA — Standard\",\n    description: \"Non-disclosure agreement template\",\n    recipientRoles: [\n      { role: \"SIGNER\", placeholder: \"Counterparty\" },\n      { role: \"CC\", placeholder: \"Legal Team\" },\n    ],\n    fields: [\n      { recipientIndex: 0, type: \"SIGNATURE\", page: 2, x: 10, y: 80, width: 30, height: 5 },\n      { recipientIndex: 0, type: \"DATE\", page: 2, x: 60, y: 80, width: 20, height: 3 },\n      { recipientIndex: 0, type: \"NAME\", page: 2, x: 10, y: 75, width: 30, height: 3 },\n    ],\n  },\n  \u002F\u002F ... more templates\n];\n\n\u002F\u002F Instructions: create each template in the Documenso UI using these specs\n\u002F\u002F Then record the template IDs in your config\n```\n\n### Step 4: Webhook Migration\n\n```typescript\n\u002F\u002F Map old platform events to Documenso events\nconst EVENT_MAPPING: Record\u003Cstring, string> = {\n  \u002F\u002F DocuSign → Documenso\n  \"envelope-completed\": \"document.completed\",\n  \"envelope-sent\": \"document.sent\",\n  \"envelope-declined\": \"document.rejected\",\n  \"envelope-voided\": \"document.cancelled\",\n  \"recipient-completed\": \"document.signed\",\n\n  \u002F\u002F HelloSign → Documenso\n  \"signature_request_all_signed\": \"document.completed\",\n  \"signature_request_sent\": \"document.sent\",\n  \"signature_request_declined\": \"document.rejected\",\n  \"signature_request_signed\": \"document.signed\",\n};\n\n\u002F\u002F Unified handler that works with both platforms during migration\nasync function handleSigningEvent(source: \"old\" | \"documenso\", event: string, payload: any) {\n  const normalizedEvent = source === \"old\"\n    ? EVENT_MAPPING[event] ?? event\n    : event;\n\n  switch (normalizedEvent) {\n    case \"document.completed\":\n      await onDocumentCompleted(payload);\n      break;\n    case \"document.rejected\":\n      await onDocumentRejected(payload);\n      break;\n  }\n}\n```\n\n### Step 5: Dual-Write with Feature Flag\n\n```typescript\n\u002F\u002F src\u002Fsigning\u002Frouter.ts\nconst USE_DOCUMENSO = process.env.USE_DOCUMENSO === \"true\";\n\nasync function sendForSigning(request: SigningRequest) {\n  if (USE_DOCUMENSO) {\n    return sendViaDocumenso(request);\n  }\n  return sendViaLegacy(request);\n}\n\n\u002F\u002F During parallel phase: send via both, compare results\nasync function sendForSigningParallel(request: SigningRequest) {\n  const legacyResult = await sendViaLegacy(request);\n\n  \u002F\u002F Shadow-send to Documenso (don't actually send to recipients)\n  try {\n    const doc = await documensoClient.documents.createV0({ title: request.title });\n    \u002F\u002F Don't call sendV0 — just verify creation works\n    await documensoClient.documents.deleteV0(doc.documentId);\n    console.log(\"Documenso shadow test: OK\");\n  } catch (err) {\n    console.error(\"Documenso shadow test: FAIL\", err);\n  }\n\n  return legacyResult;\n}\n```\n\n### Step 6: Rollback Procedure\n\n```bash\n# If Documenso migration causes issues:\n\n# 1. Disable feature flag\nexport USE_DOCUMENSO=false\n# Or toggle in LaunchDarkly\u002Ffeature flag service\n\n# 2. Deploy the change\n# All new signing requests go to old platform immediately\n\n# 3. Handle in-flight Documenso documents\n# Documents already sent via Documenso will complete there\n# No action needed — they just use a different platform\n\n# 4. Investigate and fix the issue\n# Review logs, fix the integration, re-enable gradually\n```\n\n## Migration Timeline\n\n| Week | Phase | Action | Risk |\n|------|-------|--------|------|\n| 1 | Assessment | Inventory templates, webhooks, integrations | Low |\n| 2 | Setup | Configure Documenso, recreate templates | Low |\n| 3 | Shadow | Run parallel, compare results (no live traffic) | Low |\n| 4 | Pilot | 10% of new documents via Documenso | Medium |\n| 5 | Expand | 50% of new documents via Documenso | Medium |\n| 6 | Cutover | 100% via Documenso, old platform read-only | Medium |\n| 8 | Decommission | Remove old platform code and webhooks | Low |\n\n## Error Handling\n\n| Migration Issue | Cause | Solution |\n|----------------|-------|----------|\n| Field position different | Different coordinate systems | Map percentage-based (Documenso) from pixel-based (old) |\n| Webhook format change | Different payload structure | Use event normalizer\u002Fadapter |\n| Template missing | Not recreated in Documenso | Create from template definitions |\n| High error rate during cutover | Integration bug | Pause rollout, rollback, investigate |\n\n## Resources\n\n- [Strangler Fig Pattern](https:\u002F\u002Fmartinfowler.com\u002Fbliki\u002FStranglerFigApplication.html)\n- [Documenso Documentation](https:\u002F\u002Fdocs.documenso.com)\n- [Documenso vs DocuSign](https:\u002F\u002Fdocumenso.com\u002Fblog)\n- [Feature Flags Best Practices](https:\u002F\u002Flaunchdarkly.com\u002Fblog\u002Ffeature-flags-best-practices\u002F)\n\n## Next Steps\n\nReview related skills for comprehensive coverage of your new Documenso integration.\n","# Documenso Migration Deep Dive\n\n## Current State\n!`npm list 2>\u002Fdev\u002Fnull | head -10`\n\n## Overview\n\nComprehensive guide for migrating to Documenso from other e-signature platforms (DocuSign, HelloSign, PandaDoc, Adobe Sign). Uses the Strangler Fig pattern for zero-downtime migration with feature flags and rollback support.\n\n## Prerequisites\n\n- Current signing platform documented (APIs, templates, webhooks)\n- Documenso account configured (see `documenso-install-auth`)\n- Feature flag infrastructure (LaunchDarkly, environment variables, etc.)\n- Parallel run capability (both platforms active during migration)\n\n## Migration Strategy: Strangler Fig Pattern\n\n```\nPhase 1: Parallel Systems (Week 1-2)\n┌──────────┐     ┌─────────────┐\n│ Your App │────▶│ Old Platform │  (100% traffic)\n│          │     └─────────────┘\n│          │────▶│  Documenso   │  (shadow: log only, don't send)\n└──────────┘     └─────────────┘\n\nPhase 2: Gradual Cutover (Week 3-4)\n┌──────────┐     ┌─────────────┐\n│ Your App │────▶│ Old Platform │  (50% traffic via feature flag)\n│          │     └─────────────┘\n│          │────▶│  Documenso   │  (50% traffic)\n└──────────┘     └─────────────┘\n\nPhase 3: Full Migration (Week 5+)\n┌──────────┐     ┌─────────────┐\n│ Your App │────▶│  Documenso   │  (100% traffic)\n└──────────┘     └─────────────┘\n                 Old platform decommissioned\n```\n\n## Instructions\n\n### Step 1: Pre-Migration Assessment\n\n```typescript\n\u002F\u002F scripts\u002Fassess-current-system.ts\n\u002F\u002F Inventory your current signing platform usage\n\ninterface MigrationAssessment {\n  platform: string;\n  activeTemplates: number;\n  documentsPerMonth: number;\n  webhookEndpoints: string[];\n  recipientRoles: string[];\n  fieldTypes: string[];\n  integrations: string[];  \u002F\u002F CRM, database, etc.\n}\n\nasync function assessCurrentSystem(): Promise\u003CMigrationAssessment> {\n  \u002F\u002F Example for DocuSign\n  return {\n    platform: \"DocuSign\",\n    activeTemplates: 15,\n    documentsPerMonth: 200,\n    webhookEndpoints: [\n      \"https:\u002F\u002Fapi.yourapp.com\u002Fwebhooks\u002Fdocusign\",\n    ],\n    recipientRoles: [\"Signer\", \"CC\", \"In Person Signer\"],\n    fieldTypes: [\"Signature\", \"Date\", \"Text\", \"Checkbox\", \"Initial\"],\n    integrations: [\"Salesforce\", \"PostgreSQL\"],\n  };\n}\n```\n\n### Step 2: Feature Mapping\n\n| DocuSign | HelloSign | Documenso | Notes |\n|----------|-----------|-----------|-------|\n| Envelope | Signature Request | Document | Documenso v2 also has Envelopes |\n| Template | Template | Template | Create via UI, use via API |\n| Signer | Signer | SIGNER role | Same concept |\n| CC | CC | CC role | Same concept |\n| In Person | N\u002FA | Direct Link | Use embedded signing |\n| Tabs\u002FFields | Form Fields | Fields | SIGNATURE, TEXT, DATE, etc. |\n| Connect (webhooks) | Callbacks | Webhooks | document.completed, etc. |\n| PowerForms | N\u002FA | Direct Links | Public signing URLs |\n\n### Step 3: Template Migration\n\n```typescript\n\u002F\u002F Templates can't be migrated via API — recreate in Documenso\n\u002F\u002F Keep template definitions in code for reproducibility\n\ninterface TemplateDef {\n  name: string;\n  description: string;\n  recipientRoles: Array\u003C{ role: string; placeholder: string }>;\n  fields: Array\u003C{\n    recipientIndex: number;\n    type: string;\n    page: number;\n    x: number;\n    y: number;\n    width: number;\n    height: number;\n  }>;\n}\n\nconst TEMPLATES: TemplateDef[] = [\n  {\n    name: \"NDA — Standard\",\n    description: \"Non-disclosure agreement template\",\n    recipientRoles: [\n      { role: \"SIGNER\", placeholder: \"Counterparty\" },\n      { role: \"CC\", placeholder: \"Legal Team\" },\n    ],\n    fields: [\n      { recipientIndex: 0, type: \"SIGNATURE\", page: 2, x: 10, y: 80, width: 30, height: 5 },\n      { recipientIndex: 0, type: \"DATE\", page: 2, x: 60, y: 80, width: 20, height: 3 },\n      { recipientIndex: 0, type: \"NAME\", page: 2, x: 10, y: 75, width: 30, height: 3 },\n    ],\n  },\n  \u002F\u002F ... more templates\n];\n\n\u002F\u002F Instructions: create each template in the Documenso UI using these specs\n\u002F\u002F Then record the template IDs in your config\n```\n\n### Step 4: Webhook Migration\n\n```typescript\n\u002F\u002F Map old platform events to Documenso events\nconst EVENT_MAPPING: Record\u003Cstring, string> = {\n  \u002F\u002F DocuSign → Documenso\n  \"envelope-completed\": \"document.completed\",\n  \"envelope-sent\": \"document.sent\",\n  \"envelope-declined\": \"document.rejected\",\n  \"envelope-voided\": \"document.cancelled\",\n  \"recipient-completed\": \"document.signed\",\n\n  \u002F\u002F HelloSign → Documenso\n  \"signature_request_all_signed\": \"document.completed\",\n  \"signature_request_sent\": \"document.sent\",\n  \"signature_request_declined\": \"document.rejected\",\n  \"signature_request_signed\": \"document.signed\",\n};\n\n\u002F\u002F Unified handler that works with both platforms during migration\nasync function handleSigningEvent(source: \"old\" | \"documenso\", event: string, payload: any) {\n  const normalizedEvent = source === \"old\"\n    ? EVENT_MAPPING[event] ?? event\n    : event;\n\n  switch (normalizedEvent) {\n    case \"document.completed\":\n      await onDocumentCompleted(payload);\n      break;\n    case \"document.rejected\":\n      await onDocumentRejected(payload);\n      break;\n  }\n}\n```\n\n### Step 5: Dual-Write with Feature Flag\n\n```typescript\n\u002F\u002F src\u002Fsigning\u002Frouter.ts\nconst USE_DOCUMENSO = process.env.USE_DOCUMENSO === \"true\";\n\nasync function sendForSigning(request: SigningRequest) {\n  if (USE_DOCUMENSO) {\n    return sendViaDocumenso(request);\n  }\n  return sendViaLegacy(request);\n}\n\n\u002F\u002F During parallel phase: send via both, compare results\nasync function sendForSigningParallel(request: SigningRequest) {\n  const legacyResult = await sendViaLegacy(request);\n\n  \u002F\u002F Shadow-send to Documenso (don't actually send to recipients)\n  try {\n    const doc = await documensoClient.documents.createV0({ title: request.title });\n    \u002F\u002F Don't call sendV0 — just verify creation works\n    await documensoClient.documents.deleteV0(doc.documentId);\n    console.log(\"Documenso shadow test: OK\");\n  } catch (err) {\n    console.error(\"Documenso shadow test: FAIL\", err);\n  }\n\n  return legacyResult;\n}\n```\n\n### Step 6: Rollback Procedure\n\n```bash\n# If Documenso migration causes issues:\n\n# 1. Disable feature flag\nexport USE_DOCUMENSO=false\n# Or toggle in LaunchDarkly\u002Ffeature flag service\n\n# 2. Deploy the change\n# All new signing requests go to old platform immediately\n\n# 3. Handle in-flight Documenso documents\n# Documents already sent via Documenso will complete there\n# No action needed — they just use a different platform\n\n# 4. Investigate and fix the issue\n# Review logs, fix the integration, re-enable gradually\n```\n\n## Migration Timeline\n\n| Week | Phase | Action | Risk |\n|------|-------|--------|------|\n| 1 | Assessment | Inventory templates, webhooks, integrations | Low |\n| 2 | Setup | Configure Documenso, recreate templates | Low |\n| 3 | Shadow | Run parallel, compare results (no live traffic) | Low |\n| 4 | Pilot | 10% of new documents via Documenso | Medium |\n| 5 | Expand | 50% of new documents via Documenso | Medium |\n| 6 | Cutover | 100% via Documenso, old platform read-only | Medium |\n| 8 | Decommission | Remove old platform code and webhooks | Low |\n\n## Error Handling\n\n| Migration Issue | Cause | Solution |\n|----------------|-------|----------|\n| Field position different | Different coordinate systems | Map percentage-based (Documenso) from pixel-based (old) |\n| Webhook format change | Different payload structure | Use event normalizer\u002Fadapter |\n| Template missing | Not recreated in Documenso | Create from template definitions |\n| High error rate during cutover | Integration bug | Pause rollout, rollback, investigate |\n\n## Resources\n\n- [Strangler Fig Pattern](https:\u002F\u002Fmartinfowler.com\u002Fbliki\u002FStranglerFigApplication.html)\n- [Documenso Documentation](https:\u002F\u002Fdocs.documenso.com)\n- [Documenso vs DocuSign](https:\u002F\u002Fdocumenso.com\u002Fblog)\n- [Feature Flags Best Practices](https:\u002F\u002Flaunchdarkly.com\u002Fblog\u002Ffeature-flags-best-practices\u002F)\n\n## Next Steps\n\nReview related skills for comprehensive coverage of your new Documenso integration.\n",{"name":5,"tags":24,"author":28,"license":15,"version":29,"description":30,"allowed-tools":31,"compatible-with":32},[25,26,27],"saas","documenso","migration","Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Execute comprehensive Documenso migration strategies for platform switches.\nUse when migrating from other signing platforms, re-platforming to Documenso,\nor performing major infrastructure changes.\nTrigger with phrases like \"migrate to documenso\", \"documenso migration\",\n\"switch to documenso\", \"documenso replatform\", \"replace docusign\".\n","Read, Write, Edit, Bash(npm:*), Bash(node:*)","claude-code, codex, openclaw","main","99825ad3f3bcc6597ddcc7294a14e6e922f2b67b","skills\u002Fsaas-packs--documenso-pack--documenso-migration-deep-dive",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 documenso-migration-deep-dive",{"tool":48,"command":49},"bunx","bunx skills add jukeyman\u002Fjukeyman-skills --skill documenso-migration-deep-dive",{"tool":51,"command":52},"pnpm","pnpm dlx skills add jukeyman\u002Fjukeyman-skills --skill documenso-migration-deep-dive","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsaas-packs--documenso-pack--documenso-migration-deep-dive\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",[],[]]