persona-sales-ops

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

Quality

35%

Does it follow best practices?

Impact

—

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

Content

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 workflow sequencing and concrete examples. The content reads more like a feature list than an actionable guide, and the tips section includes generic advice that doesn't leverage Claude's existing knowledge efficiently.

Suggestions

Add at least one end-to-end sequenced workflow (e.g., 'New Deal Pipeline' with numbered steps from initial contact through close) with explicit validation checkpoints.

Include a concrete example showing a complete command invocation with sample input and expected output for at least one key operation like deal logging or email triage.

Remove generic sales advice tips (e.g., 'maintain momentum', 'keep documents in a shared folder') that Claude already understands, and replace with tool-specific gotchas or constraints.

Add brief descriptions or link targets for referenced workflows (+meeting-prep, +email-to-task, +weekly-digest) so Claude knows what each provides without needing to load them.

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. Sales operations inherently involve multi-step processes (e.g., deal progression, follow-up sequences), but no ordering, validation checkpoints, or feedback loops are provided.	1 / 3
Progressive Disclosure	References to external workflows and utility skills are present and clearly named, but there are no hyperlinks or descriptions of what each referenced workflow actually does. The structure is flat with sections but could better signal what content lives where.	2 / 3
	Total	7 / 12 Passed

Description

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 it lacks an explicit 'Use when...' clause which is critical for skill selection. The abbreviated style ('client comms') introduces vagueness, and the trigger term coverage misses common sales-related vocabulary like 'pipeline', 'CRM', 'leads', or 'prospects'.

Suggestions

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

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

Replace the abbreviation 'client comms' with specific actions like 'draft client emails, log client interactions, send follow-up messages'.

Dimension	Reasoning	Score
Specificity	Names the domain (sales workflows) and lists some actions (track deals, schedule calls, client comms), but the actions are somewhat abbreviated and not fully concrete — 'client comms' is vague and could mean many things.	2 / 3
Completeness	Describes what the skill does but has no explicit 'Use when...' clause or equivalent trigger guidance, and per the rubric a missing 'Use when' clause caps completeness at 2 — but the 'what' is also only partially clear ('client comms' is vague), so this falls closer to 1.	1 / 3
Trigger Term Quality	Includes some natural keywords like 'deals', 'calls', 'sales', but misses common variations users might say such as 'pipeline', 'CRM', 'follow-up', 'prospects', 'leads', 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. It's somewhat distinguishable but not clearly carved out.	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: a3768d0

Reviewed: 2 months 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.