[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B9BN3BHQPZEZ28ESS4VME7":3,"skill-same:01M7B9BN3BHQPZEZ28ESS4VME7":100},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":15,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":13,"repositoryHtmlUrl":49,"repositoryHomepageUrl":6,"ownerHtmlUrl":50,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":51,"install":52,"resources":65},"01M7B9BN3BHQPZEZ28ESS4VME7","securing-helm-chart-deployments",null,"Secures Helm chart deployments by verifying chart signatures and provenance, rendering and linting templates for misconfiguration, enforcing pod security contexts through values.yaml, moving secrets into an external store instead of Helm values, and scoping RBAC for Helm operations in CI\u002FCD. Use when deploying charts to Kubernetes or reviewing chart provenance, templates, or release RBAC. Keywords: Helm, provenance file, helm verify, helm lint, values.yaml, Tiller-less, release RBAC, external secrets. Do not use for scanning the rendered manifests themselves - use scanning-kubernetes-manifests-with-kubesec.","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\u002Fsecuring-helm-chart-deployments\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fsecuring-helm-chart-deployments\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: securing-helm-chart-deployments\ndescription: >-\n  Secures Helm chart deployments by verifying chart signatures and provenance, rendering and\n  linting templates for misconfiguration, enforcing pod security contexts through values.yaml,\n  moving secrets into an external store instead of Helm values, and scoping RBAC for Helm\n  operations in CI\u002FCD. Use when deploying charts to Kubernetes or reviewing chart provenance,\n  templates, or release RBAC. Keywords: Helm, provenance file, helm verify, helm lint,\n  values.yaml, Tiller-less, release RBAC, external secrets. Do not use for scanning the\n  rendered manifests themselves - use scanning-kubernetes-manifests-with-kubesec.\ndomain: cybersecurity\nsubdomain: container-security\ntags:\n- helm\n- kubernetes\n- chart-security\n- supply-chain\n- configuration-security\n- deployment\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- PR.PS-01\n- PR.IR-01\n- ID.AM-08\n- DE.CM-01\nmitre_attack:\n- T1610\n- T1611\n- T1609\n- T1525\n- T1195\n---\n\n# Securing Helm Chart Deployments\n\n## Overview\n\nHelm is the Kubernetes package manager. Securing Helm deployments requires validating chart provenance, scanning templates for security misconfigurations, enforcing pod security contexts, managing secrets securely, and controlling RBAC for Helm operations.\n\n\n## When to Use\n\n- When deploying or configuring securing helm chart deployments 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- Helm 3.12+ installed\n- kubectl with cluster access\n- GnuPG for chart signing\u002Fverification\n- kubesec or checkov for template scanning\n\n## Chart Provenance and Integrity\n\n### Sign a Helm Chart\n\n```bash\n# Generate GPG key for signing\ngpg --full-generate-key\n\n# Package and sign chart\nhelm package .\u002Fmychart --sign --key \"helm-signing@example.com\" --keyring ~\u002F.gnupg\u002Fpubring.gpg\n\n# Verify chart signature\nhelm verify mychart-0.1.0.tgz --keyring ~\u002F.gnupg\u002Fpubring.gpg\n```\n\n### Verify Chart Before Install\n\n```bash\n# Verify chart from repository\nhelm pull myrepo\u002Fmychart --verify --keyring \u002Fpath\u002Fto\u002Fkeyring.gpg\n\n# Check chart provenance file\ncat mychart-0.1.0.tgz.prov\n```\n\n## Template Security Scanning\n\n### Render and Scan Templates\n\n```bash\n# Render templates without deploying\nhelm template myrelease .\u002Fmychart --values values-prod.yaml > rendered.yaml\n\n# Scan with kubesec\nkubesec scan rendered.yaml\n\n# Scan with checkov\ncheckov -f rendered.yaml --framework kubernetes\n\n# Scan with trivy\ntrivy config rendered.yaml\n\n# Scan with kube-linter\nkube-linter lint rendered.yaml\n```\n\n### Helm Lint for Misconfigurations\n\n```bash\n# Lint chart\nhelm lint .\u002Fmychart --values values-prod.yaml --strict\n\n# Lint with debug output\nhelm lint .\u002Fmychart --debug\n```\n\n## Security Context Enforcement in values.yaml\n\n```yaml\n# values.yaml - Security hardened defaults\nsecurityContext:\n  runAsNonRoot: true\n  runAsUser: 1000\n  runAsGroup: 3000\n  fsGroup: 2000\n  readOnlyRootFilesystem: true\n  allowPrivilegeEscalation: false\n  capabilities:\n    drop:\n      - ALL\n\npodSecurityContext:\n  seccompProfile:\n    type: RuntimeDefault\n\nresources:\n  limits:\n    cpu: 500m\n    memory: 512Mi\n  requests:\n    cpu: 100m\n    memory: 128Mi\n\nnetworkPolicy:\n  enabled: true\n\nserviceAccount:\n  create: true\n  automountServiceAccountToken: false\n\nimage:\n  pullPolicy: Always\n  # Use digest instead of tag for immutability\n  # tag: \"1.0.0\"\n  # digest: \"sha256:abc123...\"\n```\n\n### Template with Security Contexts\n\n```yaml\n# templates\u002Fdeployment.yaml\napiVersion: apps\u002Fv1\nkind: Deployment\nmetadata:\n  name: {{ include \"mychart.fullname\" . }}\nspec:\n  template:\n    spec:\n      automountServiceAccountToken: {{ .Values.serviceAccount.automountServiceAccountToken }}\n      securityContext:\n        {{- toYaml .Values.podSecurityContext | nindent 8 }}\n      containers:\n        - name: {{ .Chart.Name }}\n          securityContext:\n            {{- toYaml .Values.securityContext | nindent 12 }}\n          image: \"{{ .Values.image.repository }}:{{ .Values.image.tag }}\"\n          resources:\n            {{- toYaml .Values.resources | nindent 12 }}\n```\n\n## Secrets Management\n\n### Use External Secrets (Not Helm Values)\n\n```yaml\n# templates\u002Fexternal-secret.yaml\napiVersion: external-secrets.io\u002Fv1beta1\nkind: ExternalSecret\nmetadata:\n  name: {{ include \"mychart.fullname\" . }}-secrets\nspec:\n  refreshInterval: 1h\n  secretStoreRef:\n    name: aws-secretsmanager\n    kind: ClusterSecretStore\n  target:\n    name: {{ include \"mychart.fullname\" . }}-secrets\n  data:\n    - secretKey: db-password\n      remoteRef:\n        key: production\u002Fdatabase\n        property: password\n```\n\n### helm-secrets Plugin\n\n```bash\n# Install helm-secrets plugin\nhelm plugin install https:\u002F\u002Fgithub.com\u002Fjkroepke\u002Fhelm-secrets\n\n# Encrypt values file\nhelm secrets encrypt values-secrets.yaml\n\n# Deploy with encrypted secrets\nhelm secrets install myrelease .\u002Fmychart -f values.yaml -f values-secrets.yaml\n\n# Decrypt for editing\nhelm secrets edit values-secrets.yaml\n```\n\n## RBAC for Helm Operations\n\n```yaml\n# helm-deployer-role.yaml\napiVersion: rbac.authorization.k8s.io\u002Fv1\nkind: Role\nmetadata:\n  name: helm-deployer\n  namespace: production\nrules:\n  - apiGroups: [\"\", \"apps\", \"batch\", \"networking.k8s.io\"]\n    resources: [\"deployments\", \"services\", \"configmaps\", \"secrets\", \"ingresses\", \"jobs\"]\n    verbs: [\"get\", \"list\", \"create\", \"update\", \"patch\", \"delete\"]\n  - apiGroups: [\"\"]\n    resources: [\"pods\", \"pods\u002Flog\"]\n    verbs: [\"get\", \"list\"]\n\n---\napiVersion: rbac.authorization.k8s.io\u002Fv1\nkind: RoleBinding\nmetadata:\n  name: helm-deployer-binding\n  namespace: production\nsubjects:\n  - kind: ServiceAccount\n    name: helm-deployer\n    namespace: production\nroleRef:\n  kind: Role\n  name: helm-deployer\n  apiGroup: rbac.authorization.k8s.io\n```\n\n## CI\u002FCD Helm Security Pipeline\n\n```yaml\n# .github\u002Fworkflows\u002Fhelm-security.yaml\nname: Helm Chart Security\non:\n  pull_request:\n    paths: ['charts\u002F**']\n\njobs:\n  lint-and-scan:\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions\u002Fcheckout@v4\n\n      - name: Helm lint\n        run: helm lint .\u002Fcharts\u002Fmychart --strict\n\n      - name: Render templates\n        run: helm template test .\u002Fcharts\u002Fmychart -f charts\u002Fmychart\u002Fvalues.yaml > rendered.yaml\n\n      - name: Scan with kube-linter\n        uses: stackrox\u002Fkube-linter-action@v1\n        with:\n          directory: rendered.yaml\n\n      - name: Scan with trivy\n        uses: aquasecurity\u002Ftrivy-action@master\n        with:\n          scan-type: config\n          scan-ref: rendered.yaml\n\n      - name: Scan with checkov\n        uses: bridgecrewio\u002Fcheckov-action@master\n        with:\n          file: rendered.yaml\n          framework: kubernetes\n```\n\n## Best Practices\n\n1. **Sign charts** with GPG and verify before installation\n2. **Render and scan** templates before deploying to catch misconfigurations\n3. **Enforce security contexts** in values.yaml defaults\n4. **Never store secrets** in Helm values - use external secrets or helm-secrets plugin\n5. **Use image digests** instead of tags for immutable references\n6. **Restrict Helm RBAC** to least privilege per namespace\n7. **Pin chart versions** in requirements - never use `latest`\n8. **Lint strictly** in CI with `--strict` flag\n9. **Review third-party charts** before deploying to production\n10. **Use Helm test hooks** to validate deployments post-install\n","# Securing Helm Chart Deployments\n\n## Overview\n\nHelm is the Kubernetes package manager. Securing Helm deployments requires validating chart provenance, scanning templates for security misconfigurations, enforcing pod security contexts, managing secrets securely, and controlling RBAC for Helm operations.\n\n\n## When to Use\n\n- When deploying or configuring securing helm chart deployments 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- Helm 3.12+ installed\n- kubectl with cluster access\n- GnuPG for chart signing\u002Fverification\n- kubesec or checkov for template scanning\n\n## Chart Provenance and Integrity\n\n### Sign a Helm Chart\n\n```bash\n# Generate GPG key for signing\ngpg --full-generate-key\n\n# Package and sign chart\nhelm package .\u002Fmychart --sign --key \"helm-signing@example.com\" --keyring ~\u002F.gnupg\u002Fpubring.gpg\n\n# Verify chart signature\nhelm verify mychart-0.1.0.tgz --keyring ~\u002F.gnupg\u002Fpubring.gpg\n```\n\n### Verify Chart Before Install\n\n```bash\n# Verify chart from repository\nhelm pull myrepo\u002Fmychart --verify --keyring \u002Fpath\u002Fto\u002Fkeyring.gpg\n\n# Check chart provenance file\ncat mychart-0.1.0.tgz.prov\n```\n\n## Template Security Scanning\n\n### Render and Scan Templates\n\n```bash\n# Render templates without deploying\nhelm template myrelease .\u002Fmychart --values values-prod.yaml > rendered.yaml\n\n# Scan with kubesec\nkubesec scan rendered.yaml\n\n# Scan with checkov\ncheckov -f rendered.yaml --framework kubernetes\n\n# Scan with trivy\ntrivy config rendered.yaml\n\n# Scan with kube-linter\nkube-linter lint rendered.yaml\n```\n\n### Helm Lint for Misconfigurations\n\n```bash\n# Lint chart\nhelm lint .\u002Fmychart --values values-prod.yaml --strict\n\n# Lint with debug output\nhelm lint .\u002Fmychart --debug\n```\n\n## Security Context Enforcement in values.yaml\n\n```yaml\n# values.yaml - Security hardened defaults\nsecurityContext:\n  runAsNonRoot: true\n  runAsUser: 1000\n  runAsGroup: 3000\n  fsGroup: 2000\n  readOnlyRootFilesystem: true\n  allowPrivilegeEscalation: false\n  capabilities:\n    drop:\n      - ALL\n\npodSecurityContext:\n  seccompProfile:\n    type: RuntimeDefault\n\nresources:\n  limits:\n    cpu: 500m\n    memory: 512Mi\n  requests:\n    cpu: 100m\n    memory: 128Mi\n\nnetworkPolicy:\n  enabled: true\n\nserviceAccount:\n  create: true\n  automountServiceAccountToken: false\n\nimage:\n  pullPolicy: Always\n  # Use digest instead of tag for immutability\n  # tag: \"1.0.0\"\n  # digest: \"sha256:abc123...\"\n```\n\n### Template with Security Contexts\n\n```yaml\n# templates\u002Fdeployment.yaml\napiVersion: apps\u002Fv1\nkind: Deployment\nmetadata:\n  name: {{ include \"mychart.fullname\" . }}\nspec:\n  template:\n    spec:\n      automountServiceAccountToken: {{ .Values.serviceAccount.automountServiceAccountToken }}\n      securityContext:\n        {{- toYaml .Values.podSecurityContext | nindent 8 }}\n      containers:\n        - name: {{ .Chart.Name }}\n          securityContext:\n            {{- toYaml .Values.securityContext | nindent 12 }}\n          image: \"{{ .Values.image.repository }}:{{ .Values.image.tag }}\"\n          resources:\n            {{- toYaml .Values.resources | nindent 12 }}\n```\n\n## Secrets Management\n\n### Use External Secrets (Not Helm Values)\n\n```yaml\n# templates\u002Fexternal-secret.yaml\napiVersion: external-secrets.io\u002Fv1beta1\nkind: ExternalSecret\nmetadata:\n  name: {{ include \"mychart.fullname\" . }}-secrets\nspec:\n  refreshInterval: 1h\n  secretStoreRef:\n    name: aws-secretsmanager\n    kind: ClusterSecretStore\n  target:\n    name: {{ include \"mychart.fullname\" . }}-secrets\n  data:\n    - secretKey: db-password\n      remoteRef:\n        key: production\u002Fdatabase\n        property: password\n```\n\n### helm-secrets Plugin\n\n```bash\n# Install helm-secrets plugin\nhelm plugin install https:\u002F\u002Fgithub.com\u002Fjkroepke\u002Fhelm-secrets\n\n# Encrypt values file\nhelm secrets encrypt values-secrets.yaml\n\n# Deploy with encrypted secrets\nhelm secrets install myrelease .\u002Fmychart -f values.yaml -f values-secrets.yaml\n\n# Decrypt for editing\nhelm secrets edit values-secrets.yaml\n```\n\n## RBAC for Helm Operations\n\n```yaml\n# helm-deployer-role.yaml\napiVersion: rbac.authorization.k8s.io\u002Fv1\nkind: Role\nmetadata:\n  name: helm-deployer\n  namespace: production\nrules:\n  - apiGroups: [\"\", \"apps\", \"batch\", \"networking.k8s.io\"]\n    resources: [\"deployments\", \"services\", \"configmaps\", \"secrets\", \"ingresses\", \"jobs\"]\n    verbs: [\"get\", \"list\", \"create\", \"update\", \"patch\", \"delete\"]\n  - apiGroups: [\"\"]\n    resources: [\"pods\", \"pods\u002Flog\"]\n    verbs: [\"get\", \"list\"]\n\n---\napiVersion: rbac.authorization.k8s.io\u002Fv1\nkind: RoleBinding\nmetadata:\n  name: helm-deployer-binding\n  namespace: production\nsubjects:\n  - kind: ServiceAccount\n    name: helm-deployer\n    namespace: production\nroleRef:\n  kind: Role\n  name: helm-deployer\n  apiGroup: rbac.authorization.k8s.io\n```\n\n## CI\u002FCD Helm Security Pipeline\n\n```yaml\n# .github\u002Fworkflows\u002Fhelm-security.yaml\nname: Helm Chart Security\non:\n  pull_request:\n    paths: ['charts\u002F**']\n\njobs:\n  lint-and-scan:\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions\u002Fcheckout@v4\n\n      - name: Helm lint\n        run: helm lint .\u002Fcharts\u002Fmychart --strict\n\n      - name: Render templates\n        run: helm template test .\u002Fcharts\u002Fmychart -f charts\u002Fmychart\u002Fvalues.yaml > rendered.yaml\n\n      - name: Scan with kube-linter\n        uses: stackrox\u002Fkube-linter-action@v1\n        with:\n          directory: rendered.yaml\n\n      - name: Scan with trivy\n        uses: aquasecurity\u002Ftrivy-action@master\n        with:\n          scan-type: config\n          scan-ref: rendered.yaml\n\n      - name: Scan with checkov\n        uses: bridgecrewio\u002Fcheckov-action@master\n        with:\n          file: rendered.yaml\n          framework: kubernetes\n```\n\n## Best Practices\n\n1. **Sign charts** with GPG and verify before installation\n2. **Render and scan** templates before deploying to catch misconfigurations\n3. **Enforce security contexts** in values.yaml defaults\n4. **Never store secrets** in Helm values - use external secrets or helm-secrets plugin\n5. **Use image digests** instead of tags for immutable references\n6. **Restrict Helm RBAC** to least privilege per namespace\n7. **Pin chart versions** in requirements - never use `latest`\n8. **Lint strictly** in CI with `--strict` flag\n9. **Review third-party charts** before deploying to production\n10. **Use Helm test hooks** to validate deployments post-install\n",{"name":5,"tags":24,"author":31,"domain":32,"license":14,"version":33,"nist_csf":34,"subdomain":39,"description":7,"mitre_attack":40},[25,26,27,28,29,30],"helm","kubernetes","chart-security","supply-chain","configuration-security","deployment","mahipal","cybersecurity","1.0",[35,36,37,38],"PR.PS-01","PR.IR-01","ID.AM-08","DE.CM-01","container-security",[41,42,43,44,45],"T1610","T1611","T1609","T1525","T1195","main","1eb986d0b0ecc180291597e08eb5a58288843536","skills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fsecuring-helm-chart-deployments","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv","2026-08-25 13:16:33",{"source":8,"skillName":5,"commands":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add vikasvardhanv\u002Fjerry_skills --skill securing-helm-chart-deployments",{"tool":58,"command":59},"bunx","bunx skills add vikasvardhanv\u002Fjerry_skills --skill securing-helm-chart-deployments",{"tool":61,"command":62},"pnpm","pnpm dlx skills add vikasvardhanv\u002Fjerry_skills --skill securing-helm-chart-deployments","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fsecuring-helm-chart-deployments\u002FSKILL.md",true,[66,72,76,82,86,90,96],{"path":67,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":70,"sourceHtmlUrl":71},"assets\u002Ftemplate.md","ASSET","资产文件",1020,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fsecuring-helm-chart-deployments\u002Fassets\u002Ftemplate.md",{"path":73,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":75,"sourceHtmlUrl":15},"LICENSE","许可证",11255,{"path":77,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Fapi-reference.md","REFERENCE","参考文档",1981,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fsecuring-helm-chart-deployments\u002Freferences\u002Fapi-reference.md",{"path":83,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":84,"sourceHtmlUrl":85},"references\u002Fstandards.md",1329,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fsecuring-helm-chart-deployments\u002Freferences\u002Fstandards.md",{"path":87,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":88,"sourceHtmlUrl":89},"references\u002Fworkflows.md",1093,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fsecuring-helm-chart-deployments\u002Freferences\u002Fworkflows.md",{"path":91,"resourceType":92,"resourceTypeDesc":93,"sizeBytes":94,"sourceHtmlUrl":95},"scripts\u002Fagent.py","SCRIPT","脚本",6768,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fsecuring-helm-chart-deployments\u002Fscripts\u002Fagent.py",{"path":97,"resourceType":92,"resourceTypeDesc":93,"sizeBytes":98,"sourceHtmlUrl":99},"scripts\u002Fprocess.py",6347,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fsecuring-helm-chart-deployments\u002Fscripts\u002Fprocess.py",[101,109,116,123,130,137],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":105,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":19},"01M7BESR1CJ3H5SP9XM8KYJZ9W","syllabus","Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Use when the user uploads a syllabus, course outline, or curriculum document and wants supplementary readings (e.g., 'create a reading list from this syllabus', 'find recent papers for my course') — even casual mentions with a syllabus attached should trigger this skill.","MIT","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\u002FSKILL.md",[],[],{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":105,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":19},"01M7BES1YA6R97W7QPMFFM1PED","pulse","Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X\u002FTwitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend\u002Fsentiment\u002Fproblems\u002Fopportunities\u002Fcomparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Use when the user requests multi-source recency intelligence on a topic (e.g., 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]'), and for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\u002FSKILL.md",[],[],{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":105,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":19},"01M7BERNHYGY035AR00VRT03KE","patent","Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search \u002F freedom-to-operate \u002F competitive landscape \u002F acquisition diligence \u002F litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Use when the user asks for patent searching or analysis (e.g., 'prior art search for [invention]', 'freedom to operate analysis for [product]'). Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\u002FSKILL.md",[],[],{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":105,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":19},"01M7BERCK1EAKTWW7R436WAR0J","notebooklm","Browser automation skill for controlling Google's NotebookLM. Use when the user wants anything done in NotebookLM (e.g., 'open NotebookLM', 'check my [name] notebook', 'ask my notebook about X', 'add [source] to NotebookLM', 'generate a Video Overview from my notebook', 'use NotebookLM Studio'). Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio\u002FVideo Overviews, Mind Maps, Reports incl. Briefing Doc\u002FStudy Guide\u002FFAQ, Flashcards, Quiz, slide decks, infographics — discover the exact set from the live Studio panel; the UI evolves fast), and creating new notebooks. Requires browser automation environment — fails gracefully when unavailable.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fnotebooklm\u002Fskills\u002Fnotebooklm\u002FSKILL.md",[],[],{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":105,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":136,"publishedAt":19},"01M7BEQZAZAQRTXFJRY7RHV3TY","litreview","Academic literature orientation skill that searches papers via free keyless APIs (PubMed E-utilities + OpenAlex) by default — with the Consensus MCP as an optional enhancement lane when connected — builds a strategic search plan using PICO (default) or SPIDER \u002F Decomposition \u002F hybrid as fallbacks, and synthesizes findings into a formatted Word (.docx) research guide. Grill-me intake (research question specificity + framework hint + tentative depth) before the recon search; a second forcing checkpoint after Phase 2 confirms framework + sub-areas + depth before searches consume budget. Configurable depth (5\u002F10\u002F20 queries) controls coverage vs. speed. Output is a 'launching pad' — an orientation guide that lets a researcher dive in confidently, not a finished review. Use when the user starts literature-oriented research (e.g., 'litreview on [topic]', 'literature review on [topic]', 'I'm starting a literature review on X', 'I'm writing a paper on X', 'help me research X', 'I'm doing research on X', 'can you help me research X'). Do NOT use for single one-off paper searches wanting a quick list — that's a plain PubMed\u002FOpenAlex (or Consensus) query.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Flitreview\u002Fskills\u002Flitreview\u002FSKILL.md",[],[],{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":105,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":143,"publishedAt":19},"01M7BEQKJ45K31QK5VRAQSVJCJ","grants","NIH grant research skill for clinical researchers. Grill-me intake (research idea + career stage + preliminary data + environment + submission posture + known institute targets) locks down the funding strategy before any search runs. Runs a 5-facet Consensus positioning analysis (with draft Significance\u002FInnovation language), maps the research to the right NIH institutes and study sections via RePORTER, finds NOSIs and funded overlap, and produces an editable Word document (.docx) with budget\u002Fscope-aware mechanism recommendations, submission timelines, and a mandatory program officer recommendation. Use when the user asks about research funding or makes any grant-related request (e.g., 'grants for [topic]', 'find grants for my research idea', 'what grants match my research', 'help me find NIH funding', 'grant opportunities for my research'). NIH-only scope — non-NIH funders (PCORI, DOD CDMRP, VA, foundations) are out of scope and flagged at intake.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fgrants\u002Fskills\u002Fgrants\u002FSKILL.md",[],[]]