CtrlK
BlogDocsLog inGet started
Tessl Logo

gog-drive-audit

Read-only Google Drive sharing and permission audits with gog.

65

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/gog-drive-audit/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

96%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A tight, highly actionable skill body: executable read-only commands, a clear read-vs-remediate workflow with dry-run validation, and disciplined token efficiency. Progressive disclosure is good though it relies on sibling SKILL.md files rather than its own references.

DimensionReasoningScore

Conciseness

Lean and efficient: it assumes Claude's competence, gives ready-to-run commands without explaining what Drive or auditing is, and every line earns its place.

5 / 5

Actionability

Provides fully executable, copy-paste-ready gog commands with concrete flags (--readonly, --max 200, --json, --wrap-untrusted) covering the common audit cases, plus a concrete output schema to include.

5 / 5

Workflow Clarity

Despite involving destructive-capable operations, it enforces read-only audits, sequences inventory then classification, and for remediation requires a separate reviewable plan with --dry-run before any approved write — explicit validation/checkpoint guidance for the risky path.

5 / 5

Progressive Disclosure

Short, well-organized single-purpose body with clear sections and one-level-deep pointers to ../gog/SKILL.md and ../gog-drive/SKILL.md; no bundle files exist so there is nothing further to offload, leaving only minor room for clearer in-skill section signaling.

4 / 5

Total

19

/

20

Passed

Description

58%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is concise and names a clear, fairly distinct niche with the gog tool, but it lacks an explicit 'Use when' trigger clause and omits common natural phrasings users would actually say, capping completeness and trigger coverage.

Suggestions

Add an explicit trigger clause, e.g., 'Use when the user asks who can access their Drive files, wants a sharing/permission audit, or needs to find externally shared documents.'

Include natural user phrasings and synonyms such as 'shared files', 'who has access', and 'Drive permissions' to improve trigger-term coverage.

Briefly enumerate the concrete audit actions (e.g., 'find public links, external-domain grants, broad domain grants, stale grants') to raise specificity.

DimensionReasoningScore

Specificity

Names the domain ('Google Drive sharing and permission audits') and several concrete attributes ('Read-only', 'sharing and permission', 'audits with gog'), but lists the tool/restrictions rather than enumerating multiple concrete audit actions; comparable to the score-4 example which lists several specific actions with minor gaps.

4 / 5

Completeness

Provides a clear 'what' (read-only Drive sharing/permission audits) but has no 'Use when...' clause or equivalent explicit trigger guidance; per judging guidelines, a missing trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

Contains relevant terms ('Google Drive', 'sharing', 'permission', 'audits') but is missing common natural variations users would say (e.g., 'who has access to my files', 'shared files', 'Drive permissions'); not quite the comprehensive synonym/extension coverage of a 4.

3 / 5

Distinctiveness Conflict Risk

The 'gog' tool and 'Google Drive sharing and permission audits' niche are fairly distinct with minimal overlap risk against generic Drive skills, though the very short description leaves minor ambiguity versus broader Drive tooling.

4 / 5

Total

14

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
openclaw/gogcli
Reviewed

Table of Contents

Is this your skill?

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.