Praesidia
v1.1.1Verify AI agents, check trust scores (0-100), fetch A2A agent cards, discover marketplace agents, apply guardrails for security and compliance. Use when user mentions agent verification, trust scores, agent discovery, A2A protocol, agent identity, agent marketplace, guardrails, security policies, content moderation, or asks "is this agent safe?" or "find agents that can [task]" or "apply guardrails to protect my agent".
⭐ 1· 1.4k·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description (agent verification, trust scores, guardrails, A2A cards) match the actual behavior: SKILL.md exclusively shows web_fetch calls to Praesidia API endpoints and examples for listing/applying guardrails and discovering agents. Requesting a PRAESIDIA_API_KEY is expected for this functionality.
Instruction Scope
Runtime instructions stay within the stated domain (calls to Praesidia API to fetch agent cards, list/apply guardrails, discovery, validation). Minor issues: instructions assume the agent can obtain an orgId from 'user profile or context' but do not specify how to retrieve it, and the README/SKILL.md tell users to add the API key to ~/.openclaw/openclaw.json even though the skill metadata declared no required config paths—this is a documentation mismatch but not malicious.
Install Mechanism
No install spec and no code files — instruction-only skill. This is low-risk from an installation/extraction perspective because nothing is written to disk by the skill itself.
Credentials
Only one required env var (PRAESIDIA_API_KEY) is declared, which is proportionate to API-based verification and guardrail management. However, the key likely grants both read and write actions (the SKILL.md includes POST examples to create guardrails), so the API key is powerful — users should ensure the key's scope is minimal for the intended use (read-only vs full admin) before supplying it.
Persistence & Privilege
always:false and no installs are appropriate. The skill is capable of making state-changing API calls (applying guardrails) which is coherent with its purpose, but because the skill can modify organization-level guardrails, autonomous invocation + an unrestricted API key increases blast radius; this is expected for a management skill but worth caution.
Assessment
This skill appears to do what it says: it calls the Praesidia API to verify agents, list/discover agents, and manage guardrails. Before installing, verify the Praesidia service and the skill source (origin is 'unknown' here). Use an API key with the least privilege necessary (prefer a read-only key for verification/discovery). If you plan to let the skill apply guardrails, ensure the key is scoped to the correct org/team and that audit logging is enabled on your Praesidia account. Confirm how the agent runtime will obtain orgId/context (the SKILL.md assumes this without explicit steps). Do not store broad-purpose admin keys in shared or global config unless you understand the key's scope. If uncertain, test with a limited-scope or staging API key and review Praesidia audit logs for changes the skill makes.Like a lobster shell, security has layers — review code before you run it.
latestvk97b3xp9p1825j1fa1wprzts8180j5xp
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🛡️ Clawdis
EnvPRAESIDIA_API_KEY
Primary envPRAESIDIA_API_KEY