[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7910M1GN0S2C8MN9P9KJSZ4":3,"skill-same:01M7910M1GN0S2C8MN9P9KJSZ4":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},"01M7910M1GN0S2C8MN9P9KJSZ4","granola-reference-architecture",null,"Enterprise reference architecture for meeting management with Granola.\nUse when designing org-wide meeting workflows, planning integration topology,\nor architecting meeting-to-action pipelines across departments.\nTrigger: \"granola architecture\", \"granola enterprise design\",\n\"granola system design\", \"meeting system architecture\".","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--granola-pack--granola-reference-architecture\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: granola-reference-architecture\ndescription: |\n  Enterprise reference architecture for meeting management with Granola.\n  Use when designing org-wide meeting workflows, planning integration topology,\n  or architecting meeting-to-action pipelines across departments.\n  Trigger: \"granola architecture\", \"granola enterprise design\",\n  \"granola system design\", \"meeting system architecture\".\nallowed-tools: Read, Write, Edit\nversion: 1.0.0\nlicense: MIT\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\ncompatible-with: claude-code, codex, openclaw\ntags: [saas, granola, architecture, enterprise]\n---\n# Granola Reference Architecture\n\n## Overview\nEnterprise reference architecture for deploying Granola as the meeting intelligence platform across an organization. Covers the core capture pipeline, Zapier middleware routing, multi-workspace topology, security layers, and integration patterns for Slack, Notion, CRM, and task management.\n\n## Prerequisites\n- Granola Enterprise plan ($35+\u002Fuser\u002Fmonth)\n- Zapier Professional or higher (for multi-step Zaps and Paths)\n- Destination systems provisioned (Slack, Notion, CRM, Linear\u002FJira)\n- IT architecture review completed\n\n## Instructions\n\n### Step 1 — Core Pipeline Architecture\n\n```\n┌─────────────────────────────────────────────────────────┐\n│                    MEETING PLATFORMS                      │\n│  Zoom  |  Google Meet  |  Microsoft Teams  |  Slack Huddle│\n└──────────────────────┬──────────────────────────────────┘\n                       │ System audio capture (no bot)\n                       ▼\n┌─────────────────────────────────────────────────────────┐\n│                    GRANOLA PLATFORM                       │\n│                                                          │\n│  ┌──────────┐  ┌──────────────┐  ┌─────────────────┐   │\n│  │ Audio    │→ │ Transcription │→ │ AI Enhancement  │   │\n│  │ Capture  │  │ (GPT-4o\u002F     │  │ (Notes + Trans- │   │\n│  │ (local)  │  │  Claude)     │  │  cript merge)   │   │\n│  └──────────┘  └──────────────┘  └────────┬────────┘   │\n│                                            │             │\n│  ┌────────────────┐  ┌──────────────────┐  │            │\n│  │ People &       │  │ Folders          │  │            │\n│  │ Companies      │  │ (routing rules)  │←─┘            │\n│  │ (built-in CRM) │  └────────┬─────────┘              │\n│  └────────────────┘           │                         │\n└───────────────────────────────┼─────────────────────────┘\n                                │\n            ┌───────────────────┼───────────────────┐\n            │           ZAPIER MIDDLEWARE            │\n            │                                       │\n            │  ┌─────────┐  ┌─────────┐  ┌──────┐ │\n            │  │ Filter  │→ │ Route   │→ │ Act  │ │\n            │  │ (type\u002F  │  │ (paths  │  │      │ │\n            │  │ attendee)│  │ \u002Frules) │  │      │ │\n            │  └─────────┘  └─────────┘  └──────┘ │\n            └──────┬──────────┬──────────┬─────────┘\n                   │          │          │\n        ┌──────────┴──┐ ┌────┴────┐ ┌───┴────────┐\n        │ COMMUNICATE │ │ ARCHIVE │ │ ACT        │\n        │ Slack       │ │ Notion  │ │ Linear\u002FJira│\n        │ Email       │ │ Drive   │ │ Asana      │\n        │ Teams       │ │ GCS\u002FS3  │ │ HubSpot    │\n        └─────────────┘ └─────────┘ └────────────┘\n```\n\n### Step 2 — Folder-Based Routing Topology\n\nDesign folder structure to drive automated routing:\n\n| Folder | Trigger Type | Destinations | Permissions |\n|--------|-------------|-------------|-------------|\n| `Sales \u002F Discovery` | Auto | Slack #sales + HubSpot Deal + Follow-up Email | Sales team |\n| `Sales \u002F Demo` | Auto | Slack #sales + HubSpot Contact | Sales team |\n| `Engineering \u002F Sprint` | Auto | Slack #eng + Linear tasks + Notion wiki | Engineering |\n| `Engineering \u002F Architecture` | Auto | Slack #eng-arch + Notion ADR database | Senior engineers |\n| `Product \u002F Customer Feedback` | Auto | Slack #product + Notion feedback DB | Product team |\n| `Leadership \u002F All-Hands` | Auto | Slack #general + Google Drive archive | All |\n| `Leadership \u002F Board` | Manual only | Private Notion, no Slack | Executives only |\n| `HR \u002F Interviews` | Manual share | Greenhouse scorecard | Hiring managers |\n| `HR \u002F 1-on-1s` | None | Private, no automation | Individual |\n\n### Step 3 — Multi-Workspace Topology\n\n```\nOrganization (Enterprise)\n├── Engineering Workspace\n│   ├── Folders: Sprint, Architecture, Standup, Retro\n│   ├── Integrations: Linear, Notion, Slack #engineering\n│   └── Retention: 2 years notes, 90 days transcripts\n│\n├── Sales Workspace\n│   ├── Folders: Discovery, Demo, Pipeline Review\n│   ├── Integrations: HubSpot, Slack #sales, Gmail\n│   └── Retention: 1 year notes, 90 days transcripts\n│\n├── Product Workspace\n│   ├── Folders: Customer Feedback, Design Review, PRD\n│   ├── Integrations: Notion, Linear, Slack #product\n│   └── Retention: 2 years notes, 90 days transcripts\n│\n├── HR Workspace (Confidential)\n│   ├── Folders: Interviews, 1-on-1s, Performance\n│   ├── Integrations: Greenhouse (via Zapier)\n│   ├── Retention: 30 days notes, 7 days transcripts\n│   └── Restrictions: No external sharing, MFA required\n│\n└── Executive Workspace (Confidential)\n    ├── Folders: Board, Strategy, M&A\n    ├── Integrations: Private Notion only\n    ├── Retention: Custom (legal hold capable)\n    └── Restrictions: IP allowlist, 4-hour session timeout\n```\n\n### Step 4 — Security Architecture\n\n```\nAuthentication Layer:\n  SSO (Okta\u002FAzure AD) → SCIM provisioning → JIT workspace assignment\n\nData Protection:\n  In Transit: TLS 1.3 (all API calls)\n  At Rest: AES-256 (server-side storage)\n  Local: FileVault\u002FBitLocker (cache-v3.json encryption)\n\nAccess Control:\n  Org Owner → Workspace Admin → Team Lead → Member → Viewer → Guest\n  ↓\n  SSO groups mapped to Granola roles per workspace\n\nData Classification:\n  Confidential: HR, Legal, Board (restricted sharing, short retention)\n  Internal: Engineering, Product (team sharing, standard retention)\n  External-Facing: Sales, Customer Success (CRM sync allowed)\n\nCompliance:\n  SOC 2 Type 2: Certified (July 2025)\n  GDPR: DPA available, data export\u002Fdeletion supported\n  AI Training: Opt-out enforced org-wide (Enterprise default)\n```\n\n### Step 5 — Integration Data Flow Patterns\n\n**Pattern A: Standard Meeting (Parallel)**\n```\nNote enhanced → Folder trigger fires\n  ├─→ Slack notification (immediate)\n  ├─→ Notion archive (immediate)\n  └─→ Linear tasks (per action item)\n```\n\n**Pattern B: Sales Meeting (Sequential)**\n```\nNote enhanced → \"Sales \u002F Discovery\" folder\n  │\n  ├─→ HubSpot: Find Contact by attendee email\n  │     ├─→ Found: Log meeting note on Contact\n  │     └─→ Not found: Create Contact, then log note\n  │\n  ├─→ ChatGPT: Generate BANT analysis + follow-up email\n  │     └─→ Gmail: Create draft to external attendees\n  │\n  └─→ Slack: Post summary to #sales with deal context\n```\n\n**Pattern C: Executive Meeting (Restricted)**\n```\nNote enhanced → \"Board\" folder (no auto-trigger)\n  │\n  └─→ Manual share to private Notion database only\n       └─→ Link expires in 7 days\n```\n\n### Step 6 — Disaster Recovery & Data Export\n\n```\nBackup Strategy:\n  Primary: Granola cloud storage (server-side, encrypted)\n  Secondary: Local cache (cache-v3.json on each user's device)\n  Tertiary: Nightly export to cloud storage (via Zapier + GCS\u002FS3)\n\nRecovery Procedures:\n  1. User device loss: Re-authenticate, data syncs from server\n  2. Integration outage: Zapier retries automatically; monitor Zap history\n  3. Granola service outage: Manual notes during outage; capture resumes on recovery\n  4. Data export request: Enterprise API bulk export or per-user Settings > Data > Export\n```\n\n## Output\n- Complete meeting ecosystem architecture documented\n- Folder-based routing configured per department\n- Multi-workspace topology deployed with appropriate isolation\n- Security and compliance controls mapped to org requirements\n- Disaster recovery plan established\n\n## Error Handling\n\n| Error | Cause | Fix |\n|-------|-------|-----|\n| Notes routing to wrong destination | Filter logic error in Zapier Paths | Review path conditions, test with sample data |\n| Cross-workspace access denied | Permission boundaries working correctly | Elevate user role or add to target workspace |\n| Integration sync delay > 5 min | Zapier queue or destination rate limit | Add delay step, check destination API limits |\n| Missing CRM updates for new contacts | Native integration doesn't auto-create | Add Zapier \"Find or Create\" step |\n| Audit log gaps | Logging not enabled on workspace | Enable in Workspace Settings > Security |\n\n## Resources\n- [Granola Enterprise](https:\u002F\u002Fwww.granola.ai\u002Fsecurity)\n- [Integrations Overview](https:\u002F\u002Fdocs.granola.ai\u002Fhelp-center\u002Fsharing\u002Fintegrations\u002Fintegrations-with-granola)\n- [Enterprise API](https:\u002F\u002Fdocs.granola.ai\u002Fhelp-center\u002Fsharing\u002Fintegrations\u002Fenterprise-api)\n- [Security Standards](https:\u002F\u002Fdocs.granola.ai\u002Fhelp-center\u002Fconsent-security-privacy\u002Four-security-standards)\n\n## Next Steps\nProceed to `granola-multi-env-setup` for workspace creation and configuration.\n","# Granola Reference Architecture\n\n## Overview\nEnterprise reference architecture for deploying Granola as the meeting intelligence platform across an organization. Covers the core capture pipeline, Zapier middleware routing, multi-workspace topology, security layers, and integration patterns for Slack, Notion, CRM, and task management.\n\n## Prerequisites\n- Granola Enterprise plan ($35+\u002Fuser\u002Fmonth)\n- Zapier Professional or higher (for multi-step Zaps and Paths)\n- Destination systems provisioned (Slack, Notion, CRM, Linear\u002FJira)\n- IT architecture review completed\n\n## Instructions\n\n### Step 1 — Core Pipeline Architecture\n\n```\n┌─────────────────────────────────────────────────────────┐\n│                    MEETING PLATFORMS                      │\n│  Zoom  |  Google Meet  |  Microsoft Teams  |  Slack Huddle│\n└──────────────────────┬──────────────────────────────────┘\n                       │ System audio capture (no bot)\n                       ▼\n┌─────────────────────────────────────────────────────────┐\n│                    GRANOLA PLATFORM                       │\n│                                                          │\n│  ┌──────────┐  ┌──────────────┐  ┌─────────────────┐   │\n│  │ Audio    │→ │ Transcription │→ │ AI Enhancement  │   │\n│  │ Capture  │  │ (GPT-4o\u002F     │  │ (Notes + Trans- │   │\n│  │ (local)  │  │  Claude)     │  │  cript merge)   │   │\n│  └──────────┘  └──────────────┘  └────────┬────────┘   │\n│                                            │             │\n│  ┌────────────────┐  ┌──────────────────┐  │            │\n│  │ People &       │  │ Folders          │  │            │\n│  │ Companies      │  │ (routing rules)  │←─┘            │\n│  │ (built-in CRM) │  └────────┬─────────┘              │\n│  └────────────────┘           │                         │\n└───────────────────────────────┼─────────────────────────┘\n                                │\n            ┌───────────────────┼───────────────────┐\n            │           ZAPIER MIDDLEWARE            │\n            │                                       │\n            │  ┌─────────┐  ┌─────────┐  ┌──────┐ │\n            │  │ Filter  │→ │ Route   │→ │ Act  │ │\n            │  │ (type\u002F  │  │ (paths  │  │      │ │\n            │  │ attendee)│  │ \u002Frules) │  │      │ │\n            │  └─────────┘  └─────────┘  └──────┘ │\n            └──────┬──────────┬──────────┬─────────┘\n                   │          │          │\n        ┌──────────┴──┐ ┌────┴────┐ ┌───┴────────┐\n        │ COMMUNICATE │ │ ARCHIVE │ │ ACT        │\n        │ Slack       │ │ Notion  │ │ Linear\u002FJira│\n        │ Email       │ │ Drive   │ │ Asana      │\n        │ Teams       │ │ GCS\u002FS3  │ │ HubSpot    │\n        └─────────────┘ └─────────┘ └────────────┘\n```\n\n### Step 2 — Folder-Based Routing Topology\n\nDesign folder structure to drive automated routing:\n\n| Folder | Trigger Type | Destinations | Permissions |\n|--------|-------------|-------------|-------------|\n| `Sales \u002F Discovery` | Auto | Slack #sales + HubSpot Deal + Follow-up Email | Sales team |\n| `Sales \u002F Demo` | Auto | Slack #sales + HubSpot Contact | Sales team |\n| `Engineering \u002F Sprint` | Auto | Slack #eng + Linear tasks + Notion wiki | Engineering |\n| `Engineering \u002F Architecture` | Auto | Slack #eng-arch + Notion ADR database | Senior engineers |\n| `Product \u002F Customer Feedback` | Auto | Slack #product + Notion feedback DB | Product team |\n| `Leadership \u002F All-Hands` | Auto | Slack #general + Google Drive archive | All |\n| `Leadership \u002F Board` | Manual only | Private Notion, no Slack | Executives only |\n| `HR \u002F Interviews` | Manual share | Greenhouse scorecard | Hiring managers |\n| `HR \u002F 1-on-1s` | None | Private, no automation | Individual |\n\n### Step 3 — Multi-Workspace Topology\n\n```\nOrganization (Enterprise)\n├── Engineering Workspace\n│   ├── Folders: Sprint, Architecture, Standup, Retro\n│   ├── Integrations: Linear, Notion, Slack #engineering\n│   └── Retention: 2 years notes, 90 days transcripts\n│\n├── Sales Workspace\n│   ├── Folders: Discovery, Demo, Pipeline Review\n│   ├── Integrations: HubSpot, Slack #sales, Gmail\n│   └── Retention: 1 year notes, 90 days transcripts\n│\n├── Product Workspace\n│   ├── Folders: Customer Feedback, Design Review, PRD\n│   ├── Integrations: Notion, Linear, Slack #product\n│   └── Retention: 2 years notes, 90 days transcripts\n│\n├── HR Workspace (Confidential)\n│   ├── Folders: Interviews, 1-on-1s, Performance\n│   ├── Integrations: Greenhouse (via Zapier)\n│   ├── Retention: 30 days notes, 7 days transcripts\n│   └── Restrictions: No external sharing, MFA required\n│\n└── Executive Workspace (Confidential)\n    ├── Folders: Board, Strategy, M&A\n    ├── Integrations: Private Notion only\n    ├── Retention: Custom (legal hold capable)\n    └── Restrictions: IP allowlist, 4-hour session timeout\n```\n\n### Step 4 — Security Architecture\n\n```\nAuthentication Layer:\n  SSO (Okta\u002FAzure AD) → SCIM provisioning → JIT workspace assignment\n\nData Protection:\n  In Transit: TLS 1.3 (all API calls)\n  At Rest: AES-256 (server-side storage)\n  Local: FileVault\u002FBitLocker (cache-v3.json encryption)\n\nAccess Control:\n  Org Owner → Workspace Admin → Team Lead → Member → Viewer → Guest\n  ↓\n  SSO groups mapped to Granola roles per workspace\n\nData Classification:\n  Confidential: HR, Legal, Board (restricted sharing, short retention)\n  Internal: Engineering, Product (team sharing, standard retention)\n  External-Facing: Sales, Customer Success (CRM sync allowed)\n\nCompliance:\n  SOC 2 Type 2: Certified (July 2025)\n  GDPR: DPA available, data export\u002Fdeletion supported\n  AI Training: Opt-out enforced org-wide (Enterprise default)\n```\n\n### Step 5 — Integration Data Flow Patterns\n\n**Pattern A: Standard Meeting (Parallel)**\n```\nNote enhanced → Folder trigger fires\n  ├─→ Slack notification (immediate)\n  ├─→ Notion archive (immediate)\n  └─→ Linear tasks (per action item)\n```\n\n**Pattern B: Sales Meeting (Sequential)**\n```\nNote enhanced → \"Sales \u002F Discovery\" folder\n  │\n  ├─→ HubSpot: Find Contact by attendee email\n  │     ├─→ Found: Log meeting note on Contact\n  │     └─→ Not found: Create Contact, then log note\n  │\n  ├─→ ChatGPT: Generate BANT analysis + follow-up email\n  │     └─→ Gmail: Create draft to external attendees\n  │\n  └─→ Slack: Post summary to #sales with deal context\n```\n\n**Pattern C: Executive Meeting (Restricted)**\n```\nNote enhanced → \"Board\" folder (no auto-trigger)\n  │\n  └─→ Manual share to private Notion database only\n       └─→ Link expires in 7 days\n```\n\n### Step 6 — Disaster Recovery & Data Export\n\n```\nBackup Strategy:\n  Primary: Granola cloud storage (server-side, encrypted)\n  Secondary: Local cache (cache-v3.json on each user's device)\n  Tertiary: Nightly export to cloud storage (via Zapier + GCS\u002FS3)\n\nRecovery Procedures:\n  1. User device loss: Re-authenticate, data syncs from server\n  2. Integration outage: Zapier retries automatically; monitor Zap history\n  3. Granola service outage: Manual notes during outage; capture resumes on recovery\n  4. Data export request: Enterprise API bulk export or per-user Settings > Data > Export\n```\n\n## Output\n- Complete meeting ecosystem architecture documented\n- Folder-based routing configured per department\n- Multi-workspace topology deployed with appropriate isolation\n- Security and compliance controls mapped to org requirements\n- Disaster recovery plan established\n\n## Error Handling\n\n| Error | Cause | Fix |\n|-------|-------|-----|\n| Notes routing to wrong destination | Filter logic error in Zapier Paths | Review path conditions, test with sample data |\n| Cross-workspace access denied | Permission boundaries working correctly | Elevate user role or add to target workspace |\n| Integration sync delay > 5 min | Zapier queue or destination rate limit | Add delay step, check destination API limits |\n| Missing CRM updates for new contacts | Native integration doesn't auto-create | Add Zapier \"Find or Create\" step |\n| Audit log gaps | Logging not enabled on workspace | Enable in Workspace Settings > Security |\n\n## Resources\n- [Granola Enterprise](https:\u002F\u002Fwww.granola.ai\u002Fsecurity)\n- [Integrations Overview](https:\u002F\u002Fdocs.granola.ai\u002Fhelp-center\u002Fsharing\u002Fintegrations\u002Fintegrations-with-granola)\n- [Enterprise API](https:\u002F\u002Fdocs.granola.ai\u002Fhelp-center\u002Fsharing\u002Fintegrations\u002Fenterprise-api)\n- [Security Standards](https:\u002F\u002Fdocs.granola.ai\u002Fhelp-center\u002Fconsent-security-privacy\u002Four-security-standards)\n\n## Next Steps\nProceed to `granola-multi-env-setup` for workspace creation and configuration.\n",{"name":5,"tags":24,"author":29,"license":15,"version":30,"description":31,"allowed-tools":32,"compatible-with":33},[25,26,27,28],"saas","granola","architecture","enterprise","Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Enterprise reference architecture for meeting management with Granola.\nUse when designing org-wide meeting workflows, planning integration topology,\nor architecting meeting-to-action pipelines across departments.\nTrigger: \"granola architecture\", \"granola enterprise design\",\n\"granola system design\", \"meeting system architecture\".\n","Read, Write, Edit","claude-code, codex, openclaw","main","99825ad3f3bcc6597ddcc7294a14e6e922f2b67b","skills\u002Fsaas-packs--granola-pack--granola-reference-architecture",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 granola-reference-architecture",{"tool":49,"command":50},"bunx","bunx skills add jukeyman\u002Fjukeyman-skills --skill granola-reference-architecture",{"tool":52,"command":53},"pnpm","pnpm dlx skills add jukeyman\u002Fjukeyman-skills --skill granola-reference-architecture","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsaas-packs--granola-pack--granola-reference-architecture\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",[],[]]