[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B6NTXSMR4GD394P3GD7G7S":3,"skill-same:01M7B6NTXSMR4GD394P3GD7G7S":80},{"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":40,"commitSha":41,"skillDirectory":42,"forksCount":13,"repositoryHtmlUrl":43,"repositoryHomepageUrl":6,"ownerHtmlUrl":44,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":45,"install":46,"resources":59},"01M7B6NTXSMR4GD394P3GD7G7S","generating-and-analyzing-sboms",null,"Generate CycloneDX and SPDX SBOMs from container images and filesystems with Syft, correlate them to CVEs with Grype, and sign\u002Fattest them with Cosign. Use when you need a machine-readable dependency inventory for supply-chain risk, want to scan images or SBOMs for known vulnerabilities, or are embedding SBOM generation and vulnerability gating into CI\u002FCD.","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\u002Fgenerating-and-analyzing-sboms\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fgenerating-and-analyzing-sboms\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: generating-and-analyzing-sboms\ndescription: Generate CycloneDX and SPDX SBOMs from container images and filesystems with Syft, correlate them to CVEs with Grype, and sign\u002Fattest them with Cosign. Use when you need a machine-readable dependency inventory for supply-chain risk, want to scan images or SBOMs for known vulnerabilities, or are embedding SBOM generation and vulnerability gating into CI\u002FCD.\ndomain: cybersecurity\nsubdomain: supply-chain-security\ntags:\n- supply-chain-security\n- sbom\n- cyclonedx\n- spdx\n- syft\n- grype\n- vulnerability-management\n- devsecops\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- ID.AM-08\nmitre_attack:\n- T1195.001\n---\n# Generating and Analyzing SBOMs\n\n> **Authorized Use Only:** Generate and scan SBOMs only for software and images you own or are authorized to assess. Treat SBOMs as sensitive inventory data — they reveal your dependency attack surface.\n\n## Overview\n\nA Software Bill of Materials (SBOM) is a formal, machine-readable inventory of every component, library, and dependency in a piece of software — the supply-chain equivalent of an ingredients label. SBOMs are central to defending against supply-chain compromise (CISA's SBOM initiative, US Executive Order 14028) because you cannot patch what you cannot see. The two dominant SBOM standards are:\n\n- **CycloneDX** — an OWASP standard optimized for security use cases (vulnerabilities, VEX, dependency relationships).\n- **SPDX** — a Linux Foundation \u002F ISO standard (ISO\u002FIEC 5962) strong on licensing and provenance.\n\nThe reference open-source toolchain is from Anchore:\n\n- **Syft** generates SBOMs (CycloneDX, SPDX, or its native format) from container images and filesystems.\n- **Grype** matches an SBOM (or image) against vulnerability databases to find CVEs.\n- **Cosign** (Sigstore) signs SBOMs and attaches them to images as signed attestations for tamper-evident provenance.\n\nThis skill covers producing standards-compliant SBOMs, correlating them with vulnerability intelligence, and embedding the workflow into CI\u002FCD.\n\n## When to Use\n\n- Establishing and maintaining a component inventory for applications and container images.\n- Continuously detecting known vulnerabilities (including newly disclosed CVEs against existing artifacts).\n- Satisfying procurement\u002Fregulatory SBOM requirements (CISA, EO 14028).\n- Producing signed SBOM attestations for downstream supply-chain trust.\n\n## Prerequisites\n\n- Install Syft and Grype (official install scripts):\n  ```bash\n  curl -sSfL https:\u002F\u002Fraw.githubusercontent.com\u002Fanchore\u002Fsyft\u002Fmain\u002Finstall.sh | sh -s -- -b \u002Fusr\u002Flocal\u002Fbin\n  curl -sSfL https:\u002F\u002Fraw.githubusercontent.com\u002Fanchore\u002Fgrype\u002Fmain\u002Finstall.sh | sh -s -- -b \u002Fusr\u002Flocal\u002Fbin\n  ```\n- Install Cosign for signing\u002Fattestation:\n  ```bash\n  # via Go, or download a release from https:\u002F\u002Fgithub.com\u002Fsigstore\u002Fcosign\u002Freleases\n  go install github.com\u002Fsigstore\u002Fcosign\u002Fv2\u002Fcmd\u002Fcosign@latest\n  ```\n- Access to the target images\u002Fsource and (for signing) a registry plus keys or keyless OIDC.\n\n## Objectives\n\n- Generate CycloneDX and SPDX SBOMs from images and directories.\n- Scan SBOMs and images for vulnerabilities with Grype.\n- Gate CI\u002FCD builds on severity thresholds.\n- Sign and attach SBOM attestations with Cosign and verify them.\n\n## MITRE ATT&CK Mapping\n\n| ID | Official Technique Name | Relevance to this skill |\n|----|------------------------|--------------------------|\n| T1195.001 | Supply Chain Compromise: Compromise Software Dependencies and Development Tools | SBOM generation and vulnerability correlation expose compromised or vulnerable dependencies — the attack surface adversaries abuse under this technique. |\n\nThis is a defensive supply-chain skill; the mapping reflects the adversary technique it is designed to detect and mitigate.\n\n## Workflow\n\n### 1. Generate a CycloneDX SBOM from a container image\n`-o \u003Cformat>` selects output; `cyclonedx-json` is security-oriented.\n```bash\nsyft alpine:latest -o cyclonedx-json=alpine.cdx.json\n```\n\n### 2. Generate an SPDX SBOM from a source directory\nUse the `dir:` source to inventory a checked-out repository; `spdx-json` for the SPDX standard.\n```bash\nsyft dir:. -o spdx-json=app.spdx.json\n```\n\n### 3. Emit multiple formats at once\nProduce both standards in a single pass for different consumers.\n```bash\nsyft myorg\u002Fapp:1.4.2 \\\n  -o cyclonedx-json=app.cdx.json \\\n  -o spdx-json=app.spdx.json \\\n  -o table\n```\n\n### 4. Scan the SBOM for vulnerabilities with Grype\nDecoupling generation from scanning lets you re-scan stored SBOMs as new CVEs land — without rebuilding.\n```bash\n# Scan an existing SBOM\ngrype sbom:app.cdx.json -o table\n\n# JSON report for automation\ngrype sbom:app.cdx.json -o json > app.vulns.json\n```\nYou can also scan an image directly (Grype generates the SBOM internally):\n```bash\ngrype myorg\u002Fapp:1.4.2 -o table\n```\n\n### 5. Gate CI\u002FCD on severity\n`--fail-on` exits non-zero at or above a severity, failing the pipeline.\n```bash\ngrype sbom:app.cdx.json --fail-on high\n```\nFilter out unfixable noise with a `.grype.yaml` policy (`only-fixed: true`) or `--only-fixed`:\n```bash\ngrype sbom:app.cdx.json --only-fixed --fail-on critical\n```\n\n### 6. Sign and attach the SBOM as an attestation\nCosign records the SBOM as a signed, in-toto attestation alongside the image in the registry.\n```bash\n# Key-based signing\ncosign attest --key cosign.key \\\n  --predicate app.spdx.json \\\n  --type spdxjson \\\n  myorg\u002Fapp:1.4.2\n\n# Keyless (Sigstore OIDC \u002F Fulcio + Rekor)\nCOSIGN_EXPERIMENTAL=1 cosign attest \\\n  --predicate app.cdx.json \\\n  --type cyclonedx \\\n  myorg\u002Fapp:1.4.2\n```\n\n### 7. Verify the attestation downstream\nConsumers verify provenance before trusting an image.\n```bash\ncosign verify-attestation --key cosign.pub --type spdxjson myorg\u002Fapp:1.4.2\n```\n\n### 8. Retrieve and re-scan attached SBOMs\nPull the attested SBOM from the registry and re-run Grype as part of continuous monitoring.\n```bash\ncosign download attestation myorg\u002Fapp:1.4.2 \\\n  | jq -r '.payload' | base64 -d | jq '.predicate' > pulled.spdx.json\ngrype sbom:pulled.spdx.json -o table\n```\n\n### 9. Correlate to vulnerability intelligence\nFeed Grype JSON into your vulnerability management workflow: deduplicate by CVE, enrich with EPSS\u002FKEV for prioritization, and track remediation SLAs. Re-scan stored SBOMs on each Grype DB update to catch newly disclosed CVEs in unchanged artifacts.\n\n## Tools and Resources\n\n| Tool | Purpose | Link |\n|------|---------|------|\n| Syft | SBOM generation | https:\u002F\u002Fgithub.com\u002Fanchore\u002Fsyft |\n| Grype | Vulnerability scanning of SBOMs\u002Fimages | https:\u002F\u002Fgithub.com\u002Fanchore\u002Fgrype |\n| Cosign | SBOM signing\u002Fattestation | https:\u002F\u002Fgithub.com\u002Fsigstore\u002Fcosign |\n| CycloneDX | Security-focused SBOM standard | https:\u002F\u002Fcyclonedx.org\u002F |\n| SPDX | ISO SBOM standard | https:\u002F\u002Fspdx.dev\u002F |\n| CISA SBOM | Guidance and minimum elements | https:\u002F\u002Fwww.cisa.gov\u002Fsbom |\n\n## Format Comparison\n\n| Aspect | CycloneDX | SPDX |\n|--------|-----------|------|\n| Steward | OWASP | Linux Foundation \u002F ISO 5962 |\n| Strength | Security, VEX, vulnerabilities | Licensing, provenance |\n| Common syft `-o` values | `cyclonedx-json`, `cyclonedx-xml` | `spdx-json`, `spdx` (tag-value) |\n\n## Validation Criteria\n\n- [ ] CycloneDX SBOM generated from the target image\n- [ ] SPDX SBOM generated from source where required\n- [ ] SBOM scanned with Grype producing a CVE report\n- [ ] CI\u002FCD gated with `--fail-on` at an agreed severity\n- [ ] SBOM signed and attached as an attestation with Cosign\n- [ ] Attestation verified downstream\n- [ ] Stored SBOMs re-scanned on Grype DB updates\n- [ ] Findings correlated\u002Fprioritized (EPSS\u002FKEV) and tracked to remediation\n","# Generating and Analyzing SBOMs\n\n> **Authorized Use Only:** Generate and scan SBOMs only for software and images you own or are authorized to assess. Treat SBOMs as sensitive inventory data — they reveal your dependency attack surface.\n\n## Overview\n\nA Software Bill of Materials (SBOM) is a formal, machine-readable inventory of every component, library, and dependency in a piece of software — the supply-chain equivalent of an ingredients label. SBOMs are central to defending against supply-chain compromise (CISA's SBOM initiative, US Executive Order 14028) because you cannot patch what you cannot see. The two dominant SBOM standards are:\n\n- **CycloneDX** — an OWASP standard optimized for security use cases (vulnerabilities, VEX, dependency relationships).\n- **SPDX** — a Linux Foundation \u002F ISO standard (ISO\u002FIEC 5962) strong on licensing and provenance.\n\nThe reference open-source toolchain is from Anchore:\n\n- **Syft** generates SBOMs (CycloneDX, SPDX, or its native format) from container images and filesystems.\n- **Grype** matches an SBOM (or image) against vulnerability databases to find CVEs.\n- **Cosign** (Sigstore) signs SBOMs and attaches them to images as signed attestations for tamper-evident provenance.\n\nThis skill covers producing standards-compliant SBOMs, correlating them with vulnerability intelligence, and embedding the workflow into CI\u002FCD.\n\n## When to Use\n\n- Establishing and maintaining a component inventory for applications and container images.\n- Continuously detecting known vulnerabilities (including newly disclosed CVEs against existing artifacts).\n- Satisfying procurement\u002Fregulatory SBOM requirements (CISA, EO 14028).\n- Producing signed SBOM attestations for downstream supply-chain trust.\n\n## Prerequisites\n\n- Install Syft and Grype (official install scripts):\n  ```bash\n  curl -sSfL https:\u002F\u002Fraw.githubusercontent.com\u002Fanchore\u002Fsyft\u002Fmain\u002Finstall.sh | sh -s -- -b \u002Fusr\u002Flocal\u002Fbin\n  curl -sSfL https:\u002F\u002Fraw.githubusercontent.com\u002Fanchore\u002Fgrype\u002Fmain\u002Finstall.sh | sh -s -- -b \u002Fusr\u002Flocal\u002Fbin\n  ```\n- Install Cosign for signing\u002Fattestation:\n  ```bash\n  # via Go, or download a release from https:\u002F\u002Fgithub.com\u002Fsigstore\u002Fcosign\u002Freleases\n  go install github.com\u002Fsigstore\u002Fcosign\u002Fv2\u002Fcmd\u002Fcosign@latest\n  ```\n- Access to the target images\u002Fsource and (for signing) a registry plus keys or keyless OIDC.\n\n## Objectives\n\n- Generate CycloneDX and SPDX SBOMs from images and directories.\n- Scan SBOMs and images for vulnerabilities with Grype.\n- Gate CI\u002FCD builds on severity thresholds.\n- Sign and attach SBOM attestations with Cosign and verify them.\n\n## MITRE ATT&CK Mapping\n\n| ID | Official Technique Name | Relevance to this skill |\n|----|------------------------|--------------------------|\n| T1195.001 | Supply Chain Compromise: Compromise Software Dependencies and Development Tools | SBOM generation and vulnerability correlation expose compromised or vulnerable dependencies — the attack surface adversaries abuse under this technique. |\n\nThis is a defensive supply-chain skill; the mapping reflects the adversary technique it is designed to detect and mitigate.\n\n## Workflow\n\n### 1. Generate a CycloneDX SBOM from a container image\n`-o \u003Cformat>` selects output; `cyclonedx-json` is security-oriented.\n```bash\nsyft alpine:latest -o cyclonedx-json=alpine.cdx.json\n```\n\n### 2. Generate an SPDX SBOM from a source directory\nUse the `dir:` source to inventory a checked-out repository; `spdx-json` for the SPDX standard.\n```bash\nsyft dir:. -o spdx-json=app.spdx.json\n```\n\n### 3. Emit multiple formats at once\nProduce both standards in a single pass for different consumers.\n```bash\nsyft myorg\u002Fapp:1.4.2 \\\n  -o cyclonedx-json=app.cdx.json \\\n  -o spdx-json=app.spdx.json \\\n  -o table\n```\n\n### 4. Scan the SBOM for vulnerabilities with Grype\nDecoupling generation from scanning lets you re-scan stored SBOMs as new CVEs land — without rebuilding.\n```bash\n# Scan an existing SBOM\ngrype sbom:app.cdx.json -o table\n\n# JSON report for automation\ngrype sbom:app.cdx.json -o json > app.vulns.json\n```\nYou can also scan an image directly (Grype generates the SBOM internally):\n```bash\ngrype myorg\u002Fapp:1.4.2 -o table\n```\n\n### 5. Gate CI\u002FCD on severity\n`--fail-on` exits non-zero at or above a severity, failing the pipeline.\n```bash\ngrype sbom:app.cdx.json --fail-on high\n```\nFilter out unfixable noise with a `.grype.yaml` policy (`only-fixed: true`) or `--only-fixed`:\n```bash\ngrype sbom:app.cdx.json --only-fixed --fail-on critical\n```\n\n### 6. Sign and attach the SBOM as an attestation\nCosign records the SBOM as a signed, in-toto attestation alongside the image in the registry.\n```bash\n# Key-based signing\ncosign attest --key cosign.key \\\n  --predicate app.spdx.json \\\n  --type spdxjson \\\n  myorg\u002Fapp:1.4.2\n\n# Keyless (Sigstore OIDC \u002F Fulcio + Rekor)\nCOSIGN_EXPERIMENTAL=1 cosign attest \\\n  --predicate app.cdx.json \\\n  --type cyclonedx \\\n  myorg\u002Fapp:1.4.2\n```\n\n### 7. Verify the attestation downstream\nConsumers verify provenance before trusting an image.\n```bash\ncosign verify-attestation --key cosign.pub --type spdxjson myorg\u002Fapp:1.4.2\n```\n\n### 8. Retrieve and re-scan attached SBOMs\nPull the attested SBOM from the registry and re-run Grype as part of continuous monitoring.\n```bash\ncosign download attestation myorg\u002Fapp:1.4.2 \\\n  | jq -r '.payload' | base64 -d | jq '.predicate' > pulled.spdx.json\ngrype sbom:pulled.spdx.json -o table\n```\n\n### 9. Correlate to vulnerability intelligence\nFeed Grype JSON into your vulnerability management workflow: deduplicate by CVE, enrich with EPSS\u002FKEV for prioritization, and track remediation SLAs. Re-scan stored SBOMs on each Grype DB update to catch newly disclosed CVEs in unchanged artifacts.\n\n## Tools and Resources\n\n| Tool | Purpose | Link |\n|------|---------|------|\n| Syft | SBOM generation | https:\u002F\u002Fgithub.com\u002Fanchore\u002Fsyft |\n| Grype | Vulnerability scanning of SBOMs\u002Fimages | https:\u002F\u002Fgithub.com\u002Fanchore\u002Fgrype |\n| Cosign | SBOM signing\u002Fattestation | https:\u002F\u002Fgithub.com\u002Fsigstore\u002Fcosign |\n| CycloneDX | Security-focused SBOM standard | https:\u002F\u002Fcyclonedx.org\u002F |\n| SPDX | ISO SBOM standard | https:\u002F\u002Fspdx.dev\u002F |\n| CISA SBOM | Guidance and minimum elements | https:\u002F\u002Fwww.cisa.gov\u002Fsbom |\n\n## Format Comparison\n\n| Aspect | CycloneDX | SPDX |\n|--------|-----------|------|\n| Steward | OWASP | Linux Foundation \u002F ISO 5962 |\n| Strength | Security, VEX, vulnerabilities | Licensing, provenance |\n| Common syft `-o` values | `cyclonedx-json`, `cyclonedx-xml` | `spdx-json`, `spdx` (tag-value) |\n\n## Validation Criteria\n\n- [ ] CycloneDX SBOM generated from the target image\n- [ ] SPDX SBOM generated from source where required\n- [ ] SBOM scanned with Grype producing a CVE report\n- [ ] CI\u002FCD gated with `--fail-on` at an agreed severity\n- [ ] SBOM signed and attached as an attestation with Cosign\n- [ ] Attestation verified downstream\n- [ ] Stored SBOMs re-scanned on Grype DB updates\n- [ ] Findings correlated\u002Fprioritized (EPSS\u002FKEV) and tracked to remediation\n",{"name":5,"tags":24,"author":33,"domain":34,"license":14,"version":35,"nist_csf":36,"subdomain":25,"description":7,"mitre_attack":38},[25,26,27,28,29,30,31,32],"supply-chain-security","sbom","cyclonedx","spdx","syft","grype","vulnerability-management","devsecops","mahipal","cybersecurity","1.0",[37],"ID.AM-08",[39],"T1195.001","main","1eb986d0b0ecc180291597e08eb5a58288843536","skills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fgenerating-and-analyzing-sboms","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv","2026-08-25 13:16:33",{"source":8,"skillName":5,"commands":47,"prompt":57,"zipAvailable":58},[48,51,54],{"tool":49,"command":50},"npx","npx skills add vikasvardhanv\u002Fjerry_skills --skill generating-and-analyzing-sboms",{"tool":52,"command":53},"bunx","bunx skills add vikasvardhanv\u002Fjerry_skills --skill generating-and-analyzing-sboms",{"tool":55,"command":56},"pnpm","pnpm dlx skills add vikasvardhanv\u002Fjerry_skills --skill generating-and-analyzing-sboms","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fgenerating-and-analyzing-sboms\u002FSKILL.md",true,[60,64,70,74],{"path":61,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":63,"sourceHtmlUrl":15},"LICENSE","许可证",11255,{"path":65,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":68,"sourceHtmlUrl":69},"references\u002Fapi-reference.md","REFERENCE","参考文档",2393,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fgenerating-and-analyzing-sboms\u002Freferences\u002Fapi-reference.md",{"path":71,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Fstandards.md",1430,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fgenerating-and-analyzing-sboms\u002Freferences\u002Fstandards.md",{"path":75,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":78,"sourceHtmlUrl":79},"scripts\u002Fagent.py","SCRIPT","脚本",5466,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fgenerating-and-analyzing-sboms\u002Fscripts\u002Fagent.py",[81,89,96,103,110,117],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":85,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"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":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":85,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"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":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":85,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"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":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":85,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"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":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":85,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"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":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":85,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":123,"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",[],[]]