persona-sales-ops

Manage sales workflows — track deals, schedule calls, client comms.

Quality

35%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/persona-sales-ops/SKILL.md

Quality

Discovery

32%

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 provides a reasonable overview of the sales workflow domain with a few concrete actions, but lacks a 'Use when...' clause that would help Claude know when to select this skill. The trigger terms are decent but incomplete, missing common sales-related vocabulary that users would naturally use.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user mentions sales pipeline, deal tracking, client outreach, or scheduling sales calls.'

Expand trigger terms to include common variations like 'pipeline', 'CRM', 'leads', 'prospects', 'follow-up', and 'meetings'.

Make 'client comms' more specific — e.g., 'draft client emails, log meeting notes, send follow-up messages' to improve specificity.

Dimension	Reasoning	Score
Specificity	Names the domain (sales workflows) and lists some actions (track deals, schedule calls, client comms), but the actions are somewhat brief and 'client comms' is vague rather than a concrete action.	2 / 3
Completeness	Describes what the skill does but has no 'Use when...' clause or equivalent explicit trigger guidance. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and since the 'what' is also only moderately detailed, this scores at 1.	1 / 3
Trigger Term Quality	Includes some natural keywords like 'deals', 'calls', and 'sales' that users might say, but misses common variations like 'pipeline', 'CRM', 'leads', 'follow-up', 'prospects', or 'meetings'.	2 / 3
Distinctiveness Conflict Risk	The sales domain provides some specificity, but 'schedule calls' and 'client comms' could overlap with general calendar/scheduling or communication skills. Not generic enough to conflict with everything, but not sharply distinct either.	2 / 3
	Total	7 / 12 Passed

Implementation

37%

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

This skill provides a reasonable overview of sales operations tooling with specific command references, but lacks depth in execution. The content reads more like a feature list than actionable guidance — there are no concrete examples with inputs/outputs, no sequenced multi-step workflows, and no validation or error-handling steps for operations like deal tracking or pipeline management.

Suggestions

Add at least one fully worked example showing a complete sales workflow sequence (e.g., preparing for a client call from start to finish with specific commands and expected outputs).

Introduce explicit workflow sequences with numbered steps and validation checkpoints, especially for multi-step processes like deal tracking or converting emails to tasks.

Remove generic advice Claude already knows (e.g., 'maintain momentum', 'keep documents in a shared folder') and replace with specific, actionable patterns unique to this tooling.

Add brief descriptions or links for each referenced workflow (e.g., `+meeting-prep`) so the user understands what each does without needing to look it up.

Dimension	Reasoning	Score
Conciseness	Reasonably lean but some lines are somewhat generic advice Claude already knows (e.g., 'Schedule follow-up calls immediately after meetings to maintain momentum'). The prerequisite and workflow references are efficient, but tips like keeping documents in a shared folder add little value.	2 / 3
Actionability	Provides specific command references (e.g., `gws sheets +append`, `gws gmail +triage --query ...`) which is helpful, but none are fully executable examples with concrete inputs/outputs. The instructions describe what to do at a high level without showing complete usage patterns or expected results.	2 / 3
Workflow Clarity	There is no clear sequenced workflow — just a flat list of independent actions. For a sales operations skill involving multi-step processes (deal tracking, client communication pipelines), there's no sequencing, no validation checkpoints, and no feedback loops for error handling.	1 / 3
Progressive Disclosure	References to external workflows and utility skills are present and clearly named, which is good. However, the references are not clearly signaled with links or descriptions of what each contains, and the overall structure is minimal — it could better organize the relationship between the prerequisite skills and the workflows.	2 / 3
	Total	7 / 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: c7c6646

Reviewed: about 9 hours 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.