Name: vpe-advisor
Rating: 67.2 (1 reviews)
Author: alirezarezvani

vpe-advisor

VP of Engineering advisory for startups: delivery throughput (DORA 4 metrics + bottleneck identification), engineering hiring funnel (sourcing → screen → onsite → offer conversion + time-to-fill + pipeline gap), engineering team structure (squad/tribe/chapter design + tech-lead manager-trigger thresholds), and production discipline (on-call, deployment cadence, postmortem culture). Use when sprint velocity is dropping, eng hiring is broken, team structure is unclear, or deciding when to add a tech-lead manager. NOT a CTO skill (which owns architecture) — VPE owns delivery operations and how the team ships.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

—

The risk profile of this skill

The canonical home for this skill is vpe-advisor in alirezarezvani/claude-skills

Quality

Content

71%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 well-structured and rich with concrete, actionable benchmark tables, commands, and sequenced workflows. Its main weakness is bundle integrity: every referenced script and reference file is missing, and script paths are inconsistent, which breaks progressive disclosure and slightly weakens actionability.

Suggestions

Bundle the three referenced scripts (delivery_throughput_analyzer.py, eng_hiring_funnel_calculator.py, eng_team_structure_designer.py) under ./scripts/ and the four referenced markdown files under ./references/ so the 'See references/X.md' pointers resolve.

Use a single consistent script path style across Quick Start and Workflows (either 'scripts/<tool>.py' or the full relative path) to avoid the current 'scripts/...' vs '../../skills/vpe-advisor/scripts/...' mismatch.

Trim minor narrative padding (e.g. 'The trap:', 'the operating model that lets the team sleep') and consider condensing the long Keywords list to keep the overview lean.

Dimension	Reasoning	Score
Conciseness	Mostly dense with value (DORA threshold tables, funnel conversion benchmarks, headcount-to-structure maps, manager-trigger thresholds, formulas), but minor narrative padding ('The trap:', 'the operating model that lets the team sleep') and a long keyword dump could be trimmed.	4 / 5
Actionability	Provides copy-paste-ready commands, specific numeric benchmarks, and concrete diagnostic questions, but the referenced scripts are not bundled and path style is inconsistent ('scripts/...' in Quick Start vs '../../skills/vpe-advisor/scripts/...' in Workflows), leaving minor executable gaps.	4 / 5
Workflow Clarity	Four workflows each have a stated goal, sequenced steps, output-review steps and cross-skill checks ('Cross-check with cs-cto-advisor'), plus a defined output template; minor gap is the absence of explicit retry/feedback loops, acceptable here since the workflows are diagnostic rather than destructive.	4 / 5
Progressive Disclosure	The overview is well-signaled with one-level-deep 'See references/X.md' pointers and a References list, but the actual ./references/, ./scripts/ and ./assets/ directories are absent, so the 7 referenced files do not exist and navigation is non-functional.	3 / 5
	Total	15 / 20 Passed

Description

92%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.

A strong, specific description that clearly states what the skill does, when to use it, and how it differs from adjacent CTO/CHRO/engineering-lead skills. Minor room to broaden trigger-term synonyms, but it is comprehensive and well-scoped.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions across four domains — 'DORA 4 metrics + bottleneck identification', 'sourcing → screen → onsite → offer conversion + time-to-fill + pipeline gap', 'squad/tribe/chapter design + tech-lead manager-trigger thresholds', 'on-call, deployment cadence, postmortem culture' — giving comprehensive coverage.	5 / 5
Completeness	Explicitly answers both 'what' (four-domain VPE advisory) and 'when' ('Use when sprint velocity is dropping, eng hiring is broken, team structure is unclear, or deciding when to add a tech-lead manager') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural trigger phrases a founder/VPE would say ('sprint velocity is dropping', 'eng hiring is broken', 'team structure is unclear', 'deciding when to add a tech-lead manager') plus synonyms (VPE / VP of Engineering), but a few natural variations (e.g. 'engineering org design', 'scaling the team') are absent.	4 / 5
Distinctiveness Conflict Risk	Carves a clear niche and explicitly disambiguates adjacent roles — 'NOT a CTO skill (which owns architecture) — VPE owns delivery operations and how the team ships' — minimizing conflict risk.	5 / 5
	Total	19 / 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
relative_links	Relative link issues: 4 missing	Warning
referenced_paths_exist	Referenced path issues: 14 missing	Warning

	Total	14 / 16 Passed

Repository: alirezarezvani/claude-skills
Path: .gemini/skills/vpe-advisor/SKILL.md
Commit: 19392f7

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