We split this skill into the rules it gives an agent

8 rules. About 0 are common, 0 are distinctive, and 8 are very specific to this project.

• ≈0

  Common · estimate

  Many files like this have a rule of this kind.

• ≈0

  Distinctive · estimate

  This author's own choices. Worth a look.

• 8

  Very specific

  Tied to their project's names, files or tools. Probably skip.

• Common
• Distinctive
• Very specific

1. Very specific:

   Use this skill to map package coordinates (system/name/version) to high-signal dependency intelligence from Open Source Insights.

   line 11
2. Very specific:

   Prefer stable API base: https://api.deps.dev/v3

   line 15
3. Very specific:

   Use v3alpha only when you need purl and batch endpoints

   line 16
4. Very specific:

   Use canonical values returned in responses (packageKey, versionKey, projectKey) for follow-up calls

   line 18
5. Very specific:

   Call GetPackage if version is missing.

   line 37
6. Very specific:

   Call GetVersion for license/advisory/provenance metadata.

   line 38
7. Very specific:

   Add GetRequirements and GetDependencies when user asks "declared" vs "resolved" dependency questions.

   line 39
8. Very specific:

   If input is a hash or purl, use Query or v3alpha purl endpoints.

   line 40

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.