[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B72E4EQ8HXD0C8HECTKZAS":3,"skill-same:01M7B72E4EQ8HXD0C8HECTKZAS":121},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":15,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":67,"commitSha":68,"skillDirectory":69,"forksCount":13,"repositoryHtmlUrl":70,"repositoryHomepageUrl":6,"ownerHtmlUrl":71,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":72,"install":73,"resources":86},"01M7B72E4EQ8HXD0C8HECTKZAS","implementing-azure-ad-privileged-identity-management",null,"Configure Microsoft Entra Privileged Identity Management (PIM) to convert standing privileged assignments into eligible, time-bound roles requiring justification, MFA, and approval, covering Entra roles, Azure resource roles, and PIM for Groups, plus access reviews. Use for role-assignment audits, just-in-time admin activation, or Zero Trust identity governance in Entra\u002FAzure AD.","vikasvardhanv\u002Fjerry_skills","vikasvardhanv","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F99010657?v=4","01M7B2B0VN78W7529RQX5BR6DZ","01M7B2B0WDNTXJHRK3QNPNWRP6",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fimplementing-azure-ad-privileged-identity-management\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fimplementing-azure-ad-privileged-identity-management\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: implementing-azure-ad-privileged-identity-management\ndescription: Configure Microsoft Entra Privileged Identity Management (PIM) to convert\n  standing privileged assignments into eligible, time-bound roles requiring justification,\n  MFA, and approval, covering Entra roles, Azure resource roles, and PIM for Groups,\n  plus access reviews. Use for role-assignment audits, just-in-time admin activation,\n  or Zero Trust identity governance in Entra\u002FAzure AD.\ndomain: cybersecurity\nsubdomain: identity-access-management\ntags:\n- azure-ad\n- pim\n- entra-id\n- just-in-time\n- privileged-roles\n- identity-governance\n- zero-trust\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  - defense-impairment\n  techniques:\n  - id: F1006\n    name: Account Takeover\n    tactic: initial-access\n    source: f3\n  - id: T1110.003\n    name: 'Brute Force: Password Spraying'\n    tactic: initial-access\n    source: attack\n  - id: F1005\n    name: Account Manipulation\n    tactic: positioning\n    source: f3\n  - id: F1005.002\n    name: 'Account Manipulation: Add Authorized User'\n    tactic: defense-impairment\n    source: f3\n---\n\n# Implementing Azure AD Privileged Identity Management\n\n## Overview\n\nMicrosoft Entra Privileged Identity Management (PIM) provides time-based and approval-based role activation to mitigate risks from excessive, unnecessary, or misused access to critical resources. PIM replaces permanent (standing) privilege assignments with eligible assignments that require users to explicitly activate their role before use, with configurable duration, MFA enforcement, approval workflows, and justification requirements. This is a core component of Zero Trust identity governance in Microsoft environments.\n\n\n## When to Use\n\n- When deploying or configuring implementing azure ad privileged identity management 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- Microsoft Entra ID P2 or Microsoft Entra ID Governance license\n- Global Administrator or Privileged Role Administrator role\n- Azure subscription for Azure resource role management\n- MFA configured for all privileged users\n- Microsoft Authenticator or FIDO2 key for admin accounts\n\n## Core Concepts\n\n### Assignment Types\n\n| Type | Behavior | Use Case |\n|------|----------|----------|\n| Eligible | User must activate the role before use; expires after configured duration | Day-to-day admin work |\n| Active | Role is always active; no activation needed | Service accounts, break-glass accounts |\n| Time-Bound | Either type with explicit start\u002Fend dates | Temporary project access, contractor access |\n\n### PIM Activation Flow\n\n```\nUser with Eligible Assignment\n        │\n        ├── Opens PIM portal → My Roles\n        │\n        ├── Clicks \"Activate\" on the desired role\n        │\n        ├── Provides justification and optional ticket number\n        │\n        ├── Completes MFA challenge (if required)\n        │\n        ├── [If approval required] → Notification sent to approvers\n        │       │\n        │       ├── Approver reviews and approves\u002Fdenies\n        │       └── User notified of decision\n        │\n        ├── Role activated for configured duration (e.g., 8 hours)\n        │\n        └── Role automatically deactivated when duration expires\n```\n\n### Supported Resource Types\n\n1. **Microsoft Entra Roles**: Global Admin, Exchange Admin, Security Admin, etc.\n2. **Azure Resource Roles**: Owner, Contributor, User Access Administrator on subscriptions\u002Fresource groups\n3. **PIM for Groups**: Manage membership in privileged security groups\n\n## Workflow\n\n### Step 1: Plan Role Assignments\n\nAudit current permanent role assignments and determine which should be converted to eligible:\n\n| Current Role | Permanent Holders | Action |\n|-------------|-------------------|--------|\n| Global Administrator | 2-3 admins | Convert to eligible, keep 1 break-glass active |\n| Exchange Administrator | IT team | Convert all to eligible |\n| Security Administrator | SOC team | Convert to eligible |\n| User Administrator | Help desk | Convert to eligible |\n| Application Administrator | DevOps | Convert to eligible |\n\nBest practice: Maintain no more than 2 permanent Global Administrators (break-glass accounts).\n\n### Step 2: Configure Role Settings\n\nFor each Entra directory role, configure PIM settings:\n\n**Via Microsoft Entra Admin Center:**\n1. Navigate to Identity Governance > Privileged Identity Management > Microsoft Entra roles\n2. Select \"Settings\" and choose the role to configure\n3. Configure the following:\n\n**Activation Settings:**\n- Maximum activation duration: 8 hours (recommended; max 72 hours)\n- Require MFA on activation: Enabled\n- Require justification: Enabled\n- Require ticket information: Enabled (for change management integration)\n- Require approval: Enabled for Global Admin, Security Admin\n\n**Assignment Settings:**\n- Allow permanent eligible assignment: No (set expiry)\n- Expire eligible assignments after: 6 months (requires re-certification)\n- Allow permanent active assignment: Only for break-glass accounts\n- Require MFA on active assignment: Enabled\n- Require justification on active assignment: Enabled\n\n**Notification Settings:**\n- Send email when members are assigned eligible: Role assigners, admins\n- Send email when members activate: Admins, security team\n- Send email when eligible members activate roles: Role assignees\n\n### Step 3: Configure via Microsoft Graph API\n\n```python\nimport requests\n\n# Acquire token for Microsoft Graph\ndef get_graph_token(tenant_id, client_id, client_secret):\n    url = f\"https:\u002F\u002Flogin.microsoftonline.com\u002F{tenant_id}\u002Foauth2\u002Fv2.0\u002Ftoken\"\n    data = {\n        \"grant_type\": \"client_credentials\",\n        \"client_id\": client_id,\n        \"client_secret\": client_secret,\n        \"scope\": \"https:\u002F\u002Fgraph.microsoft.com\u002F.default\"\n    }\n    response = requests.post(url, data=data)\n    return response.json()[\"access_token\"]\n\n# Create eligible role assignment\ndef create_eligible_assignment(token, role_definition_id, principal_id,\n                                directory_scope=\"\u002F\", duration_hours=8):\n    url = \"https:\u002F\u002Fgraph.microsoft.com\u002Fv1.0\u002FroleManagement\u002Fdirectory\u002FroleEligibilityScheduleRequests\"\n    headers = {\n        \"Authorization\": f\"Bearer {token}\",\n        \"Content-Type\": \"application\u002Fjson\"\n    }\n    body = {\n        \"action\": \"adminAssign\",\n        \"justification\": \"PIM eligible assignment\",\n        \"roleDefinitionId\": role_definition_id,\n        \"directoryScopeId\": directory_scope,\n        \"principalId\": principal_id,\n        \"scheduleInfo\": {\n            \"startDateTime\": \"2025-01-01T00:00:00Z\",\n            \"expiration\": {\n                \"type\": \"afterDuration\",\n                \"duration\": \"P180D\"  # 180-day eligible window\n            }\n        }\n    }\n    response = requests.post(url, headers=headers, json=body)\n    return response.json()\n\n# Activate a role (user self-service)\ndef activate_role(token, role_definition_id, principal_id, justification,\n                   duration_hours=8):\n    url = \"https:\u002F\u002Fgraph.microsoft.com\u002Fv1.0\u002FroleManagement\u002Fdirectory\u002FroleAssignmentScheduleRequests\"\n    headers = {\n        \"Authorization\": f\"Bearer {token}\",\n        \"Content-Type\": \"application\u002Fjson\"\n    }\n    body = {\n        \"action\": \"selfActivate\",\n        \"principalId\": principal_id,\n        \"roleDefinitionId\": role_definition_id,\n        \"directoryScopeId\": \"\u002F\",\n        \"justification\": justification,\n        \"scheduleInfo\": {\n            \"startDateTime\": None,  # Now\n            \"expiration\": {\n                \"type\": \"afterDuration\",\n                \"duration\": f\"PT{duration_hours}H\"\n            }\n        }\n    }\n    response = requests.post(url, headers=headers, json=body)\n    return response.json()\n```\n\n### Step 4: Configure Access Reviews\n\nSet up recurring access reviews to verify eligible assignments remain appropriate:\n\n1. Navigate to Identity Governance > Access Reviews > New Access Review\n2. Configure:\n   - Review scope: Privileged Identity Management role assignments\n   - Roles: Select all critical roles (Global Admin, Security Admin, etc.)\n   - Reviewers: Managers or self-review with justification\n   - Frequency: Quarterly for critical roles, semi-annually for others\n   - Auto-apply results: Remove access for non-responsive reviews\n   - Duration: 14 days for reviewers to respond\n\n### Step 5: Configure Alerts\n\nEnable PIM security alerts:\n\n| Alert | Trigger | Action |\n|-------|---------|--------|\n| Too many global admins | > 5 Global Admins | Review and reduce |\n| Roles being assigned outside PIM | Direct role assignment | Investigate and convert to PIM |\n| Roles not requiring MFA | Activation without MFA | Enable MFA requirement |\n| Stale eligible assignments | Not activated in 90 days | Review and potentially remove |\n| Potential stale service accounts | Active assignments not used | Investigate and decommission |\n\n## Validation Checklist\n\n- [ ] All permanent privileged role assignments converted to eligible (except break-glass)\n- [ ] Break-glass accounts configured as active with monitoring alerts\n- [ ] MFA required for all role activations\n- [ ] Approval workflow configured for Global Administrator and Security Administrator\n- [ ] Maximum activation duration set to 8 hours or less for critical roles\n- [ ] Eligible assignments expire after 6 months (requires re-certification)\n- [ ] Justification and ticket information required for activations\n- [ ] Email notifications configured for role assignments and activations\n- [ ] Access reviews scheduled quarterly for all privileged roles\n- [ ] PIM alerts enabled and reviewed weekly\n- [ ] Audit logs forwarded to SIEM for monitoring\n\n## References\n\n- [Microsoft Entra PIM Documentation](https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fentra\u002Fid-governance\u002Fprivileged-identity-management\u002Fpim-configure)\n- [Plan a PIM Deployment](https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fentra\u002Fid-governance\u002Fprivileged-identity-management\u002Fpim-deployment-plan)\n- [Start Using PIM](https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fentra\u002Fid-governance\u002Fprivileged-identity-management\u002Fpim-getting-started)\n- [Microsoft Graph PIM API](https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fgraph\u002Fapi\u002Fresources\u002Fprivilegedidentitymanagementv3-overview)\n","# Implementing Azure AD Privileged Identity Management\n\n## Overview\n\nMicrosoft Entra Privileged Identity Management (PIM) provides time-based and approval-based role activation to mitigate risks from excessive, unnecessary, or misused access to critical resources. PIM replaces permanent (standing) privilege assignments with eligible assignments that require users to explicitly activate their role before use, with configurable duration, MFA enforcement, approval workflows, and justification requirements. This is a core component of Zero Trust identity governance in Microsoft environments.\n\n\n## When to Use\n\n- When deploying or configuring implementing azure ad privileged identity management 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- Microsoft Entra ID P2 or Microsoft Entra ID Governance license\n- Global Administrator or Privileged Role Administrator role\n- Azure subscription for Azure resource role management\n- MFA configured for all privileged users\n- Microsoft Authenticator or FIDO2 key for admin accounts\n\n## Core Concepts\n\n### Assignment Types\n\n| Type | Behavior | Use Case |\n|------|----------|----------|\n| Eligible | User must activate the role before use; expires after configured duration | Day-to-day admin work |\n| Active | Role is always active; no activation needed | Service accounts, break-glass accounts |\n| Time-Bound | Either type with explicit start\u002Fend dates | Temporary project access, contractor access |\n\n### PIM Activation Flow\n\n```\nUser with Eligible Assignment\n        │\n        ├── Opens PIM portal → My Roles\n        │\n        ├── Clicks \"Activate\" on the desired role\n        │\n        ├── Provides justification and optional ticket number\n        │\n        ├── Completes MFA challenge (if required)\n        │\n        ├── [If approval required] → Notification sent to approvers\n        │       │\n        │       ├── Approver reviews and approves\u002Fdenies\n        │       └── User notified of decision\n        │\n        ├── Role activated for configured duration (e.g., 8 hours)\n        │\n        └── Role automatically deactivated when duration expires\n```\n\n### Supported Resource Types\n\n1. **Microsoft Entra Roles**: Global Admin, Exchange Admin, Security Admin, etc.\n2. **Azure Resource Roles**: Owner, Contributor, User Access Administrator on subscriptions\u002Fresource groups\n3. **PIM for Groups**: Manage membership in privileged security groups\n\n## Workflow\n\n### Step 1: Plan Role Assignments\n\nAudit current permanent role assignments and determine which should be converted to eligible:\n\n| Current Role | Permanent Holders | Action |\n|-------------|-------------------|--------|\n| Global Administrator | 2-3 admins | Convert to eligible, keep 1 break-glass active |\n| Exchange Administrator | IT team | Convert all to eligible |\n| Security Administrator | SOC team | Convert to eligible |\n| User Administrator | Help desk | Convert to eligible |\n| Application Administrator | DevOps | Convert to eligible |\n\nBest practice: Maintain no more than 2 permanent Global Administrators (break-glass accounts).\n\n### Step 2: Configure Role Settings\n\nFor each Entra directory role, configure PIM settings:\n\n**Via Microsoft Entra Admin Center:**\n1. Navigate to Identity Governance > Privileged Identity Management > Microsoft Entra roles\n2. Select \"Settings\" and choose the role to configure\n3. Configure the following:\n\n**Activation Settings:**\n- Maximum activation duration: 8 hours (recommended; max 72 hours)\n- Require MFA on activation: Enabled\n- Require justification: Enabled\n- Require ticket information: Enabled (for change management integration)\n- Require approval: Enabled for Global Admin, Security Admin\n\n**Assignment Settings:**\n- Allow permanent eligible assignment: No (set expiry)\n- Expire eligible assignments after: 6 months (requires re-certification)\n- Allow permanent active assignment: Only for break-glass accounts\n- Require MFA on active assignment: Enabled\n- Require justification on active assignment: Enabled\n\n**Notification Settings:**\n- Send email when members are assigned eligible: Role assigners, admins\n- Send email when members activate: Admins, security team\n- Send email when eligible members activate roles: Role assignees\n\n### Step 3: Configure via Microsoft Graph API\n\n```python\nimport requests\n\n# Acquire token for Microsoft Graph\ndef get_graph_token(tenant_id, client_id, client_secret):\n    url = f\"https:\u002F\u002Flogin.microsoftonline.com\u002F{tenant_id}\u002Foauth2\u002Fv2.0\u002Ftoken\"\n    data = {\n        \"grant_type\": \"client_credentials\",\n        \"client_id\": client_id,\n        \"client_secret\": client_secret,\n        \"scope\": \"https:\u002F\u002Fgraph.microsoft.com\u002F.default\"\n    }\n    response = requests.post(url, data=data)\n    return response.json()[\"access_token\"]\n\n# Create eligible role assignment\ndef create_eligible_assignment(token, role_definition_id, principal_id,\n                                directory_scope=\"\u002F\", duration_hours=8):\n    url = \"https:\u002F\u002Fgraph.microsoft.com\u002Fv1.0\u002FroleManagement\u002Fdirectory\u002FroleEligibilityScheduleRequests\"\n    headers = {\n        \"Authorization\": f\"Bearer {token}\",\n        \"Content-Type\": \"application\u002Fjson\"\n    }\n    body = {\n        \"action\": \"adminAssign\",\n        \"justification\": \"PIM eligible assignment\",\n        \"roleDefinitionId\": role_definition_id,\n        \"directoryScopeId\": directory_scope,\n        \"principalId\": principal_id,\n        \"scheduleInfo\": {\n            \"startDateTime\": \"2025-01-01T00:00:00Z\",\n            \"expiration\": {\n                \"type\": \"afterDuration\",\n                \"duration\": \"P180D\"  # 180-day eligible window\n            }\n        }\n    }\n    response = requests.post(url, headers=headers, json=body)\n    return response.json()\n\n# Activate a role (user self-service)\ndef activate_role(token, role_definition_id, principal_id, justification,\n                   duration_hours=8):\n    url = \"https:\u002F\u002Fgraph.microsoft.com\u002Fv1.0\u002FroleManagement\u002Fdirectory\u002FroleAssignmentScheduleRequests\"\n    headers = {\n        \"Authorization\": f\"Bearer {token}\",\n        \"Content-Type\": \"application\u002Fjson\"\n    }\n    body = {\n        \"action\": \"selfActivate\",\n        \"principalId\": principal_id,\n        \"roleDefinitionId\": role_definition_id,\n        \"directoryScopeId\": \"\u002F\",\n        \"justification\": justification,\n        \"scheduleInfo\": {\n            \"startDateTime\": None,  # Now\n            \"expiration\": {\n                \"type\": \"afterDuration\",\n                \"duration\": f\"PT{duration_hours}H\"\n            }\n        }\n    }\n    response = requests.post(url, headers=headers, json=body)\n    return response.json()\n```\n\n### Step 4: Configure Access Reviews\n\nSet up recurring access reviews to verify eligible assignments remain appropriate:\n\n1. Navigate to Identity Governance > Access Reviews > New Access Review\n2. Configure:\n   - Review scope: Privileged Identity Management role assignments\n   - Roles: Select all critical roles (Global Admin, Security Admin, etc.)\n   - Reviewers: Managers or self-review with justification\n   - Frequency: Quarterly for critical roles, semi-annually for others\n   - Auto-apply results: Remove access for non-responsive reviews\n   - Duration: 14 days for reviewers to respond\n\n### Step 5: Configure Alerts\n\nEnable PIM security alerts:\n\n| Alert | Trigger | Action |\n|-------|---------|--------|\n| Too many global admins | > 5 Global Admins | Review and reduce |\n| Roles being assigned outside PIM | Direct role assignment | Investigate and convert to PIM |\n| Roles not requiring MFA | Activation without MFA | Enable MFA requirement |\n| Stale eligible assignments | Not activated in 90 days | Review and potentially remove |\n| Potential stale service accounts | Active assignments not used | Investigate and decommission |\n\n## Validation Checklist\n\n- [ ] All permanent privileged role assignments converted to eligible (except break-glass)\n- [ ] Break-glass accounts configured as active with monitoring alerts\n- [ ] MFA required for all role activations\n- [ ] Approval workflow configured for Global Administrator and Security Administrator\n- [ ] Maximum activation duration set to 8 hours or less for critical roles\n- [ ] Eligible assignments expire after 6 months (requires re-certification)\n- [ ] Justification and ticket information required for activations\n- [ ] Email notifications configured for role assignments and activations\n- [ ] Access reviews scheduled quarterly for all privileged roles\n- [ ] PIM alerts enabled and reviewed weekly\n- [ ] Audit logs forwarded to SIEM for monitoring\n\n## References\n\n- [Microsoft Entra PIM Documentation](https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fentra\u002Fid-governance\u002Fprivileged-identity-management\u002Fpim-configure)\n- [Plan a PIM Deployment](https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fentra\u002Fid-governance\u002Fprivileged-identity-management\u002Fpim-deployment-plan)\n- [Start Using PIM](https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fentra\u002Fid-governance\u002Fprivileged-identity-management\u002Fpim-getting-started)\n- [Microsoft Graph PIM API](https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fgraph\u002Fapi\u002Fresources\u002Fprivilegedidentitymanagementv3-overview)\n",{"name":5,"tags":24,"author":32,"domain":33,"license":14,"version":34,"mitre_f3":35,"nist_csf":56,"subdomain":61,"description":7,"mitre_attack":62},[25,26,27,28,29,30,31],"azure-ad","pim","entra-id","just-in-time","privileged-roles","identity-governance","zero-trust","mahipal","cybersecurity","1.0",{"tactics":36,"version":40,"techniques":41},[37,38,39],"initial-access","positioning","defense-impairment","1.1",[42,46,50,53],{"id":43,"name":44,"source":45,"tactic":37},"F1006","Account Takeover","f3",{"id":47,"name":48,"source":49,"tactic":37},"T1110.003","Brute Force: Password Spraying","attack",{"id":51,"name":52,"source":45,"tactic":38},"F1005","Account Manipulation",{"id":54,"name":55,"source":45,"tactic":39},"F1005.002","Account Manipulation: Add Authorized User",[57,58,59,60],"PR.AA-01","PR.AA-02","PR.AA-05","PR.AA-06","identity-access-management",[63,64,65,66],"T1078","T1110","T1556","T1098","main","1eb986d0b0ecc180291597e08eb5a58288843536","skills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fimplementing-azure-ad-privileged-identity-management","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv","2026-08-25 13:16:33",{"source":8,"skillName":5,"commands":74,"prompt":84,"zipAvailable":85},[75,78,81],{"tool":76,"command":77},"npx","npx skills add vikasvardhanv\u002Fjerry_skills --skill implementing-azure-ad-privileged-identity-management",{"tool":79,"command":80},"bunx","bunx skills add vikasvardhanv\u002Fjerry_skills --skill implementing-azure-ad-privileged-identity-management",{"tool":82,"command":83},"pnpm","pnpm dlx skills add vikasvardhanv\u002Fjerry_skills --skill implementing-azure-ad-privileged-identity-management","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fimplementing-azure-ad-privileged-identity-management\u002FSKILL.md",true,[87,93,97,103,107,111,117],{"path":88,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":91,"sourceHtmlUrl":92},"assets\u002Ftemplate.md","ASSET","资产文件",1979,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fimplementing-azure-ad-privileged-identity-management\u002Fassets\u002Ftemplate.md",{"path":94,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":96,"sourceHtmlUrl":15},"LICENSE","许可证",11255,{"path":98,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":101,"sourceHtmlUrl":102},"references\u002Fapi-reference.md","REFERENCE","参考文档",1951,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fimplementing-azure-ad-privileged-identity-management\u002Freferences\u002Fapi-reference.md",{"path":104,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":105,"sourceHtmlUrl":106},"references\u002Fstandards.md",2034,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fimplementing-azure-ad-privileged-identity-management\u002Freferences\u002Fstandards.md",{"path":108,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":109,"sourceHtmlUrl":110},"references\u002Fworkflows.md",3880,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fimplementing-azure-ad-privileged-identity-management\u002Freferences\u002Fworkflows.md",{"path":112,"resourceType":113,"resourceTypeDesc":114,"sizeBytes":115,"sourceHtmlUrl":116},"scripts\u002Fagent.py","SCRIPT","脚本",6070,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fimplementing-azure-ad-privileged-identity-management\u002Fscripts\u002Fagent.py",{"path":118,"resourceType":113,"resourceTypeDesc":114,"sizeBytes":119,"sourceHtmlUrl":120},"scripts\u002Fprocess.py",8510,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fimplementing-azure-ad-privileged-identity-management\u002Fscripts\u002Fprocess.py",[122,130,137,144,151,158],{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":126,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":19},"01M7BESR1CJ3H5SP9XM8KYJZ9W","syllabus","Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Use when the user uploads a syllabus, course outline, or curriculum document and wants supplementary readings (e.g., 'create a reading list from this syllabus', 'find recent papers for my course') — even casual mentions with a syllabus attached should trigger this skill.","MIT","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\u002FSKILL.md",[],[],{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":126,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":136,"publishedAt":19},"01M7BES1YA6R97W7QPMFFM1PED","pulse","Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X\u002FTwitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend\u002Fsentiment\u002Fproblems\u002Fopportunities\u002Fcomparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Use when the user requests multi-source recency intelligence on a topic (e.g., 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]'), and for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\u002FSKILL.md",[],[],{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":126,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":143,"publishedAt":19},"01M7BERNHYGY035AR00VRT03KE","patent","Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search \u002F freedom-to-operate \u002F competitive landscape \u002F acquisition diligence \u002F litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Use when the user asks for patent searching or analysis (e.g., 'prior art search for [invention]', 'freedom to operate analysis for [product]'). Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\u002FSKILL.md",[],[],{"skillNo":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":126,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":150,"publishedAt":19},"01M7BERCK1EAKTWW7R436WAR0J","notebooklm","Browser automation skill for controlling Google's NotebookLM. Use when the user wants anything done in NotebookLM (e.g., 'open NotebookLM', 'check my [name] notebook', 'ask my notebook about X', 'add [source] to NotebookLM', 'generate a Video Overview from my notebook', 'use NotebookLM Studio'). Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio\u002FVideo Overviews, Mind Maps, Reports incl. Briefing Doc\u002FStudy Guide\u002FFAQ, Flashcards, Quiz, slide decks, infographics — discover the exact set from the live Studio panel; the UI evolves fast), and creating new notebooks. Requires browser automation environment — fails gracefully when unavailable.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fnotebooklm\u002Fskills\u002Fnotebooklm\u002FSKILL.md",[],[],{"skillNo":152,"name":153,"nameZh":6,"description":154,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":126,"licenseFileUrl":6,"sourceHtmlUrl":155,"categories":156,"keywords":157,"publishedAt":19},"01M7BEQZAZAQRTXFJRY7RHV3TY","litreview","Academic literature orientation skill that searches papers via free keyless APIs (PubMed E-utilities + OpenAlex) by default — with the Consensus MCP as an optional enhancement lane when connected — builds a strategic search plan using PICO (default) or SPIDER \u002F Decomposition \u002F hybrid as fallbacks, and synthesizes findings into a formatted Word (.docx) research guide. Grill-me intake (research question specificity + framework hint + tentative depth) before the recon search; a second forcing checkpoint after Phase 2 confirms framework + sub-areas + depth before searches consume budget. Configurable depth (5\u002F10\u002F20 queries) controls coverage vs. speed. Output is a 'launching pad' — an orientation guide that lets a researcher dive in confidently, not a finished review. Use when the user starts literature-oriented research (e.g., 'litreview on [topic]', 'literature review on [topic]', 'I'm starting a literature review on X', 'I'm writing a paper on X', 'help me research X', 'I'm doing research on X', 'can you help me research X'). Do NOT use for single one-off paper searches wanting a quick list — that's a plain PubMed\u002FOpenAlex (or Consensus) query.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Flitreview\u002Fskills\u002Flitreview\u002FSKILL.md",[],[],{"skillNo":159,"name":160,"nameZh":6,"description":161,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":126,"licenseFileUrl":6,"sourceHtmlUrl":162,"categories":163,"keywords":164,"publishedAt":19},"01M7BEQKJ45K31QK5VRAQSVJCJ","grants","NIH grant research skill for clinical researchers. Grill-me intake (research idea + career stage + preliminary data + environment + submission posture + known institute targets) locks down the funding strategy before any search runs. Runs a 5-facet Consensus positioning analysis (with draft Significance\u002FInnovation language), maps the research to the right NIH institutes and study sections via RePORTER, finds NOSIs and funded overlap, and produces an editable Word document (.docx) with budget\u002Fscope-aware mechanism recommendations, submission timelines, and a mandatory program officer recommendation. Use when the user asks about research funding or makes any grant-related request (e.g., 'grants for [topic]', 'find grants for my research idea', 'what grants match my research', 'help me find NIH funding', 'grant opportunities for my research'). NIH-only scope — non-NIH funders (PCORI, DOD CDMRP, VA, foundations) are out of scope and flagged at intake.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fgrants\u002Fskills\u002Fgrants\u002FSKILL.md",[],[]]