Release Tracker
Analysis
This looks like a coherent release-monitoring skill, but it can use your GitHub login, run on a schedule, and post summaries to configured chat channels.
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.
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.
Based on `outputFormat`: `discord-forum`: `message(action=thread-create, channelId=<outputChannel>...)`; `discord-channel`: `message(action=send...)`; `telegram`; `slack`
The skill can cause the agent to create forum posts or send messages to external chat channels. This is clearly disclosed and central to the release-tracking purpose.
Required binaries (all must exist): none; Required env vars: none; Primary credential: none
The registry metadata does not declare the GitHub CLI/auth dependency that is stated in the skill instructions and checked by the setup script. This is an install-contract completeness issue, not evidence of hidden behavior.
Create the cron job for automated checking: Name: release-tracker; Schedule: {config.schedule}; Session: isolated; Payload: agentTurn with message referencing this skill; Delivery: none (skill handles its own delivery)The skill explicitly sets up recurring agent-driven checks. This persistence is disclosed and aligned with release monitoring, but it will continue until the cron job is changed or removed.
Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.
- `gh` CLI installed and authenticated (`gh auth status`)
The workflow relies on the user's authenticated GitHub CLI context. That is expected for GitHub release tracking, and no artifact shows credential leakage or unrelated account use.