My Admapix
Analysis
The skill is mostly aligned with AdMapix analytics, but it needs review because it stores an API key and automatically routes complex requests to a server-side AI service that hosts shareable reports.
Findings (3)
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.
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.
Source: unknown; Homepage: none
The registry metadata does not provide a verified source or homepage for the package, which weakens provenance for a credential-using integration.
Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.
Auth header: `X-API-Key: $ADMAPIX_API_KEY` ... `openclaw config set skills.entries.admapix.apiKey "{KEY}"`The skill uses and persists an AdMapix API key for authenticated API access. This is expected for the service, but it gives the skill access to the user’s AdMapix API account.
Checks for exposed credentials, poisoned memory or context, unclear communication boundaries, or sensitive data that could leave the user's control.
“server-side AI research engine” ... “autonomously plans and executes a multi-step investigation — orchestrating dozens of API calls” ... “Reports are hosted and shareable via link.”
Complex queries are routed to an external AI/reporting service that can perform many API calls and publish a hosted report, but the artifacts do not define report access controls, retention, or a separate approval step before hosting.
