[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B8VZSZZWGSJCQRHJHSGX1P":3,"skill-same:01M7B8VZSZZWGSJCQRHJHSGX1P":100},{"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":46,"commitSha":47,"skillDirectory":48,"forksCount":13,"repositoryHtmlUrl":49,"repositoryHomepageUrl":6,"ownerHtmlUrl":50,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":51,"install":52,"resources":65},"01M7B8VZSZZWGSJCQRHJHSGX1P","performing-privileged-account-access-review",null,"Conducts systematic reviews of privileged accounts to validate access rights, identify excessive or stale permissions, and enforce least privilege across PAM infrastructure. Use when auditing privileged access for compliance, periodic access recertification, or investigating whether privileged entitlements are still justified.","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\u002Fperforming-privileged-account-access-review\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fperforming-privileged-account-access-review\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: performing-privileged-account-access-review\ndescription: Conducts systematic reviews of privileged accounts to validate access\n  rights, identify excessive or stale permissions, and enforce least privilege across\n  PAM infrastructure. Use when auditing privileged access for compliance, periodic\n  access recertification, or investigating whether privileged entitlements are still\n  justified.\ndomain: cybersecurity\nsubdomain: identity-access-management\ntags:\n- pam\n- access-review\n- privileged-accounts\n- least-privilege\n- compliance\n- audit\n- identity-governance\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\n---\n\n# Performing Privileged Account Access Review\n\n## Overview\n\nPrivileged Account Access Review is a critical identity governance process that validates whether users with elevated permissions still require their access. This review covers domain admins, service accounts, database administrators, cloud IAM roles, and application-level privileged accounts. Regular access reviews are mandated by SOC 2, PCI DSS, HIPAA, and SOX compliance frameworks, typically required quarterly for high-privilege accounts.\n\n\n## When to Use\n\n- When conducting security assessments that involve performing privileged account access review\n- When following incident response procedures for related security events\n- When performing scheduled security testing or auditing activities\n- When validating security controls through hands-on testing\n\n## Prerequisites\n\n- PAM solution deployed (CyberArk, BeyondTrust, Delinea, or equivalent)\n- Identity governance platform (SailPoint, Saviynt, or equivalent)\n- Complete inventory of privileged accounts across all platforms\n- Defined access review policy with SLAs and escalation procedures\n- Designated reviewers (account owners, managers, security team)\n\n## Core Concepts\n\n### Privileged Account Categories\n\n| Category | Examples | Risk Level | Review Frequency |\n|----------|----------|------------|-----------------|\n| Domain Admins | Enterprise Admin, Domain Admin, Schema Admin | Critical | Monthly |\n| Service Accounts | SQL service, backup agents, monitoring agents | High | Quarterly |\n| Cloud IAM | AWS root, Azure Global Admin, GCP Owner | Critical | Monthly |\n| Database Admin | DBA accounts, sa\u002Fsys accounts | High | Quarterly |\n| Application Admin | App admin roles, API keys with admin scope | Medium | Semi-annually |\n| Emergency\u002FBreak-glass | Firecall accounts, emergency access | Critical | After each use |\n\n### Four-Pillar Review Framework\n\n```\nDISCOVER                    VALIDATE                    REMEDIATE                 MONITOR\n    │                           │                           │                       │\n    ├─ Enumerate all            ├─ Verify business          ├─ Remove excess        ├─ Continuous\n    │  privileged accounts      │  justification            │  privileges           │  monitoring\n    │                           │                           │                       │\n    ├─ Identify orphaned        ├─ Confirm account          ├─ Disable orphaned     ├─ Anomaly\n    │  accounts                 │  ownership                │  accounts             │  detection\n    │                           │                           │                       │\n    ├─ Map permissions to       ├─ Check compliance         ├─ Enforce password     ├─ Session\n    │  business roles           │  with policies            │  rotation             │  recording\n    │                           │                           │                       │\n    └─ Classify by risk         └─ Review last usage        └─ Implement JIT        └─ Audit\n       level                       and activity                access                  logging\n```\n\n## Workflow\n\n### Step 1: Account Discovery and Inventory\n\nEnumerate all privileged accounts across the environment:\n\n**Active Directory:**\n- Domain Admins, Enterprise Admins, Schema Admins groups\n- Accounts with AdminCount=1 attribute\n- Service accounts with SPN (Service Principal Names)\n- Accounts with delegation rights (Unconstrained\u002FConstrained)\n\n**Cloud Platforms:**\n- AWS: IAM users\u002Froles with AdministratorAccess, PowerUserAccess, or `iam:*` permissions\n- Azure: Global Administrator, Privileged Role Administrator, Security Administrator roles\n- GCP: Owner, Editor roles at organization\u002Fproject level\n\n**Databases:**\n- SQL Server: sysadmin, db_owner, securityadmin fixed roles\n- Oracle: DBA, SYSDBA, SYSOPER privileges\n- PostgreSQL: superuser, createrole, createdb attributes\n\n### Step 2: Establish Review Criteria\n\nEach privileged account must be evaluated against:\n\n1. **Business Justification**: Does the user's current role require this privilege?\n2. **Least Privilege**: Can the task be performed with lower privileges?\n3. **Account Activity**: Has the account been active in the last 90 days?\n4. **Compliance Status**: Does the account meet password policy, MFA requirements?\n5. **Separation of Duties**: Does the access create SoD conflicts?\n6. **Ownership**: Is a responsible owner assigned and active?\n\n### Step 3: Conduct the Review\n\nFor each account, the designated reviewer must:\n\n1. Review the account details, permissions, and last activity date\n2. Approve (certify) the access if still required with documented justification\n3. Revoke access if no longer needed or the reviewer cannot justify the privilege\n4. Flag for investigation if anomalous activity or policy violations are detected\n5. Escalate if the reviewer cannot make a determination\n\nDecision matrix:\n\n| Condition | Action |\n|-----------|--------|\n| Active user, justified privilege | Certify - maintain access |\n| Active user, excessive privilege | Remediate - reduce to least privilege |\n| Inactive > 90 days | Disable account, notify owner |\n| No owner identified | Disable account, escalate to security |\n| SoD conflict detected | Remediate - reassign or add compensating controls |\n| Break-glass account | Verify last use was authorized, reset credentials |\n\n### Step 4: Remediation and Enforcement\n\nAfter reviews are completed:\n\n- Revoke access for accounts that were not certified within the SLA period\n- Implement automatic revocation for accounts not reviewed within 14 days\n- Rotate credentials for all certified privileged accounts\n- Convert standing privileges to just-in-time (JIT) access where possible\n- Update PAM vault with current account inventory\n\n### Step 5: Reporting and Documentation\n\nGenerate review reports including:\n\n- Total accounts reviewed vs. total in scope\n- Certification rate (approved vs. revoked)\n- Average review completion time\n- Overdue reviews and escalations\n- Remediation actions taken\n- Comparison with previous review cycle\n\n## Validation Checklist\n\n- [ ] Complete inventory of all privileged accounts documented\n- [ ] All accounts assigned to a responsible owner\u002Freviewer\n- [ ] Review criteria and decision matrix defined\n- [ ] Reviewers completed certification within SLA (14 days)\n- [ ] Revoked accounts disabled and credentials rotated\n- [ ] Orphaned accounts identified and disabled\n- [ ] Service accounts reviewed for least privilege\n- [ ] Break-glass accounts audited for authorized use only\n- [ ] Review report generated with metrics and trends\n- [ ] Remediation tickets created and tracked to completion\n- [ ] Evidence preserved for compliance audit\n\n## References\n\n- [NIST SP 800-53 AC-2: Account Management](https:\u002F\u002Fcsf.tools\u002Freference\u002Fnist-sp-800-53\u002Fr5\u002Fac\u002Fac-2\u002F)\n- [CIS Controls v8 - Control 5: Account Management](https:\u002F\u002Fwww.cisecurity.org\u002Fcontrols\u002Faccount-management)\n- [Netwrix PAM Best Practices Guide](https:\u002F\u002Fnetwrix.com\u002Fen\u002Fresources\u002Fguides\u002Fprivileged-account-management-best-practices\u002F)\n- [StrongDM PAM Best Practices 2025](https:\u002F\u002Fwww.strongdm.com\u002Fblog\u002Fprivileged-access-management-best-practices)\n","# Performing Privileged Account Access Review\n\n## Overview\n\nPrivileged Account Access Review is a critical identity governance process that validates whether users with elevated permissions still require their access. This review covers domain admins, service accounts, database administrators, cloud IAM roles, and application-level privileged accounts. Regular access reviews are mandated by SOC 2, PCI DSS, HIPAA, and SOX compliance frameworks, typically required quarterly for high-privilege accounts.\n\n\n## When to Use\n\n- When conducting security assessments that involve performing privileged account access review\n- When following incident response procedures for related security events\n- When performing scheduled security testing or auditing activities\n- When validating security controls through hands-on testing\n\n## Prerequisites\n\n- PAM solution deployed (CyberArk, BeyondTrust, Delinea, or equivalent)\n- Identity governance platform (SailPoint, Saviynt, or equivalent)\n- Complete inventory of privileged accounts across all platforms\n- Defined access review policy with SLAs and escalation procedures\n- Designated reviewers (account owners, managers, security team)\n\n## Core Concepts\n\n### Privileged Account Categories\n\n| Category | Examples | Risk Level | Review Frequency |\n|----------|----------|------------|-----------------|\n| Domain Admins | Enterprise Admin, Domain Admin, Schema Admin | Critical | Monthly |\n| Service Accounts | SQL service, backup agents, monitoring agents | High | Quarterly |\n| Cloud IAM | AWS root, Azure Global Admin, GCP Owner | Critical | Monthly |\n| Database Admin | DBA accounts, sa\u002Fsys accounts | High | Quarterly |\n| Application Admin | App admin roles, API keys with admin scope | Medium | Semi-annually |\n| Emergency\u002FBreak-glass | Firecall accounts, emergency access | Critical | After each use |\n\n### Four-Pillar Review Framework\n\n```\nDISCOVER                    VALIDATE                    REMEDIATE                 MONITOR\n    │                           │                           │                       │\n    ├─ Enumerate all            ├─ Verify business          ├─ Remove excess        ├─ Continuous\n    │  privileged accounts      │  justification            │  privileges           │  monitoring\n    │                           │                           │                       │\n    ├─ Identify orphaned        ├─ Confirm account          ├─ Disable orphaned     ├─ Anomaly\n    │  accounts                 │  ownership                │  accounts             │  detection\n    │                           │                           │                       │\n    ├─ Map permissions to       ├─ Check compliance         ├─ Enforce password     ├─ Session\n    │  business roles           │  with policies            │  rotation             │  recording\n    │                           │                           │                       │\n    └─ Classify by risk         └─ Review last usage        └─ Implement JIT        └─ Audit\n       level                       and activity                access                  logging\n```\n\n## Workflow\n\n### Step 1: Account Discovery and Inventory\n\nEnumerate all privileged accounts across the environment:\n\n**Active Directory:**\n- Domain Admins, Enterprise Admins, Schema Admins groups\n- Accounts with AdminCount=1 attribute\n- Service accounts with SPN (Service Principal Names)\n- Accounts with delegation rights (Unconstrained\u002FConstrained)\n\n**Cloud Platforms:**\n- AWS: IAM users\u002Froles with AdministratorAccess, PowerUserAccess, or `iam:*` permissions\n- Azure: Global Administrator, Privileged Role Administrator, Security Administrator roles\n- GCP: Owner, Editor roles at organization\u002Fproject level\n\n**Databases:**\n- SQL Server: sysadmin, db_owner, securityadmin fixed roles\n- Oracle: DBA, SYSDBA, SYSOPER privileges\n- PostgreSQL: superuser, createrole, createdb attributes\n\n### Step 2: Establish Review Criteria\n\nEach privileged account must be evaluated against:\n\n1. **Business Justification**: Does the user's current role require this privilege?\n2. **Least Privilege**: Can the task be performed with lower privileges?\n3. **Account Activity**: Has the account been active in the last 90 days?\n4. **Compliance Status**: Does the account meet password policy, MFA requirements?\n5. **Separation of Duties**: Does the access create SoD conflicts?\n6. **Ownership**: Is a responsible owner assigned and active?\n\n### Step 3: Conduct the Review\n\nFor each account, the designated reviewer must:\n\n1. Review the account details, permissions, and last activity date\n2. Approve (certify) the access if still required with documented justification\n3. Revoke access if no longer needed or the reviewer cannot justify the privilege\n4. Flag for investigation if anomalous activity or policy violations are detected\n5. Escalate if the reviewer cannot make a determination\n\nDecision matrix:\n\n| Condition | Action |\n|-----------|--------|\n| Active user, justified privilege | Certify - maintain access |\n| Active user, excessive privilege | Remediate - reduce to least privilege |\n| Inactive > 90 days | Disable account, notify owner |\n| No owner identified | Disable account, escalate to security |\n| SoD conflict detected | Remediate - reassign or add compensating controls |\n| Break-glass account | Verify last use was authorized, reset credentials |\n\n### Step 4: Remediation and Enforcement\n\nAfter reviews are completed:\n\n- Revoke access for accounts that were not certified within the SLA period\n- Implement automatic revocation for accounts not reviewed within 14 days\n- Rotate credentials for all certified privileged accounts\n- Convert standing privileges to just-in-time (JIT) access where possible\n- Update PAM vault with current account inventory\n\n### Step 5: Reporting and Documentation\n\nGenerate review reports including:\n\n- Total accounts reviewed vs. total in scope\n- Certification rate (approved vs. revoked)\n- Average review completion time\n- Overdue reviews and escalations\n- Remediation actions taken\n- Comparison with previous review cycle\n\n## Validation Checklist\n\n- [ ] Complete inventory of all privileged accounts documented\n- [ ] All accounts assigned to a responsible owner\u002Freviewer\n- [ ] Review criteria and decision matrix defined\n- [ ] Reviewers completed certification within SLA (14 days)\n- [ ] Revoked accounts disabled and credentials rotated\n- [ ] Orphaned accounts identified and disabled\n- [ ] Service accounts reviewed for least privilege\n- [ ] Break-glass accounts audited for authorized use only\n- [ ] Review report generated with metrics and trends\n- [ ] Remediation tickets created and tracked to completion\n- [ ] Evidence preserved for compliance audit\n\n## References\n\n- [NIST SP 800-53 AC-2: Account Management](https:\u002F\u002Fcsf.tools\u002Freference\u002Fnist-sp-800-53\u002Fr5\u002Fac\u002Fac-2\u002F)\n- [CIS Controls v8 - Control 5: Account Management](https:\u002F\u002Fwww.cisecurity.org\u002Fcontrols\u002Faccount-management)\n- [Netwrix PAM Best Practices Guide](https:\u002F\u002Fnetwrix.com\u002Fen\u002Fresources\u002Fguides\u002Fprivileged-account-management-best-practices\u002F)\n- [StrongDM PAM Best Practices 2025](https:\u002F\u002Fwww.strongdm.com\u002Fblog\u002Fprivileged-access-management-best-practices)\n",{"name":5,"tags":24,"author":32,"domain":33,"license":14,"version":34,"nist_csf":35,"subdomain":40,"description":7,"mitre_attack":41},[25,26,27,28,29,30,31],"pam","access-review","privileged-accounts","least-privilege","compliance","audit","identity-governance","mahipal","cybersecurity","1.0",[36,37,38,39],"PR.AA-01","PR.AA-02","PR.AA-05","PR.AA-06","identity-access-management",[42,43,44,45],"T1078","T1110","T1556","T1098","main","1eb986d0b0ecc180291597e08eb5a58288843536","skills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fperforming-privileged-account-access-review","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv","2026-08-25 13:16:33",{"source":8,"skillName":5,"commands":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add vikasvardhanv\u002Fjerry_skills --skill performing-privileged-account-access-review",{"tool":58,"command":59},"bunx","bunx skills add vikasvardhanv\u002Fjerry_skills --skill performing-privileged-account-access-review",{"tool":61,"command":62},"pnpm","pnpm dlx skills add vikasvardhanv\u002Fjerry_skills --skill performing-privileged-account-access-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fperforming-privileged-account-access-review\u002FSKILL.md",true,[66,72,76,82,86,90,96],{"path":67,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":70,"sourceHtmlUrl":71},"assets\u002Ftemplate.md","ASSET","资产文件",1695,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fperforming-privileged-account-access-review\u002Fassets\u002Ftemplate.md",{"path":73,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":75,"sourceHtmlUrl":15},"LICENSE","许可证",11255,{"path":77,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Fapi-reference.md","REFERENCE","参考文档",2403,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fperforming-privileged-account-access-review\u002Freferences\u002Fapi-reference.md",{"path":83,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":84,"sourceHtmlUrl":85},"references\u002Fstandards.md",2249,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fperforming-privileged-account-access-review\u002Freferences\u002Fstandards.md",{"path":87,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":88,"sourceHtmlUrl":89},"references\u002Fworkflows.md",3543,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fperforming-privileged-account-access-review\u002Freferences\u002Fworkflows.md",{"path":91,"resourceType":92,"resourceTypeDesc":93,"sizeBytes":94,"sourceHtmlUrl":95},"scripts\u002Fagent.py","SCRIPT","脚本",5842,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fperforming-privileged-account-access-review\u002Fscripts\u002Fagent.py",{"path":97,"resourceType":92,"resourceTypeDesc":93,"sizeBytes":98,"sourceHtmlUrl":99},"scripts\u002Fprocess.py",12693,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fperforming-privileged-account-access-review\u002Fscripts\u002Fprocess.py",[101,109,116,123,130,137],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":105,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"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":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":105,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"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":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":105,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"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":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":105,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":129,"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":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":105,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":136,"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":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":105,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":143,"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",[],[]]