[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7D9FAM5HZ2PN83TYJVV5ZPN":3,"skill-same:01M7D9FAM5HZ2PN83TYJVV5ZPN":53},{"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},"01M7D9FAM5HZ2PN83TYJVV5ZPN","dependency-vetting",null,"Verify a package or tool is authentic before installing, adding, upgrading, or recommending it. Use whenever a task would add a dependency to a project, suggest a CLI tool, or pull a package from npm, PyPI, crates.io, Go modules, RubyGems, Homebrew, or any other registry. Also use when a registry page, install command, or installed artifact looks inconsistent with the project that supposedly publishes it.","svyatov\u002Fsupermatt","svyatov","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F310043?v=4","01M7D9EFJRGYJSP1A1AYF25H9D","Leonid Svyatov","01M7D9EFKC246EDMASMKXGSCQ7",27,"MIT","https:\u002F\u002Fgithub.com\u002Fsvyatov\u002Fsupermatt\u002Fblob\u002Fmain\u002Fskills\u002Fdependency-vetting\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: dependency-vetting\ndescription: Verify a package or tool is authentic before installing, adding, upgrading, or recommending it. Use whenever a task would add a dependency to a project, suggest a CLI tool, or pull a package from npm, PyPI, crates.io, Go modules, RubyGems, Homebrew, or any other registry. Also use when a registry page, install command, or installed artifact looks inconsistent with the project that supposedly publishes it.\nlicense: MIT\n---\n\n# Dependency vetting\n\nThe rule: never install, add, or recommend a package until you have opened the upstream project's own repo or docs and used the install command or import path published there. The sections below are the full reasoning behind it.\n\n## Direction of trust\n\nFollow the link **from the upstream project to the install command**. Never work the other direction, from a search result or a registry page back to a project.\n\nTreat unverified registry metadata as publisher-supplied claims: author, email, homepage, repository link, README, and license. Where the registry independently verifies a field or attestation, check what that verification establishes and compare the verified identity with the intended upstream project. Still open the upstream repository or docs and confirm the published installation instructions.\n\nIf upstream documents no registry install, then there is no registry package, whatever the registry shows. Stop and say so. Do not install it, do not pin around it, and do not quietly swap in an alternative. Pinning untrusted code to a SHA is the same code with better bookkeeping, not a fix.\n\n## Registry signals worth using\n\nUse the registry's own independent signal where one exists:\n\n| Registry | Signal |\n|----------|--------|\n| npm | `npm audit signatures` |\n| PyPI | \"Verified details\" plus PEP 740 attestations |\n| GitHub release binaries | `gh attestation verify` |\n| crates.io, Go modules, most others | checksum only, so the upstream link carries all the weight |\n\nDownload counts, stars, and search ranking are not evidence of authenticity.\n\n## Stop signals\n\nAny mismatch between the installed artifact and upstream docs is a stop signal: a different executable name, version, file set, or dependency list. Confirm with the user. Never record it as a quirk and move on.\n\n## Keep it proportionate\n\nA tool a project genuinely publishes passes these checks in seconds, so this costs nothing in the normal case and fires only when something is actually wrong. Do not turn it into pin-everything ceremony.\n\nSeparately: do not add or suggest outdated dependencies. Check the current release before pinning a version.\n","# Dependency vetting\n\nThe rule: never install, add, or recommend a package until you have opened the upstream project's own repo or docs and used the install command or import path published there. The sections below are the full reasoning behind it.\n\n## Direction of trust\n\nFollow the link **from the upstream project to the install command**. Never work the other direction, from a search result or a registry page back to a project.\n\nTreat unverified registry metadata as publisher-supplied claims: author, email, homepage, repository link, README, and license. Where the registry independently verifies a field or attestation, check what that verification establishes and compare the verified identity with the intended upstream project. Still open the upstream repository or docs and confirm the published installation instructions.\n\nIf upstream documents no registry install, then there is no registry package, whatever the registry shows. Stop and say so. Do not install it, do not pin around it, and do not quietly swap in an alternative. Pinning untrusted code to a SHA is the same code with better bookkeeping, not a fix.\n\n## Registry signals worth using\n\nUse the registry's own independent signal where one exists:\n\n| Registry | Signal |\n|----------|--------|\n| npm | `npm audit signatures` |\n| PyPI | \"Verified details\" plus PEP 740 attestations |\n| GitHub release binaries | `gh attestation verify` |\n| crates.io, Go modules, most others | checksum only, so the upstream link carries all the weight |\n\nDownload counts, stars, and search ranking are not evidence of authenticity.\n\n## Stop signals\n\nAny mismatch between the installed artifact and upstream docs is a stop signal: a different executable name, version, file set, or dependency list. Confirm with the user. Never record it as a quirk and move on.\n\n## Keep it proportionate\n\nA tool a project genuinely publishes passes these checks in seconds, so this costs nothing in the normal case and fires only when something is actually wrong. Do not turn it into pin-everything ceremony.\n\nSeparately: do not add or suggest outdated dependencies. Check the current release before pinning a version.\n",{"name":5,"license":15,"description":7},"main","58dabace448725e473477545bead7633bd496274","skills\u002Fdependency-vetting",9,"https:\u002F\u002Fgithub.com\u002Fsvyatov\u002Fsupermatt","https:\u002F\u002Fgithub.com\u002Fsvyatov","https:\u002F\u002Fsvyatov.com","Design, build, and ship end-to-end features - backend, frontend, infra - with agentic AI in the loop. Open-source maintainer and contributor.","2026-11-11 17:34:49",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add svyatov\u002Fsupermatt --skill dependency-vetting",{"tool":39,"command":40},"bunx","bunx skills add svyatov\u002Fsupermatt --skill dependency-vetting",{"tool":42,"command":43},"pnpm","pnpm dlx skills add svyatov\u002Fsupermatt --skill dependency-vetting","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsvyatov\u002Fsupermatt\u002Fblob\u002Fmain\u002Fskills\u002Fdependency-vetting\u002FSKILL.md",true,[47],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"agents\u002Fopenai.yaml","REFERENCE","参考文档",129,"https:\u002F\u002Fgithub.com\u002Fsvyatov\u002Fsupermatt\u002Fblob\u002Fmain\u002Fskills\u002Fdependency-vetting\u002Fagents\u002Fopenai.yaml",[54,61,68,75,82,89],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7D9K2XEWAR8C8PE20FQ097V","writing-for-agents","Writing documents for agents. Use when creating or editing skills, modifying AGENTS.md or CLAUDE.md, or writing any doc an agent reaches by a pointer.","https:\u002F\u002Fgithub.com\u002Fsvyatov\u002Fsupermatt\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-for-agents\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7D9K0E95MEVKRY2XZRZC6G9","what-would-you-do","Explain the question you just asked and recommend an answer, with the case for and against each option.","https:\u002F\u002Fgithub.com\u002Fsvyatov\u002Fsupermatt\u002Fblob\u002Fmain\u002Fskills\u002Fwhat-would-you-do\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7D9JXRZ9BMJ8G1MXFZN2GR5","wayfinder","Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.","https:\u002F\u002Fgithub.com\u002Fsvyatov\u002Fsupermatt\u002Fblob\u002Fmain\u002Fskills\u002Fwayfinder\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7D9JW0Y9RJ2HMCE27ST242X","wait-what","Stop. That last message did not land: re-pitch it.","https:\u002F\u002Fgithub.com\u002Fsvyatov\u002Fsupermatt\u002Fblob\u002Fmain\u002Fskills\u002Fwait-what\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7D9JSFKR7FRYAYT8HPJPMXS","triage","Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.","https:\u002F\u002Fgithub.com\u002Fsvyatov\u002Fsupermatt\u002Fblob\u002Fmain\u002Fskills\u002Ftriage\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M7D9JNZZR3YBQ5PKE50A7CS0","to-tickets","Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker (edges as text in one file per ticket locally, or native blocking links on a real tracker).","https:\u002F\u002Fgithub.com\u002Fsvyatov\u002Fsupermatt\u002Fblob\u002Fmain\u002Fskills\u002Fto-tickets\u002FSKILL.md",[],[]]