CtrlK
BlogDocsLog inGet started
Tessl Logo

google-docs-automation

Lightweight Google Docs integration with standalone OAuth authentication. No MCP server required.

54

Quality

62%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/google-docs-automation/SKILL.md

The canonical home for this skill is google-docs in sanjay3290/ai-skills

SKILL.md
Quality
Evals
Security

Quality

Content

76%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.

The body is an efficient, highly actionable command reference with clean sectioning. Its main gap is the absence of validation/verification steps for the document-mutating commands, which caps workflow clarity.

Suggestions

Add a verification step after mutating commands, e.g. re-run `get-text` after `replace-text`/`insert-text` to confirm the change landed correctly.

Drop the redundant opening sentence that repeats the frontmatter description to tighten conciseness further.

If the skill grows, move the command catalog or token-management detail into a referenced file to keep SKILL.md a lean overview.

DimensionReasoningScore

Conciseness

The body is a lean command reference that assumes Claude's competence with no concept over-explanation; only minor trimmable bits remain (the opening line repeats the frontmatter description and the warning box is slightly padded).

4 / 5

Actionability

Every operation is given as a fully executable `python scripts/docs.py …` command with realistic document IDs and a full URL example, covering create/find/get-text/append/insert/replace — copy-paste ready across the common cases.

5 / 5

Workflow Clarity

First-time setup is sequenced (login→status→logout) and commands are listed, but mutating operations like replace-text and insert-text have no validation/verification checkpoint, so the destructive-operation cap of 3 applies.

3 / 5

Progressive Disclosure

Content is well-organized into clear sections (Setup, Commands, Document ID Format, Token Management) and is self-contained with no bundle files present; at ~70 lines it slightly exceeds the 50-line simple-skill threshold, so it sits just below a 5.

4 / 5

Total

16

/

20

Passed

Description

48%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 identifies a clear niche and a useful differentiator but is vague on concrete capabilities and omits any explicit usage trigger. Adding one or two concrete actions and a 'Use when…' clause would lift the weakest dimensions.

Suggestions

Add concrete actions to the description, e.g. 'Create, find, read, and edit Google Docs' so capabilities are explicit rather than implied by 'integration'.

Append a 'Use when…' trigger clause such as 'Use when the user wants to create or edit Google Docs documents.' to satisfy the 'when' half of completeness.

Include natural synonyms (e.g. 'documents', 'Google Workspace docs') alongside 'Google Docs' to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain ('Google Docs integration') and the auth mechanism ('standalone OAuth authentication') but lists no concrete document actions — 'integration' is generic and the verbs (create/edit/append) that appear in the body are absent from the description.

2 / 5

Completeness

Provides a clear-ish 'what' (Google Docs integration via OAuth) but no 'when'/'Use when…' trigger guidance, so completeness is capped at 3 per the missing-trigger-clause guideline.

3 / 5

Trigger Term Quality

'Google Docs' is a strong natural keyword a user would say, but variations/synonyms (docs, documents, Google Workspace) are missing and 'OAuth authentication'/'MCP server' are technical rather than user-spoken terms.

3 / 5

Distinctiveness Conflict Risk

'Google Docs' is a clear niche and 'No MCP server required' explicitly distinguishes it from MCP-based integrations, leaving only minor overlap risk with other Google Workspace skills.

4 / 5

Total

12

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 12 missing

Warning

Total

14

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.