Post.at Tracking
Analysis
The skill is a coherent post.at CLI reference, but it uses postal account credentials and can change package delivery instructions, so users should confirm sensitive actions.
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.
Set all upcoming deliveries to door: ```bash # First list deliveries post-at deliveries --json > /tmp/deliveries.json # Then set place for each (requires scripting) # Example for a specific one: post-at routing place 1042348411302810212306 \
The skill documents commands that can change delivery-place routing, including a bulk-oriented workflow. This matches the stated purpose, but it affects where physical packages may be left.
homepage: https://github.com/krausefx/post-at-cli ... ```bash post-at login ```
The skill is instruction-only and invokes an external `post-at` command, while the provided artifacts include no install spec or CLI code. This is not suspicious by itself, but users should verify the external CLI provenance.
Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.
requires your own account credentials. Credentials: `POST_AT_USERNAME` and `POST_AT_PASSWORD` environment variables (or `--username` / `--password` options).
The skill requires the user's post.at account credentials to access delivery information. This is expected for the integration, but it is sensitive account authority and is not reflected in the registry's credential/env-var declarations.
