Authensor Gateway
[](https://agentverus.ai/skill/0deaa080-0c6d-4f61-a957-66e502c0588b)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/0deaa080-0c6d-4f61-a957-66e502c0588b/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":"0deaa080-0c6d-4f61-a957-66e502c0588b","interactedAt":"2026-03-15T12:00:00Z","outcome":"success"}'curl https://agentverus.ai/api/v1/skill/0deaa080-0c6d-4f61-a957-66e502c0588b/trustCategory Scores
Findings (15)
The skill instructs users to download and execute code from a remote URL, a common supply-chain attack vector.
→ Remove curl-pipe-to-shell patterns. Provide dependencies through safe, verifiable channels.
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 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. Related auth/profile context: - related auth/profile capability-contract signals — Capability contract mismatch: inferred network access is not declared
→ 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 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 ~/.ssh/id_rsa"
→ Remove references to credentials and secrets. Skills should never access sensitive authentication data.
Found credential access pattern: "~/.ssh/id_rsa"
→ Remove references to credentials and secrets. Skills should never access sensitive authentication data.
The skill contains a download-and-execute pattern inside a code block. Verify the URL is trustworthy.
→ Pin the installer to a specific version or hash. Consider bundling dependencies instead.
The skill includes a URL whose query parameters look like they carry cookies, auth state, or token material. URLs are commonly logged and replayed, so credential-bearing parameters expand the dependency risk surface even on first-party domains. Related auth/profile context: - overlapping signals from the same local context — Unknown external reference
→ Avoid query-string credential transport. Prefer secure headers, dedicated cookie APIs, or other mechanisms that do not expose bearer material in URLs.
Found package bootstrap execution pattern: "npm install"
→ Surface package bootstrap commands for review. Ephemeral package execution and install-time dependency pulls increase supply-chain risk, especially when versions are not pinned or provenance is unclear.
Found state persistence pattern: "write file"
→ If state persistence is needed, document what data is stored and where. Allow users to review stored data.
The skill lacks a meaningful description, making it difficult to assess its purpose.
→ Add a clear, detailed description of what the skill does and what it needs access to.
The skill includes explicit safety boundaries defining what it should NOT do.
→ Keep these safety boundaries. They improve trust.