agentsclimarketplace

Check artifact reputation

Skill gaelic-ghost/socket/skills/check-artifact-reputation

Check reputation for a suspicious artifact, signer, hash, URL, domain, certificate, package, or vendor. Use when threat intelligence informs triage while privacy, stale data, false positives, and behavior limits stay explicit.From its SKILL.md

Install
npx -y skills add gaelic-ghost/socket --skill check-artifact-reputation

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 9 stars9 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.9 KB, as published. Nobody here has run it

Check Artifact Reputation

Overview

Gather provenance and intelligence without treating popularity, valid signing, a clean lookup, or a vendor label as a safety verdict. Prefer local identity and vendor sources before sending data to third parties.

Read references/reputation-evidence.md for source ordering and interpretation.

Workflow

  1. Fix identity.

    • Record artifact hashes, signer/certificate, exact version, source URL, domain, resolved destinations, and acquisition time.
  2. Check local evidence.

    • Inspect quarantine/provenance, signature/notarization, known installation records, local security detections, and expected vendor distribution paths.
  3. Check authoritative sources.

    • Prefer vendor advisories, release checksums/signatures, certificate status, official repositories, and current platform security sources.
    • Date each lookup.
  4. Decide whether external intelligence is appropriate.

    • Explain whether the service receives only a hash/domain or may upload/retain the artifact.
    • Obtain explicit approval before sending private artifacts, URLs, customer data, or unknown binaries.
  5. Correlate results.

    • Record detection names, engines/sources, first/last seen, submission context, prevalence, relations, and conflicting classifications.
    • Distinguish “not present” from “known benign.”
  6. Feed behavior analysis.

    • Use reputation to prioritize static/dynamic checks, not replace them.

Output

Return identity, sources/date, privacy decision, reputation observations, conflicts, interpretation limits, confidence effect, and next behavioral check.

What ships with it: 2 files

1.2 KB alongside SKILL.md

agents/

references/

Gives 0 of the 12 instructions most quality gates skills give

Counted across 1,524 of the 2,830 authors here whose files we hold, read 2026-09-06

  • Read full output and check exit codein 45 of 1524, across 40 files
  • Verify output confirms the claimin 44 of 1524, across 39 files
  • Identify the command that proves the claimin 43 of 1524, across 39 files
  • Execute the full verification commandin 36 of 1524, across 30 files
  • Produce a verification reportin 34 of 1524, across 18 files
  • Review git diff changesin 30 of 1524, across 16 files
  • Fix build failures immediatelyin 29 of 1524, across 9 files
  • Group findings by severityin 28 of 1524
  • State claim only with evidencein 27 of 1524, across 22 files
  • Verify regression tests with red-green cyclein 26 of 1524, across 22 files
  • Run the full test suitein 26 of 1524, across 25 files
  • Run test suite with coveragein 25 of 1524, across 10 files

Said here and by no other author read

  • Record artifact identity details
  • Inspect local provenance and signatures
  • Check authoritative vendor sources
  • Date every lookup performed
  • Obtain approval before sending private data
  • Correlate detection results

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.

Keep looking

Skills are one crate of 611,884. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.