v2.1.1

Social Media Assistant (via postsyncer.com)

ReviewClawScan verdict for this skill. Analyzed May 1, 2026, 8:19 AM.

Analysis

This is a coherent PostSyncer social-media integration, but it gives an agent broad posting and management power over connected public social accounts.

GuidanceInstall only if you are comfortable letting an agent manage your connected social media through PostSyncer. Use a limited token, verify the official source, and require manual confirmation before any post, schedule, update, deletion, upload, or campaign change.

Findings (4)

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.

Abnormal behavior control

Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.

Tool Misuse and Exploitation

SeverityMediumConfidenceMediumStatusConcern

SKILL.md

Autonomously manage social media ... Use `web_fetch`, `curl`, or any HTTP tool available ... **Create Post** — `POST /api/v1/posts`

The skill gives the agent raw API instructions for creating and managing social posts through a bearer token. Public posting and account mutation are high-impact actions, and the provided instructions show confirmation only for some delete actions, not for publishing or updating posts.

User impactIf the agent misunderstands a request or acts too broadly, it could publish, schedule, or modify content on connected social media accounts.

RecommendationRequire explicit user approval before creating, updating, scheduling, or deleting posts or media, and confirm the exact workspace, account, content, timing, and platforms before sending requests.

Agentic Supply Chain Vulnerabilities

SeverityLowConfidenceMediumStatusNote

metadata

Source: unknown ... Homepage: https://postsyncer.com/openclaw ... No install spec — this is an instruction-only skill.

There is no executable install mechanism shown, but the registry source is not identified. Because the skill requires a powerful service token, provenance verification matters.

User impactA user could configure a sensitive token for a skill whose registry source is not clearly identified.

RecommendationVerify that the skill and homepage are the official PostSyncer distribution before adding the API token.

Permission boundary

Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.

Identity and Privilege Abuse

SeverityMediumConfidenceHighStatusNote

SKILL.md

create a personal access token with abilities: `workspaces`, `accounts`, `posts`, and (if you use them) `labels`, `campaigns` ... `POSTSYNCER_API_TOKEN=your_token`

The token permissions are expected for this integration, but they grant delegated authority over connected workspaces, accounts, and posting functions.

User impactAnyone or any agent with this token may be able to view account/workspace information and manage social content according to the token's abilities.

RecommendationUse the least-privileged token possible, limit it to needed abilities, avoid exposing it in chats or logs, and revoke or rotate it when no longer needed.

Sensitive data protection

Checks for exposed credentials, poisoned memory or context, unclear communication boundaries, or sensitive data that could leave the user's control.

Insecure Inter-Agent Communication

SeverityLowConfidenceHighStatusNote

SKILL.md

PostSyncer MCP ... uses the **same Bearer token** as REST. Typical tools: `list-workspaces`, `list-accounts`, post CRUD, ... `delete-media`

The optional MCP path reuses the same credential and exposes remote tools for account, post, and media operations. This is purpose-aligned, but users should verify the MCP endpoint and data boundary.

User impactUsing MCP or REST will send social account metadata, post content, media references, and the bearer token to the PostSyncer service/tooling path.

RecommendationUse only the official PostSyncer endpoint or MCP server, and avoid sending content or media that should not be processed by that service.