[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M793EWF8ZAC74ZSCMD8DNED0":3,"skill-same:01M793EWF8ZAC74ZSCMD8DNED0":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},"01M793EWF8ZAC74ZSCMD8DNED0","navan-entity-management",null,"Manage Navan users, departments, cost centers, and approval chains via API and SCIM provisioning.\nUse when onboarding departments, integrating identity providers, or auditing user access.\nTrigger with \"navan entity management\", \"navan user management\", \"navan SCIM setup\".","jukeyman\u002Fjukeyman-skills","jukeyman","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F142960420?v=4","01M78FR4Y3DHMMCBCC0GXXNB3F","RICK JEFFERSON","01M78FR4Z8RVQRAD31Y5J7V6EB",1,"MIT","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsaas-packs--navan-pack--navan-entity-management\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: navan-entity-management\ndescription: |\n  Manage Navan users, departments, cost centers, and approval chains via API and SCIM provisioning.\n  Use when onboarding departments, integrating identity providers, or auditing user access.\n  Trigger with \"navan entity management\", \"navan user management\", \"navan SCIM setup\".\nallowed-tools: Read, Write, Edit, Bash(npm:*), Bash(curl:*), Grep\nversion: 1.0.0\nlicense: MIT\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\ntags: [saas, navan, travel]\ncompatible-with: claude-code\n---\n\n# Navan — Entity Management\n\n## Overview\n\nThis skill covers organizational entity management in Navan: users, departments, cost centers, and approval chains. Navan supports two approaches for user lifecycle management — the REST API with GET \u002Fget_users for querying and auditing, and SCIM 2.0 provisioning for automated sync with identity providers like Okta, Entra ID (Azure AD), and OneLogin. Travel policies are assigned at the department level, and approval chains support multi-level routing based on expense thresholds and trip types. This skill is essential for organizations managing 100+ travelers.\n\n## Prerequisites\n\n- Navan account with admin-level API credentials (see `navan-install-auth`)\n- OAuth 2.0 token with admin scope\n- For SCIM: Okta, Entra ID, or OneLogin with SCIM 2.0 support\n- For SSO: SAML 2.0 or Google Workspace configured in Navan Admin\n- Environment variables: `NAVAN_CLIENT_ID`, `NAVAN_CLIENT_SECRET`, `NAVAN_BASE_URL`\n\n## Instructions\n\n### Step 1: Authenticate and Retrieve Booking Data\n\n```typescript\nconst tokenRes = await fetch(`${process.env.NAVAN_BASE_URL}\u002Fta-auth\u002Foauth\u002Ftoken`, {\n  method: 'POST',\n  headers: { 'Content-Type': 'application\u002Fx-www-form-urlencoded' },\n  body: new URLSearchParams({\n    grant_type: 'client_credentials',\n    client_id: process.env.NAVAN_CLIENT_ID!,\n    client_secret: process.env.NAVAN_CLIENT_SECRET!,\n  }),\n});\nconst { access_token } = await tokenRes.json();\nconst headers = { Authorization: `Bearer ${access_token}` };\n\n\u002F\u002F GET \u002Fv1\u002Fbookings — retrieve bookings (records in .data array)\nconst bookingsRes = await fetch(\n  `${process.env.NAVAN_BASE_URL}\u002Fv1\u002Fbookings?page=0&size=50`,\n  { headers }\n);\nconst { data: bookings } = await bookingsRes.json();\n\n\u002F\u002F Extract unique users from booking data\nconst users = [...new Map(bookings.map((b: any) => [b.traveler_email, b])).values()];\n\nusers.forEach((user: any) => {\n  console.log(`${user.email} | Role: ${user.role} | Dept: ${user.department}`);\n  console.log(`  Cost Center: ${user.cost_center} | Manager: ${user.manager_email}`);\n  console.log(`  Travel Policy: ${user.travel_policy_name}`);\n});\n```\n\n### Step 2: Audit User Access and Roles\n\n```typescript\n\u002F\u002F Build an access audit report\ninterface UserAudit {\n  email: string;\n  role: string;\n  department: string;\n  hasManagerAssigned: boolean;\n  hasCostCenter: boolean;\n  hasTravelPolicy: boolean;\n}\n\nconst audit: UserAudit[] = users.map((u: any) => ({\n  email: u.email,\n  role: u.role,\n  department: u.department ?? 'UNASSIGNED',\n  hasManagerAssigned: Boolean(u.manager_email),\n  hasCostCenter: Boolean(u.cost_center),\n  hasTravelPolicy: Boolean(u.travel_policy_name),\n}));\n\n\u002F\u002F Flag users missing required configuration\nconst incomplete = audit.filter(\n  u => !u.hasManagerAssigned || !u.hasCostCenter || !u.hasTravelPolicy\n);\nconsole.log(`\\nUsers with incomplete setup: ${incomplete.length}\u002F${audit.length}`);\nincomplete.forEach(u => {\n  const missing = [];\n  if (!u.hasManagerAssigned) missing.push('manager');\n  if (!u.hasCostCenter) missing.push('cost_center');\n  if (!u.hasTravelPolicy) missing.push('travel_policy');\n  console.log(`  ${u.email}: missing ${missing.join(', ')}`);\n});\n```\n\n### Step 3: Configure SCIM Provisioning (Okta)\n\nSCIM 2.0 enables automated user lifecycle management. Configure in the Navan admin console:\n\n1. Navigate to Admin > Travel admin > Settings > Identity Provider\n2. Select \"SCIM 2.0\" as the provisioning method\n3. Copy the SCIM endpoint URL and bearer token\n\nIn Okta:\n1. Add the Navan application from the OIN catalog\n2. Configure provisioning with the SCIM endpoint URL\n3. Enable: Create Users, Update User Attributes, Deactivate Users\n4. Map attributes: `userName`, `email`, `department`, `costCenter`, `manager`\n\n```bash\n# Test SCIM endpoint connectivity (replace with your SCIM URL and token)\ncurl -s -o \u002Fdev\u002Fnull -w \"%{http_code}\" \\\n  -H \"Authorization: Bearer ${NAVAN_SCIM_TOKEN}\" \\\n  \"${NAVAN_SCIM_URL}\u002FUsers?count=1\"\n# Expected: 200\n```\n\n### Step 4: Configure SCIM Provisioning (Entra ID)\n\nFor Microsoft Entra ID (formerly Azure AD):\n\n1. In Entra ID portal, add Navan as an Enterprise Application\n2. Under Provisioning, set mode to \"Automatic\"\n3. Enter the Navan SCIM tenant URL and secret token\n4. Map attributes: `userPrincipalName` -> `userName`, `department`, `companyName`\n5. Enable provisioning and set scope to \"Sync only assigned users\"\n\n### Step 5: Department and Cost Center Structure\n\n```typescript\n\u002F\u002F Organize users by department for policy assignment analysis\nconst byDepartment: Record\u003Cstring, any[]> = {};\nusers.forEach((u: any) => {\n  const dept = u.department ?? 'Unassigned';\n  if (!byDepartment[dept]) byDepartment[dept] = [];\n  byDepartment[dept].push(u);\n});\n\nconsole.log('\\nDepartment Summary:');\nObject.entries(byDepartment)\n  .sort((a, b) => b[1].length - a[1].length)\n  .forEach(([dept, members]) => {\n    const costCenters = [...new Set(members.map((m: any) => m.cost_center))];\n    console.log(`  ${dept}: ${members.length} users, cost centers: ${costCenters.join(', ')}`);\n  });\n```\n\n### Step 6: Approval Chain Configuration\n\n```typescript\n\u002F\u002F Define multi-level approval routing\n\u002F\u002F Configure in Navan Admin > Policies > Approval Chains\ninterface ApprovalChain {\n  department: string;\n  levels: {\n    threshold: number;\n    approverRole: string;\n    approverEmail: string;\n  }[];\n}\n\nconst approvalChains: ApprovalChain[] = [\n  {\n    department: 'Engineering',\n    levels: [\n      { threshold: 500, approverRole: 'manager', approverEmail: 'eng-mgr@company.com' },\n      { threshold: 2000, approverRole: 'director', approverEmail: 'eng-dir@company.com' },\n      { threshold: Infinity, approverRole: 'vp', approverEmail: 'vp-eng@company.com' },\n    ],\n  },\n  {\n    department: 'Sales',\n    levels: [\n      { threshold: 1000, approverRole: 'manager', approverEmail: 'sales-mgr@company.com' },\n      { threshold: 5000, approverRole: 'director', approverEmail: 'sales-dir@company.com' },\n      { threshold: Infinity, approverRole: 'cro', approverEmail: 'cro@company.com' },\n    ],\n  },\n];\n\n\u002F\u002F Determine required approver for a given expense\nfunction routeForApproval(dept: string, amount: number): string {\n  const chain = approvalChains.find(c => c.department === dept);\n  if (!chain) return 'finance@company.com'; \u002F\u002F fallback\n  const level = chain.levels.find(l => amount \u003C= l.threshold);\n  return level?.approverEmail ?? 'cfo@company.com';\n}\n```\n\n## Output\n\nSuccessful execution produces:\n- Complete user roster with roles, departments, cost centers, and policy assignments\n- Access audit report identifying users with incomplete configuration\n- SCIM provisioning configuration for Okta or Entra ID\n- Department hierarchy with cost center mappings\n- Approval chain definitions with threshold-based routing\n\n## Error Handling\n\n| Error | HTTP Code | Cause | Solution |\n|-------|-----------|-------|----------|\n| Unauthorized | 401 | Expired or invalid bearer token | Re-authenticate via POST \u002Fta-auth\u002Foauth\u002Ftoken |\n| Forbidden | 403 | Non-admin credentials used | Verify admin-level API credentials |\n| Rate Limited | 429 | Too many requests | Implement exponential backoff (start at 1s) |\n| SCIM Auth Failed | 401 | Invalid SCIM bearer token | Regenerate token in Navan Admin > Identity Provider |\n| SCIM Mapping Error | 400 | Missing required attribute | Verify userName and email mappings in IdP |\n| Server Error | 500 | Navan platform issue | Retry with backoff; check Navan status page |\n\n## Examples\n\n**Python — User audit with CSV export:**\n\n```python\nimport requests\nimport csv\nimport os\n\nbase_url = os.environ.get('NAVAN_BASE_URL', 'https:\u002F\u002Fapi.navan.com')\nauth = requests.post(f'{base_url}\u002Fta-auth\u002Foauth\u002Ftoken', data={\n    'grant_type': 'client_credentials',\n    'client_id': os.environ['NAVAN_CLIENT_ID'],\n    'client_secret': os.environ['NAVAN_CLIENT_SECRET'],\n})\nheaders = {'Authorization': f'Bearer {auth.json()[\"access_token\"]}'}\n\n# Retrieve bookings and extract user data\nresp = requests.get(f'{base_url}\u002Fv1\u002Fbookings', params={'page': 0, 'size': 50}, headers=headers).json()\nbookings = resp['data']\n# Deduplicate users from booking records\nusers = list({b.get('traveler_email'): b for b in bookings}.values())\n\nwith open('navan-user-audit.csv', 'w', newline='') as f:\n    writer = csv.DictWriter(f, fieldnames=[\n        'email', 'role', 'department', 'cost_center', 'manager', 'policy'\n    ])\n    writer.writeheader()\n    for u in users:\n        writer.writerow({\n            'email': u.get('email'),\n            'role': u.get('role'),\n            'department': u.get('department', ''),\n            'cost_center': u.get('cost_center', ''),\n            'manager': u.get('manager_email', ''),\n            'policy': u.get('travel_policy_name', ''),\n        })\nprint(f'Exported {len(users)} users to navan-user-audit.csv')\n```\n\n## Resources\n\n- [Navan Help Center](https:\u002F\u002Fapp.navan.com\u002Fapp\u002Fhelpcenter) — Official documentation and support\n- [Navan Integrations](https:\u002F\u002Fnavan.com\u002Fintegrations) — Okta, Entra ID, BambooHR, Workday, ADP connectors\n- [Booking Data Integration](https:\u002F\u002Fapp.navan.com\u002Fapp\u002Fhelpcenter\u002Farticles\u002Ftravel\u002Fadmin\u002Fother-integrations\u002Fbooking-data-integration) — Data export and user management\n\n## Next Steps\n\nAfter configuring entities, proceed to `navan-core-workflow-a` for travel booking workflows or `navan-enterprise-rbac` for role-based access control.\n","# Navan — Entity Management\n\n## Overview\n\nThis skill covers organizational entity management in Navan: users, departments, cost centers, and approval chains. Navan supports two approaches for user lifecycle management — the REST API with GET \u002Fget_users for querying and auditing, and SCIM 2.0 provisioning for automated sync with identity providers like Okta, Entra ID (Azure AD), and OneLogin. Travel policies are assigned at the department level, and approval chains support multi-level routing based on expense thresholds and trip types. This skill is essential for organizations managing 100+ travelers.\n\n## Prerequisites\n\n- Navan account with admin-level API credentials (see `navan-install-auth`)\n- OAuth 2.0 token with admin scope\n- For SCIM: Okta, Entra ID, or OneLogin with SCIM 2.0 support\n- For SSO: SAML 2.0 or Google Workspace configured in Navan Admin\n- Environment variables: `NAVAN_CLIENT_ID`, `NAVAN_CLIENT_SECRET`, `NAVAN_BASE_URL`\n\n## Instructions\n\n### Step 1: Authenticate and Retrieve Booking Data\n\n```typescript\nconst tokenRes = await fetch(`${process.env.NAVAN_BASE_URL}\u002Fta-auth\u002Foauth\u002Ftoken`, {\n  method: 'POST',\n  headers: { 'Content-Type': 'application\u002Fx-www-form-urlencoded' },\n  body: new URLSearchParams({\n    grant_type: 'client_credentials',\n    client_id: process.env.NAVAN_CLIENT_ID!,\n    client_secret: process.env.NAVAN_CLIENT_SECRET!,\n  }),\n});\nconst { access_token } = await tokenRes.json();\nconst headers = { Authorization: `Bearer ${access_token}` };\n\n\u002F\u002F GET \u002Fv1\u002Fbookings — retrieve bookings (records in .data array)\nconst bookingsRes = await fetch(\n  `${process.env.NAVAN_BASE_URL}\u002Fv1\u002Fbookings?page=0&size=50`,\n  { headers }\n);\nconst { data: bookings } = await bookingsRes.json();\n\n\u002F\u002F Extract unique users from booking data\nconst users = [...new Map(bookings.map((b: any) => [b.traveler_email, b])).values()];\n\nusers.forEach((user: any) => {\n  console.log(`${user.email} | Role: ${user.role} | Dept: ${user.department}`);\n  console.log(`  Cost Center: ${user.cost_center} | Manager: ${user.manager_email}`);\n  console.log(`  Travel Policy: ${user.travel_policy_name}`);\n});\n```\n\n### Step 2: Audit User Access and Roles\n\n```typescript\n\u002F\u002F Build an access audit report\ninterface UserAudit {\n  email: string;\n  role: string;\n  department: string;\n  hasManagerAssigned: boolean;\n  hasCostCenter: boolean;\n  hasTravelPolicy: boolean;\n}\n\nconst audit: UserAudit[] = users.map((u: any) => ({\n  email: u.email,\n  role: u.role,\n  department: u.department ?? 'UNASSIGNED',\n  hasManagerAssigned: Boolean(u.manager_email),\n  hasCostCenter: Boolean(u.cost_center),\n  hasTravelPolicy: Boolean(u.travel_policy_name),\n}));\n\n\u002F\u002F Flag users missing required configuration\nconst incomplete = audit.filter(\n  u => !u.hasManagerAssigned || !u.hasCostCenter || !u.hasTravelPolicy\n);\nconsole.log(`\\nUsers with incomplete setup: ${incomplete.length}\u002F${audit.length}`);\nincomplete.forEach(u => {\n  const missing = [];\n  if (!u.hasManagerAssigned) missing.push('manager');\n  if (!u.hasCostCenter) missing.push('cost_center');\n  if (!u.hasTravelPolicy) missing.push('travel_policy');\n  console.log(`  ${u.email}: missing ${missing.join(', ')}`);\n});\n```\n\n### Step 3: Configure SCIM Provisioning (Okta)\n\nSCIM 2.0 enables automated user lifecycle management. Configure in the Navan admin console:\n\n1. Navigate to Admin > Travel admin > Settings > Identity Provider\n2. Select \"SCIM 2.0\" as the provisioning method\n3. Copy the SCIM endpoint URL and bearer token\n\nIn Okta:\n1. Add the Navan application from the OIN catalog\n2. Configure provisioning with the SCIM endpoint URL\n3. Enable: Create Users, Update User Attributes, Deactivate Users\n4. Map attributes: `userName`, `email`, `department`, `costCenter`, `manager`\n\n```bash\n# Test SCIM endpoint connectivity (replace with your SCIM URL and token)\ncurl -s -o \u002Fdev\u002Fnull -w \"%{http_code}\" \\\n  -H \"Authorization: Bearer ${NAVAN_SCIM_TOKEN}\" \\\n  \"${NAVAN_SCIM_URL}\u002FUsers?count=1\"\n# Expected: 200\n```\n\n### Step 4: Configure SCIM Provisioning (Entra ID)\n\nFor Microsoft Entra ID (formerly Azure AD):\n\n1. In Entra ID portal, add Navan as an Enterprise Application\n2. Under Provisioning, set mode to \"Automatic\"\n3. Enter the Navan SCIM tenant URL and secret token\n4. Map attributes: `userPrincipalName` -> `userName`, `department`, `companyName`\n5. Enable provisioning and set scope to \"Sync only assigned users\"\n\n### Step 5: Department and Cost Center Structure\n\n```typescript\n\u002F\u002F Organize users by department for policy assignment analysis\nconst byDepartment: Record\u003Cstring, any[]> = {};\nusers.forEach((u: any) => {\n  const dept = u.department ?? 'Unassigned';\n  if (!byDepartment[dept]) byDepartment[dept] = [];\n  byDepartment[dept].push(u);\n});\n\nconsole.log('\\nDepartment Summary:');\nObject.entries(byDepartment)\n  .sort((a, b) => b[1].length - a[1].length)\n  .forEach(([dept, members]) => {\n    const costCenters = [...new Set(members.map((m: any) => m.cost_center))];\n    console.log(`  ${dept}: ${members.length} users, cost centers: ${costCenters.join(', ')}`);\n  });\n```\n\n### Step 6: Approval Chain Configuration\n\n```typescript\n\u002F\u002F Define multi-level approval routing\n\u002F\u002F Configure in Navan Admin > Policies > Approval Chains\ninterface ApprovalChain {\n  department: string;\n  levels: {\n    threshold: number;\n    approverRole: string;\n    approverEmail: string;\n  }[];\n}\n\nconst approvalChains: ApprovalChain[] = [\n  {\n    department: 'Engineering',\n    levels: [\n      { threshold: 500, approverRole: 'manager', approverEmail: 'eng-mgr@company.com' },\n      { threshold: 2000, approverRole: 'director', approverEmail: 'eng-dir@company.com' },\n      { threshold: Infinity, approverRole: 'vp', approverEmail: 'vp-eng@company.com' },\n    ],\n  },\n  {\n    department: 'Sales',\n    levels: [\n      { threshold: 1000, approverRole: 'manager', approverEmail: 'sales-mgr@company.com' },\n      { threshold: 5000, approverRole: 'director', approverEmail: 'sales-dir@company.com' },\n      { threshold: Infinity, approverRole: 'cro', approverEmail: 'cro@company.com' },\n    ],\n  },\n];\n\n\u002F\u002F Determine required approver for a given expense\nfunction routeForApproval(dept: string, amount: number): string {\n  const chain = approvalChains.find(c => c.department === dept);\n  if (!chain) return 'finance@company.com'; \u002F\u002F fallback\n  const level = chain.levels.find(l => amount \u003C= l.threshold);\n  return level?.approverEmail ?? 'cfo@company.com';\n}\n```\n\n## Output\n\nSuccessful execution produces:\n- Complete user roster with roles, departments, cost centers, and policy assignments\n- Access audit report identifying users with incomplete configuration\n- SCIM provisioning configuration for Okta or Entra ID\n- Department hierarchy with cost center mappings\n- Approval chain definitions with threshold-based routing\n\n## Error Handling\n\n| Error | HTTP Code | Cause | Solution |\n|-------|-----------|-------|----------|\n| Unauthorized | 401 | Expired or invalid bearer token | Re-authenticate via POST \u002Fta-auth\u002Foauth\u002Ftoken |\n| Forbidden | 403 | Non-admin credentials used | Verify admin-level API credentials |\n| Rate Limited | 429 | Too many requests | Implement exponential backoff (start at 1s) |\n| SCIM Auth Failed | 401 | Invalid SCIM bearer token | Regenerate token in Navan Admin > Identity Provider |\n| SCIM Mapping Error | 400 | Missing required attribute | Verify userName and email mappings in IdP |\n| Server Error | 500 | Navan platform issue | Retry with backoff; check Navan status page |\n\n## Examples\n\n**Python — User audit with CSV export:**\n\n```python\nimport requests\nimport csv\nimport os\n\nbase_url = os.environ.get('NAVAN_BASE_URL', 'https:\u002F\u002Fapi.navan.com')\nauth = requests.post(f'{base_url}\u002Fta-auth\u002Foauth\u002Ftoken', data={\n    'grant_type': 'client_credentials',\n    'client_id': os.environ['NAVAN_CLIENT_ID'],\n    'client_secret': os.environ['NAVAN_CLIENT_SECRET'],\n})\nheaders = {'Authorization': f'Bearer {auth.json()[\"access_token\"]}'}\n\n# Retrieve bookings and extract user data\nresp = requests.get(f'{base_url}\u002Fv1\u002Fbookings', params={'page': 0, 'size': 50}, headers=headers).json()\nbookings = resp['data']\n# Deduplicate users from booking records\nusers = list({b.get('traveler_email'): b for b in bookings}.values())\n\nwith open('navan-user-audit.csv', 'w', newline='') as f:\n    writer = csv.DictWriter(f, fieldnames=[\n        'email', 'role', 'department', 'cost_center', 'manager', 'policy'\n    ])\n    writer.writeheader()\n    for u in users:\n        writer.writerow({\n            'email': u.get('email'),\n            'role': u.get('role'),\n            'department': u.get('department', ''),\n            'cost_center': u.get('cost_center', ''),\n            'manager': u.get('manager_email', ''),\n            'policy': u.get('travel_policy_name', ''),\n        })\nprint(f'Exported {len(users)} users to navan-user-audit.csv')\n```\n\n## Resources\n\n- [Navan Help Center](https:\u002F\u002Fapp.navan.com\u002Fapp\u002Fhelpcenter) — Official documentation and support\n- [Navan Integrations](https:\u002F\u002Fnavan.com\u002Fintegrations) — Okta, Entra ID, BambooHR, Workday, ADP connectors\n- [Booking Data Integration](https:\u002F\u002Fapp.navan.com\u002Fapp\u002Fhelpcenter\u002Farticles\u002Ftravel\u002Fadmin\u002Fother-integrations\u002Fbooking-data-integration) — Data export and user management\n\n## Next Steps\n\nAfter configuring entities, proceed to `navan-core-workflow-a` for travel booking workflows or `navan-enterprise-rbac` for role-based access control.\n",{"name":5,"tags":24,"author":28,"license":15,"version":29,"description":30,"allowed-tools":31,"compatible-with":32},[25,26,27],"saas","navan","travel","Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Manage Navan users, departments, cost centers, and approval chains via API and SCIM provisioning.\nUse when onboarding departments, integrating identity providers, or auditing user access.\nTrigger with \"navan entity management\", \"navan user management\", \"navan SCIM setup\".\n","Read, Write, Edit, Bash(npm:*), Bash(curl:*), Grep","claude-code","main","99825ad3f3bcc6597ddcc7294a14e6e922f2b67b","skills\u002Fsaas-packs--navan-pack--navan-entity-management",0,"https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills","https:\u002F\u002Fgithub.com\u002Fjukeyman","https:\u002F\u002FRJBUSINESSSOLUTIONS.ORG","Credit and Finance Expert | Developer\r\n\r\nI'm Rick Jefferson, a seasoned credit and finance expert with over a decade of experience in financial literacy,","2026-07-13 07:03:29",{"source":8,"skillName":5,"commands":43,"prompt":53,"zipAvailable":54},[44,47,50],{"tool":45,"command":46},"npx","npx skills add jukeyman\u002Fjukeyman-skills --skill navan-entity-management",{"tool":48,"command":49},"bunx","bunx skills add jukeyman\u002Fjukeyman-skills --skill navan-entity-management",{"tool":51,"command":52},"pnpm","pnpm dlx skills add jukeyman\u002Fjukeyman-skills --skill navan-entity-management","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsaas-packs--navan-pack--navan-entity-management\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",[],[]]