v1.0.0

B2c Marketing 1.0.1

ReviewClawScan verdict for this skill. Analyzed May 1, 2026, 5:48 AM.

Analysis

This appears to be a real social-media marketing playbook, but it gives the agent instructions to use a third-party API key to publish or schedule posts on connected public social accounts without clear approval guardrails.

GuidanceInstall only if you are comfortable giving the agent access to a Post Bridge key connected to your social accounts. Before any publish or schedule action, require the agent to show the exact video, caption, target accounts, and time and wait for your explicit approval.

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

SeverityMediumConfidenceHighStatusConcern

SKILL.md

Upload media → create post → schedule or post instantly

This instructs the agent to publish or schedule content through the Post Bridge API, including instant posting, but the visible workflow does not require a final user confirmation of the selected media, caption, destination accounts, or posting time.

User impactUnapproved or incorrect content could be posted publicly across connected social accounts, creating reputational or account-management harm.

RecommendationRequire explicit user approval before every create-post call, including the exact media, caption, platforms/accounts, and schedule; prefer draft mode or limited test accounts where possible.

Agentic Supply Chain Vulnerabilities

SeverityLowConfidenceMediumStatusNote

metadata

Source: unknown; Homepage: none; Version: 1.0.0; Owner ID: kn7e82s66abcjhjf538anjt7ws8128ab

The supplied _meta.json lists a different owner ID, slug, and version, creating package identity ambiguity. There is no code or install script, so this is a provenance note rather than evidence of malicious behavior.

User impactIt may be harder to verify that this is the intended publisher and version before trusting it with posting authority.

RecommendationVerify the publisher and registry entry before installing, especially before adding any API key or connecting social accounts.

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

SeverityMediumConfidenceHighStatusConcern

SKILL.md

Connect your social accounts ... Get API key ... Store in workspace `.env`: `POST_BRIDGE_API_KEY=pb_live_xxxxx`

The API key represents delegated authority over connected social accounts. This is central to the skill, but the registry metadata declares no required env vars or primary credential, so the sensitive authority is under-disclosed.

User impactIf the API key is exposed or used too broadly, an agent or anyone with workspace access may be able to publish through the connected accounts.

RecommendationUse the least-privileged key available, restrict which social accounts are connected, store the key outside shared workspaces when possible, declare the credential requirement, and rotate the key if exposed.

Sensitive data protection

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

Memory and Context Poisoning

SeverityLowConfidenceHighStatusNote

SKILL.md

Track every post in a local file: Post ID, platform, caption, format type, date

The skill recommends a persistent local performance log. This is proportionate for marketing analysis, but it retains campaign and post metadata beyond a single task.

User impactCampaign details, captions, and post identifiers may remain in local workspace files and could be reused or shared unintentionally.

RecommendationKeep the tracking file in a known location, avoid storing secrets in it, review it before sharing the workspace, and delete old records when no longer needed.