HolySpiritOS
A Christian alignment layer for AI agents.
[](https://agentverus.ai/skill/6c4a78c0-0e61-497d-8023-bfcf5a2e9efd)Community Comments
Public comments are the active feedback surface on skill reports right now. Use them to share implementation notes, edge cases, and operator context.
Sign in to comment on this skill
No comments yet. Be the first to share your thoughts.
Keep this report moving through the activation path: rescan from the submit flow, capture real-world interactions, and wire the trust endpoint into your automation.
https://agentverus.ai/api/v1/skill/6c4a78c0-0e61-497d-8023-bfcf5a2e9efd/trustUse your saved key to act on this report immediately instead of returning to onboarding.
Use these current-skill command blocks to keep this exact report moving through your workflow.
curl -X POST https://agentverus.ai/api/v1/interactions \
-H "Authorization: Bearer at_your_api_key" \
-H "Content-Type: application/json" \
-d '{"agentPlatform":"openclaw","skillId":"6c4a78c0-0e61-497d-8023-bfcf5a2e9efd","interactedAt":"2026-03-15T12:00:00Z","outcome":"success"}'curl https://agentverus.ai/api/v1/skill/6c4a78c0-0e61-497d-8023-bfcf5a2e9efd/trustCategory Scores
Findings (7)
The skill requests the "write_config" permission which is classified as high risk.
→ Consider whether "write_config" is necessary for the skill's stated functionality.
Piping a downloaded script directly to a shell interpreter. This executes remote code without verification — a classic supply chain attack vector.
→ Review the code block starting at line 55. Ensure this pattern is necessary and does not pose a security risk.
The scanner inferred a risky capability from the skill content/metadata, but no matching declaration was found. Add a declaration with a clear justification, or remove the behavior.
→ Declare this capability explicitly in frontmatter permissions with a specific justification, or remove the risky behavior.
The skill references a raw content hosting service which is classified as medium risk.
→ Use official package registries instead of raw content URLs. Raw URLs can be changed without notice.
The skill references a well-known installer script in its setup instructions.
→ Consider documenting the exact version or hash of the installer for supply chain verification.
The skill contains a curl-pipe-to-shell pattern in its setup/prerequisites section.
→ Consider pinning the installer to a specific version or hash for supply chain verification.
The skill does not include explicit safety boundaries defining what it should NOT do.
→ Add a 'Safety Boundaries' section listing what the skill must NOT do (e.g., no file deletion, no network access beyond needed APIs).