cs-growth-strategist

Growth Strategist agent for revenue operations, sales engineering, customer success, and business development. Orchestrates business-growth skills. Spawn when users need pipeline analysis, churn prevention, expansion scoring, sales demos, or proposal writing.

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.gemini/skills/cs-growth-strategist/SKILL.md

Quality

Content

57%Weight 40%Scale 1-5

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

The body is concise and clearly sequenced across four revenue workflows, but it stays at mid-range because every script is referenced by bare name with no executable invocation, inputs, or location, and none of the batch workflows include validation/verification checkpoints that the rubric requires.

Suggestions

Give each referenced script a concrete invocation (e.g. `python business-growth/scripts/pipeline_analyzer.py --deals deals.csv`) with required arguments and expected input/output format so guidance is executable, not just named.

Add a validation/verification checkpoint to each batch workflow (e.g. confirm forecast inputs are complete before generating, verify health-score segments before exporting) to satisfy the workflow-clarity validation requirement.

Either provide the referenced *.py scripts as bundle files under scripts/ and link to them by path, or mark them as external/assumed-available so the progressive-disclosure references resolve to real navigable files.

Dimension	Reasoning	Score
Conciseness	The body is lean, well-sectioned, and assumes Claude's competence without explaining known concepts, matching the 'efficient; minor instances of over-explanation' anchor; the Role & Expertise line lightly restates the frontmatter, the only thing keeping it from 5.	4 / 5
Actionability	Workflows name concrete scripts ('Run `pipeline_analyzer.py` on deal data', 'Calculate health scores via `health_score_calculator.py`') and metrics (CAC, LTV, NRR), but give no invocation, arguments, input format, or where the scripts live, matching the 'some concrete guidance but incomplete' anchor; it is not a 4 because nothing shown is copy-paste executable.	3 / 5
Workflow Clarity	Four numbered workflows are clearly sequenced, but batch/analysis operations (forecast generation, churn intervention, expansion proposals) have no validation or verification checkpoints, so the rubric's missing-validation cap applies; it is capped at 3 even though the sequences are otherwise clear.	3 / 5
Progressive Disclosure	Sections are well organized, but referenced scripts (*.py) and linked agents are cited by bare name with no bundle files present to navigate to, matching the 'some structure but references not clearly signaled / navigation incomplete' anchor; it is not a 4 because the cited supporting materials are unverifiable rather than cleanly one level deep.	3 / 5
	Total	13 / 20 Passed

Description

83%Weight 40%Scale 1-5

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 is strong: third-person voice, concrete domain actions, and an explicit 'Spawn when...' trigger clause that jointly answer what and when. It sits just below top marks only because the keyword/coverage is curated rather than exhaustive.

Dimension	Reasoning	Score
Specificity	Names the revenue-lifecycle domain and several concrete actions ('pipeline analysis, churn prevention, expansion scoring, sales demos, or proposal writing'), matching the 'lists several specific actions; minor gaps' anchor; it is not a 5 because coverage is a curated trigger list rather than a comprehensive action enumeration.	4 / 5
Completeness	Explicitly answers both 'what' (Growth Strategist agent for revenue operations, sales engineering, customer success, and business development) and 'when' via the concrete 'Spawn when users need pipeline analysis, churn prevention, expansion scoring, sales demos, or proposal writing' trigger clause, matching the 5 anchor.	5 / 5
Trigger Term Quality	Phrases like 'pipeline analysis', 'churn prevention', 'expansion scoring', 'sales demos', and 'proposal writing' are natural user language with good coverage, matching the 'good keyword coverage; a few natural terms missing' anchor; missing common synonyms (e.g. 'retention', 'NRR', 'revenue') keep it below 5.	4 / 5
Distinctiveness Conflict Risk	It carves a clear revenue-lifecycle niche with distinct triggers, matching the 'mostly distinct; minor overlap risk' anchor; minor overlap with general business/finance skills keeps it just below 5.	4 / 5
	Total	17 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 2 suspicious	Warning

	Total	14 / 16 Passed

Repository: alirezarezvani/claude-skills
Path: .gemini/skills/cs-growth-strategist/SKILL.md
Commit: 19392f7

Reviewed: ~5 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.