Enable Chrome Gemini
PassAudited by ClawScan on May 1, 2026.
Overview
This skill transparently runs a local Python script to back up and modify Chrome's Local State so Gemini appears, but it makes persistent browser profile changes that users should understand first.
Install only if you are comfortable with a script changing Chrome's Local State to set Gemini eligibility, region, flags, and language. Run a dry run first, close Chrome before applying changes, verify the profile path, and keep the backup so you can restore the previous state if needed.
Findings (3)
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.
Chrome's Gemini eligibility, region, experiment flags, and language settings can be changed for the selected profile.
The script changes Chrome region/eligibility fields and replaces the Local State file, so it is not just diagnostic; it mutates persistent browser profile configuration.
data["variations_country"] = "us" ... glic["is_glic_eligible"] = True ... temp_path.replace(local_state)
Use --dry-run first, close Chrome before writing, confirm the target user-data directory, and keep the generated backup until Chrome is verified.
Users have less external context about who authored or maintains the script.
The skill includes local runnable code but has limited provenance metadata. The code is present for review and has no external package install path shown, so this is a provenance note rather than a concern.
Source: unknown; Homepage: none; Install specifications: No install spec — this is an instruction-only skill.
Review the included Python file before running it, especially because it modifies a browser profile file.
In managed enterprise Chrome environments, the script may not work or may conflict with organizational policy expectations.
The skill presents managed-policy handling as a guardrail, but the included script does not show an automated managed-policy check before editing Local State. Users should treat this as a manual check.
If the profile is managed by policy, stop and report that the fix may be blocked.
If Chrome says it is managed by an organization, check with the administrator before running the repair script.