Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Sardis Identity
v1.0.0Agent identity management with TAP protocol verification and reputation tracking
⭐ 0· 281·1 current·1 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
Name, description, and runtime instructions consistently target Sardis's identity/reputation API and require an API key. Declared binaries (curl, jq) are appropriate for the provided examples. However, the SKILL.md metadata advertises an npm package install (@sardis/sdk) despite the registry listing this as an instruction-only skill with no install spec — this mismatch should be resolved.
Instruction Scope
Runtime instructions include generating keypairs with openssl and reading/writing key files and using the SARDIS_API_KEY to register agents and submit reputation. Those actions are within the skill's stated purpose, but the instructions call the openssl CLI while the registry's required binaries list does not include openssl — an undeclared dependency. The skill also emphasizes payment-capable capabilities (e.g., 'payments', 'wallet_id'), so the SARDIS_API_KEY may grant high privileges; that risk is not documented in detail.
Install Mechanism
The top-level registry says 'No install spec' and no code files exist, but SKILL.md metadata includes an npm install:@sardis/sdk entry. That is an inconsistency: if the agent or installer follows SKILL.md metadata it could install a public npm package (moderate risk). If the platform ignores it, no install happens. Confirm which behavior applies and audit the @sardis/sdk package before allowing installation.
Credentials
Only one environment variable is required: SARDIS_API_KEY, which fits the purpose. However, the skill warns that identities may be 'tied to payment capabilities' — the single API key could therefore be high-privilege. The skill does not request unrelated secrets, but you should verify the API key's scope and rotate/limit permissions if possible.
Persistence & Privilege
The skill is not always-enabled and does not request system config paths or other skills' credentials. disable-model-invocation is false (normal). No evidence it modifies other skills or persists beyond its own use.
What to consider before installing
This skill appears to do what it says (manage agent identities via Sardis) but has two things to check before installing: (1) SKILL.md mentions installing @sardis/sdk via npm while the registry says 'no install spec' — confirm whether your platform will actually install that package, and if so, review the package on npm (publisher, versions, source) before proceeding. (2) The examples use openssl to create keys, but openssl is not listed in the required binaries — ensure openssl availability and understand where private keys will be stored. Treat SARDIS_API_KEY as sensitive (it may enable payment or wallet actions); prefer a least-privilege API key and confirm the key's scope and revocation procedures. If you rely on this skill in production, validate the sardis.sh service identity (homepage and package source) and consider testing in an isolated environment first.Like a lobster shell, security has layers — review code before you run it.
latestvk973heg62hqwjvjxcxydrdbm0x82hqn2
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🆔 Clawdis
Binscurl, jq
EnvSARDIS_API_KEY
Primary envSARDIS_API_KEY