[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7D46M0YPMR4HS9621B9FJFP":3,"skill-same:01M7D46M0YPMR4HS9621B9FJFP":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7D46M0YPMR4HS9621B9FJFP","dep-diff-review",null,"Review what a change or pull request introduces into the dependency tree - new packages, version bumps, typosquats, install scripts, vulnerabilities - using postmortem diff plus mlab.sh enrichment. Use when reviewing a PR that touches a lockfile, comparing two branches' dependencies, or gating dependency changes in CI.","mlab-sh\u002Fmlab-claude","mlab-sh","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F197380970?v=4","01M7D45Z8NKEZYYHGF1F1HFZ00","Mlab.sh","01M7D45Z9FXN34R73J4E5D9F63",1,"MIT","https:\u002F\u002Fgithub.com\u002Fmlab-sh\u002Fmlab-claude\u002Fblob\u002Fmain\u002Fplugins\u002Fmlab\u002Fskills\u002Fdep-diff-review\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: dep-diff-review\ndescription: Review what a change or pull request introduces into the dependency tree - new packages, version bumps, typosquats, install scripts, vulnerabilities - using postmortem diff plus mlab.sh enrichment. Use when reviewing a PR that touches a lockfile, comparing two branches' dependencies, or gating dependency changes in CI.\n---\n\n# Dependency Diff Review\n\n> CLI details and preflight: `${CLAUDE_PLUGIN_ROOT}\u002Fdocs\u002Fpostmortem-reference.md`. mlab output shapes: `${CLAUDE_PLUGIN_ROOT}\u002Fdocs\u002Ftool-reference.md`.\n\nThe question is never \"is this project healthy\" but \"what does THIS CHANGE introduce\". Cost scales with the diff, so `--online --vulns` are cheap here - use them.\n\n## Workflow\n\n### 1. Preflight and target\n\n`postmortem --version`. Then one of:\n- GitHub PR: `postmortem diff https:\u002F\u002Fgithub.com\u002F\u003Cowner>\u002F\u003Crepo>\u002Fpull\u002F\u003Cn> --online --vulns --json -o -` (both sides come from the PR)\n- Two local states: `postmortem diff \u003Cold-dir> \u003Cnew-dir> --online --vulns --json -o -` (e.g. two worktrees\u002Fcheckouts)\n- Production focus: add `--omit dev` when the review only gates what ships.\n\n### 2. Read the diff\n\nThree buckets: added, removed, version-changed. For each ADDED or version-changed package, the online pass already carries reputation and provenance. Escalate on:\n- brand-new or recently transferred packages (`postmortem timeline \u003Cpkg>` for npm: handovers, install-script appearance)\n- packages that gain an install script in this change (`postmortem scripts \u003Cnew-dir>` and compare)\n- names one edit away from popular packages (typosquat suspicion)\n- vulnerabilities the change INTRODUCES (ignore pre-existing ones here; they belong to sbom-audit)\n\n### 3. Enrich what deserves it\n\nSuspicious added package → `postmortem why \u003Cpkg> \u003Cnew-dir> --blast` for what a compromise would reach. Registry\u002Fhomepage domains that look off → mlab domain\u002FURL scans. Introduced CVEs → KEV\u002FEPSS triage from the results, `actors_by_cve` on anything KEV.\n\n### 4. Verdict for the review\n\n```\n## Dep review: \u003CPR\u002Fchange> - \u003Capprove | approve with comments | block>\n\n| Package | Change | Risk | Why |\n|---|---|---|---|\n\n### Blocking\n\u003Cfindings that must be resolved, each with the evidence>\n\n### Non-blocking\n\u003Cworth a comment>\n\nIntroduced vulns: \u003Cn> (\u003Cworst>) | New install scripts: \u003Cn> | New maintainers reached: \u003Cn>\n```\n\nFor CI use, point the user at `postmortem scan --sarif` (GitHub Code Scanning) and `postmortem ci` for pipeline templates; a review skill run is the interactive complement, not the gate itself.\n\n## Rules\n\n- Judge the delta, not the repo: pre-existing debt is out of scope and saying so keeps reviews fast.\n- \"block\" needs evidence tied to the change; suspicion without evidence is a comment, not a block.\n- Never install or execute the changed dependencies to inspect them.\n","# Dependency Diff Review\n\n> CLI details and preflight: `${CLAUDE_PLUGIN_ROOT}\u002Fdocs\u002Fpostmortem-reference.md`. mlab output shapes: `${CLAUDE_PLUGIN_ROOT}\u002Fdocs\u002Ftool-reference.md`.\n\nThe question is never \"is this project healthy\" but \"what does THIS CHANGE introduce\". Cost scales with the diff, so `--online --vulns` are cheap here - use them.\n\n## Workflow\n\n### 1. Preflight and target\n\n`postmortem --version`. Then one of:\n- GitHub PR: `postmortem diff https:\u002F\u002Fgithub.com\u002F\u003Cowner>\u002F\u003Crepo>\u002Fpull\u002F\u003Cn> --online --vulns --json -o -` (both sides come from the PR)\n- Two local states: `postmortem diff \u003Cold-dir> \u003Cnew-dir> --online --vulns --json -o -` (e.g. two worktrees\u002Fcheckouts)\n- Production focus: add `--omit dev` when the review only gates what ships.\n\n### 2. Read the diff\n\nThree buckets: added, removed, version-changed. For each ADDED or version-changed package, the online pass already carries reputation and provenance. Escalate on:\n- brand-new or recently transferred packages (`postmortem timeline \u003Cpkg>` for npm: handovers, install-script appearance)\n- packages that gain an install script in this change (`postmortem scripts \u003Cnew-dir>` and compare)\n- names one edit away from popular packages (typosquat suspicion)\n- vulnerabilities the change INTRODUCES (ignore pre-existing ones here; they belong to sbom-audit)\n\n### 3. Enrich what deserves it\n\nSuspicious added package → `postmortem why \u003Cpkg> \u003Cnew-dir> --blast` for what a compromise would reach. Registry\u002Fhomepage domains that look off → mlab domain\u002FURL scans. Introduced CVEs → KEV\u002FEPSS triage from the results, `actors_by_cve` on anything KEV.\n\n### 4. Verdict for the review\n\n```\n## Dep review: \u003CPR\u002Fchange> - \u003Capprove | approve with comments | block>\n\n| Package | Change | Risk | Why |\n|---|---|---|---|\n\n### Blocking\n\u003Cfindings that must be resolved, each with the evidence>\n\n### Non-blocking\n\u003Cworth a comment>\n\nIntroduced vulns: \u003Cn> (\u003Cworst>) | New install scripts: \u003Cn> | New maintainers reached: \u003Cn>\n```\n\nFor CI use, point the user at `postmortem scan --sarif` (GitHub Code Scanning) and `postmortem ci` for pipeline templates; a review skill run is the interactive complement, not the gate itself.\n\n## Rules\n\n- Judge the delta, not the repo: pre-existing debt is out of scope and saying so keeps reviews fast.\n- \"block\" needs evidence tied to the change; suspicion without evidence is a comment, not a block.\n- Never install or execute the changed dependencies to inspect them.\n",{"name":5,"description":7},"main","0678f3559c0b5576fd964874a3debae3f6b5a31c","plugins\u002Fmlab\u002Fskills\u002Fdep-diff-review",0,"https:\u002F\u002Fgithub.com\u002Fmlab-sh\u002Fmlab-claude","https:\u002F\u002Fgithub.com\u002Fmlab-sh","https:\u002F\u002Fmlab.sh","MLAB is a modular security analysis platform for IOC analysis at scale","2026-10-22 03:39:43",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add mlab-sh\u002Fmlab-claude --skill dep-diff-review",{"tool":39,"command":40},"bunx","bunx skills add mlab-sh\u002Fmlab-claude --skill dep-diff-review",{"tool":42,"command":43},"pnpm","pnpm dlx skills add mlab-sh\u002Fmlab-claude --skill dep-diff-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmlab-sh\u002Fmlab-claude\u002Fblob\u002Fmain\u002Fplugins\u002Fmlab\u002Fskills\u002Fdep-diff-review\u002FSKILL.md",true,[],[48,55,62,69,76,83],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7D494QGV4DTD8PE8NTDHRM4","threat-watch","Generate a threat landscape digest from mlab.sh - recent critical\u002FKEV CVEs filtered to a declared technology stack, with actor attribution. Use when the user asks what is new in vulnerabilities, wants a daily\u002Fweekly threat brief, asks about recent CVEs for a product, or sets up a recurring watch on their stack.","https:\u002F\u002Fgithub.com\u002Fmlab-sh\u002Fmlab-claude\u002Fblob\u002Fmain\u002Fplugins\u002Fmlab\u002Fskills\u002Fthreat-watch\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M7D48Z3YTQN4ZHMGTH1EXXR5","supply-chain-audit","Full supply-chain audit of a project - postmortem detects malicious code, install hooks and risky dependencies locally, then mlab.sh enriches what it finds (hashes, endpoints, actors, CVEs). Use when the user asks to audit a project's dependencies or supply chain, check a repo for malicious packages, or vet a codebase before adoption or deployment.","https:\u002F\u002Fgithub.com\u002Fmlab-sh\u002Fmlab-claude\u002Fblob\u002Fmain\u002Fplugins\u002Fmlab\u002Fskills\u002Fsupply-chain-audit\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7D48RXRAHKVAE6SWQT2EN6H","smishing-campaign","Analyze a batch of reported SMS\u002Ftext messages through mlab.sh - score each for smishing, cluster them into campaigns, and extract the shared infrastructure (URLs, callback numbers, sender patterns). Use when the user has multiple reported SMS from users\u002Femployees, or investigates an SMS phishing wave. For a single message, phishing-triage does the job.","https:\u002F\u002Fgithub.com\u002Fmlab-sh\u002Fmlab-claude\u002Fblob\u002Fmain\u002Fplugins\u002Fmlab\u002Fskills\u002Fsmishing-campaign\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7D48KBNYFBJNS9MEHHWMW80","script-triage","Statically analyze a suspicious shell script through mlab.sh - install.sh, cron payloads, CI steps, curl-pipe-sh one-liners. Flags dangerous constructs (download-piped-to-shell, base64 decoding, reverse shells, persistence, anti-forensics, destructive deletes), extracts every IOC and enriches them. Use when the user pastes shell code and asks if it is safe\u002Fmalicious, or provides a .sh file to vet before running it.","https:\u002F\u002Fgithub.com\u002Fmlab-sh\u002Fmlab-claude\u002Fblob\u002Fmain\u002Fplugins\u002Fmlab\u002Fskills\u002Fscript-triage\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7D48E9ZYDPAN85NXAED50E6","sbom-export","Generate a CycloneDX SBOM locally with postmortem and push it through mlab.sh vulnerability scanning - for projects or container images where no single lockfile can be pasted. Use when the user asks for an SBOM, needs vuln scanning of a container image or a multi-ecosystem repo, or when sbom-audit lacks a usable lockfile.","https:\u002F\u002Fgithub.com\u002Fmlab-sh\u002Fmlab-claude\u002Fblob\u002Fmain\u002Fplugins\u002Fmlab\u002Fskills\u002Fsbom-export\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7D487A4AZ6KK5CV214QG013","sbom-audit","Audit a dependency lockfile or SBOM for known vulnerabilities via mlab.sh, prioritize findings by KEV status and EPSS, and attribute actively exploited CVEs to threat actors. Use when the user provides a lockfile (package-lock.json, yarn.lock, pnpm-lock.yaml, Cargo.lock, requirements.txt, poetry.lock, uv.lock, Pipfile.lock, go.sum, composer.lock, Gemfile.lock, pom.xml, gradle.lockfile, packages.lock.json, pubspec.lock, mix.lock) or a CycloneDX \u002F SPDX SBOM, or asks to check dependencies for vulnerabilities.","https:\u002F\u002Fgithub.com\u002Fmlab-sh\u002Fmlab-claude\u002Fblob\u002Fmain\u002Fplugins\u002Fmlab\u002Fskills\u002Fsbom-audit\u002FSKILL.md",[],[]]