v0.2.0

Code Share

BenignClawScan verdict for this skill. Analyzed May 1, 2026, 5:54 AM.

Analysis

This skill coherently creates or updates GitHub Gists for code sharing, but users should remember it uses their GitHub account and posts code to an external link.

GuidanceInstall only if you want longer code answers shared as GitHub Gist links. Confirm gh is authenticated to the right account, review generated files for secrets or personal data, and remember that secret Gists are still external share links.

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.

Abnormal behavior control

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.

Tool Misuse and Exploitation

SeverityLowConfidenceHighStatusNote

SKILL.md

gh gist create <file> --desc "<short description>"

The skill instructs the agent to use GitHub CLI commands to upload file contents to a Gist. This is purpose-aligned, but it is still an external sharing action.

User impactCode may be posted to GitHub as a persistent Gist link instead of being shown directly in chat.

RecommendationReview the file for secrets or private information before sharing, and only choose public visibility when intended.

Human-Agent Trust Exploitation

SeverityInfoConfidenceMediumStatusNote

SKILL.md

Default to **secret gist** unless user asks for public.

The default is safer than public sharing, and the skill also warns not to publish secrets, but users should not mistake an externally shared Gist link for private local storage.

User impactAnyone who obtains the Gist URL may be able to view the shared code, depending on GitHub's Gist visibility behavior.

RecommendationTreat secret Gists as shareable external links, not as a place for credentials, private keys, or personal data.

Agentic Supply Chain Vulnerabilities

SeverityInfoConfidenceHighStatusNote

metadata

Required binaries (all must exist): none ... Primary credential: none

The registry metadata under-declares the GitHub CLI and GitHub authentication that the SKILL.md and scripts clearly require. This is a completeness issue, not hidden behavior.

User impactInstallation metadata may not warn users ahead of time that gh and GitHub login are needed.

RecommendationBefore use, install GitHub CLI if needed and confirm the authenticated account and permissions.

Permission boundary

Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.

Identity and Privilege Abuse

SeverityLowConfidenceHighStatusNote

SKILL.md

Verify GitHub CLI auth: `gh auth status` ... ask user to run: `gh auth login`

Creating and updating Gists requires use of the user's authenticated GitHub CLI session and gist permissions. That is expected for this integration, but it uses delegated account authority.

User impactThe skill can create or edit Gists under the GitHub account currently authenticated in gh.

RecommendationMake sure gh is logged into the intended GitHub account and has only the permissions needed for Gist creation.