Didit Proof Of Address
Analysis
The skill appears purpose-aligned for Didit proof-of-address checks, but users should know it uploads sensitive address documents to Didit using their API key.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.
Source: unknown
The registry does not identify a source repository or verified publisher, which matters because the skill handles API credentials and sensitive identity/address documents.
Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.
api_key = os.environ.get("DIDIT_API_KEY") ... headers={"x-api-key": api_key}The script uses the user's Didit API key to authenticate requests to the proof-of-address API, which is expected for this integration but still grants account/API usage authority.
Checks for exposed credentials, poisoned memory or context, unclear communication boundaries, or sensitive data that could leave the user's control.
files = {"document": (os.path.basename(document_path), f, mime)} ... requests.post(ENDPOINT, headers={"x-api-key": api_key}, files=files, data=data, timeout=60)The selected proof-of-address document is uploaded to the external Didit verification service; this is central to the skill but involves sensitive personal documents.
