No separate API key, token, or environment variable is declared, and the skill itself does not collect or expose credentials. If the user manually runs the gh commands, authentication would typically rely on existing local GitHub CLI credentials, but that is external tool behavior rather than embedded secret handling by this skill.

The skill material itself contains no remote endpoint configuration and does not appear to be an active networked component. The README only shows command examples for GitHub notification APIs; if executed, traffic would go to GitHub's official endpoints rather than to an unknown third party.

The system flags this as prompt-only; the material is documentation-style command examples without auditable auto-execution logic, install scripts, or local process-spawning capability. Any impact would come from a user's manual execution, not from the skill itself executing code.

No local file read/write, system directory access, or extra resource authorization is described. Its stated scope is limited to marking all notifications, repository-specific notifications, or notifications since a given time as read on the user's GitHub account, which is a bounded remote state change rather than excessive local data access.

The source is a publicly auditable GitHub repository under microsoft/vscode-team-kit, and its open-source nature reduces supply-chain opacity. Although it has 0 stars, no declared license, and unknown maintenance status, these facts are still materially better than closed-source or unattributed materials, and no specific supply-chain red flags are evident here.