Back to skill
Skillv1.0.0
ClawScan security
Daily Standup Generator · ClawHub's context-aware review of the artifact, metadata, and declared behavior.
Scanner verdict
SuspiciousApr 30, 2026, 12:43 AM
- Verdict
- suspicious
- Confidence
- high
- Model
- gpt-5-mini
- Summary
- The skill's runtime instructions require access to local git repositories and the GitHub CLI (and likely GitHub credentials), but the skill metadata does not declare those binaries or credentials — an inconsistency that requires clarification before use.
- Guidance
- Before installing or enabling this skill, be aware it intends to run local git commands and call repository-hosting APIs (examples use the GitHub CLI). Confirm the following: (1) the agent runtime will have git and the GitHub CLI (gh) installed — the skill metadata does not declare these but the SKILL.md requires them; (2) an authenticated gh/GitHub context or token will be needed for private repos and PR/issue queries — only provide a token with minimal scopes you trust; (3) the skill will read local repo data including uncommitted changes and stash entries, so avoid running it against repositories containing secrets or highly sensitive work without review; (4) ask the skill author to update metadata to list required binaries (git, gh) and required credentials (e.g., GH_TOKEN or note that gh must be logged in), and to explain how holiday detection works and which Git hosts are supported (GitHub vs GitLab). If you proceed, test it first on a non-sensitive repo and prefer read-only or limited-scope credentials.
Review Dimensions
- Purpose & Capability
- concernThe SKILL.md clearly expects to run local git commands and GitHub CLI (gh) to read commits, branches, uncommitted/stashed work, PRs and issues. That matches the described purpose. However, the registry metadata declares no required binaries and no credentials/config paths, which is inconsistent: a standup generator that inspects PRs and issues legitimately needs git and a GitHub/GitLab client and authenticated access to those APIs.
- Instruction Scope
- noteThe instructions are concrete and scoped to the stated purpose: read git history, branch state, stash, and call PR/issue APIs. These commands will read local repository .git data, uncommitted changes, and stash entries — privacy-sensitive but coherent for a standup generator. Some items are vague (e.g., 'adjusts for holidays automatically' with no source explained) and the sample commands include hardcoded example timestamps; the skill also assumes access to multiple repo paths and an authenticated gh context.
- Install Mechanism
- okThe skill is instruction-only with no install spec (lowest install risk). No archives or remote downloads are requested. However, it implicitly depends on external CLIs (git, gh) but does not declare them in metadata.
- Credentials
- concernNo environment variables or primary credential are declared, yet the SKILL.md uses GitHub CLI patterns (e.g., --author='@me') and will require authenticated API access for PRs/issues and possibly GIT credentials for private repos. The skill also reads git config user.name/email and local repo state. The absence of declared credential requirements (GH_TOKEN, GIT credential helpers, or similar) is a proportionality/information gap.
- Persistence & Privilege
- okThe skill is not marked always:true and has no install steps that would persist code or alter other skills. It runs at invocation time and does not request elevated platform privileges in the metadata.