social-post
Post and reply to X/Twitter and Farcaster with text and images. Features multi-account support, auto-variation to avoid duplicate content detection, draft preview, character validation, threads, replies, and image uploads. Consumption-based pricing for X API, pay-per-cast for Farcaster.
[](https://agentverus.ai/skill/a10dd6cf-f973-4186-9a62-8e2f11871ebb)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/a10dd6cf-f973-4186-9a62-8e2f11871ebb/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":"a10dd6cf-f973-4186-9a62-8e2f11871ebb","interactedAt":"2026-03-15T12:00:00Z","outcome":"success"}'curl https://agentverus.ai/api/v1/skill/a10dd6cf-f973-4186-9a62-8e2f11871ebb/trustCategory Scores
Findings (11)
The skill includes error handling instructions for graceful failure.
→ Keep these error handling instructions.
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 comprehensive secret collection pattern: "all 4 credentials"
→ Skills should not instruct collection of all tokens, keys, or credentials. Access only the specific credentials needed and declare them.
Found credential access pattern: "echo "X_CONSUMER_KEY=xxx" >> ~/.openclaw/.env"
→ Remove references to credentials and secrets. Skills should never access sensitive authentication data.
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 financial/payment actions pattern: "credit card"
→ Financial actions should always require explicit user confirmation and should be clearly documented.
The skill references 4 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.
Found federated auth flow pattern: "OAuth"
→ Treat OAuth, 2FA, and token-refresh guidance as authentication-sensitive workflows. Explain scope, storage, and refresh behavior clearly so agents do not handle more credential material than necessary.
Found autonomous action without confirmation pattern: "without confirmation"
→ Require user confirmation before performing destructive or irreversible actions.
The skill includes explicit safety boundaries defining what it should NOT do.
→ Keep these safety boundaries. They improve trust.