Copy a Google Docs template, fill in content, and share with collaborators.
Install with Tessl CLI
npx tessl i github:googleworkspace/cli --skill recipe-create-doc-from-template69
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
42%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 specific capabilities (copy, fill, share) for Google Docs templates, demonstrating good specificity. However, it lacks explicit trigger guidance ('Use when...') which is critical for skill selection, and could benefit from more natural keyword variations to improve discoverability.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user wants to create documents from templates, duplicate Google Docs, or share documents with team members'
Include additional natural trigger terms such as 'gdoc', 'Google document', 'doc template', 'document collaboration', or 'sharing permissions'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists three specific concrete actions: 'Copy a Google Docs template', 'fill in content', and 'share with collaborators'. These are clear, actionable capabilities. | 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. | 1 / 3 |
Trigger Term Quality | Includes 'Google Docs', 'template', 'share', and 'collaborators' which are natural terms, but missing common variations like 'gdoc', 'doc template', 'document sharing', or file extensions. | 2 / 3 |
Distinctiveness Conflict Risk | The Google Docs focus provides some distinction, but 'template' and 'share' are generic enough to potentially overlap with other document or collaboration skills. | 2 / 3 |
Total | 8 / 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 CLI commands for a common workflow. The main weakness is the lack of validation steps - there's no guidance on verifying the copy succeeded or checking that permissions were applied correctly before proceeding.
Suggestions
Add a validation step after copying the template (e.g., verify the new doc ID exists in the response before proceeding)
Include error handling guidance for common failures like invalid template ID or permission denied on sharing
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, providing only the essential commands without explaining what Google Docs or templates are. Every line serves a purpose. | 3 / 3 |
Actionability | Provides fully executable CLI commands with concrete examples including realistic parameter values. Commands are copy-paste ready with clear placeholders. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced but lack validation checkpoints. No verification that the copy succeeded, content was added correctly, or sharing permissions were applied. | 2 / 3 |
Progressive Disclosure | For a simple 4-step recipe under 20 lines, the structure is appropriate. The prerequisite skills are clearly referenced at the top, and content is well-organized without needing external files. | 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 | |
Table of Contents
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.