persona-content-creator
Create, organize, and distribute content across Workspace.
40
26%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/persona-content-creator/SKILL.mdQuality
Discovery
0%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 far too vague to be useful for skill selection. It fails to specify what type of content, what 'Workspace' refers to, what concrete actions are supported, and when the skill should be triggered. It would easily conflict with many other content-related skills.
Suggestions
Specify what 'Workspace' refers to (e.g., Google Workspace, Slack workspace) and what types of content are handled (e.g., documents, spreadsheets, slides).
Add a 'Use when...' clause with explicit trigger terms, such as 'Use when the user asks about creating Google Docs, sharing files in Google Drive, or organizing folders in Google Workspace.'
List concrete actions instead of generic verbs—e.g., 'Creates Google Docs, manages shared Drive folders, schedules email distribution of reports' rather than 'create, organize, and distribute content.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague actions ('create, organize, distribute') without specifying what kind of content or what concrete operations are performed. 'Workspace' is undefined and abstract. | 1 / 3 |
Completeness | The description weakly addresses 'what' with vague actions and completely lacks a 'when' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | The terms 'content', 'Workspace', 'organize', and 'distribute' are overly generic and not natural keywords a user would say when needing a specific skill. 'Workspace' is ambiguous—it could refer to many different platforms. | 1 / 3 |
Distinctiveness Conflict Risk | Extremely generic—'create, organize, and distribute content' could apply to dozens of different skills. 'Workspace' is not specific enough to carve out a clear niche. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
52%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill is concise and avoids unnecessary verbosity, which is its main strength. However, it reads more like a command reference card than an actionable workflow—the instructions lack sequencing, validation steps, and concrete examples showing actual usage with parameters. The content would benefit significantly from a clear ordered workflow and at least one end-to-end example.
Suggestions
Add a clear numbered workflow sequence showing the typical content creation pipeline (draft → organize → review → distribute) with explicit validation checkpoints (e.g., verify doc creation before sharing).
Include at least one concrete end-to-end example showing actual command invocations with realistic parameters and expected outputs.
Add brief descriptions next to the prerequisite skill references explaining what each provides, so the user understands the dependency structure without loading them first.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. Every line serves a purpose—no unnecessary explanations of what Google Docs or Drive are. It assumes Claude knows the underlying concepts and just provides the specific commands and workflows. | 3 / 3 |
Actionability | The skill provides specific command references (e.g., `gws docs +write`, `gws drive files list`) which are concrete, but there are no executable examples showing actual usage with parameters, expected inputs, or outputs. The instructions are more like a menu of commands than fully actionable guidance. | 2 / 3 |
Workflow Clarity | The instructions are a flat list of independent actions with no clear sequencing, no validation checkpoints, and no feedback loops. For a content creation workflow that involves drafting, organizing, and distributing, there should be a clear multi-step sequence with verification steps (e.g., confirm doc was created before sharing). | 1 / 3 |
Progressive Disclosure | It references prerequisite utility skills and a workflow (`gws workflow +file-announce`), which is good progressive disclosure. However, the references aren't clearly signaled with descriptions of what each linked skill provides, and the relationship between the prerequisite skills and the instructions could be better organized. | 2 / 3 |
Total | 8 / 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.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_field | 'metadata' should map string keys to string values | Warning |
Total | 10 / 11 Passed | |
- Repository
- googleworkspace/cli
- Commit
c7c6646
- 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.