Name: vpe-advisor
Rating: 60 (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

71%

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/skills-vpe-advisor/SKILL.md

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

Quality

Content

50%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 with useful tables, executable command forms, and a clear output template, but it is held back by repeated conceptual explanation, missing validation checkpoints in workflows, and references/scripts that are advertised but not actually present in the bundle.

Suggestions

Add the missing bundle files: create references/{delivery_throughput,engineering_hiring_funnel,eng_team_structure,production_discipline}.md and scripts/{delivery_throughput_analyzer,eng_hiring_funnel_calculator,eng_team_structure_designer}.py so the advertised commands and links resolve.

Trim repetition — the CTO-vs-VPE distinction and the DORA/hiring-framework preamble are stated multiple times; state each once and push detail to the reference files.

Insert explicit validation checkpoints in the workflows (e.g., verify tool output is non-empty / within expected ranges before acting) so multi-step processes have feedback loops.

Dimension	Reasoning	Score
Conciseness	Tables for DORA metrics and funnel stages are token-dense and useful, but the body over-explains concepts Claude knows (the DORA framework, the hiring 'trap' preamble) and repeats the CTO-vs-VPE distinction three times, so it is mostly efficient with notable trimmable padding.	3 / 5
Actionability	Concrete commands, benchmark tables, and an output template are present, but the referenced scripts (delivery_throughput_analyzer.py, eng_hiring_funnel_calculator.py, eng_team_structure_designer.py) do not exist in the bundle, so the guidance is concrete in form yet not actually runnable as written.	3 / 5
Workflow Clarity	Four workflows are sequenced with numbered steps and time budgets, but explicit validation/verify-then-proceed checkpoints are absent or only implicit, leaving sequence present but checkpoints missing.	3 / 5
Progressive Disclosure	Structure is well-organized on paper with one-level-deep references to four references/*.md files, but those referenced files (and the scripts/ directory) are absent from the bundle, so the navigation the body advertises is broken.	3 / 5
	Total	12 / 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.

The description is strong: it enumerates four concrete capability domains, gives explicit 'Use when' triggers, and draws a sharp boundary against the adjacent CTO skill. The only minor weakness is that some natural synonyms (DORA, MTTR) appear only in the body rather than the description itself.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capability areas with specifics — 'DORA 4 metrics + bottleneck identification', 'sourcing → screen → onsite → offer conversion', 'squad/tribe/chapter design + tech-lead manager-trigger thresholds', 'on-call, deployment cadence, postmortem culture' — giving comprehensive coverage rather than minor gaps.	5 / 5
Completeness	Explicitly answers both 'what' (four enumerated advisory domains) 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 and an explicit negative boundary.	5 / 5
Trigger Term Quality	Natural triggers like 'sprint velocity is dropping', 'eng hiring is broken', 'team structure is unclear', and 'deciding when to add a tech-lead manager' are phrases users would say, but some synonyms (DORA, MTTR variants) live only in the body, not the description.	4 / 5
Distinctiveness Conflict Risk	The negative boundary clause ('NOT a CTO skill — VPE owns delivery operations and how the team ships') carves a clear niche with distinct triggers and minimal conflict risk against sibling C-level skills.	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/skills-vpe-advisor/SKILL.md
Commit: 19392f7

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