Skip to content
Development
Skill

/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 plugin
socket
7200 skills5 MCP
Install
$ npx -y skills add gaelic-ghost/socket --skill check-artifact-reputation --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/check-artifact-reputation

Context preview

The summary Claude sees to decide when to auto-load this skill.

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.

SKILL.md

check-artifact-reputation.SKILL.md
name: check-artifact-reputation
description: 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.

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](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.

Read more
Ships withsocket

Stuff for Agents on macOS Promo audio: Socket Codex Marketplace Promo

Get the whole plugin

Other skills on socket.