persona-content-creator

Create, organize, and distribute content across Workspace.

Quality

36%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/persona-content-creator/SKILL.md

Quality

Discovery

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 name the concrete tools or file types involved (e.g., Docs, Sheets, Slides, Gmail).

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 content in Google Workspace.'

Replace vague verbs like 'organize' and 'distribute' with specific actions (e.g., 'create documents, manage folder structures, share files with collaborators, schedule email distributions').

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

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 concise, well-structured orchestration skill that effectively delegates to sub-skills and keeps its scope appropriately narrow. Its main weaknesses are the lack of concrete usage examples with parameters and the absence of a clear sequential workflow with validation steps for the content creation and distribution process.

Suggestions

Add a concrete end-to-end example showing the full content creation workflow with actual command invocations and expected outputs (e.g., creating a doc, organizing it, and announcing it).

Sequence the instructions into a numbered workflow with explicit validation checkpoints (e.g., verify doc was created before sharing, confirm file upload before announcing).

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`, `gws workflow +file-announce`) but lacks concrete examples of usage with actual parameters, expected inputs/outputs, or copy-paste ready command invocations. The guidance is more directional than fully executable.	2 / 3
Workflow Clarity	The instructions list steps for different content operations but lack a clear sequenced workflow with validation checkpoints. There's no explicit ordering (e.g., draft → organize → review → distribute) or verification steps to confirm content was successfully created/shared before proceeding.	2 / 3
Progressive Disclosure	The skill appropriately serves as a high-level overview, referencing prerequisite utility skills (`gws-docs`, `gws-drive`, etc.) and a specific workflow (`gws workflow +file-announce`) for deeper detail. References are one level deep and clearly signaled.	3 / 3
	Total	10 / 12 Passed

Validation

90%

Warnings & errors only

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: a3768d0

Reviewed: about 1 month ago

Table of Contents

Discovery Implementation Validation

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.