recipe-audit-external-sharing
Find and review Google Drive files shared outside the organization.
Install with Tessl CLI
npx tessl i github:googleworkspace/cli --skill recipe-audit-external-sharing65
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
32%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 identifies a clear domain (Google Drive external sharing) but is too brief and lacks explicit trigger guidance. It would benefit from more specific actions (e.g., 'audit permissions', 'list externally shared files', 'revoke access') and a clear 'Use when...' clause to help Claude know when to select this skill.
Suggestions
Add a 'Use when...' clause with trigger terms like 'external sharing', 'shared outside', 'Drive audit', 'sharing permissions', or 'public access'
Expand the action list to be more specific: e.g., 'audit sharing permissions, identify externally shared files, review public links, generate sharing reports'
Include common user phrasings like 'who has access', 'check sharing settings', or 'find files shared with external users'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Google Drive) and two actions (find and review), but lacks comprehensive detail about what 'review' entails or what specific operations are performed on externally shared files. | 2 / 3 |
Completeness | Describes what the skill does but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes 'Google Drive' and 'shared outside the organization' which are relevant, but misses common variations like 'external sharing', 'shared externally', 'sharing permissions', 'public files', or 'Drive audit'. | 2 / 3 |
Distinctiveness Conflict Risk | The focus on external sharing is somewhat specific, but 'Google Drive files' could overlap with general Drive management skills; the external sharing angle provides some distinction but isn't strongly emphasized. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted, concise skill that provides actionable commands for auditing external Drive sharing. Its main strength is token efficiency and executable guidance. The workflow could be improved with an explicit verification step after revoking permissions, especially since this is a destructive operation.
Suggestions
Add a verification step after revocation: re-run permissions list to confirm the permission was removed
Consider adding error handling guidance for common failures (e.g., permission denied, file not found)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. No unnecessary explanations about what Google Drive is or how sharing works. Every line serves a purpose - prerequisite, warning, and three concrete commands. | 3 / 3 |
Actionability | Provides fully executable CLI commands with proper parameter syntax. Commands are copy-paste ready with clear placeholders (FILE_ID, PERM_ID) for user-specific values. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced (list → check → revoke), but lacks explicit validation checkpoint. The caution note is good but there's no feedback loop for verifying the revocation succeeded or handling errors. | 2 / 3 |
Progressive Disclosure | For this simple, single-purpose skill under 50 lines, the structure is appropriate. Clear prerequisite reference to external skill, well-organized sections, and no need for additional file references. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
72%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 8 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 8 / 11 Passed | |
- 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.