[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BRA862DFY3J98A7T52384W":3,"skill-same:01M7BRA862DFY3J98A7T52384W":52},{"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":6,"updatedAt":31,"install":32,"resources":45},"01M7BRA862DFY3J98A7T52384W","audit-a-dependency-from-its-artifact",null,"Use when a dependency question needs an answer that prose cannot be trusted for: whether anything is behind its latest release, what a version requires of the toolchain, or whether an artifact carries any code at all. Fires on \"is everything up to date\", \"what does AGP 9.4 need\", \"can we drop this -ktx dependency\", and before raising any cap whose comment cites a floor. Owns the guard that makes a measurement worth quoting, which is proving the query is aimed at the right artifact before reading anything off it. Do NOT fire for what a dependency DOES after a bump (that is verify-dependency-behaviour), for applying a bump already decided, or where the registry cannot be reached.","damson\u002Fhard-won-skills","damson","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F804217?v=4","01M7BR01SMVEGA4HRD46VV1SXF","Damien D.","01M7BR01TR37MB9R73C1C0ENGG",1,"MIT","https:\u002F\u002Fgithub.com\u002Fdamson\u002Fhard-won-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fverification\u002Fskills\u002Faudit-a-dependency-from-its-artifact\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: audit-a-dependency-from-its-artifact\ndescription: >\n  Use when a dependency question needs an answer that prose cannot be trusted\n  for: whether anything is behind its latest release, what a version requires of\n  the toolchain, or whether an artifact carries any code at all. Fires on \"is\n  everything up to date\", \"what does AGP 9.4 need\", \"can we drop this -ktx\n  dependency\", and before raising any cap whose comment cites a floor. Owns the\n  guard that makes a measurement worth quoting, which is proving the query is\n  aimed at the right artifact before reading anything off it. Do NOT fire for\n  what a dependency DOES after a bump (that is verify-dependency-behaviour), for\n  applying a bump already decided, or where the registry cannot be reached.\n---\n\n# Audit a dependency from its artifact\n\nRelease notes go stale, changelogs skip minors, and a version table in a comment\nis true on the day it is written. The artifact is not any of those: it is what\nthe build will actually resolve. This skill reads the answer out of the artifact\nand, more importantly, refuses to report a number it cannot show is about the\nright thing.\n\nThe failure it prevents is not a wrong bump. It is a **confident wrong number**:\na measurement is numeric, so it reads as authoritative whatever it measured.\n\n## Procedure\n\n### 1. Ask the registry what exists\n\n```bash\n# every published version, from the repository that serves the artifact\ncurl -sfL \"\u003Crepo>\u002F\u003Cgroup with slashes>\u002F\u003Cartifact>\u002Fmaven-metadata.xml\"\n```\n\nTranslate the group with `tr '.' '\u002F'` or the host language's own replace. Do\n**not** build the path with a shell substitution like `${g\u002F\u002F.\u002F\\\u002F}`: zsh leaves\nthe backslash in, every URL 404s, and it reads as the registry being wrong.\n\n### 2. Prove the query is aimed right, per row\n\nThis is the step the skill exists for. For every artifact, **the version\ncurrently in use must appear in the list that came back**. If it does not, the\ncoordinates are wrong, the repository is wrong, or the artifact moved, and every\nother number from that query is worthless.\n\n**Membership is necessary and not sufficient.** Two different artifacts can\npublish the same version string, so a query aimed at the wrong coordinates can\nstill find the version in use and hand back that other artifact's `latest` as\nthough it were an answer. Check the coordinates themselves against what the build\nresolved, then check membership.\n\n```\nfor each artifact:\n    if queried_coordinates != coordinates the build resolved:\n        report \"unusable: queried \u003Cg:a>, the build resolves \u003Cg:a>\"     # never a result\n    published = versions(coordinates)\n    if current_version not in published:\n        report \"unusable: current \u003Cv> is not in the published list\"   # never a result\n        continue\n    latest = max(stable versions)\n```\n\nA row that fails this is reported as unusable, never folded into the answer and\nnever silently dropped. \"27 verified, 0 unusable\" is the shape of a trustworthy\nreport; \"27 checked\" is not.\n\n### 3. Read a constraint out of the artifact, not out of a note\n\nA tool that enforces a floor carries that floor inside itself:\n\n```bash\nunzip -p \u003Cplugin>.jar | strings          # or unzip -o to a temp dir, then javap\n```\n\nFind the class that does the enforcing and read its constants. This answers the\nquestion for a version nobody has written about yet, which is exactly when a\nrelease note cannot help. Say which class the value came from, so the next\nreader can repeat it rather than trust the quote.\n\nThe same holds for metadata a build tool enforces: an AAR's own metadata entry\nstates the compile level it demands, and that is what the build will read.\n\n### 4. Judge \"does this carry code\" by counting, with the caveat\n\n```bash\nart=$HOME\u002F.gradle\u002Fcaches\u002F...\u002Fthing-1.2.3.aar    # the file you are auditing\n\ncase \"$art\" in\n  *.aar) # an AAR holds its code in an inner classes.jar\n         unzip -p \"$art\" classes.jar > \u002Ftmp\u002Finner.jar\n         unzip -l \u002Ftmp\u002Finner.jar | grep -c '\\.class$' ;;\n  *.jar) # a jar holds it directly, and the AAR command finds nothing here\n         unzip -l \"$art\" | grep -c '\\.class$' ;;\n  *)     echo \"not an archive this step can read: $art\" ;;\nesac\n```\n\nThe two cases are not interchangeable. `unzip -p \u003Cjar> classes.jar` on a plain\njar extracts nothing and the count comes back 0, which is the same answer this\nstep uses to mean \"carries no code\".\n\n**A count of 0 has not answered the question until the comparison is non-zero.**\nWhere the artifact under test and the one you are comparing it against both\nreport 0, the method has failed, not the artifacts: multiplatform publishing puts\nnothing in the top-level artifact and everything in a platform variant. Count the\nvariant, and read the POM, where an umbrella names its variant as a compile\ndependency.\n\nA suffix is never evidence either way. Check each artifact; one that looks like\nan empty alias by its name can carry real classes.\n\n### 5. Report the measurement, not a derived difference\n\nQuote what you measured, with when. A delta between two counts taken at\ndifferent times, or under different tool versions, is a third number nobody\nmeasured, and it is the one that turns out wrong.\n\n## When to STOP\n\n- **The question is what changes after the bump.** Whether the new version still\n  behaves as the code expects is a different job; `verify-dependency-behaviour`\n  owns it, and this skill stops at what the artifact is.\n- **The registry cannot be reached.** Report the answer as unknown. Falling back\n  to release notes is how the stale number gets in, which is what this exists to\n  prevent.\n- **Step 2 fails for most rows.** One unusable row is a coordinate typo; most of\n  them means the wrong repository or a moved group. Fix the query and start\n  again rather than reporting the survivors.\n- **The cap comment gives a reason this cannot see.** A pin that exists because\n  of a bug, a licence or a downstream consumer is not answered by version\n  numbers. Read the comment, and hand the decision back.\n","# Audit a dependency from its artifact\n\nRelease notes go stale, changelogs skip minors, and a version table in a comment\nis true on the day it is written. The artifact is not any of those: it is what\nthe build will actually resolve. This skill reads the answer out of the artifact\nand, more importantly, refuses to report a number it cannot show is about the\nright thing.\n\nThe failure it prevents is not a wrong bump. It is a **confident wrong number**:\na measurement is numeric, so it reads as authoritative whatever it measured.\n\n## Procedure\n\n### 1. Ask the registry what exists\n\n```bash\n# every published version, from the repository that serves the artifact\ncurl -sfL \"\u003Crepo>\u002F\u003Cgroup with slashes>\u002F\u003Cartifact>\u002Fmaven-metadata.xml\"\n```\n\nTranslate the group with `tr '.' '\u002F'` or the host language's own replace. Do\n**not** build the path with a shell substitution like `${g\u002F\u002F.\u002F\\\u002F}`: zsh leaves\nthe backslash in, every URL 404s, and it reads as the registry being wrong.\n\n### 2. Prove the query is aimed right, per row\n\nThis is the step the skill exists for. For every artifact, **the version\ncurrently in use must appear in the list that came back**. If it does not, the\ncoordinates are wrong, the repository is wrong, or the artifact moved, and every\nother number from that query is worthless.\n\n**Membership is necessary and not sufficient.** Two different artifacts can\npublish the same version string, so a query aimed at the wrong coordinates can\nstill find the version in use and hand back that other artifact's `latest` as\nthough it were an answer. Check the coordinates themselves against what the build\nresolved, then check membership.\n\n```\nfor each artifact:\n    if queried_coordinates != coordinates the build resolved:\n        report \"unusable: queried \u003Cg:a>, the build resolves \u003Cg:a>\"     # never a result\n    published = versions(coordinates)\n    if current_version not in published:\n        report \"unusable: current \u003Cv> is not in the published list\"   # never a result\n        continue\n    latest = max(stable versions)\n```\n\nA row that fails this is reported as unusable, never folded into the answer and\nnever silently dropped. \"27 verified, 0 unusable\" is the shape of a trustworthy\nreport; \"27 checked\" is not.\n\n### 3. Read a constraint out of the artifact, not out of a note\n\nA tool that enforces a floor carries that floor inside itself:\n\n```bash\nunzip -p \u003Cplugin>.jar | strings          # or unzip -o to a temp dir, then javap\n```\n\nFind the class that does the enforcing and read its constants. This answers the\nquestion for a version nobody has written about yet, which is exactly when a\nrelease note cannot help. Say which class the value came from, so the next\nreader can repeat it rather than trust the quote.\n\nThe same holds for metadata a build tool enforces: an AAR's own metadata entry\nstates the compile level it demands, and that is what the build will read.\n\n### 4. Judge \"does this carry code\" by counting, with the caveat\n\n```bash\nart=$HOME\u002F.gradle\u002Fcaches\u002F...\u002Fthing-1.2.3.aar    # the file you are auditing\n\ncase \"$art\" in\n  *.aar) # an AAR holds its code in an inner classes.jar\n         unzip -p \"$art\" classes.jar > \u002Ftmp\u002Finner.jar\n         unzip -l \u002Ftmp\u002Finner.jar | grep -c '\\.class$' ;;\n  *.jar) # a jar holds it directly, and the AAR command finds nothing here\n         unzip -l \"$art\" | grep -c '\\.class$' ;;\n  *)     echo \"not an archive this step can read: $art\" ;;\nesac\n```\n\nThe two cases are not interchangeable. `unzip -p \u003Cjar> classes.jar` on a plain\njar extracts nothing and the count comes back 0, which is the same answer this\nstep uses to mean \"carries no code\".\n\n**A count of 0 has not answered the question until the comparison is non-zero.**\nWhere the artifact under test and the one you are comparing it against both\nreport 0, the method has failed, not the artifacts: multiplatform publishing puts\nnothing in the top-level artifact and everything in a platform variant. Count the\nvariant, and read the POM, where an umbrella names its variant as a compile\ndependency.\n\nA suffix is never evidence either way. Check each artifact; one that looks like\nan empty alias by its name can carry real classes.\n\n### 5. Report the measurement, not a derived difference\n\nQuote what you measured, with when. A delta between two counts taken at\ndifferent times, or under different tool versions, is a third number nobody\nmeasured, and it is the one that turns out wrong.\n\n## When to STOP\n\n- **The question is what changes after the bump.** Whether the new version still\n  behaves as the code expects is a different job; `verify-dependency-behaviour`\n  owns it, and this skill stops at what the artifact is.\n- **The registry cannot be reached.** Report the answer as unknown. Falling back\n  to release notes is how the stale number gets in, which is what this exists to\n  prevent.\n- **Step 2 fails for most rows.** One unusable row is a coordinate typo; most of\n  them means the wrong repository or a moved group. Fix the query and start\n  again rather than reporting the survivors.\n- **The cap comment gives a reason this cannot see.** A pin that exists because\n  of a bug, a licence or a downstream consumer is not answered by version\n  numbers. Read the comment, and hand the decision back.\n",{"name":5,"description":7},"main","9435f9fa04b69d2217f8cab3c817dd5c3c1d1021","plugins\u002Fverification\u002Fskills\u002Faudit-a-dependency-from-its-artifact",0,"https:\u002F\u002Fgithub.com\u002Fdamson\u002Fhard-won-skills","https:\u002F\u002Fgithub.com\u002Fdamson","http:\u002F\u002Fgoo.gl\u002F3UwFRt","2026-11-14 14:28:11",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add damson\u002Fhard-won-skills --skill audit-a-dependency-from-its-artifact",{"tool":38,"command":39},"bunx","bunx skills add damson\u002Fhard-won-skills --skill audit-a-dependency-from-its-artifact",{"tool":41,"command":42},"pnpm","pnpm dlx skills add damson\u002Fhard-won-skills --skill audit-a-dependency-from-its-artifact","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdamson\u002Fhard-won-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fverification\u002Fskills\u002Faudit-a-dependency-from-its-artifact\u002FSKILL.md",true,[46],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"README.md","REFERENCE","参考文档",3243,"https:\u002F\u002Fgithub.com\u002Fdamson\u002Fhard-won-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fverification\u002Fskills\u002Faudit-a-dependency-from-its-artifact\u002FREADME.md",[53,60,66,71,76,81],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M7BRCESR9BRFAH87J2ZQY5T2","skill-two","Fixture skill","https:\u002F\u002Fgithub.com\u002Fdamson\u002Fhard-won-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fwrong_welcome_total\u002Fplugins\u002Falpha\u002Fskills\u002Fskill-two\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M7BRCDPHEPZES71BYBRTZ1G3","skill-one","https:\u002F\u002Fgithub.com\u002Fdamson\u002Fhard-won-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fwrong_welcome_total\u002Fplugins\u002Falpha\u002Fskills\u002Fskill-one\u002FSKILL.md",[],[],{"skillNo":67,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7BRCCHHB3Q07BR0QN339D3F","https:\u002F\u002Fgithub.com\u002Fdamson\u002Fhard-won-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fwrong_table_count\u002Fplugins\u002Falpha\u002Fskills\u002Fskill-two\u002FSKILL.md",[],[],{"skillNo":72,"name":62,"nameZh":6,"description":56,"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},"01M7BRC9J97QKZHGKVXMER5ZEE","https:\u002F\u002Fgithub.com\u002Fdamson\u002Fhard-won-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fwrong_table_count\u002Fplugins\u002Falpha\u002Fskills\u002Fskill-one\u002FSKILL.md",[],[],{"skillNo":77,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7BRC8C39NM8VVAQ3TKP0CRS","https:\u002F\u002Fgithub.com\u002Fdamson\u002Fhard-won-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fvalid_marketplace\u002Fplugins\u002Falpha\u002Fskills\u002Fskill-two\u002FSKILL.md",[],[],{"skillNo":82,"name":62,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7BRC75THG394KDGYV35ET19","https:\u002F\u002Fgithub.com\u002Fdamson\u002Fhard-won-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fvalid_marketplace\u002Fplugins\u002Falpha\u002Fskills\u002Fskill-one\u002FSKILL.md",[],[]]