[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B7ZN0ZAXPXZSZ1WDR5F5RX":3,"skill-same:01M7B7ZN0ZAXPXZSZ1WDR5F5RX":125},{"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":71,"commitSha":72,"skillDirectory":73,"forksCount":13,"repositoryHtmlUrl":74,"repositoryHomepageUrl":6,"ownerHtmlUrl":75,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":76,"install":77,"resources":90},"01M7B7ZN0ZAXPXZSZ1WDR5F5RX","implementing-zero-trust-with-hashicorp-boundary",null,"Installs and configures HashiCorp Boundary as a default-deny, identity-aware proxy for infrastructure access, including controller\u002Fworker setup, Vault-backed credential brokering, session recording, and OIDC\u002FLDAP auth across an org\u002Fproject scope hierarchy. Use when replacing VPN or direct network access with just-in-time, credential-less Boundary sessions, or standing up Boundary controllers and workers.","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-zero-trust-with-hashicorp-boundary\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fimplementing-zero-trust-with-hashicorp-boundary\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: implementing-zero-trust-with-hashicorp-boundary\ndescription: Installs and configures HashiCorp Boundary as a default-deny, identity-aware proxy for infrastructure access, including controller\u002Fworker setup, Vault-backed credential brokering, session recording, and OIDC\u002FLDAP auth across an org\u002Fproject scope hierarchy. Use when replacing VPN or direct network access with just-in-time, credential-less Boundary sessions, or standing up Boundary controllers and workers.\ndomain: cybersecurity\nsubdomain: zero-trust-architecture\ntags:\n- zero-trust\n- hashicorp\n- boundary\n- privileged-access\n- vault\n- identity-aware-proxy\n- session-recording\n- just-in-time-access\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- PR.AA-01\n- PR.AA-05\n- PR.IR-01\n- GV.PO-01\nmitre_attack:\n- T1078\n- T1190\n- T1059\n- T1003\n- T1110\nmitre_f3:\n  version: '1.1'\n  tactics:\n  - initial-access\n  - positioning\n  - resource-development\n  techniques:\n  - id: T1586\n    name: Compromise Accounts\n    tactic: resource-development\n    source: attack\n  - id: T1110\n    name: Brute Force\n    tactic: initial-access\n    source: attack\n  - id: T1110.004\n    name: 'Brute Force:  Credential Stuffing'\n    tactic: initial-access\n    source: attack\n  - id: T1219\n    name: Remote Access Tools\n    tactic: positioning\n    source: attack\n  - id: F1033\n    name: Insider Access Abuse\n    tactic: initial-access\n    source: f3\n---\n\n# Implementing Zero Trust with HashiCorp Boundary\n\n## Overview\n\nHashiCorp Boundary is an identity-aware proxy that provides secure, zero trust access to infrastructure resources without traditional VPNs or direct network access. Boundary operates on a default-deny model -- users start with no access and must be explicitly granted permissions for specific resources. When integrated with HashiCorp Vault, Boundary can dynamically broker credentials, ensuring users never see or manage underlying secrets. This eliminates credential sprawl and enables just-in-time access with automatic credential revocation when sessions end. Boundary supports session recording for audit compliance, OIDC\u002FLDAP authentication, and manages access through a hierarchical scope model of organizations and projects.\n\n\n## When to Use\n\n- When deploying or configuring implementing zero trust with hashicorp boundary capabilities in your environment\n- When establishing security controls aligned to compliance requirements\n- When building or improving security architecture for this domain\n- When conducting security assessments that require this implementation\n\n## Prerequisites\n\n- HashiCorp Boundary server (self-hosted or HCP Boundary)\n- HashiCorp Vault (for credential brokering)\n- Identity provider supporting OIDC (Okta, Azure AD, Auth0)\n- PostgreSQL database for Boundary's backend\n- TLS certificates for secure communication\n- Understanding of PKI and X.509 certificate management\n\n## Architecture\n\n```\n                    Identity Provider (OIDC)\n                           |\n                    Authentication\n                           |\n                  +--------+--------+\n                  |   Boundary      |\n                  |   Controller    |\n                  |  (Control Plane)|\n                  +--------+--------+\n                           |\n              +------------+------------+\n              |                         |\n     +--------+--------+      +--------+--------+\n     | Boundary Worker |      | Boundary Worker |\n     | (Data Plane)    |      | (Data Plane)    |\n     +--------+--------+      +--------+--------+\n              |                         |\n     +--------+--------+      +--------+--------+\n     |  Target Hosts   |      |  Target Hosts   |\n     |  (SSH, RDP,     |      |  (Databases,    |\n     |   K8s, HTTP)    |      |   APIs)         |\n     +-----------------+      +-----------------+\n\n     Vault (Credential Brokering)\n     - Dynamic database credentials\n     - SSH certificate signing\n     - Credential libraries\n```\n\n## Installation and Configuration\n\n### Boundary Server Setup\n\n```bash\n# Install Boundary\ncurl -fsSL https:\u002F\u002Fapt.releases.hashicorp.com\u002Fgpg | sudo apt-key add -\nsudo apt-add-repository \"deb [arch=amd64] https:\u002F\u002Fapt.releases.hashicorp.com $(lsb_release -cs) main\"\nsudo apt-get update && sudo apt-get install boundary\n\n# Initialize the database\nboundary database init \\\n  -config=\u002Fetc\u002Fboundary\u002Fcontroller.hcl\n\n# Start the controller\nboundary server -config=\u002Fetc\u002Fboundary\u002Fcontroller.hcl\n```\n\n### Controller Configuration\n\n```hcl\n# \u002Fetc\u002Fboundary\u002Fcontroller.hcl\ncontroller {\n  name = \"boundary-controller-1\"\n  description = \"Primary Boundary Controller\"\n  database {\n    url = \"postgresql:\u002F\u002Fboundary:password@localhost:5432\u002Fboundary?sslmode=require\"\n  }\n  public_cluster_addr = \"boundary.example.com\"\n}\n\nlistener \"tcp\" {\n  address = \"0.0.0.0:9200\"\n  purpose = \"api\"\n  tls_cert_file = \"\u002Fetc\u002Fboundary\u002Ftls\u002Fcert.pem\"\n  tls_key_file  = \"\u002Fetc\u002Fboundary\u002Ftls\u002Fkey.pem\"\n}\n\nlistener \"tcp\" {\n  address = \"0.0.0.0:9201\"\n  purpose = \"cluster\"\n  tls_cert_file = \"\u002Fetc\u002Fboundary\u002Ftls\u002Fcert.pem\"\n  tls_key_file  = \"\u002Fetc\u002Fboundary\u002Ftls\u002Fkey.pem\"\n}\n\nkms \"aead\" {\n  purpose = \"root\"\n  aead_type = \"aes-gcm\"\n  key = \"sP1fnF5Xz85RrXM...\"  # Use Vault Transit in production\n  key_id = \"global_root\"\n}\n\nkms \"aead\" {\n  purpose = \"worker-auth\"\n  aead_type = \"aes-gcm\"\n  key = \"8fZBjCUfN0TzjEG...\"\n  key_id = \"global_worker-auth\"\n}\n\nkms \"aead\" {\n  purpose = \"recovery\"\n  aead_type = \"aes-gcm\"\n  key = \"8fZBjCUfN0TzjEG...\"\n  key_id = \"global_recovery\"\n}\n```\n\n### Worker Configuration\n\n```hcl\n# \u002Fetc\u002Fboundary\u002Fworker.hcl\nworker {\n  name = \"boundary-worker-1\"\n  description = \"Worker in production VPC\"\n  public_addr = \"worker1.example.com\"\n\n  controllers = [\n    \"boundary.example.com:9201\"\n  ]\n\n  tags {\n    type = [\"production\"]\n    region = [\"us-east-1\"]\n  }\n}\n\nlistener \"tcp\" {\n  address = \"0.0.0.0:9202\"\n  purpose = \"proxy\"\n}\n\nkms \"aead\" {\n  purpose = \"worker-auth\"\n  aead_type = \"aes-gcm\"\n  key = \"8fZBjCUfN0TzjEG...\"\n  key_id = \"global_worker-auth\"\n}\n```\n\n## Terraform Configuration\n\n### Scope and Auth Configuration\n\n```hcl\n# main.tf - Boundary resources via Terraform\nterraform {\n  required_providers {\n    boundary = {\n      source  = \"hashicorp\u002Fboundary\"\n      version = \"~> 1.1\"\n    }\n  }\n}\n\nprovider \"boundary\" {\n  addr             = \"https:\u002F\u002Fboundary.example.com:9200\"\n  recovery_kms_hcl = file(\"recovery_kms.hcl\")\n}\n\n# Organization scope\nresource \"boundary_scope\" \"org\" {\n  scope_id                 = \"global\"\n  name                     = \"production-org\"\n  description              = \"Production organization scope\"\n  auto_create_admin_role   = true\n  auto_create_default_role = true\n}\n\n# Project scope\nresource \"boundary_scope\" \"production\" {\n  name                     = \"production\"\n  description              = \"Production infrastructure project\"\n  scope_id                 = boundary_scope.org.id\n  auto_create_admin_role   = true\n  auto_create_default_role = true\n}\n\n# OIDC Auth Method (Okta example)\nresource \"boundary_auth_method_oidc\" \"okta\" {\n  scope_id               = boundary_scope.org.id\n  name                   = \"okta\"\n  description            = \"Okta OIDC authentication\"\n  issuer                 = \"https:\u002F\u002Fcompany.okta.com\u002Foauth2\u002Fdefault\"\n  client_id              = var.okta_client_id\n  client_secret          = var.okta_client_secret\n  signing_algorithms     = [\"RS256\"]\n  api_url_prefix         = \"https:\u002F\u002Fboundary.example.com:9200\"\n  claims_scopes          = [\"groups\"]\n  account_claim_maps     = [\"oid=sub\"]\n  is_primary_for_scope   = true\n}\n\n# Managed group for auto-assignment\nresource \"boundary_managed_group\" \"sre_team\" {\n  auth_method_id = boundary_auth_method_oidc.okta.id\n  name           = \"sre-team\"\n  description    = \"SRE team members from Okta\"\n  filter         = \"\\\"sre-team\\\" in \\\"\u002Ftoken\u002Fgroups\\\"\"\n}\n\nresource \"boundary_managed_group\" \"dev_team\" {\n  auth_method_id = boundary_auth_method_oidc.okta.id\n  name           = \"dev-team\"\n  description    = \"Development team from Okta\"\n  filter         = \"\\\"dev-team\\\" in \\\"\u002Ftoken\u002Fgroups\\\"\"\n}\n```\n\n### Host Catalogs and Targets\n\n```hcl\n# Static host catalog for known infrastructure\nresource \"boundary_host_catalog_static\" \"production_servers\" {\n  name     = \"production-servers\"\n  scope_id = boundary_scope.production.id\n}\n\nresource \"boundary_host_static\" \"web_server\" {\n  name            = \"web-server-1\"\n  host_catalog_id = boundary_host_catalog_static.production_servers.id\n  address         = \"10.0.1.10\"\n}\n\nresource \"boundary_host_static\" \"db_server\" {\n  name            = \"db-server-1\"\n  host_catalog_id = boundary_host_catalog_static.production_servers.id\n  address         = \"10.0.2.20\"\n}\n\n# Host set grouping\nresource \"boundary_host_set_static\" \"web_servers\" {\n  name            = \"web-servers\"\n  host_catalog_id = boundary_host_catalog_static.production_servers.id\n  host_ids        = [boundary_host_static.web_server.id]\n}\n\nresource \"boundary_host_set_static\" \"db_servers\" {\n  name            = \"database-servers\"\n  host_catalog_id = boundary_host_catalog_static.production_servers.id\n  host_ids        = [boundary_host_static.db_server.id]\n}\n\n# SSH target\nresource \"boundary_target\" \"ssh_production\" {\n  name         = \"ssh-production-servers\"\n  description  = \"SSH access to production servers\"\n  type         = \"ssh\"\n  scope_id     = boundary_scope.production.id\n  default_port = 22\n\n  host_source_ids = [\n    boundary_host_set_static.web_servers.id\n  ]\n\n  session_max_seconds          = 3600  # 1 hour max session\n  session_connection_limit     = 1\n  enable_session_recording     = true\n  storage_bucket_id            = boundary_storage_bucket.sessions.id\n\n  injected_application_credential_source_ids = [\n    boundary_credential_library_vault_ssh_certificate.ssh_cert.id\n  ]\n}\n\n# Database target with Vault credential brokering\nresource \"boundary_target\" \"postgres_production\" {\n  name         = \"postgres-production\"\n  description  = \"PostgreSQL production database\"\n  type         = \"tcp\"\n  scope_id     = boundary_scope.production.id\n  default_port = 5432\n\n  host_source_ids = [\n    boundary_host_set_static.db_servers.id\n  ]\n\n  session_max_seconds      = 1800  # 30 min max\n  session_connection_limit = 5\n\n  brokered_credential_source_ids = [\n    boundary_credential_library_vault.postgres_creds.id\n  ]\n}\n```\n\n### Vault Integration for Credential Brokering\n\n```hcl\n# Vault credential store\nresource \"boundary_credential_store_vault\" \"vault\" {\n  name        = \"vault-store\"\n  scope_id    = boundary_scope.production.id\n  address     = \"https:\u002F\u002Fvault.example.com:8200\"\n  token       = var.vault_token\n  namespace   = \"production\"\n}\n\n# Dynamic database credentials from Vault\nresource \"boundary_credential_library_vault\" \"postgres_creds\" {\n  name                = \"postgres-dynamic-creds\"\n  credential_store_id = boundary_credential_store_vault.vault.id\n  path                = \"database\u002Fcreds\u002Freadonly\"\n  http_method         = \"GET\"\n  credential_type     = \"username_password\"\n}\n\n# SSH certificate signing via Vault\nresource \"boundary_credential_library_vault_ssh_certificate\" \"ssh_cert\" {\n  name                = \"ssh-certificate\"\n  credential_store_id = boundary_credential_store_vault.vault.id\n  path                = \"ssh-client-signer\u002Fsign\u002Fproduction\"\n  username            = \"admin\"\n  key_type            = \"ed25519\"\n  key_bits            = 256\n  extensions = {\n    \"permit-pty\" = \"\"\n  }\n}\n\n# Session recording storage\nresource \"boundary_storage_bucket\" \"sessions\" {\n  name        = \"session-recordings\"\n  scope_id    = \"global\"\n  plugin_name = \"aws\"\n  bucket_name = \"boundary-session-recordings\"\n  attributes_json = jsonencode({\n    \"region\"                      = \"us-east-1\"\n    \"disable_credential_rotation\" = true\n  })\n  secrets_json = jsonencode({\n    \"access_key_id\"     = var.aws_access_key\n    \"secret_access_key\" = var.aws_secret_key\n  })\n}\n```\n\n### Role-Based Access Control\n\n```hcl\n# SRE team role - full production access\nresource \"boundary_role\" \"sre_production\" {\n  name          = \"sre-production-access\"\n  scope_id      = boundary_scope.production.id\n  grant_strings = [\n    \"ids=*;type=target;actions=list,read,authorize-session\",\n    \"ids=*;type=session;actions=list,read,cancel\",\n    \"ids=*;type=host;actions=list,read\",\n  ]\n  principal_ids = [\n    boundary_managed_group.sre_team.id\n  ]\n}\n\n# Dev team role - limited access\nresource \"boundary_role\" \"dev_staging\" {\n  name          = \"dev-staging-access\"\n  scope_id      = boundary_scope.production.id\n  grant_strings = [\n    \"ids=${boundary_target.ssh_production.id};type=target;actions=read,authorize-session\",\n  ]\n  principal_ids = [\n    boundary_managed_group.dev_team.id\n  ]\n}\n```\n\n## Connecting to Targets\n\n```bash\n# Authenticate via OIDC\nboundary authenticate oidc \\\n  -auth-method-id amoidc_xxxxx\n\n# List available targets\nboundary targets list -scope-id p_xxxxx\n\n# Connect to SSH target (credentials injected by Vault)\nboundary connect ssh \\\n  -target-id ttcp_xxxxx\n\n# Connect to database (credentials brokered by Vault)\nboundary connect postgres \\\n  -target-id ttcp_xxxxx \\\n  -dbname production\n\n# Use Boundary Desktop client for GUI access\n# Download from: https:\u002F\u002Fdeveloper.hashicorp.com\u002Fboundary\u002Finstall\n```\n\n## Session Recording and Auditing\n\n```bash\n# List session recordings\nboundary session-recordings list \\\n  -scope-id p_xxxxx\n\n# Download session recording for review\nboundary session-recordings download \\\n  -id sr_xxxxx \\\n  -output recording.cast\n\n# Play back with asciinema\nasciinema play recording.cast\n```\n\n## Dynamic Host Catalogs\n\n```hcl\n# AWS dynamic host catalog - auto-discovers EC2 instances\nresource \"boundary_host_catalog_plugin\" \"aws_catalog\" {\n  scope_id    = boundary_scope.production.id\n  name        = \"aws-production\"\n  plugin_name = \"aws\"\n\n  attributes_json = jsonencode({\n    \"region\"                      = \"us-east-1\"\n    \"disable_credential_rotation\" = true\n  })\n\n  secrets_json = jsonencode({\n    \"access_key_id\"     = var.aws_access_key\n    \"secret_access_key\" = var.aws_secret_key\n  })\n}\n\nresource \"boundary_host_set_plugin\" \"web_tier\" {\n  host_catalog_id = boundary_host_catalog_plugin.aws_catalog.id\n  name            = \"web-tier\"\n  attributes_json = jsonencode({\n    \"filters\" = [\n      \"tag:Environment=production\",\n      \"tag:Tier=web\"\n    ]\n  })\n}\n```\n\n## Security Best Practices\n\n1. **Use Vault KMS for key management** instead of static AEAD keys in production\n2. **Enable session recording** for all privileged access targets\n3. **Set session time limits** appropriate to the resource sensitivity\n4. **Use OIDC managed groups** for automatic role assignment from IdP\n5. **Deploy multi-hop workers** for accessing resources across network boundaries\n6. **Rotate Vault tokens** used by credential stores regularly\n7. **Enable audit logging** on both controllers and workers\n8. **Use credential injection** (SSH certificates) over brokering when possible\n9. **Implement least-privilege grants** -- avoid wildcard permissions\n10. **Review session recordings** regularly for compliance and incident response\n\n## References\n\n- [HashiCorp Boundary Documentation](https:\u002F\u002Fdeveloper.hashicorp.com\u002Fboundary\u002Fdocs)\n- [Boundary and Vault Integration](https:\u002F\u002Fdeveloper.hashicorp.com\u002Fboundary\u002Fdocs\u002Fconcepts\u002Fcredential-management)\n- [From Zero to Hero with Boundary](https:\u002F\u002Fwww.hashicorp.com\u002Fen\u002Fblog\u002Ffrom-zero-to-hero-hashicorp-boundary)\n- [Boundary Terraform Provider](https:\u002F\u002Fregistry.terraform.io\u002Fproviders\u002Fhashicorp\u002Fboundary\u002Flatest\u002Fdocs)\n- [Zero Trust with Vault, Consul, and Boundary](https:\u002F\u002Fwww.hashicorp.com\u002Fen\u002Fresources\u002Fzero-trust-security-with-hashicorp-vault-consul-and-boundary)\n","# Implementing Zero Trust with HashiCorp Boundary\n\n## Overview\n\nHashiCorp Boundary is an identity-aware proxy that provides secure, zero trust access to infrastructure resources without traditional VPNs or direct network access. Boundary operates on a default-deny model -- users start with no access and must be explicitly granted permissions for specific resources. When integrated with HashiCorp Vault, Boundary can dynamically broker credentials, ensuring users never see or manage underlying secrets. This eliminates credential sprawl and enables just-in-time access with automatic credential revocation when sessions end. Boundary supports session recording for audit compliance, OIDC\u002FLDAP authentication, and manages access through a hierarchical scope model of organizations and projects.\n\n\n## When to Use\n\n- When deploying or configuring implementing zero trust with hashicorp boundary capabilities in your environment\n- When establishing security controls aligned to compliance requirements\n- When building or improving security architecture for this domain\n- When conducting security assessments that require this implementation\n\n## Prerequisites\n\n- HashiCorp Boundary server (self-hosted or HCP Boundary)\n- HashiCorp Vault (for credential brokering)\n- Identity provider supporting OIDC (Okta, Azure AD, Auth0)\n- PostgreSQL database for Boundary's backend\n- TLS certificates for secure communication\n- Understanding of PKI and X.509 certificate management\n\n## Architecture\n\n```\n                    Identity Provider (OIDC)\n                           |\n                    Authentication\n                           |\n                  +--------+--------+\n                  |   Boundary      |\n                  |   Controller    |\n                  |  (Control Plane)|\n                  +--------+--------+\n                           |\n              +------------+------------+\n              |                         |\n     +--------+--------+      +--------+--------+\n     | Boundary Worker |      | Boundary Worker |\n     | (Data Plane)    |      | (Data Plane)    |\n     +--------+--------+      +--------+--------+\n              |                         |\n     +--------+--------+      +--------+--------+\n     |  Target Hosts   |      |  Target Hosts   |\n     |  (SSH, RDP,     |      |  (Databases,    |\n     |   K8s, HTTP)    |      |   APIs)         |\n     +-----------------+      +-----------------+\n\n     Vault (Credential Brokering)\n     - Dynamic database credentials\n     - SSH certificate signing\n     - Credential libraries\n```\n\n## Installation and Configuration\n\n### Boundary Server Setup\n\n```bash\n# Install Boundary\ncurl -fsSL https:\u002F\u002Fapt.releases.hashicorp.com\u002Fgpg | sudo apt-key add -\nsudo apt-add-repository \"deb [arch=amd64] https:\u002F\u002Fapt.releases.hashicorp.com $(lsb_release -cs) main\"\nsudo apt-get update && sudo apt-get install boundary\n\n# Initialize the database\nboundary database init \\\n  -config=\u002Fetc\u002Fboundary\u002Fcontroller.hcl\n\n# Start the controller\nboundary server -config=\u002Fetc\u002Fboundary\u002Fcontroller.hcl\n```\n\n### Controller Configuration\n\n```hcl\n# \u002Fetc\u002Fboundary\u002Fcontroller.hcl\ncontroller {\n  name = \"boundary-controller-1\"\n  description = \"Primary Boundary Controller\"\n  database {\n    url = \"postgresql:\u002F\u002Fboundary:password@localhost:5432\u002Fboundary?sslmode=require\"\n  }\n  public_cluster_addr = \"boundary.example.com\"\n}\n\nlistener \"tcp\" {\n  address = \"0.0.0.0:9200\"\n  purpose = \"api\"\n  tls_cert_file = \"\u002Fetc\u002Fboundary\u002Ftls\u002Fcert.pem\"\n  tls_key_file  = \"\u002Fetc\u002Fboundary\u002Ftls\u002Fkey.pem\"\n}\n\nlistener \"tcp\" {\n  address = \"0.0.0.0:9201\"\n  purpose = \"cluster\"\n  tls_cert_file = \"\u002Fetc\u002Fboundary\u002Ftls\u002Fcert.pem\"\n  tls_key_file  = \"\u002Fetc\u002Fboundary\u002Ftls\u002Fkey.pem\"\n}\n\nkms \"aead\" {\n  purpose = \"root\"\n  aead_type = \"aes-gcm\"\n  key = \"sP1fnF5Xz85RrXM...\"  # Use Vault Transit in production\n  key_id = \"global_root\"\n}\n\nkms \"aead\" {\n  purpose = \"worker-auth\"\n  aead_type = \"aes-gcm\"\n  key = \"8fZBjCUfN0TzjEG...\"\n  key_id = \"global_worker-auth\"\n}\n\nkms \"aead\" {\n  purpose = \"recovery\"\n  aead_type = \"aes-gcm\"\n  key = \"8fZBjCUfN0TzjEG...\"\n  key_id = \"global_recovery\"\n}\n```\n\n### Worker Configuration\n\n```hcl\n# \u002Fetc\u002Fboundary\u002Fworker.hcl\nworker {\n  name = \"boundary-worker-1\"\n  description = \"Worker in production VPC\"\n  public_addr = \"worker1.example.com\"\n\n  controllers = [\n    \"boundary.example.com:9201\"\n  ]\n\n  tags {\n    type = [\"production\"]\n    region = [\"us-east-1\"]\n  }\n}\n\nlistener \"tcp\" {\n  address = \"0.0.0.0:9202\"\n  purpose = \"proxy\"\n}\n\nkms \"aead\" {\n  purpose = \"worker-auth\"\n  aead_type = \"aes-gcm\"\n  key = \"8fZBjCUfN0TzjEG...\"\n  key_id = \"global_worker-auth\"\n}\n```\n\n## Terraform Configuration\n\n### Scope and Auth Configuration\n\n```hcl\n# main.tf - Boundary resources via Terraform\nterraform {\n  required_providers {\n    boundary = {\n      source  = \"hashicorp\u002Fboundary\"\n      version = \"~> 1.1\"\n    }\n  }\n}\n\nprovider \"boundary\" {\n  addr             = \"https:\u002F\u002Fboundary.example.com:9200\"\n  recovery_kms_hcl = file(\"recovery_kms.hcl\")\n}\n\n# Organization scope\nresource \"boundary_scope\" \"org\" {\n  scope_id                 = \"global\"\n  name                     = \"production-org\"\n  description              = \"Production organization scope\"\n  auto_create_admin_role   = true\n  auto_create_default_role = true\n}\n\n# Project scope\nresource \"boundary_scope\" \"production\" {\n  name                     = \"production\"\n  description              = \"Production infrastructure project\"\n  scope_id                 = boundary_scope.org.id\n  auto_create_admin_role   = true\n  auto_create_default_role = true\n}\n\n# OIDC Auth Method (Okta example)\nresource \"boundary_auth_method_oidc\" \"okta\" {\n  scope_id               = boundary_scope.org.id\n  name                   = \"okta\"\n  description            = \"Okta OIDC authentication\"\n  issuer                 = \"https:\u002F\u002Fcompany.okta.com\u002Foauth2\u002Fdefault\"\n  client_id              = var.okta_client_id\n  client_secret          = var.okta_client_secret\n  signing_algorithms     = [\"RS256\"]\n  api_url_prefix         = \"https:\u002F\u002Fboundary.example.com:9200\"\n  claims_scopes          = [\"groups\"]\n  account_claim_maps     = [\"oid=sub\"]\n  is_primary_for_scope   = true\n}\n\n# Managed group for auto-assignment\nresource \"boundary_managed_group\" \"sre_team\" {\n  auth_method_id = boundary_auth_method_oidc.okta.id\n  name           = \"sre-team\"\n  description    = \"SRE team members from Okta\"\n  filter         = \"\\\"sre-team\\\" in \\\"\u002Ftoken\u002Fgroups\\\"\"\n}\n\nresource \"boundary_managed_group\" \"dev_team\" {\n  auth_method_id = boundary_auth_method_oidc.okta.id\n  name           = \"dev-team\"\n  description    = \"Development team from Okta\"\n  filter         = \"\\\"dev-team\\\" in \\\"\u002Ftoken\u002Fgroups\\\"\"\n}\n```\n\n### Host Catalogs and Targets\n\n```hcl\n# Static host catalog for known infrastructure\nresource \"boundary_host_catalog_static\" \"production_servers\" {\n  name     = \"production-servers\"\n  scope_id = boundary_scope.production.id\n}\n\nresource \"boundary_host_static\" \"web_server\" {\n  name            = \"web-server-1\"\n  host_catalog_id = boundary_host_catalog_static.production_servers.id\n  address         = \"10.0.1.10\"\n}\n\nresource \"boundary_host_static\" \"db_server\" {\n  name            = \"db-server-1\"\n  host_catalog_id = boundary_host_catalog_static.production_servers.id\n  address         = \"10.0.2.20\"\n}\n\n# Host set grouping\nresource \"boundary_host_set_static\" \"web_servers\" {\n  name            = \"web-servers\"\n  host_catalog_id = boundary_host_catalog_static.production_servers.id\n  host_ids        = [boundary_host_static.web_server.id]\n}\n\nresource \"boundary_host_set_static\" \"db_servers\" {\n  name            = \"database-servers\"\n  host_catalog_id = boundary_host_catalog_static.production_servers.id\n  host_ids        = [boundary_host_static.db_server.id]\n}\n\n# SSH target\nresource \"boundary_target\" \"ssh_production\" {\n  name         = \"ssh-production-servers\"\n  description  = \"SSH access to production servers\"\n  type         = \"ssh\"\n  scope_id     = boundary_scope.production.id\n  default_port = 22\n\n  host_source_ids = [\n    boundary_host_set_static.web_servers.id\n  ]\n\n  session_max_seconds          = 3600  # 1 hour max session\n  session_connection_limit     = 1\n  enable_session_recording     = true\n  storage_bucket_id            = boundary_storage_bucket.sessions.id\n\n  injected_application_credential_source_ids = [\n    boundary_credential_library_vault_ssh_certificate.ssh_cert.id\n  ]\n}\n\n# Database target with Vault credential brokering\nresource \"boundary_target\" \"postgres_production\" {\n  name         = \"postgres-production\"\n  description  = \"PostgreSQL production database\"\n  type         = \"tcp\"\n  scope_id     = boundary_scope.production.id\n  default_port = 5432\n\n  host_source_ids = [\n    boundary_host_set_static.db_servers.id\n  ]\n\n  session_max_seconds      = 1800  # 30 min max\n  session_connection_limit = 5\n\n  brokered_credential_source_ids = [\n    boundary_credential_library_vault.postgres_creds.id\n  ]\n}\n```\n\n### Vault Integration for Credential Brokering\n\n```hcl\n# Vault credential store\nresource \"boundary_credential_store_vault\" \"vault\" {\n  name        = \"vault-store\"\n  scope_id    = boundary_scope.production.id\n  address     = \"https:\u002F\u002Fvault.example.com:8200\"\n  token       = var.vault_token\n  namespace   = \"production\"\n}\n\n# Dynamic database credentials from Vault\nresource \"boundary_credential_library_vault\" \"postgres_creds\" {\n  name                = \"postgres-dynamic-creds\"\n  credential_store_id = boundary_credential_store_vault.vault.id\n  path                = \"database\u002Fcreds\u002Freadonly\"\n  http_method         = \"GET\"\n  credential_type     = \"username_password\"\n}\n\n# SSH certificate signing via Vault\nresource \"boundary_credential_library_vault_ssh_certificate\" \"ssh_cert\" {\n  name                = \"ssh-certificate\"\n  credential_store_id = boundary_credential_store_vault.vault.id\n  path                = \"ssh-client-signer\u002Fsign\u002Fproduction\"\n  username            = \"admin\"\n  key_type            = \"ed25519\"\n  key_bits            = 256\n  extensions = {\n    \"permit-pty\" = \"\"\n  }\n}\n\n# Session recording storage\nresource \"boundary_storage_bucket\" \"sessions\" {\n  name        = \"session-recordings\"\n  scope_id    = \"global\"\n  plugin_name = \"aws\"\n  bucket_name = \"boundary-session-recordings\"\n  attributes_json = jsonencode({\n    \"region\"                      = \"us-east-1\"\n    \"disable_credential_rotation\" = true\n  })\n  secrets_json = jsonencode({\n    \"access_key_id\"     = var.aws_access_key\n    \"secret_access_key\" = var.aws_secret_key\n  })\n}\n```\n\n### Role-Based Access Control\n\n```hcl\n# SRE team role - full production access\nresource \"boundary_role\" \"sre_production\" {\n  name          = \"sre-production-access\"\n  scope_id      = boundary_scope.production.id\n  grant_strings = [\n    \"ids=*;type=target;actions=list,read,authorize-session\",\n    \"ids=*;type=session;actions=list,read,cancel\",\n    \"ids=*;type=host;actions=list,read\",\n  ]\n  principal_ids = [\n    boundary_managed_group.sre_team.id\n  ]\n}\n\n# Dev team role - limited access\nresource \"boundary_role\" \"dev_staging\" {\n  name          = \"dev-staging-access\"\n  scope_id      = boundary_scope.production.id\n  grant_strings = [\n    \"ids=${boundary_target.ssh_production.id};type=target;actions=read,authorize-session\",\n  ]\n  principal_ids = [\n    boundary_managed_group.dev_team.id\n  ]\n}\n```\n\n## Connecting to Targets\n\n```bash\n# Authenticate via OIDC\nboundary authenticate oidc \\\n  -auth-method-id amoidc_xxxxx\n\n# List available targets\nboundary targets list -scope-id p_xxxxx\n\n# Connect to SSH target (credentials injected by Vault)\nboundary connect ssh \\\n  -target-id ttcp_xxxxx\n\n# Connect to database (credentials brokered by Vault)\nboundary connect postgres \\\n  -target-id ttcp_xxxxx \\\n  -dbname production\n\n# Use Boundary Desktop client for GUI access\n# Download from: https:\u002F\u002Fdeveloper.hashicorp.com\u002Fboundary\u002Finstall\n```\n\n## Session Recording and Auditing\n\n```bash\n# List session recordings\nboundary session-recordings list \\\n  -scope-id p_xxxxx\n\n# Download session recording for review\nboundary session-recordings download \\\n  -id sr_xxxxx \\\n  -output recording.cast\n\n# Play back with asciinema\nasciinema play recording.cast\n```\n\n## Dynamic Host Catalogs\n\n```hcl\n# AWS dynamic host catalog - auto-discovers EC2 instances\nresource \"boundary_host_catalog_plugin\" \"aws_catalog\" {\n  scope_id    = boundary_scope.production.id\n  name        = \"aws-production\"\n  plugin_name = \"aws\"\n\n  attributes_json = jsonencode({\n    \"region\"                      = \"us-east-1\"\n    \"disable_credential_rotation\" = true\n  })\n\n  secrets_json = jsonencode({\n    \"access_key_id\"     = var.aws_access_key\n    \"secret_access_key\" = var.aws_secret_key\n  })\n}\n\nresource \"boundary_host_set_plugin\" \"web_tier\" {\n  host_catalog_id = boundary_host_catalog_plugin.aws_catalog.id\n  name            = \"web-tier\"\n  attributes_json = jsonencode({\n    \"filters\" = [\n      \"tag:Environment=production\",\n      \"tag:Tier=web\"\n    ]\n  })\n}\n```\n\n## Security Best Practices\n\n1. **Use Vault KMS for key management** instead of static AEAD keys in production\n2. **Enable session recording** for all privileged access targets\n3. **Set session time limits** appropriate to the resource sensitivity\n4. **Use OIDC managed groups** for automatic role assignment from IdP\n5. **Deploy multi-hop workers** for accessing resources across network boundaries\n6. **Rotate Vault tokens** used by credential stores regularly\n7. **Enable audit logging** on both controllers and workers\n8. **Use credential injection** (SSH certificates) over brokering when possible\n9. **Implement least-privilege grants** -- avoid wildcard permissions\n10. **Review session recordings** regularly for compliance and incident response\n\n## References\n\n- [HashiCorp Boundary Documentation](https:\u002F\u002Fdeveloper.hashicorp.com\u002Fboundary\u002Fdocs)\n- [Boundary and Vault Integration](https:\u002F\u002Fdeveloper.hashicorp.com\u002Fboundary\u002Fdocs\u002Fconcepts\u002Fcredential-management)\n- [From Zero to Hero with Boundary](https:\u002F\u002Fwww.hashicorp.com\u002Fen\u002Fblog\u002Ffrom-zero-to-hero-hashicorp-boundary)\n- [Boundary Terraform Provider](https:\u002F\u002Fregistry.terraform.io\u002Fproviders\u002Fhashicorp\u002Fboundary\u002Flatest\u002Fdocs)\n- [Zero Trust with Vault, Consul, and Boundary](https:\u002F\u002Fwww.hashicorp.com\u002Fen\u002Fresources\u002Fzero-trust-security-with-hashicorp-vault-consul-and-boundary)\n",{"name":5,"tags":24,"author":33,"domain":34,"license":14,"version":35,"mitre_f3":36,"nist_csf":60,"subdomain":65,"description":7,"mitre_attack":66},[25,26,27,28,29,30,31,32],"zero-trust","hashicorp","boundary","privileged-access","vault","identity-aware-proxy","session-recording","just-in-time-access","mahipal","cybersecurity","1.0",{"tactics":37,"version":41,"techniques":42},[38,39,40],"initial-access","positioning","resource-development","1.1",[43,47,50,53,56],{"id":44,"name":45,"source":46,"tactic":40},"T1586","Compromise Accounts","attack",{"id":48,"name":49,"source":46,"tactic":38},"T1110","Brute Force",{"id":51,"name":52,"source":46,"tactic":38},"T1110.004","Brute Force:  Credential Stuffing",{"id":54,"name":55,"source":46,"tactic":39},"T1219","Remote Access Tools",{"id":57,"name":58,"source":59,"tactic":38},"F1033","Insider Access Abuse","f3",[61,62,63,64],"PR.AA-01","PR.AA-05","PR.IR-01","GV.PO-01","zero-trust-architecture",[67,68,69,70,48],"T1078","T1190","T1059","T1003","main","1eb986d0b0ecc180291597e08eb5a58288843536","skills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fimplementing-zero-trust-with-hashicorp-boundary","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv","2026-08-25 13:16:33",{"source":8,"skillName":5,"commands":78,"prompt":88,"zipAvailable":89},[79,82,85],{"tool":80,"command":81},"npx","npx skills add vikasvardhanv\u002Fjerry_skills --skill implementing-zero-trust-with-hashicorp-boundary",{"tool":83,"command":84},"bunx","bunx skills add vikasvardhanv\u002Fjerry_skills --skill implementing-zero-trust-with-hashicorp-boundary",{"tool":86,"command":87},"pnpm","pnpm dlx skills add vikasvardhanv\u002Fjerry_skills --skill implementing-zero-trust-with-hashicorp-boundary","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fimplementing-zero-trust-with-hashicorp-boundary\u002FSKILL.md",true,[91,97,101,107,111,115,121],{"path":92,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":95,"sourceHtmlUrl":96},"assets\u002Ftemplate.md","ASSET","资产文件",1381,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fimplementing-zero-trust-with-hashicorp-boundary\u002Fassets\u002Ftemplate.md",{"path":98,"resourceType":98,"resourceTypeDesc":99,"sizeBytes":100,"sourceHtmlUrl":15},"LICENSE","许可证",11255,{"path":102,"resourceType":103,"resourceTypeDesc":104,"sizeBytes":105,"sourceHtmlUrl":106},"references\u002Fapi-reference.md","REFERENCE","参考文档",1636,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fimplementing-zero-trust-with-hashicorp-boundary\u002Freferences\u002Fapi-reference.md",{"path":108,"resourceType":103,"resourceTypeDesc":104,"sizeBytes":109,"sourceHtmlUrl":110},"references\u002Fstandards.md",2275,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fimplementing-zero-trust-with-hashicorp-boundary\u002Freferences\u002Fstandards.md",{"path":112,"resourceType":103,"resourceTypeDesc":104,"sizeBytes":113,"sourceHtmlUrl":114},"references\u002Fworkflows.md",3496,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fimplementing-zero-trust-with-hashicorp-boundary\u002Freferences\u002Fworkflows.md",{"path":116,"resourceType":117,"resourceTypeDesc":118,"sizeBytes":119,"sourceHtmlUrl":120},"scripts\u002Fagent.py","SCRIPT","脚本",6815,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fimplementing-zero-trust-with-hashicorp-boundary\u002Fscripts\u002Fagent.py",{"path":122,"resourceType":117,"resourceTypeDesc":118,"sizeBytes":123,"sourceHtmlUrl":124},"scripts\u002Fprocess.py",12374,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fimplementing-zero-trust-with-hashicorp-boundary\u002Fscripts\u002Fprocess.py",[126,134,141,148,155,162],{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":130,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":133,"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":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":130,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":140,"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":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":130,"licenseFileUrl":6,"sourceHtmlUrl":145,"categories":146,"keywords":147,"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":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":130,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":154,"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":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":130,"licenseFileUrl":6,"sourceHtmlUrl":159,"categories":160,"keywords":161,"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":163,"name":164,"nameZh":6,"description":165,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":130,"licenseFileUrl":6,"sourceHtmlUrl":166,"categories":167,"keywords":168,"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",[],[]]