ProofAI

Provide cryptographic proof of AI decisions compliant with EU AI Act Article 12, including certification, logging, verification, and monitoring tools.

This skill sends prompts, AI outputs, and analysis to a third-party ProofAI backend (defaulting to a Supabase functions URL) and anchors evidence on Polygon. Before installing: 1) Verify the project source (review the linked GitHub repository and npm package) to confirm authorship and integrity. 2) Treat PROOFAI_API_KEY and PROOFAI_ANON_KEY as sensitive — do not provide production/secrets until you trust the service; consider a read-only or test key. 3) Avoid sending PII or secrets to the tool without explicit approval from your privacy/compliance team. 4) Confirm the npm package name/version and check its npm publisher and release history. 5) If you need stronger assurance, run the package in an isolated environment, review network calls (to the supabase URL and Polygon), and inspect server responses. The main technical inconsistency to resolve is that the registry metadata declares no required env vars while the code and SKILL.md require service keys — ask the publisher to correct that and to provide provenance (official repo, maintainer identity) before broad deployment.

Type: OpenClaw Skill Name: proofai Version: 1.0.1 The bundle implements an MCP server for 'ProofAI,' a tool designed to provide cryptographic and blockchain-based certification for AI decisions. The code (src/index.ts) functions as a wrapper for a Supabase-hosted API (apzgbajvwzykygrxxrwm.supabase.co), facilitating data compression, execution, analysis, and anchoring to the Polygon blockchain. While the tool sends prompt and response data to an external endpoint and requires API keys, this behavior is explicitly aligned with its stated purpose of AI compliance and auditing. No evidence of malicious exfiltration, unauthorized command execution, or harmful prompt injection was found.