Atoship
Analysis
Atoship appears purpose-aligned, but it needs an API key that can buy shipping labels and spend wallet funds, and it sends shipment details to Atoship/carriers.
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.
Always show the user the carrier, service, price, and full addresses, then ask for explicit confirmation ... before calling the purchase API.
The skill can call a purchase API that creates paid shipping labels, but the artifact also includes a clear explicit-confirmation safeguard.
Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.
Your API key authorizes label purchases and wallet charges.
The required credential has spend authority on the user's Atoship account, which is expected for shipping labels but important to handle carefully.
Checks for exposed credentials, poisoned memory or context, unclear communication boundaries, or sensitive data that could leave the user's control.
Your AI assistant calls the atoship API directly using your API key ... Sender: Name, Street, City, State, ZIP ... Recipient: Name, Street, City, State, ZIP
The workflow sends names, addresses, package details, and related shipment data to an external shipping API as part of its purpose.
