[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B76ZPXXM98YRSC33DDE3EQ":3,"skill-same:01M7B76ZPXXM98YRSC33DDE3EQ":106},{"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":70,"commitSha":71,"skillDirectory":72,"forksCount":13,"repositoryHtmlUrl":73,"repositoryHomepageUrl":6,"ownerHtmlUrl":74,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":75,"install":76,"resources":89},"01M7B76ZPXXM98YRSC33DDE3EQ","implementing-delinea-secret-server-for-pam",null,"Implements Delinea Secret Server for privileged access management, covering secret vault configuration, role-based access policies, automated password rotation, session recording, and Active Directory\u002Fcloud integration. Use when centralizing privileged credential management, replacing spreadsheet-based secrets, automating password rotation, or meeting PAM compliance (SOX, PCI-DSS, HIPAA, NIST 800-53).","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-delinea-secret-server-for-pam\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fimplementing-delinea-secret-server-for-pam\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: implementing-delinea-secret-server-for-pam\ndescription: 'Implements Delinea Secret Server for privileged access management,\n  covering secret vault configuration, role-based access policies, automated password\n  rotation, session recording, and Active Directory\u002Fcloud integration. Use when centralizing\n  privileged credential management, replacing spreadsheet-based secrets, automating\n  password rotation, or meeting PAM compliance (SOX, PCI-DSS, HIPAA, NIST 800-53).\n\n  '\ndomain: cybersecurity\nsubdomain: identity-access-management\ntags:\n- PAM\n- Delinea\n- Secret-Server\n- privileged-access\n- password-vault\n- credential-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\n- T1003\nmitre_f3:\n  version: '1.1'\n  tactics:\n  - reconnaissance\n  - initial-access\n  - positioning\n  techniques:\n  - id: T1555.005\n    name: 'Credentials from Password Stores: Password Managers'\n    tactic: reconnaissance\n    source: attack\n  - id: T1110\n    name: Brute Force\n    tactic: initial-access\n    source: attack\n  - id: F1006\n    name: Account Takeover\n    tactic: initial-access\n    source: f3\n  - id: F1006.002\n    name: 'Account Takeover: Exposed Login Credential'\n    tactic: initial-access\n    source: f3\n  - id: F1005\n    name: Account Manipulation\n    tactic: positioning\n    source: f3\n---\n\n# Implementing Delinea Secret Server for PAM\n\n## When to Use\n\n- Organization needs centralized privileged credential management across hybrid infrastructure\n- Compliance requirements mandate privileged access controls (SOX, PCI-DSS, HIPAA, NIST 800-53)\n- Service accounts and shared credentials are stored in spreadsheets or plaintext files\n- Need to implement automated password rotation for privileged accounts\n- Require session recording and keystroke logging for privileged user activity\n- Migrating from manual PAM processes to an enterprise vault solution\n\n**Do not use** for standard end-user password management; Delinea Secret Server is designed for privileged and shared account credential management requiring enterprise-grade controls.\n\n## Prerequisites\n\n- Delinea Secret Server license (On-Premises or Cloud)\n- Windows Server 2019\u002F2022 for on-premises deployment with IIS and SQL Server\n- Active Directory service account with read permissions for discovery\n- SSL\u002FTLS certificate for web interface encryption\n- Network connectivity to target systems for password rotation\n- PowerShell 5.1+ for automation scripts\n\n## Workflow\n\n### Step 1: Deploy Secret Server Infrastructure\n\nInstall and configure the Secret Server application server:\n\n```powershell\n# Pre-installation checks for on-premises deployment\n# Verify IIS is installed with required features\nImport-Module ServerManager\nInstall-WindowsFeature Web-Server, Web-Asp-Net45, Web-Windows-Auth, Web-Mgmt-Console\n\n# Verify SQL Server connectivity\n$sqlConn = New-Object System.Data.SqlClient.SqlConnection\n$sqlConn.ConnectionString = \"Server=sql01.corp.local;Database=master;Integrated Security=True\"\n$sqlConn.Open()\nWrite-Host \"SQL Server connection successful: $($sqlConn.ServerVersion)\"\n$sqlConn.Close()\n\n# Create Secret Server database\nInvoke-Sqlcmd -ServerInstance \"sql01.corp.local\" -Query @\"\nCREATE DATABASE SecretServer\nGO\nALTER DATABASE SecretServer SET RECOVERY FULL\nGO\n\"@\n\n# Download and run Secret Server installer\n# Navigate to https:\u002F\u002Fthy.center\u002Fss\u002Flink\u002FSSDownload for latest version\n# Run setup.exe and follow the installation wizard\n\n# Post-installation: Configure application pool\nImport-Module WebAdministration\nSet-ItemProperty \"IIS:\\AppPools\\SecretServer\" -Name processModel.identityType -Value SpecificUser\nSet-ItemProperty \"IIS:\\AppPools\\SecretServer\" -Name processModel.userName -Value \"CORP\\svc-secretserver\"\n```\n\n### Step 2: Configure Secret Templates and Folder Structure\n\nDefine secret templates and organize the vault hierarchy:\n\n```powershell\n# Connect to Secret Server API\n$baseUrl = \"https:\u002F\u002Fpam.corp.local\u002FSecretServer\"\n$creds = @{\n    username = \"ss-admin\"\n    password = $env:SS_ADMIN_PASSWORD\n    grant_type = \"password\"\n}\n$token = (Invoke-RestMethod \"$baseUrl\u002Foauth2\u002Ftoken\" -Method POST -Body $creds).access_token\n$headers = @{ Authorization = \"Bearer $token\" }\n\n# Create folder structure for organizing secrets\n$folders = @(\n    @{ folderName = \"Windows Servers\"; parentFolderId = -1; inheritPermissions = $false },\n    @{ folderName = \"Linux Servers\"; parentFolderId = -1; inheritPermissions = $false },\n    @{ folderName = \"Network Devices\"; parentFolderId = -1; inheritPermissions = $false },\n    @{ folderName = \"Cloud Accounts\"; parentFolderId = -1; inheritPermissions = $false },\n    @{ folderName = \"Service Accounts\"; parentFolderId = -1; inheritPermissions = $false },\n    @{ folderName = \"Database Accounts\"; parentFolderId = -1; inheritPermissions = $false }\n)\n\nforeach ($folder in $folders) {\n    Invoke-RestMethod \"$baseUrl\u002Fapi\u002Fv1\u002Ffolders\" -Method POST -Headers $headers `\n        -ContentType \"application\u002Fjson\" -Body ($folder | ConvertTo-Json)\n}\n\n# Create custom secret template for database credentials\n$template = @{\n    name = \"Database Credential\"\n    fields = @(\n        @{ name = \"Server\"; isRequired = $true; fieldType = \"Text\" },\n        @{ name = \"Port\"; isRequired = $true; fieldType = \"Text\" },\n        @{ name = \"Database\"; isRequired = $true; fieldType = \"Text\" },\n        @{ name = \"Username\"; isRequired = $true; fieldType = \"Text\" },\n        @{ name = \"Password\"; isRequired = $true; fieldType = \"Password\" },\n        @{ name = \"Connection String\"; isRequired = $false; fieldType = \"Notes\" }\n    )\n}\nInvoke-RestMethod \"$baseUrl\u002Fapi\u002Fv1\u002Fsecret-templates\" -Method POST -Headers $headers `\n    -ContentType \"application\u002Fjson\" -Body ($template | ConvertTo-Json -Depth 3)\n```\n\n### Step 3: Configure Discovery and Account Onboarding\n\nSet up automated discovery of privileged accounts across the environment:\n\n```powershell\n# Configure Active Directory discovery source\n$adDiscovery = @{\n    name = \"Corporate AD Discovery\"\n    discoverySourceType = \"ActiveDirectory\"\n    active = $true\n    settings = @{\n        domainName = \"corp.local\"\n        friendlyName = \"Corporate Domain\"\n        discoveryAccountId = 12  # Service account secret ID\n        ouFilters = @(\n            \"OU=Servers,DC=corp,DC=local\",\n            \"OU=Workstations,DC=corp,DC=local\"\n        )\n    }\n    scanInterval = 86400  # 24 hours\n}\nInvoke-RestMethod \"$baseUrl\u002Fapi\u002Fv1\u002Fdiscovery\" -Method POST -Headers $headers `\n    -ContentType \"application\u002Fjson\" -Body ($adDiscovery | ConvertTo-Json -Depth 3)\n\n# Configure local account discovery for Windows servers\n$localDiscovery = @{\n    name = \"Windows Local Account Discovery\"\n    discoverySourceType = \"Machine\"\n    active = $true\n    settings = @{\n        machineType = \"Windows\"\n        accountScanTemplate = \"Windows Local Account\"\n        dependencyScanTemplate = \"Windows Service\"\n    }\n}\nInvoke-RestMethod \"$baseUrl\u002Fapi\u002Fv1\u002Fdiscovery\" -Method POST -Headers $headers `\n    -ContentType \"application\u002Fjson\" -Body ($localDiscovery | ConvertTo-Json -Depth 3)\n\n# Import discovered accounts as secrets\n# After discovery runs, review and import found accounts\n$discoveredAccounts = Invoke-RestMethod \"$baseUrl\u002Fapi\u002Fv1\u002Fdiscovery\u002Fstatus\" -Headers $headers\nWrite-Host \"Discovered $($discoveredAccounts.totalAccounts) accounts\"\nWrite-Host \"  - Domain Admins: $($discoveredAccounts.domainAdmins)\"\nWrite-Host \"  - Local Admins: $($discoveredAccounts.localAdmins)\"\nWrite-Host \"  - Service Accounts: $($discoveredAccounts.serviceAccounts)\"\n```\n\n### Step 4: Implement Password Rotation Policies\n\nConfigure automated password rotation with complexity requirements:\n\n```powershell\n# Create password rotation policy\n$rotationPolicy = @{\n    name = \"High-Security 30-Day Rotation\"\n    rotationIntervalDays = 30\n    passwordRequirements = @{\n        minimumLength = 24\n        maximumLength = 32\n        requireUpperCase = $true\n        requireLowerCase = $true\n        requireNumbers = $true\n        requireSymbols = $true\n        allowedSymbols = \"!@#$%^&*()-_=+[]{}|;:,.\u003C>?\"\n    }\n    rotationType = \"AutoChange\"\n    autoChangeSchedule = @{\n        changeType = \"RecurringSchedule\"\n        recurrenceType = \"Monthly\"\n        dayOfMonth = 1\n        startTime = \"02:00\"\n    }\n}\nInvoke-RestMethod \"$baseUrl\u002Fapi\u002Fv1\u002Fremote-password-changing\u002Fconfiguration\" -Method POST `\n    -Headers $headers -ContentType \"application\u002Fjson\" -Body ($rotationPolicy | ConvertTo-Json -Depth 4)\n\n# Configure Remote Password Changing (RPC) for Windows accounts\n$rpcConfig = @{\n    secretId = 100  # Target secret\n    autoChangeEnabled = $true\n    autoChangeNextPassword = $true\n    privilegedAccountSecretId = 50  # Account used to perform the change\n    changePasswordUsing = \"PrivilegedAccount\"\n}\nInvoke-RestMethod \"$baseUrl\u002Fapi\u002Fv1\u002Fsecrets\u002F100\u002Fremote-password-changing\" -Method PUT `\n    -Headers $headers -ContentType \"application\u002Fjson\" -Body ($rpcConfig | ConvertTo-Json)\n\n# Configure heartbeat monitoring to verify credential validity\n$heartbeat = @{\n    enabled = $true\n    intervalMinutes = 60\n    onFailure = \"SendAlert\"\n    alertEmailGroupId = 5\n}\nInvoke-RestMethod \"$baseUrl\u002Fapi\u002Fv1\u002Fsecrets\u002F100\u002Fheartbeat\" -Method PUT `\n    -Headers $headers -ContentType \"application\u002Fjson\" -Body ($heartbeat | ConvertTo-Json)\n```\n\n### Step 5: Configure Session Recording and Monitoring\n\nEnable session recording for privileged access sessions:\n\n```powershell\n# Enable session recording policy\n$sessionPolicy = @{\n    name = \"Full Recording Policy\"\n    recordSessions = $true\n    recordKeystrokes = $true\n    recordApplications = $true\n    maxSessionDurationMinutes = 480\n    requireComment = $true\n    requireTicketNumber = $true\n    ticketSystemId = 1  # ServiceNow integration\n    settings = @{\n        videoCodec = \"H264\"\n        videoQuality = \"High\"\n        captureInterval = 1000  # milliseconds\n        storageLocation = \"\\\\\\\\fileserver\\\\SSRecordings\"\n        retentionDays = 365\n    }\n}\nInvoke-RestMethod \"$baseUrl\u002Fapi\u002Fv1\u002Fsecret-policy\" -Method POST -Headers $headers `\n    -ContentType \"application\u002Fjson\" -Body ($sessionPolicy | ConvertTo-Json -Depth 3)\n\n# Configure session launcher for RDP sessions\n$rdpLauncher = @{\n    launcherType = \"RDP\"\n    enableRecording = $true\n    enableDualControl = $true\n    approverGroupId = 10  # Security team group\n    connectAsSecretId = 100\n    settings = @{\n        useSSL = $true\n        restrictedEndpoints = @(\"192.168.1.0\u002F24\")\n        inactivityTimeout = 30  # minutes\n    }\n}\nInvoke-RestMethod \"$baseUrl\u002Fapi\u002Fv1\u002Flaunchers\" -Method POST -Headers $headers `\n    -ContentType \"application\u002Fjson\" -Body ($rdpLauncher | ConvertTo-Json -Depth 3)\n\n# Configure dual control \u002F approval workflow\n$approvalWorkflow = @{\n    name = \"Tier-0 Account Approval\"\n    requireApproval = $true\n    approvers = @(\n        @{ groupId = 10; requiredApprovals = 1 }\n    )\n    accessRequestExpirationMinutes = 60\n    notifyOnApproval = $true\n    notifyOnDenial = $true\n}\n```\n\n### Step 6: Integrate with SIEM and Compliance Reporting\n\nConnect Secret Server events to security monitoring:\n\n```powershell\n# Configure Syslog forwarding to SIEM\n$syslogConfig = @{\n    enabled = $true\n    syslogServer = \"siem.corp.local\"\n    port = 514\n    protocol = \"TLS\"\n    facility = \"Auth\"\n    severity = \"Informational\"\n    events = @(\n        \"SecretView\", \"SecretEdit\", \"SecretCreate\", \"SecretDelete\",\n        \"PasswordChange\", \"PasswordChangeFailure\",\n        \"SessionStart\", \"SessionEnd\",\n        \"LoginFailure\", \"LoginSuccess\",\n        \"PermissionChange\", \"ApprovalRequest\"\n    )\n}\nInvoke-RestMethod \"$baseUrl\u002Fapi\u002Fv1\u002Fconfiguration\u002Fsyslog\" -Method PUT -Headers $headers `\n    -ContentType \"application\u002Fjson\" -Body ($syslogConfig | ConvertTo-Json -Depth 2)\n\n# Generate compliance report\n$report = @{\n    reportType = \"PasswordCompliance\"\n    dateRange = @{\n        startDate = (Get-Date).AddDays(-30).ToString(\"yyyy-MM-dd\")\n        endDate = (Get-Date).ToString(\"yyyy-MM-dd\")\n    }\n    filters = @{\n        folderIds = @(1, 2, 3, 4, 5, 6)\n        includeSubFolders = $true\n    }\n}\n$reportResult = Invoke-RestMethod \"$baseUrl\u002Fapi\u002Fv1\u002Freports\" -Method POST -Headers $headers `\n    -ContentType \"application\u002Fjson\" -Body ($report | ConvertTo-Json -Depth 3)\n\n# Display compliance summary\nWrite-Host \"PAM Compliance Report\"\nWrite-Host \"=====================\"\nWrite-Host \"Total Secrets:         $($reportResult.totalSecrets)\"\nWrite-Host \"Rotation Compliant:    $($reportResult.rotationCompliant) ($($reportResult.rotationCompliancePct)%)\"\nWrite-Host \"Heartbeat Healthy:     $($reportResult.heartbeatHealthy) ($($reportResult.heartbeatHealthyPct)%)\"\nWrite-Host \"Password Age > 90d:    $($reportResult.passwordAgeViolations)\"\nWrite-Host \"Orphaned Accounts:     $($reportResult.orphanedAccounts)\"\n```\n\n## Key Concepts\n\n| Term | Definition |\n|------|------------|\n| **Privileged Access Management (PAM)** | Security framework for controlling, monitoring, and auditing elevated access to critical systems and data through credential vaulting and session management |\n| **Secret** | A stored credential or sensitive data item in the vault, including passwords, SSH keys, API tokens, and certificates |\n| **Remote Password Changing (RPC)** | Automated mechanism that connects to target systems to rotate passwords according to defined policies without manual intervention |\n| **Heartbeat** | Periodic check that validates stored credentials against target systems to ensure vault contents remain synchronized and functional |\n| **Dual Control** | Security mechanism requiring approval from a second authorized user before granting access to highly sensitive secrets |\n| **Discovery** | Automated scanning of infrastructure to identify privileged accounts, service accounts, and dependencies across Active Directory, servers, and network devices |\n| **Session Recording** | Capture of complete privileged session activity including video, keystrokes, and application usage for audit and forensic review |\n\n## Tools & Systems\n\n- **Delinea Secret Server**: Enterprise PAM solution providing credential vaulting, password rotation, session recording, and privileged access workflows\n- **Delinea Distributed Engine**: Agent deployed in network segments to enable password changing and discovery across firewalled environments\n- **Secret Server REST API**: RESTful API for programmatic secret management, automation, and integration with DevOps pipelines\n- **Secret Server SDK**: .NET and PowerShell SDKs for application-level integration with Secret Server vault\n\n## Common Scenarios\n\n### Scenario: Migrating Shared Admin Credentials to Vault\n\n**Context**: An organization stores 500+ shared administrator credentials in Excel spreadsheets and password-protected documents. Auditors flagged this as a critical finding requiring remediation within 90 days.\n\n**Approach**:\n1. Deploy Secret Server with SQL Server backend and configure HTTPS access\n2. Design folder hierarchy mirroring the organizational structure (by department, system type, environment)\n3. Create secret templates matching the credential types in use (Windows, Linux, database, network device)\n4. Import existing credentials via CSV import or PowerShell bulk creation\n5. Configure discovery to find undocumented privileged accounts across AD and local systems\n6. Enable Remote Password Changing starting with non-production accounts to validate rotation\n7. Roll out session launchers to replace direct RDP\u002FSSH connections\n8. Gradually enable dual control for Tier-0 accounts (Domain Admins, root accounts)\n9. Configure SIEM integration and compliance reporting for audit evidence\n\n**Pitfalls**:\n- Not identifying all service account dependencies before enabling password rotation (causes service outages)\n- Enabling RPC for production accounts without testing in non-production first\n- Setting rotation intervals too short for service accounts that require coordinated restarts\n- Not configuring Distributed Engines for network segments separated by firewalls\n\n## Output Format\n\n```\nDELINEA SECRET SERVER PAM DEPLOYMENT REPORT\n=============================================\nEnvironment:       Hybrid (On-Premises + Azure)\nVersion:           Secret Server 11.6\nDeployment Mode:   On-Premises (High Availability)\n\nVAULT STATISTICS\nTotal Secrets:           1,247\n  Windows Credentials:   523\n  Linux\u002FSSH Keys:        312\n  Database Accounts:     198\n  Network Devices:       87\n  Cloud API Keys:        127\n\nPASSWORD ROTATION STATUS\nAuto-Change Enabled:     1,089 \u002F 1,247 (87.3%)\nRotation Compliant:      1,056 \u002F 1,089 (97.0%)\nHeartbeat Healthy:       1,198 \u002F 1,247 (96.1%)\nFailed Rotations (30d):  12\n\nSESSION MANAGEMENT\nActive Sessions:         23\nRecorded Sessions (30d): 4,567\nAverage Session Length:  22 minutes\nApproval Requests (30d): 189 (174 approved, 15 denied)\n\nDISCOVERY RESULTS\nScanned Systems:         2,340\nDiscovered Accounts:     3,891\nOnboarded to Vault:      1,247 (32.1%)\nPending Review:          892\n\nCOMPLIANCE\nSOX Controls Met:        12\u002F12\nPCI-DSS Requirements:    8\u002F8\nPassword Age Violations: 3 (remediation in progress)\n```\n","# Implementing Delinea Secret Server for PAM\n\n## When to Use\n\n- Organization needs centralized privileged credential management across hybrid infrastructure\n- Compliance requirements mandate privileged access controls (SOX, PCI-DSS, HIPAA, NIST 800-53)\n- Service accounts and shared credentials are stored in spreadsheets or plaintext files\n- Need to implement automated password rotation for privileged accounts\n- Require session recording and keystroke logging for privileged user activity\n- Migrating from manual PAM processes to an enterprise vault solution\n\n**Do not use** for standard end-user password management; Delinea Secret Server is designed for privileged and shared account credential management requiring enterprise-grade controls.\n\n## Prerequisites\n\n- Delinea Secret Server license (On-Premises or Cloud)\n- Windows Server 2019\u002F2022 for on-premises deployment with IIS and SQL Server\n- Active Directory service account with read permissions for discovery\n- SSL\u002FTLS certificate for web interface encryption\n- Network connectivity to target systems for password rotation\n- PowerShell 5.1+ for automation scripts\n\n## Workflow\n\n### Step 1: Deploy Secret Server Infrastructure\n\nInstall and configure the Secret Server application server:\n\n```powershell\n# Pre-installation checks for on-premises deployment\n# Verify IIS is installed with required features\nImport-Module ServerManager\nInstall-WindowsFeature Web-Server, Web-Asp-Net45, Web-Windows-Auth, Web-Mgmt-Console\n\n# Verify SQL Server connectivity\n$sqlConn = New-Object System.Data.SqlClient.SqlConnection\n$sqlConn.ConnectionString = \"Server=sql01.corp.local;Database=master;Integrated Security=True\"\n$sqlConn.Open()\nWrite-Host \"SQL Server connection successful: $($sqlConn.ServerVersion)\"\n$sqlConn.Close()\n\n# Create Secret Server database\nInvoke-Sqlcmd -ServerInstance \"sql01.corp.local\" -Query @\"\nCREATE DATABASE SecretServer\nGO\nALTER DATABASE SecretServer SET RECOVERY FULL\nGO\n\"@\n\n# Download and run Secret Server installer\n# Navigate to https:\u002F\u002Fthy.center\u002Fss\u002Flink\u002FSSDownload for latest version\n# Run setup.exe and follow the installation wizard\n\n# Post-installation: Configure application pool\nImport-Module WebAdministration\nSet-ItemProperty \"IIS:\\AppPools\\SecretServer\" -Name processModel.identityType -Value SpecificUser\nSet-ItemProperty \"IIS:\\AppPools\\SecretServer\" -Name processModel.userName -Value \"CORP\\svc-secretserver\"\n```\n\n### Step 2: Configure Secret Templates and Folder Structure\n\nDefine secret templates and organize the vault hierarchy:\n\n```powershell\n# Connect to Secret Server API\n$baseUrl = \"https:\u002F\u002Fpam.corp.local\u002FSecretServer\"\n$creds = @{\n    username = \"ss-admin\"\n    password = $env:SS_ADMIN_PASSWORD\n    grant_type = \"password\"\n}\n$token = (Invoke-RestMethod \"$baseUrl\u002Foauth2\u002Ftoken\" -Method POST -Body $creds).access_token\n$headers = @{ Authorization = \"Bearer $token\" }\n\n# Create folder structure for organizing secrets\n$folders = @(\n    @{ folderName = \"Windows Servers\"; parentFolderId = -1; inheritPermissions = $false },\n    @{ folderName = \"Linux Servers\"; parentFolderId = -1; inheritPermissions = $false },\n    @{ folderName = \"Network Devices\"; parentFolderId = -1; inheritPermissions = $false },\n    @{ folderName = \"Cloud Accounts\"; parentFolderId = -1; inheritPermissions = $false },\n    @{ folderName = \"Service Accounts\"; parentFolderId = -1; inheritPermissions = $false },\n    @{ folderName = \"Database Accounts\"; parentFolderId = -1; inheritPermissions = $false }\n)\n\nforeach ($folder in $folders) {\n    Invoke-RestMethod \"$baseUrl\u002Fapi\u002Fv1\u002Ffolders\" -Method POST -Headers $headers `\n        -ContentType \"application\u002Fjson\" -Body ($folder | ConvertTo-Json)\n}\n\n# Create custom secret template for database credentials\n$template = @{\n    name = \"Database Credential\"\n    fields = @(\n        @{ name = \"Server\"; isRequired = $true; fieldType = \"Text\" },\n        @{ name = \"Port\"; isRequired = $true; fieldType = \"Text\" },\n        @{ name = \"Database\"; isRequired = $true; fieldType = \"Text\" },\n        @{ name = \"Username\"; isRequired = $true; fieldType = \"Text\" },\n        @{ name = \"Password\"; isRequired = $true; fieldType = \"Password\" },\n        @{ name = \"Connection String\"; isRequired = $false; fieldType = \"Notes\" }\n    )\n}\nInvoke-RestMethod \"$baseUrl\u002Fapi\u002Fv1\u002Fsecret-templates\" -Method POST -Headers $headers `\n    -ContentType \"application\u002Fjson\" -Body ($template | ConvertTo-Json -Depth 3)\n```\n\n### Step 3: Configure Discovery and Account Onboarding\n\nSet up automated discovery of privileged accounts across the environment:\n\n```powershell\n# Configure Active Directory discovery source\n$adDiscovery = @{\n    name = \"Corporate AD Discovery\"\n    discoverySourceType = \"ActiveDirectory\"\n    active = $true\n    settings = @{\n        domainName = \"corp.local\"\n        friendlyName = \"Corporate Domain\"\n        discoveryAccountId = 12  # Service account secret ID\n        ouFilters = @(\n            \"OU=Servers,DC=corp,DC=local\",\n            \"OU=Workstations,DC=corp,DC=local\"\n        )\n    }\n    scanInterval = 86400  # 24 hours\n}\nInvoke-RestMethod \"$baseUrl\u002Fapi\u002Fv1\u002Fdiscovery\" -Method POST -Headers $headers `\n    -ContentType \"application\u002Fjson\" -Body ($adDiscovery | ConvertTo-Json -Depth 3)\n\n# Configure local account discovery for Windows servers\n$localDiscovery = @{\n    name = \"Windows Local Account Discovery\"\n    discoverySourceType = \"Machine\"\n    active = $true\n    settings = @{\n        machineType = \"Windows\"\n        accountScanTemplate = \"Windows Local Account\"\n        dependencyScanTemplate = \"Windows Service\"\n    }\n}\nInvoke-RestMethod \"$baseUrl\u002Fapi\u002Fv1\u002Fdiscovery\" -Method POST -Headers $headers `\n    -ContentType \"application\u002Fjson\" -Body ($localDiscovery | ConvertTo-Json -Depth 3)\n\n# Import discovered accounts as secrets\n# After discovery runs, review and import found accounts\n$discoveredAccounts = Invoke-RestMethod \"$baseUrl\u002Fapi\u002Fv1\u002Fdiscovery\u002Fstatus\" -Headers $headers\nWrite-Host \"Discovered $($discoveredAccounts.totalAccounts) accounts\"\nWrite-Host \"  - Domain Admins: $($discoveredAccounts.domainAdmins)\"\nWrite-Host \"  - Local Admins: $($discoveredAccounts.localAdmins)\"\nWrite-Host \"  - Service Accounts: $($discoveredAccounts.serviceAccounts)\"\n```\n\n### Step 4: Implement Password Rotation Policies\n\nConfigure automated password rotation with complexity requirements:\n\n```powershell\n# Create password rotation policy\n$rotationPolicy = @{\n    name = \"High-Security 30-Day Rotation\"\n    rotationIntervalDays = 30\n    passwordRequirements = @{\n        minimumLength = 24\n        maximumLength = 32\n        requireUpperCase = $true\n        requireLowerCase = $true\n        requireNumbers = $true\n        requireSymbols = $true\n        allowedSymbols = \"!@#$%^&*()-_=+[]{}|;:,.\u003C>?\"\n    }\n    rotationType = \"AutoChange\"\n    autoChangeSchedule = @{\n        changeType = \"RecurringSchedule\"\n        recurrenceType = \"Monthly\"\n        dayOfMonth = 1\n        startTime = \"02:00\"\n    }\n}\nInvoke-RestMethod \"$baseUrl\u002Fapi\u002Fv1\u002Fremote-password-changing\u002Fconfiguration\" -Method POST `\n    -Headers $headers -ContentType \"application\u002Fjson\" -Body ($rotationPolicy | ConvertTo-Json -Depth 4)\n\n# Configure Remote Password Changing (RPC) for Windows accounts\n$rpcConfig = @{\n    secretId = 100  # Target secret\n    autoChangeEnabled = $true\n    autoChangeNextPassword = $true\n    privilegedAccountSecretId = 50  # Account used to perform the change\n    changePasswordUsing = \"PrivilegedAccount\"\n}\nInvoke-RestMethod \"$baseUrl\u002Fapi\u002Fv1\u002Fsecrets\u002F100\u002Fremote-password-changing\" -Method PUT `\n    -Headers $headers -ContentType \"application\u002Fjson\" -Body ($rpcConfig | ConvertTo-Json)\n\n# Configure heartbeat monitoring to verify credential validity\n$heartbeat = @{\n    enabled = $true\n    intervalMinutes = 60\n    onFailure = \"SendAlert\"\n    alertEmailGroupId = 5\n}\nInvoke-RestMethod \"$baseUrl\u002Fapi\u002Fv1\u002Fsecrets\u002F100\u002Fheartbeat\" -Method PUT `\n    -Headers $headers -ContentType \"application\u002Fjson\" -Body ($heartbeat | ConvertTo-Json)\n```\n\n### Step 5: Configure Session Recording and Monitoring\n\nEnable session recording for privileged access sessions:\n\n```powershell\n# Enable session recording policy\n$sessionPolicy = @{\n    name = \"Full Recording Policy\"\n    recordSessions = $true\n    recordKeystrokes = $true\n    recordApplications = $true\n    maxSessionDurationMinutes = 480\n    requireComment = $true\n    requireTicketNumber = $true\n    ticketSystemId = 1  # ServiceNow integration\n    settings = @{\n        videoCodec = \"H264\"\n        videoQuality = \"High\"\n        captureInterval = 1000  # milliseconds\n        storageLocation = \"\\\\\\\\fileserver\\\\SSRecordings\"\n        retentionDays = 365\n    }\n}\nInvoke-RestMethod \"$baseUrl\u002Fapi\u002Fv1\u002Fsecret-policy\" -Method POST -Headers $headers `\n    -ContentType \"application\u002Fjson\" -Body ($sessionPolicy | ConvertTo-Json -Depth 3)\n\n# Configure session launcher for RDP sessions\n$rdpLauncher = @{\n    launcherType = \"RDP\"\n    enableRecording = $true\n    enableDualControl = $true\n    approverGroupId = 10  # Security team group\n    connectAsSecretId = 100\n    settings = @{\n        useSSL = $true\n        restrictedEndpoints = @(\"192.168.1.0\u002F24\")\n        inactivityTimeout = 30  # minutes\n    }\n}\nInvoke-RestMethod \"$baseUrl\u002Fapi\u002Fv1\u002Flaunchers\" -Method POST -Headers $headers `\n    -ContentType \"application\u002Fjson\" -Body ($rdpLauncher | ConvertTo-Json -Depth 3)\n\n# Configure dual control \u002F approval workflow\n$approvalWorkflow = @{\n    name = \"Tier-0 Account Approval\"\n    requireApproval = $true\n    approvers = @(\n        @{ groupId = 10; requiredApprovals = 1 }\n    )\n    accessRequestExpirationMinutes = 60\n    notifyOnApproval = $true\n    notifyOnDenial = $true\n}\n```\n\n### Step 6: Integrate with SIEM and Compliance Reporting\n\nConnect Secret Server events to security monitoring:\n\n```powershell\n# Configure Syslog forwarding to SIEM\n$syslogConfig = @{\n    enabled = $true\n    syslogServer = \"siem.corp.local\"\n    port = 514\n    protocol = \"TLS\"\n    facility = \"Auth\"\n    severity = \"Informational\"\n    events = @(\n        \"SecretView\", \"SecretEdit\", \"SecretCreate\", \"SecretDelete\",\n        \"PasswordChange\", \"PasswordChangeFailure\",\n        \"SessionStart\", \"SessionEnd\",\n        \"LoginFailure\", \"LoginSuccess\",\n        \"PermissionChange\", \"ApprovalRequest\"\n    )\n}\nInvoke-RestMethod \"$baseUrl\u002Fapi\u002Fv1\u002Fconfiguration\u002Fsyslog\" -Method PUT -Headers $headers `\n    -ContentType \"application\u002Fjson\" -Body ($syslogConfig | ConvertTo-Json -Depth 2)\n\n# Generate compliance report\n$report = @{\n    reportType = \"PasswordCompliance\"\n    dateRange = @{\n        startDate = (Get-Date).AddDays(-30).ToString(\"yyyy-MM-dd\")\n        endDate = (Get-Date).ToString(\"yyyy-MM-dd\")\n    }\n    filters = @{\n        folderIds = @(1, 2, 3, 4, 5, 6)\n        includeSubFolders = $true\n    }\n}\n$reportResult = Invoke-RestMethod \"$baseUrl\u002Fapi\u002Fv1\u002Freports\" -Method POST -Headers $headers `\n    -ContentType \"application\u002Fjson\" -Body ($report | ConvertTo-Json -Depth 3)\n\n# Display compliance summary\nWrite-Host \"PAM Compliance Report\"\nWrite-Host \"=====================\"\nWrite-Host \"Total Secrets:         $($reportResult.totalSecrets)\"\nWrite-Host \"Rotation Compliant:    $($reportResult.rotationCompliant) ($($reportResult.rotationCompliancePct)%)\"\nWrite-Host \"Heartbeat Healthy:     $($reportResult.heartbeatHealthy) ($($reportResult.heartbeatHealthyPct)%)\"\nWrite-Host \"Password Age > 90d:    $($reportResult.passwordAgeViolations)\"\nWrite-Host \"Orphaned Accounts:     $($reportResult.orphanedAccounts)\"\n```\n\n## Key Concepts\n\n| Term | Definition |\n|------|------------|\n| **Privileged Access Management (PAM)** | Security framework for controlling, monitoring, and auditing elevated access to critical systems and data through credential vaulting and session management |\n| **Secret** | A stored credential or sensitive data item in the vault, including passwords, SSH keys, API tokens, and certificates |\n| **Remote Password Changing (RPC)** | Automated mechanism that connects to target systems to rotate passwords according to defined policies without manual intervention |\n| **Heartbeat** | Periodic check that validates stored credentials against target systems to ensure vault contents remain synchronized and functional |\n| **Dual Control** | Security mechanism requiring approval from a second authorized user before granting access to highly sensitive secrets |\n| **Discovery** | Automated scanning of infrastructure to identify privileged accounts, service accounts, and dependencies across Active Directory, servers, and network devices |\n| **Session Recording** | Capture of complete privileged session activity including video, keystrokes, and application usage for audit and forensic review |\n\n## Tools & Systems\n\n- **Delinea Secret Server**: Enterprise PAM solution providing credential vaulting, password rotation, session recording, and privileged access workflows\n- **Delinea Distributed Engine**: Agent deployed in network segments to enable password changing and discovery across firewalled environments\n- **Secret Server REST API**: RESTful API for programmatic secret management, automation, and integration with DevOps pipelines\n- **Secret Server SDK**: .NET and PowerShell SDKs for application-level integration with Secret Server vault\n\n## Common Scenarios\n\n### Scenario: Migrating Shared Admin Credentials to Vault\n\n**Context**: An organization stores 500+ shared administrator credentials in Excel spreadsheets and password-protected documents. Auditors flagged this as a critical finding requiring remediation within 90 days.\n\n**Approach**:\n1. Deploy Secret Server with SQL Server backend and configure HTTPS access\n2. Design folder hierarchy mirroring the organizational structure (by department, system type, environment)\n3. Create secret templates matching the credential types in use (Windows, Linux, database, network device)\n4. Import existing credentials via CSV import or PowerShell bulk creation\n5. Configure discovery to find undocumented privileged accounts across AD and local systems\n6. Enable Remote Password Changing starting with non-production accounts to validate rotation\n7. Roll out session launchers to replace direct RDP\u002FSSH connections\n8. Gradually enable dual control for Tier-0 accounts (Domain Admins, root accounts)\n9. Configure SIEM integration and compliance reporting for audit evidence\n\n**Pitfalls**:\n- Not identifying all service account dependencies before enabling password rotation (causes service outages)\n- Enabling RPC for production accounts without testing in non-production first\n- Setting rotation intervals too short for service accounts that require coordinated restarts\n- Not configuring Distributed Engines for network segments separated by firewalls\n\n## Output Format\n\n```\nDELINEA SECRET SERVER PAM DEPLOYMENT REPORT\n=============================================\nEnvironment:       Hybrid (On-Premises + Azure)\nVersion:           Secret Server 11.6\nDeployment Mode:   On-Premises (High Availability)\n\nVAULT STATISTICS\nTotal Secrets:           1,247\n  Windows Credentials:   523\n  Linux\u002FSSH Keys:        312\n  Database Accounts:     198\n  Network Devices:       87\n  Cloud API Keys:        127\n\nPASSWORD ROTATION STATUS\nAuto-Change Enabled:     1,089 \u002F 1,247 (87.3%)\nRotation Compliant:      1,056 \u002F 1,089 (97.0%)\nHeartbeat Healthy:       1,198 \u002F 1,247 (96.1%)\nFailed Rotations (30d):  12\n\nSESSION MANAGEMENT\nActive Sessions:         23\nRecorded Sessions (30d): 4,567\nAverage Session Length:  22 minutes\nApproval Requests (30d): 189 (174 approved, 15 denied)\n\nDISCOVERY RESULTS\nScanned Systems:         2,340\nDiscovered Accounts:     3,891\nOnboarded to Vault:      1,247 (32.1%)\nPending Review:          892\n\nCOMPLIANCE\nSOX Controls Met:        12\u002F12\nPCI-DSS Requirements:    8\u002F8\nPassword Age Violations: 3 (remediation in progress)\n```\n",{"name":5,"tags":24,"author":31,"domain":32,"license":14,"version":33,"mitre_f3":34,"nist_csf":58,"subdomain":63,"description":64,"mitre_attack":65},[25,26,27,28,29,30],"PAM","Delinea","Secret-Server","privileged-access","password-vault","credential-management","mahipal","cybersecurity","1.0",{"tactics":35,"version":39,"techniques":40},[36,37,38],"reconnaissance","initial-access","positioning","1.1",[41,45,48,52,55],{"id":42,"name":43,"source":44,"tactic":36},"T1555.005","Credentials from Password Stores: Password Managers","attack",{"id":46,"name":47,"source":44,"tactic":37},"T1110","Brute Force",{"id":49,"name":50,"source":51,"tactic":37},"F1006","Account Takeover","f3",{"id":53,"name":54,"source":51,"tactic":37},"F1006.002","Account Takeover: Exposed Login Credential",{"id":56,"name":57,"source":51,"tactic":38},"F1005","Account Manipulation",[59,60,61,62],"PR.AA-01","PR.AA-02","PR.AA-05","PR.AA-06","identity-access-management","Implements Delinea Secret Server for privileged access management, covering secret vault configuration, role-based access policies, automated password rotation, session recording, and Active Directory\u002Fcloud integration. Use when centralizing privileged credential management, replacing spreadsheet-based secrets, automating password rotation, or meeting PAM compliance (SOX, PCI-DSS, HIPAA, NIST 800-53).\n",[66,46,67,68,69],"T1078","T1556","T1098","T1003","main","1eb986d0b0ecc180291597e08eb5a58288843536","skills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fimplementing-delinea-secret-server-for-pam","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv","2026-08-25 13:16:33",{"source":8,"skillName":5,"commands":77,"prompt":87,"zipAvailable":88},[78,81,84],{"tool":79,"command":80},"npx","npx skills add vikasvardhanv\u002Fjerry_skills --skill implementing-delinea-secret-server-for-pam",{"tool":82,"command":83},"bunx","bunx skills add vikasvardhanv\u002Fjerry_skills --skill implementing-delinea-secret-server-for-pam",{"tool":85,"command":86},"pnpm","pnpm dlx skills add vikasvardhanv\u002Fjerry_skills --skill implementing-delinea-secret-server-for-pam","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fimplementing-delinea-secret-server-for-pam\u002FSKILL.md",true,[90,94,100],{"path":91,"resourceType":91,"resourceTypeDesc":92,"sizeBytes":93,"sourceHtmlUrl":15},"LICENSE","许可证",11255,{"path":95,"resourceType":96,"resourceTypeDesc":97,"sizeBytes":98,"sourceHtmlUrl":99},"references\u002Fapi-reference.md","REFERENCE","参考文档",2330,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fimplementing-delinea-secret-server-for-pam\u002Freferences\u002Fapi-reference.md",{"path":101,"resourceType":102,"resourceTypeDesc":103,"sizeBytes":104,"sourceHtmlUrl":105},"scripts\u002Fagent.py","SCRIPT","脚本",7204,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fimplementing-delinea-secret-server-for-pam\u002Fscripts\u002Fagent.py",[107,115,122,129,136,143],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":111,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"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":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":111,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"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":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":111,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":128,"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":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":111,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":135,"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":137,"name":138,"nameZh":6,"description":139,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":111,"licenseFileUrl":6,"sourceHtmlUrl":140,"categories":141,"keywords":142,"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":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":111,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":149,"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",[],[]]