CtrlK
BlogDocsLog inGet started
Tessl Logo

recipe-create-doc-from-template

Copy a Google Docs template, fill in content, and share with collaborators.

71

Quality

64%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/recipe-create-doc-from-template/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Discovery

50%

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 clearly articulates three specific actions (copy, fill, share) within the Google Docs domain, giving it good specificity and distinctiveness. However, it critically lacks any 'Use when...' guidance, which would help Claude know when to select this skill over others. Adding trigger terms and explicit usage conditions would significantly improve its effectiveness.

Suggestions

Add a 'Use when...' clause such as 'Use when the user asks to create a document from a template, populate a Google Docs template, or share a document with team members.'

Include additional natural trigger terms like 'Google Drive', 'doc template', 'fill out', 'document sharing', 'copy template' to improve keyword coverage.

DimensionReasoningScore

Specificity

Lists three specific concrete actions: copy a template, fill in content, and share with collaborators. These are clear, actionable operations.

3 / 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. Per rubric guidelines, missing 'Use when' caps completeness at 2, and since the 'when' is entirely absent, this scores at 1.

1 / 3

Trigger Term Quality

Includes 'Google Docs', 'template', 'share', and 'collaborators' which are natural terms, but misses common variations like 'Google Drive', 'doc template', 'fill out form', or file-sharing related terms users might say.

2 / 3

Distinctiveness Conflict Risk

The combination of Google Docs templates, content filling, and sharing with collaborators is a clear, specific niche that is unlikely to conflict with other skills.

3 / 3

Total

9

/

12

Passed

Implementation

79%

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

This is a concise, actionable recipe with clear concrete commands for each step. Its main weakness is the lack of validation checkpoints—there's no verification that the copy succeeded before writing content, or that the write succeeded before sharing. Step 2 is also vaguely described compared to the otherwise concrete instructions.

Suggestions

Add explicit validation after the copy step, e.g., show how to extract the new doc ID from the JSON response and verify the file exists before proceeding.

Add a verification step after sharing, such as listing permissions to confirm the share succeeded: `gws drive permissions list --params '{"fileId": "NEW_DOC_ID"}'`

DimensionReasoningScore

Conciseness

The skill is lean and efficient. The prerequisite note is necessary context, and every step provides only the concrete command needed. No unnecessary explanations of what Google Docs or templates are.

3 / 3

Actionability

Each step provides a fully concrete, copy-paste ready CLI command with realistic example parameters. The commands include specific flags, JSON payloads, and placeholder values that are clearly named.

3 / 3

Workflow Clarity

Steps are clearly sequenced and logical, but there are no validation checkpoints. Step 2 ('Get the new doc ID from the response') is vague—it doesn't show how to extract the ID. No error handling or verification that the copy/write/share succeeded.

2 / 3

Progressive Disclosure

The prerequisite references to gws-drive and gws-docs skills are good one-level-deep references. However, the references aren't linked, and there's no navigation to more advanced usage patterns (e.g., batch sharing, template variable substitution). For a simple skill this is adequate but could be slightly better signaled.

2 / 3

Total

10

/

12

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

Total

10

/

11

Passed

Repository
googleworkspace/cli
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.