XReplyAI - Social Post Manager

AdvisoryAudited by Static analysis on May 12, 2026.

Overview

No suspicious patterns detected.

Findings (0)

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

What this means

If invoked, the agent may create, schedule, or publish content visible to other people and may consume XreplyAI quota.

Why it was flagged

The skill exposes tools that can publish or schedule public social content. This is central to the stated purpose and is disclosed, but it is still a high-impact action for a user's public accounts.

Skill content
Generate, schedule, and publish posts to X, LinkedIn, and Threads in your voice using AI.
Recommendation

Review the final post text, target platform, media, scheduled time, and quota impact before allowing publish or schedule actions.

What this means

Anyone or any agent run with this token could potentially manage posts through the connected XreplyAI account within the token's permissions.

Why it was flagged

The skill requires a credential that lets the MCP tools act through the user's XreplyAI account. That is expected for this service, and the artifacts do not show unrelated token use or leakage.

Skill content
All tools require an `XREPLY_TOKEN` environment variable — a JWT token from XreplyAI Settings.
Recommendation

Set the token only for trusted use, rotate it if exposed, and prefer the least-privileged or revocable token option if XreplyAI provides one.

What this means

Runtime behavior depends on the external npm package and its published contents, not just the SKILL.md instructions reviewed here.

Why it was flagged

The runtime MCP server is pulled and executed from npm via npx. The version is pinned and the behavior is disclosed, but the package code is not included in the reviewed skill artifacts.

Skill content
mcporter call 'npx @xreplyai/mcp@0.3.19' <tool_name> [param:value ...]
Recommendation

Install only if you trust the XreplyAI npm package and publisher; consider reviewing the package provenance or lock/pinning behavior in your environment.