[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73CK7QM7GPWM1BHWDCB7P6M":3,"skill-same:01M73CK7QM7GPWM1BHWDCB7P6M":91},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":54,"repositoryHtmlUrl":55,"repositoryHomepageUrl":56,"ownerHtmlUrl":57,"ownerBlogUrl":58,"ownerDescription":59,"updatedAt":60,"install":61,"resources":74},"01M73CK7QM7GPWM1BHWDCB7P6M","implementing-delinea-secret-server-for-pam",null,"Implements Delinea Secret Server for privileged access management (PAM) including secret vault configuration, role-based access policies, automated password rotation, session recording, and integration with Active Directory and cloud platforms. Activates for requests involving PAM deployment, privileged credential vaulting, secret server administration, or password rotation automation.","Horonomos-laps\u002FYana-AI","Horonomos-laps","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F355299122?v=4","01M76B3QPXE88ET2SQPDPVATZT"," Horonomos-laps","01M72ZQRJPCYPSSWT4D00VJR2A",13,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fimplementing-delinea-secret-server-for-pam\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fimplementing-delinea-secret-server-for-pam\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: implementing-delinea-secret-server-for-pam\ndescription: 'Implements Delinea Secret Server for privileged access management (PAM)\n  including secret vault configuration, role-based access policies, automated password\n  rotation, session recording, and integration with Active Directory and cloud platforms.\n  Activates for requests involving PAM deployment, privileged credential vaulting,\n  secret server administration, or password rotation automation.\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\nsource: https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\nsource_commit: 04450304b12645cb2b974ab96d28c0664758a88d\nnote: \"Vendored verbatim from an external Apache-2.0 security-skill library, pinned by commit. Exceeds the internal 300-line skill guideline (agent-code-constraints.md) -- kept as-is because this is vendored reference material (forensics\u002Fthreat-intel procedure), not Yana AI-authored content, and trimming would damage technical accuracy.\"\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,"note":25,"tags":26,"author":33,"domain":34,"source":35,"license":15,"version":36,"nist_csf":37,"subdomain":42,"description":43,"mitre_attack":44,"source_commit":50},"Vendored verbatim from an external Apache-2.0 security-skill library, pinned by commit. Exceeds the internal 300-line skill guideline (agent-code-constraints.md) -- kept as-is because this is vendored reference material (forensics\u002Fthreat-intel procedure), not Yana AI-authored content, and trimming would damage technical accuracy.",[27,28,29,30,31,32],"PAM","Delinea","Secret-Server","privileged-access","password-vault","credential-management","mahipal","cybersecurity","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills","1.0",[38,39,40,41],"PR.AA-01","PR.AA-02","PR.AA-05","PR.AA-06","identity-access-management","Implements Delinea Secret Server for privileged access management (PAM) including secret vault configuration, role-based access policies, automated password rotation, session recording, and integration with Active Directory and cloud platforms. Activates for requests involving PAM deployment, privileged credential vaulting, secret server administration, or password rotation automation.\n",[45,46,47,48,49],"T1078","T1110","T1556","T1098","T1003","04450304b12645cb2b974ab96d28c0664758a88d","main","481dcd7dd2e288b9d627a2bd017db70e64e6c6fa","core\u002Fskills\u002Fimplementing-delinea-secret-server-for-pam",2,"https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI","https:\u002F\u002Fyana.vutam.link\u002F","https:\u002F\u002Fgithub.com\u002FHoronomos-laps","https:\u002F\u002Fyana.vutam.link","An open-source governed runtime & execution environment for multi-agent AI systems.","2026-11-14 13:24:09",{"source":8,"skillName":5,"commands":62,"prompt":72,"zipAvailable":73},[63,66,69],{"tool":64,"command":65},"npx","npx skills add Horonomos-laps\u002FYana-AI --skill implementing-delinea-secret-server-for-pam",{"tool":67,"command":68},"bunx","bunx skills add Horonomos-laps\u002FYana-AI --skill implementing-delinea-secret-server-for-pam",{"tool":70,"command":71},"pnpm","pnpm dlx skills add Horonomos-laps\u002FYana-AI --skill implementing-delinea-secret-server-for-pam","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fimplementing-delinea-secret-server-for-pam\u002FSKILL.md",true,[75,79,85],{"path":76,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":78,"sourceHtmlUrl":16},"LICENSE","许可证",11255,{"path":80,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Fapi-reference.md","REFERENCE","参考文档",2330,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fimplementing-delinea-secret-server-for-pam\u002Freferences\u002Fapi-reference.md",{"path":86,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":89,"sourceHtmlUrl":90},"scripts\u002Fagent.py","SCRIPT","脚本",7204,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fimplementing-delinea-secret-server-for-pam\u002Fscripts\u002Fagent.py",[92,100,107,115,123,131],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":96,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":20},"01M735GKET5YVYKAY62W2P5YXB","openai--sentry--sentry","Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.","MIT","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fopenai--sentry--sentry\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":20},"01M73DCAP83T17HY7SMGK7MGFE","ito-basket-compare","Compare Itô prediction-market baskets against a user's knowledge base, portfolio notes, financial context, watchlist, or research thesis. Use for read-only basket comparison and gap analysis without investment advice or live trading.","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fito-basket-compare\u002FSKILL.md",[],[],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":111,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":20},"01M734CYEMZFDR3KH6SW0JP8TD","implementing-network-traffic-baselining","Build network traffic baselines from NetFlow\u002FIPFIX data using Python pandas for statistical analysis, z-score anomaly detection, and hourly\u002Fdaily traffic pattern profiling","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-network-traffic-baselining\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-network-traffic-baselining\u002FSKILL.md",[],[],{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":119,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":20},"01M73ASZ6NJRJM44Z2P84NGQ3Q","detecting-evasion-techniques-in-endpoint-logs","Detects defense evasion techniques used by adversaries in endpoint logs including log tampering, timestomping, process injection, and security tool disabling. Use when investigating suspicious endpoint behavior, building detection rules for evasion tactics, or conducting threat hunting for stealthy adversary activity. Activates for requests involving evasion detection, defense evasion analysis, log tampering detection, or MITRE ATT&CK TA0005.","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdetecting-evasion-techniques-in-endpoint-logs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdetecting-evasion-techniques-in-endpoint-logs\u002FSKILL.md",[],[],{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":127,"sourceHtmlUrl":128,"categories":129,"keywords":130,"publishedAt":20},"01M734AFNXD06Z78QRK0VKGT7Q","implementing-microsegmentation-with-guardicore","Implementing microsegmentation using Akamai Guardicore Segmentation to map application dependencies, create granular network policies, visualize east-west traffic flows, and enforce least-privilege communication between workloads across data centers and cloud.","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-microsegmentation-with-guardicore\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-microsegmentation-with-guardicore\u002FSKILL.md",[],[],{"skillNo":132,"name":133,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":136,"publishedAt":20},"01M736TK27QMCXK0DVCH25SJN5","ramdisk-tmpfs-patterns","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Framdisk-tmpfs-patterns\u002FSKILL.md",[],[]]