persona-content-creator
Create, organize, and distribute content across Workspace.
Install with Tessl CLI
npx tessl i github:googleworkspace/cli --skill persona-content-creator50
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
9%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is too vague to be useful for skill selection. It lacks specific actions, natural trigger terms, explicit usage guidance, and distinctive identifiers. Without knowing what 'Workspace' refers to or what types of 'content' are involved, Claude cannot reliably choose this skill over alternatives.
Suggestions
Specify which Workspace platform this applies to (e.g., 'Google Workspace', 'Slack workspace') and list concrete content types (e.g., 'documents, spreadsheets, presentations').
Add a 'Use when...' clause with natural trigger terms like 'Google Docs', 'share files', 'team collaboration', or specific file types.
List specific concrete actions instead of generic verbs (e.g., 'Create Google Docs, organize Drive folders, share files with team members' instead of 'create, organize, distribute content').
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names some actions ('create, organize, distribute') and a domain ('Workspace'), but the actions are generic and 'content' is vague. Does not specify what types of content or concrete operations. | 2 / 3 |
Completeness | Only partially addresses 'what' with vague terms, and completely missing 'when' guidance. No 'Use when...' clause or explicit trigger guidance exists. | 1 / 3 |
Trigger Term Quality | Contains no natural keywords users would say. 'Workspace' is ambiguous (Google Workspace? Slack workspace? Generic workspace?), and 'content' is too generic to serve as a useful trigger term. | 1 / 3 |
Distinctiveness Conflict Risk | 'Content' and 'Workspace' are extremely generic terms that could conflict with many other skills. Nothing distinguishes this from document management, file organization, or collaboration tools. | 1 / 3 |
Total | 5 / 12 Passed |
Implementation
72%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-structured persona skill that efficiently delegates to underlying utility skills and maintains good organization. However, it lacks concrete examples showing actual command usage with parameters, and the workflow could benefit from explicit sequencing showing how the content creation process flows from drafting to distribution.
Suggestions
Add a concrete example showing a complete content creation flow, e.g., 'Draft blog post → Upload images → Announce in Chat' with actual command invocations
Include at least one executable example with parameters, such as `gws docs +write --title 'Q4 Newsletter' --content 'Draft content here'`
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, with no unnecessary explanations. Every line serves a purpose - it lists prerequisites, workflows, instructions, and tips without padding or explaining concepts Claude already knows. | 3 / 3 |
Actionability | Provides specific command patterns (e.g., `gws docs +write`, `gws drive files list`) but lacks concrete executable examples showing actual usage with parameters or expected outputs. The guidance is directive but not copy-paste ready. | 2 / 3 |
Workflow Clarity | Instructions list discrete actions but lack clear sequencing for a content creation workflow. No validation checkpoints or feedback loops are mentioned for what could be a multi-step content creation and distribution process. | 2 / 3 |
Progressive Disclosure | Appropriately structured with clear prerequisite skills referenced, a relevant workflow link, and well-organized sections. The skill correctly delegates to other utility skills rather than duplicating content. | 3 / 3 |
Total | 10 / 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.