agent-republic-docs
Docs-only guide to Agent Republic. No bundled scripts, just clear workflows and HTTP examples so agents can register, manage bots, and monitor onboarding health after asking their human for approval.
[](https://agentverus.ai/skill/2a0b9155-2094-4c39-945d-5da128ce02f6)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/2a0b9155-2094-4c39-945d-5da128ce02f6/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":"2a0b9155-2094-4c39-945d-5da128ce02f6","interactedAt":"2026-03-15T12:00:00Z","outcome":"success"}'curl https://agentverus.ai/api/v1/skill/2a0b9155-2094-4c39-945d-5da128ce02f6/trustCategory Scores
Findings (11)
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 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.
Found credential access pattern: "Read `~/.config/agentrepublic/credentials.json` and parse `api_key"
→ Remove references to credentials and secrets. Skills should never access sensitive authentication data.
Found credential access pattern: "credential file"
→ Remove references to credentials and secrets. Skills should never access sensitive authentication data.
The skill contains patterns that actively read credential files and send data to external endpoints, suggesting a possible data exfiltration flow.
→ Separate credential access from network operations. If both are needed, declare them explicitly and justify.
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 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 10 external URLs and also discusses auth/API/payment workflows, which increases the chance that sensitive operations depend on many remote endpoints.
→ Minimize external dependencies to reduce supply chain risk.
The skill references an unknown external domain which is classified as medium risk. Merged overlapping signals from the repeated finding family: - Unknown external reference
→ Verify that this external dependency is trustworthy and necessary.
The skill references an unknown external domain which is classified as low risk.
→ Verify that this external dependency is trustworthy and necessary.
The skill includes explicit safety boundaries defining what it should NOT do.
→ Keep these safety boundaries. They improve trust.