Read-only Google Drive sharing and permission audits with gog.
66
78%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Low
Low-risk findings worth noting
Fix and improve this skill with Tessl
tessl review fix ./.agents/skills/gog-drive-audit/SKILL.mdRead ../gog/SKILL.md and ../gog-drive/SKILL.md first.
Run bounded, read-only inventory commands:
gog --account user@example.com --readonly drive audit sharing --max 200 --json --wrap-untrusted
gog --account user@example.com --readonly drive audit sharing --internal-domain example.com \
--max 200 --json --wrap-untrusted
gog --account user@example.com --readonly drive audit user person@example.com --max 200 \
--json --wrap-untrustedClassify public links, external-domain grants, broad domain grants, stale-looking direct grants, and ownership anomalies separately. Include file ID, name, owner, permission, and evidence.
Do not change permissions during an audit. If remediation is requested, present a separate,
reviewable plan and use each mutation's --dry-run before any approved write.
1dbd820
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.