a2a-Market-Google-OAuth
PassAudited by VirusTotal on May 11, 2026.
Overview
Type: OpenClaw Skill Name: a2a-market-google-oauth Version: 0.2.0 The skill bundle contains architectural instructions and metadata for implementing a standard Google OAuth 2.0 flow. The SKILL.md file outlines a secure implementation strategy, including state/nonce validation and token rotation, and does not contain any malicious commands, data exfiltration logic, or prompt injection attempts.
Findings (0)
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.
Generated or implemented code based on this skill could affect who can log in, how accounts are linked, and how access or refresh tokens are issued.
The skill is explicitly about mapping Google identities to internal principals and issuing sessions, which is high-impact identity/session authority even though it is purpose-aligned.
- Link external identity to internal Agent/Operator profile. - Bootstrap session token and refresh workflow after callback.
Use this only for intended authentication work, define exact OAuth scopes and credential handling, and manually review account-linking and token-lifecycle code before deployment.
A user may believe there is reviewed implementation and test coverage when the supplied artifact set only contains instructions.
The skill references runtime code paths and tests, while the provided manifest contains only SKILL.md and no code files; users should not assume those referenced files were reviewed as part of this artifact.
- Status: implemented in local runtime package. - Primary code paths: - `runtime/src/integrations/oauth/google-oauth-service.js` - Validation: covered by `runtime/tests` and `npm test` in `runtime/`.
Review any referenced runtime package, implementation files, and tests separately before relying on them for authentication behavior.
If implemented carelessly, login or session events could expose sensitive account/session metadata to unintended consumers.
The skill describes sending authentication-related events to audit and WebSocket channels; this is purpose-aligned, but event payloads and access boundaries are not specified in the artifact.
- Emit login event to audit log stream. - Emit session-created event for WebSocket presence bootstrap.
Ensure events never include raw tokens, minimize identity data in payloads, and restrict audit/WebSocket stream access to authorized services.