[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7E4ZEHS61ATPP8THYCS3H2X":3,"skill-same:01M7E4ZEHS61ATPP8THYCS3H2X":127},{"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":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":71,"commitSha":72,"skillDirectory":73,"forksCount":74,"repositoryHtmlUrl":75,"repositoryHomepageUrl":6,"ownerHtmlUrl":76,"ownerBlogUrl":6,"ownerDescription":77,"updatedAt":78,"install":79,"resources":92},"01M7E4ZEHS61ATPP8THYCS3H2X","implementing-scim-provisioning-with-okta",null,"Implement automated user lifecycle provisioning and deprovisioning using the SCIM 2.0 protocol with Okta as the identity provider. Use when automating account creation, attribute sync, or deactivation across downstream applications through Okta SCIM integration, or when troubleshooting SCIM provisioning failures.","sanjeevafk\u002Fagent-skills","sanjeevafk","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F230678117?v=4","01M7C540EFY46ETG1NNWKS5X3Q","Sanjeev","01M7C540F366J5C1D587BMKH9Q",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fcybersecurity-skills\u002Fskills\u002Fimplementing-scim-provisioning-with-okta\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fcybersecurity-skills\u002Fskills\u002Fimplementing-scim-provisioning-with-okta\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: implementing-scim-provisioning-with-okta\ndescription: Implement automated user lifecycle provisioning and deprovisioning using\n  the SCIM 2.0 protocol with Okta as the identity provider. Use when automating account\n  creation, attribute sync, or deactivation across downstream applications through\n  Okta SCIM integration, or when troubleshooting SCIM provisioning failures.\ndomain: cybersecurity\nsubdomain: identity-access-management\ntags:\n- scim\n- okta\n- provisioning\n- identity-management\n- automation\n- sso\n- lifecycle-management\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- PR.AA-01\n- PR.AA-02\n- PR.AA-05\n- PR.AA-06\nmitre_attack:\n- T1078\n- T1110\n- T1556\n- T1098\nmitre_f3:\n  version: '1.1'\n  tactics:\n  - initial-access\n  - positioning\n  - resource-development\n  techniques:\n  - id: T1586\n    name: Compromise Accounts\n    tactic: resource-development\n    source: attack\n  - id: F1005.002\n    name: 'Account Manipulation: Add Authorized User'\n    tactic: positioning\n    source: f3\n  - id: F1005.004\n    name: 'Account Manipulation: Change Account Details'\n    tactic: positioning\n    source: f3\n  - id: F1042\n    name: Reactivate Account\n    tactic: positioning\n    source: f3\n  - id: F1006.002\n    name: 'Account Takeover: Exposed Login Credential'\n    tactic: initial-access\n    source: f3\n---\n\n# Implementing SCIM Provisioning with Okta\n\n## Overview\n\nSCIM (System for Cross-domain Identity Management) is an open standard protocol (RFC 7644) that automates the exchange of user identity information between identity providers like Okta and service providers. This skill covers building a SCIM 2.0-compliant API endpoint and integrating it with Okta for automated user lifecycle management including provisioning, deprovisioning, profile updates, and group management.\n\n\n## When to Use\n\n- When deploying or configuring implementing scim provisioning with okta capabilities in your environment\n- When establishing security controls aligned to compliance requirements\n- When building or improving security architecture for this domain\n- When conducting security assessments that require this implementation\n\n## Prerequisites\n\n- Okta tenant with admin access (Developer or Production)\n- Application with REST API capable of user management\n- TLS-secured endpoint (HTTPS required)\n- Okta API token or OAuth 2.0 client credentials\n- Python 3.9+ with Flask or FastAPI\n\n## Core Concepts\n\n### SCIM 2.0 Protocol\n\nSCIM defines a standard schema for representing users and groups via JSON, with a RESTful API for CRUD operations:\n\n| Operation | HTTP Method | Endpoint | Description |\n|-----------|-------------|----------|-------------|\n| Create User | POST | \u002Fscim\u002Fv2\u002FUsers | Provisions a new user account |\n| Read User | GET | \u002Fscim\u002Fv2\u002FUsers\u002F{id} | Retrieves user details |\n| Update User | PUT\u002FPATCH | \u002Fscim\u002Fv2\u002FUsers\u002F{id} | Modifies user attributes |\n| Delete User | DELETE | \u002Fscim\u002Fv2\u002FUsers\u002F{id} | Removes user account |\n| List Users | GET | \u002Fscim\u002Fv2\u002FUsers | Lists users with filtering |\n| Create Group | POST | \u002Fscim\u002Fv2\u002FGroups | Creates a group |\n| Manage Group | PATCH | \u002Fscim\u002Fv2\u002FGroups\u002F{id} | Add\u002Fremove group members |\n\n### Okta SCIM Integration Architecture\n\n```\nOkta (IdP) ──SCIM 2.0 over HTTPS──> SCIM Server ──> Application Database\n     │                                     │\n     ├── User Assignment                   ├── Create\u002FUpdate User\n     ├── User Unassignment                 ├── Deactivate User\n     ├── Profile Push                      ├── Sync Attributes\n     └── Group Push                        └── Manage Groups\n```\n\n### Required SCIM Endpoints\n\n1. **ServiceProviderConfig** (`\u002Fscim\u002Fv2\u002FServiceProviderConfig`): Advertises SCIM capabilities\n2. **ResourceTypes** (`\u002Fscim\u002Fv2\u002FResourceTypes`): Describes supported resource types\n3. **Schemas** (`\u002Fscim\u002Fv2\u002FSchemas`): Publishes the SCIM schema definitions\n4. **Users** (`\u002Fscim\u002Fv2\u002FUsers`): User lifecycle operations\n5. **Groups** (`\u002Fscim\u002Fv2\u002FGroups`): Group management operations\n\n## Workflow\n\n### Step 1: Build SCIM 2.0 API Server\n\nCreate a Flask-based SCIM server that implements the core endpoints. The server must handle:\n\n- **User CRUD**: Create, read, update, delete, and list users\n- **Filtering**: Support `eq` filter on `userName` (required by Okta)\n- **Pagination**: Return `startIndex`, `itemsPerPage`, and `totalResults`\n- **Authentication**: Bearer token validation on all endpoints\n\n```python\nfrom flask import Flask, request, jsonify\nimport uuid\nfrom datetime import datetime\n\napp = Flask(__name__)\n\n# Bearer token for Okta authentication\nSCIM_BEARER_TOKEN = \"your-secure-token-here\"\n\ndef require_auth(f):\n    def wrapper(*args, **kwargs):\n        auth = request.headers.get(\"Authorization\", \"\")\n        if not auth.startswith(\"Bearer \") or auth[7:] != SCIM_BEARER_TOKEN:\n            return jsonify({\"detail\": \"Unauthorized\"}), 401\n        return f(*args, **kwargs)\n    wrapper.__name__ = f.__name__\n    return wrapper\n\n@app.route(\"\u002Fscim\u002Fv2\u002FUsers\", methods=[\"POST\"])\n@require_auth\ndef create_user():\n    data = request.json\n    user_id = str(uuid.uuid4())\n    user = {\n        \"schemas\": [\"urn:ietf:params:scim:schemas:core:2.0:User\"],\n        \"id\": user_id,\n        \"userName\": data.get(\"userName\"),\n        \"name\": data.get(\"name\", {}),\n        \"emails\": data.get(\"emails\", []),\n        \"active\": True,\n        \"meta\": {\n            \"resourceType\": \"User\",\n            \"created\": datetime.utcnow().isoformat() + \"Z\",\n            \"lastModified\": datetime.utcnow().isoformat() + \"Z\",\n            \"location\": f\"\u002Fscim\u002Fv2\u002FUsers\u002F{user_id}\"\n        }\n    }\n    # Persist user to database\n    return jsonify(user), 201\n\n@app.route(\"\u002Fscim\u002Fv2\u002FUsers\", methods=[\"GET\"])\n@require_auth\ndef list_users():\n    filter_param = request.args.get(\"filter\", \"\")\n    start_index = int(request.args.get(\"startIndex\", 1))\n    count = int(request.args.get(\"count\", 100))\n    # Parse filter: userName eq \"john@example.com\"\n    # Query database with filter\n    return jsonify({\n        \"schemas\": [\"urn:ietf:params:scim:api:messages:2.0:ListResponse\"],\n        \"totalResults\": 0,\n        \"startIndex\": start_index,\n        \"itemsPerPage\": count,\n        \"Resources\": []\n    })\n```\n\n### Step 2: Configure Okta Application\n\n1. **Create SCIM App Integration**:\n   - Navigate to Okta Admin Console > Applications > Create App Integration\n   - Select SWA or SAML 2.0 as sign-on method\n   - In the General tab, select SCIM for Provisioning\n\n2. **Configure SCIM Connection**:\n   - SCIM connector base URL: `https:\u002F\u002Fyour-app.com\u002Fscim\u002Fv2`\n   - Unique identifier field: `userName`\n   - Supported provisioning actions: Push New Users, Push Profile Updates, Push Groups\n   - Authentication Mode: HTTP Header (Bearer Token)\n\n3. **Enable Provisioning Features**:\n   - To App: Create Users, Update User Attributes, Deactivate Users\n   - Configure attribute mappings between Okta profile and SCIM schema\n\n### Step 3: Map Attributes\n\nMap Okta user profile attributes to your SCIM schema:\n\n| Okta Attribute | SCIM Attribute | Direction |\n|---------------|----------------|-----------|\n| login | userName | Okta -> App |\n| firstName | name.givenName | Okta -> App |\n| lastName | name.familyName | Okta -> App |\n| email | emails[type eq \"work\"].value | Okta -> App |\n| department | urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:department | Okta -> App |\n\n### Step 4: Implement Error Handling\n\nSCIM specifies standard error response format:\n\n```json\n{\n  \"schemas\": [\"urn:ietf:params:scim:api:messages:2.0:Error\"],\n  \"detail\": \"User already exists\",\n  \"status\": \"409\",\n  \"scimType\": \"uniqueness\"\n}\n```\n\nCommon error codes: 400 (Bad Request), 401 (Unauthorized), 404 (Not Found), 409 (Conflict), 500 (Internal Server Error).\n\n### Step 5: Test with Runscope\u002FOkta SCIM Validator\n\nOkta provides an automated SCIM test suite (via Runscope\u002FBlazeMeter) that validates your SCIM implementation against all required operations:\n\n1. Import the Okta SCIM 2.0 test suite from the OIN submission portal\n2. Configure the base URL and authentication token\n3. Run the full test suite covering user CRUD, filtering, and pagination\n4. Fix any failing tests before submitting to OIN\n\n## Validation Checklist\n\n- [ ] SCIM server accessible over HTTPS with valid TLS certificate\n- [ ] Bearer token authentication enforced on all endpoints\n- [ ] User creation returns 201 with full user representation\n- [ ] User search by `userName eq \"...\"` filter works correctly\n- [ ] Pagination parameters (`startIndex`, `count`) handled properly\n- [ ] User deactivation sets `active: false` (not hard delete)\n- [ ] PATCH operations support `add`, `replace`, `remove` ops\n- [ ] Group push creates and manages group memberships\n- [ ] Okta SCIM validator test suite passes all tests\n- [ ] Error responses conform to SCIM error schema\n\n## References\n\n- [SCIM 2.0 Protocol RFC 7644](https:\u002F\u002Ftools.ietf.org\u002Fhtml\u002Frfc7644)\n- [Okta SCIM Developer Guide](https:\u002F\u002Fdeveloper.okta.com\u002Fdocs\u002Fguides\u002Fscim-provisioning-integration-overview\u002Fmain\u002F)\n- [Build a SCIM API Service - Okta](https:\u002F\u002Fdeveloper.okta.com\u002Fdocs\u002Fguides\u002Fscim-provisioning-integration-prepare\u002Fmain\u002F)\n- [SCIM Core Schema RFC 7643](https:\u002F\u002Ftools.ietf.org\u002Fhtml\u002Frfc7643)\n","# Implementing SCIM Provisioning with Okta\n\n## Overview\n\nSCIM (System for Cross-domain Identity Management) is an open standard protocol (RFC 7644) that automates the exchange of user identity information between identity providers like Okta and service providers. This skill covers building a SCIM 2.0-compliant API endpoint and integrating it with Okta for automated user lifecycle management including provisioning, deprovisioning, profile updates, and group management.\n\n\n## When to Use\n\n- When deploying or configuring implementing scim provisioning with okta capabilities in your environment\n- When establishing security controls aligned to compliance requirements\n- When building or improving security architecture for this domain\n- When conducting security assessments that require this implementation\n\n## Prerequisites\n\n- Okta tenant with admin access (Developer or Production)\n- Application with REST API capable of user management\n- TLS-secured endpoint (HTTPS required)\n- Okta API token or OAuth 2.0 client credentials\n- Python 3.9+ with Flask or FastAPI\n\n## Core Concepts\n\n### SCIM 2.0 Protocol\n\nSCIM defines a standard schema for representing users and groups via JSON, with a RESTful API for CRUD operations:\n\n| Operation | HTTP Method | Endpoint | Description |\n|-----------|-------------|----------|-------------|\n| Create User | POST | \u002Fscim\u002Fv2\u002FUsers | Provisions a new user account |\n| Read User | GET | \u002Fscim\u002Fv2\u002FUsers\u002F{id} | Retrieves user details |\n| Update User | PUT\u002FPATCH | \u002Fscim\u002Fv2\u002FUsers\u002F{id} | Modifies user attributes |\n| Delete User | DELETE | \u002Fscim\u002Fv2\u002FUsers\u002F{id} | Removes user account |\n| List Users | GET | \u002Fscim\u002Fv2\u002FUsers | Lists users with filtering |\n| Create Group | POST | \u002Fscim\u002Fv2\u002FGroups | Creates a group |\n| Manage Group | PATCH | \u002Fscim\u002Fv2\u002FGroups\u002F{id} | Add\u002Fremove group members |\n\n### Okta SCIM Integration Architecture\n\n```\nOkta (IdP) ──SCIM 2.0 over HTTPS──> SCIM Server ──> Application Database\n     │                                     │\n     ├── User Assignment                   ├── Create\u002FUpdate User\n     ├── User Unassignment                 ├── Deactivate User\n     ├── Profile Push                      ├── Sync Attributes\n     └── Group Push                        └── Manage Groups\n```\n\n### Required SCIM Endpoints\n\n1. **ServiceProviderConfig** (`\u002Fscim\u002Fv2\u002FServiceProviderConfig`): Advertises SCIM capabilities\n2. **ResourceTypes** (`\u002Fscim\u002Fv2\u002FResourceTypes`): Describes supported resource types\n3. **Schemas** (`\u002Fscim\u002Fv2\u002FSchemas`): Publishes the SCIM schema definitions\n4. **Users** (`\u002Fscim\u002Fv2\u002FUsers`): User lifecycle operations\n5. **Groups** (`\u002Fscim\u002Fv2\u002FGroups`): Group management operations\n\n## Workflow\n\n### Step 1: Build SCIM 2.0 API Server\n\nCreate a Flask-based SCIM server that implements the core endpoints. The server must handle:\n\n- **User CRUD**: Create, read, update, delete, and list users\n- **Filtering**: Support `eq` filter on `userName` (required by Okta)\n- **Pagination**: Return `startIndex`, `itemsPerPage`, and `totalResults`\n- **Authentication**: Bearer token validation on all endpoints\n\n```python\nfrom flask import Flask, request, jsonify\nimport uuid\nfrom datetime import datetime\n\napp = Flask(__name__)\n\n# Bearer token for Okta authentication\nSCIM_BEARER_TOKEN = \"your-secure-token-here\"\n\ndef require_auth(f):\n    def wrapper(*args, **kwargs):\n        auth = request.headers.get(\"Authorization\", \"\")\n        if not auth.startswith(\"Bearer \") or auth[7:] != SCIM_BEARER_TOKEN:\n            return jsonify({\"detail\": \"Unauthorized\"}), 401\n        return f(*args, **kwargs)\n    wrapper.__name__ = f.__name__\n    return wrapper\n\n@app.route(\"\u002Fscim\u002Fv2\u002FUsers\", methods=[\"POST\"])\n@require_auth\ndef create_user():\n    data = request.json\n    user_id = str(uuid.uuid4())\n    user = {\n        \"schemas\": [\"urn:ietf:params:scim:schemas:core:2.0:User\"],\n        \"id\": user_id,\n        \"userName\": data.get(\"userName\"),\n        \"name\": data.get(\"name\", {}),\n        \"emails\": data.get(\"emails\", []),\n        \"active\": True,\n        \"meta\": {\n            \"resourceType\": \"User\",\n            \"created\": datetime.utcnow().isoformat() + \"Z\",\n            \"lastModified\": datetime.utcnow().isoformat() + \"Z\",\n            \"location\": f\"\u002Fscim\u002Fv2\u002FUsers\u002F{user_id}\"\n        }\n    }\n    # Persist user to database\n    return jsonify(user), 201\n\n@app.route(\"\u002Fscim\u002Fv2\u002FUsers\", methods=[\"GET\"])\n@require_auth\ndef list_users():\n    filter_param = request.args.get(\"filter\", \"\")\n    start_index = int(request.args.get(\"startIndex\", 1))\n    count = int(request.args.get(\"count\", 100))\n    # Parse filter: userName eq \"john@example.com\"\n    # Query database with filter\n    return jsonify({\n        \"schemas\": [\"urn:ietf:params:scim:api:messages:2.0:ListResponse\"],\n        \"totalResults\": 0,\n        \"startIndex\": start_index,\n        \"itemsPerPage\": count,\n        \"Resources\": []\n    })\n```\n\n### Step 2: Configure Okta Application\n\n1. **Create SCIM App Integration**:\n   - Navigate to Okta Admin Console > Applications > Create App Integration\n   - Select SWA or SAML 2.0 as sign-on method\n   - In the General tab, select SCIM for Provisioning\n\n2. **Configure SCIM Connection**:\n   - SCIM connector base URL: `https:\u002F\u002Fyour-app.com\u002Fscim\u002Fv2`\n   - Unique identifier field: `userName`\n   - Supported provisioning actions: Push New Users, Push Profile Updates, Push Groups\n   - Authentication Mode: HTTP Header (Bearer Token)\n\n3. **Enable Provisioning Features**:\n   - To App: Create Users, Update User Attributes, Deactivate Users\n   - Configure attribute mappings between Okta profile and SCIM schema\n\n### Step 3: Map Attributes\n\nMap Okta user profile attributes to your SCIM schema:\n\n| Okta Attribute | SCIM Attribute | Direction |\n|---------------|----------------|-----------|\n| login | userName | Okta -> App |\n| firstName | name.givenName | Okta -> App |\n| lastName | name.familyName | Okta -> App |\n| email | emails[type eq \"work\"].value | Okta -> App |\n| department | urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:department | Okta -> App |\n\n### Step 4: Implement Error Handling\n\nSCIM specifies standard error response format:\n\n```json\n{\n  \"schemas\": [\"urn:ietf:params:scim:api:messages:2.0:Error\"],\n  \"detail\": \"User already exists\",\n  \"status\": \"409\",\n  \"scimType\": \"uniqueness\"\n}\n```\n\nCommon error codes: 400 (Bad Request), 401 (Unauthorized), 404 (Not Found), 409 (Conflict), 500 (Internal Server Error).\n\n### Step 5: Test with Runscope\u002FOkta SCIM Validator\n\nOkta provides an automated SCIM test suite (via Runscope\u002FBlazeMeter) that validates your SCIM implementation against all required operations:\n\n1. Import the Okta SCIM 2.0 test suite from the OIN submission portal\n2. Configure the base URL and authentication token\n3. Run the full test suite covering user CRUD, filtering, and pagination\n4. Fix any failing tests before submitting to OIN\n\n## Validation Checklist\n\n- [ ] SCIM server accessible over HTTPS with valid TLS certificate\n- [ ] Bearer token authentication enforced on all endpoints\n- [ ] User creation returns 201 with full user representation\n- [ ] User search by `userName eq \"...\"` filter works correctly\n- [ ] Pagination parameters (`startIndex`, `count`) handled properly\n- [ ] User deactivation sets `active: false` (not hard delete)\n- [ ] PATCH operations support `add`, `replace`, `remove` ops\n- [ ] Group push creates and manages group memberships\n- [ ] Okta SCIM validator test suite passes all tests\n- [ ] Error responses conform to SCIM error schema\n\n## References\n\n- [SCIM 2.0 Protocol RFC 7644](https:\u002F\u002Ftools.ietf.org\u002Fhtml\u002Frfc7644)\n- [Okta SCIM Developer Guide](https:\u002F\u002Fdeveloper.okta.com\u002Fdocs\u002Fguides\u002Fscim-provisioning-integration-overview\u002Fmain\u002F)\n- [Build a SCIM API Service - Okta](https:\u002F\u002Fdeveloper.okta.com\u002Fdocs\u002Fguides\u002Fscim-provisioning-integration-prepare\u002Fmain\u002F)\n- [SCIM Core Schema RFC 7643](https:\u002F\u002Ftools.ietf.org\u002Fhtml\u002Frfc7643)\n",{"name":5,"tags":25,"author":33,"domain":34,"license":15,"version":35,"mitre_f3":36,"nist_csf":60,"subdomain":65,"description":7,"mitre_attack":66},[26,27,28,29,30,31,32],"scim","okta","provisioning","identity-management","automation","sso","lifecycle-management","mahipal","cybersecurity","1.0",{"tactics":37,"version":41,"techniques":42},[38,39,40],"initial-access","positioning","resource-development","1.1",[43,47,51,54,57],{"id":44,"name":45,"source":46,"tactic":40},"T1586","Compromise Accounts","attack",{"id":48,"name":49,"source":50,"tactic":39},"F1005.002","Account Manipulation: Add Authorized User","f3",{"id":52,"name":53,"source":50,"tactic":39},"F1005.004","Account Manipulation: Change Account Details",{"id":55,"name":56,"source":50,"tactic":39},"F1042","Reactivate Account",{"id":58,"name":59,"source":50,"tactic":38},"F1006.002","Account Takeover: Exposed Login Credential",[61,62,63,64],"PR.AA-01","PR.AA-02","PR.AA-05","PR.AA-06","identity-access-management",[67,68,69,70],"T1078","T1110","T1556","T1098","main","4e084e84eb42fc53e144c89c0f7f48b39c8a4b0f","collections\u002Fcybersecurity-skills\u002Fskills\u002Fimplementing-scim-provisioning-with-okta",1,"https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills","https:\u002F\u002Fgithub.com\u002Fsanjeevafk","First make it work. Then make it right. Then make it fast.","2026-11-14 13:36:16",{"source":8,"skillName":5,"commands":80,"prompt":90,"zipAvailable":91},[81,84,87],{"tool":82,"command":83},"npx","npx skills add sanjeevafk\u002Fagent-skills --skill implementing-scim-provisioning-with-okta",{"tool":85,"command":86},"bunx","bunx skills add sanjeevafk\u002Fagent-skills --skill implementing-scim-provisioning-with-okta",{"tool":88,"command":89},"pnpm","pnpm dlx skills add sanjeevafk\u002Fagent-skills --skill implementing-scim-provisioning-with-okta","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fcybersecurity-skills\u002Fskills\u002Fimplementing-scim-provisioning-with-okta\u002FSKILL.md",true,[93,99,103,109,113,117,123],{"path":94,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":97,"sourceHtmlUrl":98},"assets\u002Ftemplate.md","ASSET","资产文件",2541,"https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fcybersecurity-skills\u002Fskills\u002Fimplementing-scim-provisioning-with-okta\u002Fassets\u002Ftemplate.md",{"path":100,"resourceType":100,"resourceTypeDesc":101,"sizeBytes":102,"sourceHtmlUrl":16},"LICENSE","许可证",11255,{"path":104,"resourceType":105,"resourceTypeDesc":106,"sizeBytes":107,"sourceHtmlUrl":108},"references\u002Fapi-reference.md","REFERENCE","参考文档",4722,"https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fcybersecurity-skills\u002Fskills\u002Fimplementing-scim-provisioning-with-okta\u002Freferences\u002Fapi-reference.md",{"path":110,"resourceType":105,"resourceTypeDesc":106,"sizeBytes":111,"sourceHtmlUrl":112},"references\u002Fstandards.md",2315,"https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fcybersecurity-skills\u002Fskills\u002Fimplementing-scim-provisioning-with-okta\u002Freferences\u002Fstandards.md",{"path":114,"resourceType":105,"resourceTypeDesc":106,"sizeBytes":115,"sourceHtmlUrl":116},"references\u002Fworkflows.md",2903,"https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fcybersecurity-skills\u002Fskills\u002Fimplementing-scim-provisioning-with-okta\u002Freferences\u002Fworkflows.md",{"path":118,"resourceType":119,"resourceTypeDesc":120,"sizeBytes":121,"sourceHtmlUrl":122},"scripts\u002Fagent.py","SCRIPT","脚本",9251,"https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fcybersecurity-skills\u002Fskills\u002Fimplementing-scim-provisioning-with-okta\u002Fscripts\u002Fagent.py",{"path":124,"resourceType":119,"resourceTypeDesc":120,"sizeBytes":125,"sourceHtmlUrl":126},"scripts\u002Fprocess.py",15669,"https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fcybersecurity-skills\u002Fskills\u002Fimplementing-scim-provisioning-with-okta\u002Fscripts\u002Fprocess.py",[128,136,144,152,160,167],{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":132,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":135,"publishedAt":20},"01M7EFHX67M3KKXT1BXVPA5ADT","zarr-python","Chunked N-D arrays for cloud storage (Zarr-Python 3). Compressed arrays, parallel I\u002FO, S3\u002FGCS via fsspec, NumPy\u002FDask\u002FXarray compatible, for large-scale scientific computing pipelines.","MIT","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzarr-python\u002FSKILL.md",[],[],{"skillNo":137,"name":138,"nameZh":6,"description":139,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":132,"licenseFileUrl":140,"sourceHtmlUrl":141,"categories":142,"keywords":143,"publishedAt":20},"01M7EFFQGM51TZBGRENXY50ZYM","whiteboard-diagrams","Create accurate, simple, hand-drawn whiteboard diagrams from a user's process, system, architecture, learning workflow, comparison, or causal explanation. Use when the user asks for a scribbly whiteboard visual, educational workflow graphic, hand-drawn explainer, or diagram like the bundled reference; ask one focused clarification question when the subject or relationships are missing, then generate and visually verify the final image.","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwhiteboard-diagrams\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwhiteboard-diagrams\u002FSKILL.md",[],[],{"skillNo":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":148,"sourceHtmlUrl":149,"categories":150,"keywords":151,"publishedAt":20},"01M7EFF1CSQNTDMHFK4ZGY6NYK","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwebapp-testing\u002FSKILL.md",[],[],{"skillNo":153,"name":154,"nameZh":6,"description":155,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":156,"sourceHtmlUrl":157,"categories":158,"keywords":159,"publishedAt":20},"01M7EFE8106X6C28FT8PA74427","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fweb-artifacts-builder\u002FSKILL.md",[],[],{"skillNo":161,"name":162,"nameZh":6,"description":163,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":132,"licenseFileUrl":6,"sourceHtmlUrl":164,"categories":165,"keywords":166,"publishedAt":20},"01M7EFCSNZM9G7ZHS6F127Q71X","verification-loop","A comprehensive verification system for Claude Code sessions.","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fverification-loop\u002FSKILL.md",[],[],{"skillNo":168,"name":169,"nameZh":6,"description":170,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":132,"licenseFileUrl":171,"sourceHtmlUrl":172,"categories":173,"keywords":174,"publishedAt":20},"01M7EFCE7EZMKPRYDDNKBQ9EEH","vercel-deploy","Deploy applications and websites to Vercel. Use when the user requests deployment actions like \"deploy my app\", \"deploy and give me the link\", \"push this live\", or \"create a preview deployment\".","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvercel-deploy\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvercel-deploy\u002FSKILL.md",[],[]]