[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ETAXM5JDVMK6R1T549AFKZ":3,"skill-same:01M7ETAXM5JDVMK6R1T549AFKZ":59},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7ETAXM5JDVMK6R1T549AFKZ","supply-chain-risk-auditor",null,"Audits a project's dependencies for supply-chain risk: version-matched advisories for direct dependencies and the full lockfile tree, abandoned or archived upstreams, npm publisher concentration, and install-time script execution. Use when asked to audit dependencies, assess supply-chain or third-party package risk, or review a dependency tree before an engagement.","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fsupply-chain-risk-auditor-trailofbits__skills\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: supply-chain-risk-auditor\ndescription: \"Audits a project's dependencies for supply-chain risk: version-matched advisories for direct dependencies and the full lockfile tree, abandoned or archived upstreams, npm publisher concentration, and install-time script execution. Use when asked to audit dependencies, assess supply-chain or third-party package risk, or review a dependency tree before an engagement.\"\nallowed-tools: Read Write Bash Glob Grep\n---\n\n# Supply Chain Risk Auditor\n\nGenerates a supply-chain risk report for a project's direct dependencies (npm, PyPI,\nGo), plus an advisory sweep of everything its lockfile resolves. Two deterministic\nscripts do the measuring; your job is the judgment they refuse to automate.\n\n## Why the scripts do the measuring, not you\n\nEvery figure in this report is a claim about somebody else's project, and hand-collected\nfigures were measured wrong before this skill was rebuilt around scripts: GitHub\ncontributor counts said five-plus people maintain `lodash` where npm's ACL says one, and\n`gh` saw zero downloads for a package that moves 164 million a week. Do not estimate\nmaintainer counts, downloads, staleness, or CVE history from `gh`, web search, or\nmemory — run the collector, and quote what it measured.\n\nThe scripts enforce two rules worth knowing before you read their output:\n\n- **Unavailable data is never evidence of risk.** Every criterion resolves to\n  assessed-clean, assessed-flagged, or unassessable-with-a-reason.\n- **An absent measurement is never a clean verdict.** A run that measured nothing exits\n  non-zero instead of printing a report that finds nothing.\n\n## Workflow\n\n1. Confirm the target directory has manifests: `package.json`, `pyproject.toml`,\n   `requirements*.txt`, or `go.mod`. If none exist, say so and stop — do not audit an\n   ecosystem this collector does not parse by hand. Lockfiles read for exact versions\n   and the transitive sweep: `package-lock.json`\u002F`npm-shrinkwrap.json`, `uv.lock`, and\n   a go 1.17+ `go.mod`. `yarn.lock`, `pnpm-lock.yaml`, and `poetry.lock` are not read —\n   the report says so when they are present, and versions fall back to pins or the\n   latest release.\n2. Check `gh auth status`. Unauthenticated GitHub allows 60 requests\u002Fhour against 5,000,\n   and the collector makes several per dependency; expect repository criteria to come\n   back unassessable without it. Say so rather than fixing it silently.\n3. Collect, then render. Put outputs somewhere outside the audited repository unless\n   asked otherwise:\n\n   ```sh\n   uv run {baseDir}\u002Fscripts\u002Fcollect.py \u003Cproject-dir> --json \u003Cout-dir>\u002Ffindings.json\n   uv run {baseDir}\u002Fscripts\u002Frender.py \u003Cout-dir>\u002Ffindings.json --out \u003Cout-dir>\u002Freport.md\n   ```\n\n   Expect a few minutes for ~50 dependencies — several HTTP requests per dependency,\n   more with many Go modules, and slower without authenticated `gh`. If `collect.py`\n   exits non-zero, it is refusing to report — relay its message verbatim instead of\n   retrying or working around it.\n4. Read `report.md` and `findings.json`. The report is the deliverable; the JSON carries\n   the datum behind every verdict when you need to cite one.\n5. Add what the collector cannot, clearly separated from what it measured:\n   - A short narrative for this reader: what to act on first, and why.\n   - Upgrade paths for advisory findings — check whether the fix is a patch or a major\n     version away.\n   - Replacement candidates for abandoned or archived dependencies. Verify a candidate\n     exists in the registry before naming it, and label these as judgment, not\n     measurement.\n   - For flagged install scripts: whether `npm ci --ignore-scripts` is viable for this\n     project's build.\n\n## Style for what you add\n\nWrite added prose the way a security report reads, and apply the same register to the\nreport addendum and the final reply alike — replies get pasted into tickets and reports\nverbatim. State the finding, the datum behind it, and the action.\n\n- Impersonal and declarative: no first or second person (\"I ran the collector\", \"you\n  should upgrade\"), no contractions, no exclamation points.\n- Active voice, with the subject matter as the actor: \"upgrading to 1.19.0 clears all\n  25 advisories\", not \"it is recommended that axios be upgraded\".\n- Objective: no intensifiers or subjective framing (\"very\", \"significant\",\n  \"fortunately\"), and no guesses about why the project chose what it chose.\n- Tense: past for what the audit did, present for the state of the dependencies,\n  future for the consequences of acting or not.\n- Constructive: a recommendation names the action and its cost, never a culprit.\n\nIf the `report-writing:writing-style` skill is available in the session, follow it —\nit is the full version of this register.\n\nThe rendered report carries facts only. The interpretive rules below are instructions\nto you, not content for the reader — do not copy them into the deliverable as caveats\nor framing.\n\n## Reading the report\n\n- **Unassessable is not risk.** PyPI publishes no maintainer ACL and Go has no registry;\n  those rows say what could not be known, not what is wrong.\n- **The coverage table bounds every claim.** \"No advisories\" means \"none among what was\n  assessed\" — check the assessed count before repeating a clean verdict.\n- **Quote figures verbatim.** Do not re-derive, round, or embellish the report's\n  numbers; every one is reproducible from the artifact.\n- **Absence from the findings is not endorsement.** A dependency with no findings was\n  measured against these criteria only.\n\n## Rationalizations to reject\n\n- \"`gh` can give me maintainer counts faster than the collector.\" Measured wrong — repo\n  contributors and registry publish rights are different populations.\n- \"No findings, so the dependencies are safe.\" Read the coverage table; on PyPI and Go,\n  half the criteria are structurally unassessable.\n- \"The unassessable rows would just confuse the reader; I'll drop them.\" They are the\n  boundary of every claim in the report. Dropping them turns partial coverage into a\n  clean bill of health, which is the failure this skill was rebuilt to prevent.\n- \"The version is probably close enough.\" A range checked at latest-release and a\n  lockfile-resolved version are different claims; the report labels which one it makes.\n  Keep the label.\n\n## When not to use\n\n- License compliance auditing.\n- Scanning the target's own source for vulnerabilities or secrets — this skill never\n  reads dependency source, only registry, advisory, and repository metadata.\n- Judging whether the project installs or builds. The audit is designed to work from\n  nothing more than the dependency list — manifests and lockfiles — and never installs,\n  builds, or executes anything. Broken installs and import-time breakage are out of\n  scope, and worth saying so if the user seems to expect them.\n- Ecosystems other than npm, PyPI, and Go; say the ecosystem is unsupported rather than\n  improvising an audit for it.\n","# Supply Chain Risk Auditor\n\nGenerates a supply-chain risk report for a project's direct dependencies (npm, PyPI,\nGo), plus an advisory sweep of everything its lockfile resolves. Two deterministic\nscripts do the measuring; your job is the judgment they refuse to automate.\n\n## Why the scripts do the measuring, not you\n\nEvery figure in this report is a claim about somebody else's project, and hand-collected\nfigures were measured wrong before this skill was rebuilt around scripts: GitHub\ncontributor counts said five-plus people maintain `lodash` where npm's ACL says one, and\n`gh` saw zero downloads for a package that moves 164 million a week. Do not estimate\nmaintainer counts, downloads, staleness, or CVE history from `gh`, web search, or\nmemory — run the collector, and quote what it measured.\n\nThe scripts enforce two rules worth knowing before you read their output:\n\n- **Unavailable data is never evidence of risk.** Every criterion resolves to\n  assessed-clean, assessed-flagged, or unassessable-with-a-reason.\n- **An absent measurement is never a clean verdict.** A run that measured nothing exits\n  non-zero instead of printing a report that finds nothing.\n\n## Workflow\n\n1. Confirm the target directory has manifests: `package.json`, `pyproject.toml`,\n   `requirements*.txt`, or `go.mod`. If none exist, say so and stop — do not audit an\n   ecosystem this collector does not parse by hand. Lockfiles read for exact versions\n   and the transitive sweep: `package-lock.json`\u002F`npm-shrinkwrap.json`, `uv.lock`, and\n   a go 1.17+ `go.mod`. `yarn.lock`, `pnpm-lock.yaml`, and `poetry.lock` are not read —\n   the report says so when they are present, and versions fall back to pins or the\n   latest release.\n2. Check `gh auth status`. Unauthenticated GitHub allows 60 requests\u002Fhour against 5,000,\n   and the collector makes several per dependency; expect repository criteria to come\n   back unassessable without it. Say so rather than fixing it silently.\n3. Collect, then render. Put outputs somewhere outside the audited repository unless\n   asked otherwise:\n\n   ```sh\n   uv run {baseDir}\u002Fscripts\u002Fcollect.py \u003Cproject-dir> --json \u003Cout-dir>\u002Ffindings.json\n   uv run {baseDir}\u002Fscripts\u002Frender.py \u003Cout-dir>\u002Ffindings.json --out \u003Cout-dir>\u002Freport.md\n   ```\n\n   Expect a few minutes for ~50 dependencies — several HTTP requests per dependency,\n   more with many Go modules, and slower without authenticated `gh`. If `collect.py`\n   exits non-zero, it is refusing to report — relay its message verbatim instead of\n   retrying or working around it.\n4. Read `report.md` and `findings.json`. The report is the deliverable; the JSON carries\n   the datum behind every verdict when you need to cite one.\n5. Add what the collector cannot, clearly separated from what it measured:\n   - A short narrative for this reader: what to act on first, and why.\n   - Upgrade paths for advisory findings — check whether the fix is a patch or a major\n     version away.\n   - Replacement candidates for abandoned or archived dependencies. Verify a candidate\n     exists in the registry before naming it, and label these as judgment, not\n     measurement.\n   - For flagged install scripts: whether `npm ci --ignore-scripts` is viable for this\n     project's build.\n\n## Style for what you add\n\nWrite added prose the way a security report reads, and apply the same register to the\nreport addendum and the final reply alike — replies get pasted into tickets and reports\nverbatim. State the finding, the datum behind it, and the action.\n\n- Impersonal and declarative: no first or second person (\"I ran the collector\", \"you\n  should upgrade\"), no contractions, no exclamation points.\n- Active voice, with the subject matter as the actor: \"upgrading to 1.19.0 clears all\n  25 advisories\", not \"it is recommended that axios be upgraded\".\n- Objective: no intensifiers or subjective framing (\"very\", \"significant\",\n  \"fortunately\"), and no guesses about why the project chose what it chose.\n- Tense: past for what the audit did, present for the state of the dependencies,\n  future for the consequences of acting or not.\n- Constructive: a recommendation names the action and its cost, never a culprit.\n\nIf the `report-writing:writing-style` skill is available in the session, follow it —\nit is the full version of this register.\n\nThe rendered report carries facts only. The interpretive rules below are instructions\nto you, not content for the reader — do not copy them into the deliverable as caveats\nor framing.\n\n## Reading the report\n\n- **Unassessable is not risk.** PyPI publishes no maintainer ACL and Go has no registry;\n  those rows say what could not be known, not what is wrong.\n- **The coverage table bounds every claim.** \"No advisories\" means \"none among what was\n  assessed\" — check the assessed count before repeating a clean verdict.\n- **Quote figures verbatim.** Do not re-derive, round, or embellish the report's\n  numbers; every one is reproducible from the artifact.\n- **Absence from the findings is not endorsement.** A dependency with no findings was\n  measured against these criteria only.\n\n## Rationalizations to reject\n\n- \"`gh` can give me maintainer counts faster than the collector.\" Measured wrong — repo\n  contributors and registry publish rights are different populations.\n- \"No findings, so the dependencies are safe.\" Read the coverage table; on PyPI and Go,\n  half the criteria are structurally unassessable.\n- \"The unassessable rows would just confuse the reader; I'll drop them.\" They are the\n  boundary of every claim in the report. Dropping them turns partial coverage into a\n  clean bill of health, which is the failure this skill was rebuilt to prevent.\n- \"The version is probably close enough.\" A range checked at latest-release and a\n  lockfile-resolved version are different claims; the report labels which one it makes.\n  Keep the label.\n\n## When not to use\n\n- License compliance auditing.\n- Scanning the target's own source for vulnerabilities or secrets — this skill never\n  reads dependency source, only registry, advisory, and repository metadata.\n- Judging whether the project installs or builds. The audit is designed to work from\n  nothing more than the dependency list — manifests and lockfiles — and never installs,\n  builds, or executes anything. Broken installs and import-time breakage are out of\n  scope, and worth saying so if the user seems to expect them.\n- Ecosystems other than npm, PyPI, and Go; say the ecosystem is unsupported rather than\n  improvising an audit for it.\n",{"name":5,"description":7,"allowed-tools":24},"Read Write Bash Glob Grep","main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","04-安全渗透\u002Fsupply-chain-risk-auditor-trailofbits__skills",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill supply-chain-risk-auditor",{"tool":39,"command":40},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill supply-chain-risk-auditor",{"tool":42,"command":43},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill supply-chain-risk-auditor","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fsupply-chain-risk-auditor-trailofbits__skills\u002FSKILL.md",true,[47,53],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"agents\u002Fopenai.yaml","REFERENCE","参考文档",252,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fsupply-chain-risk-auditor-trailofbits__skills\u002Fagents\u002Fopenai.yaml",{"path":54,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":57,"sourceHtmlUrl":58},"scripts\u002Fpyproject.toml","SCRIPT","脚本",683,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fsupply-chain-risk-auditor-trailofbits__skills\u002Fscripts\u002Fpyproject.toml",[60,68,73,80,87,94],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":67},"01M7FFG485KY83TD6HSC4YPCMC","obsidian-clipper-template-creator","Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator\u002FSKILL.md",[],[],"2026-11-16 10:05:34",{"skillNo":69,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":67},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":67},"01M7FFFY0QEM14SKWPDYGMXM2P","python-api","Programmatic Object-Detection-Metrics API guidance for BoundingBox, BoundingBoxes, Evaluator, enums, coordinate conversion, AP\u002FmAP semantics, and source-style import diagnostics.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Fpython-api\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":67},"01M7FFFVZQZ2GJ0C0TGP7JHD20","file-evaluation","Folder-based PASCAL VOC AP\u002FmAP evaluation from ground-truth and detection text files.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Ffile-evaluation\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":67},"01M7FFFSFNYSE77SJ6PE1CK2DA","object-detection-metrics","Guides legacy Object-Detection-Metrics PASCAL VOC AP\u002FmAP evaluation from detection text folders and direct Python API classes.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":67},"01M7FFFP0GCK1RVXBCPQ8APBMT","nx-workspace-patterns","Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fnx-workspace-patterns\u002FSKILL.md",[],[]]