Praesidia

This skill appears to implement a Praesidia integration (it will call praesidia.ai endpoints) and only asks for a PRAESIDIA_API_KEY — that part is reasonable. Before installing, double-check the following: - PRAESIDIA_API_URL mismatch: The documentation uses PRAESIDIA_API_URL (and local dev URLs) but the skill metadata only declares PRAESIDIA_API_KEY. Ensure you set PRAESIDIA_API_URL where required (or confirm the platform supplies a default) to avoid accidental calls to an unexpected endpoint. - API key handling: The skill expects you to store an API key in ~/.openclaw/openclaw.json. Use a least-privilege key if Praesidia supports scoped keys, and avoid exposing long-lived production keys in shared environments. - Data exposure: The skill sends agent IDs, guardrail content, and arbitrary text to Praesidia's API. Review Praesidia's privacy/security policies to ensure sending that data is acceptable for your use case. - orgId ambiguity: The runtime instructions say to obtain orgId from the 'user's profile or context' but do not constrain where to look. Decide and document where orgId should come from (explicit user input, authenticated account profile, or config) to avoid the agent searching unexpected files or contexts for it. - Test in dev first: Use a restricted test API key and the local dev URL option to verify behavior before enabling in production. Monitor the first few requests to confirm that only expected data is transmitted. If you cannot confirm PRAESIDIA's vendor identity or the intended config for orgId/PRAESIDIA_API_URL, treat this skill with caution and ask the skill author or vendor for clarifications and a minimal-scope API key before enabling it.