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

89%

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

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

A well-structured, highly actionable skill body with concrete commands, benchmark tables, and clear reference deferral. The main weakness is mild verbosity from the redundant Keywords list and repeated four-decisions framing rather than over-explanation of basic concepts.

Suggestions

Trim or relocate the long Keywords comma-list — it largely duplicates trigger terms already in the description and adds token cost without new guidance.

Reduce repetition of the four-decisions framing (it appears in the intro list, each Core Responsibilities section header, and the Workflows); state it once and reference forward.

Add an explicit validate/retry note in at least Workflow 1 (e.g., re-run the analyzer after applying a bottleneck fix to confirm improvement) to lift workflow clarity toward a feedback-loop model.

Dimension	Reasoning	Score
Conciseness	Mostly information-dense (benchmark tables, thresholds), but the long comma-separated Keywords list and the four-decisions framing repeated across intro, sections, and workflows could be tightened; some redundancy with the description.	3 / 5
Actionability	Fully executable guidance — concrete `python scripts/*.py` invocations, specific benchmark tables (DORA elite/low bands, funnel conversion rates), quantitative thresholds ("5-7 ICs without a manager = first EM hire"), and a worked funnel-math example.	5 / 5
Workflow Clarity	Four workflows each have a stated goal and numbered sequenced steps with commands and cross-checks (e.g., "Cross-check with cs-cto-advisor"); minor gap is the absence of explicit validate/retry feedback loops, though these are read-only analytical workflows so the destructive-cap does not apply.	4 / 5
Progressive Disclosure	Body is an overview that defers full frameworks to clearly signaled one-level-deep references ("See references/delivery_throughput.md for the full framework"); all four reference files and three scripts verified present, with a consolidated References section for navigation.	5 / 5
	Total	17 / 20 Passed

Description

100%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, concrete description that names specific capabilities across four VPE domains, gives explicit natural trigger phrases, and disambiguates from adjacent CTO and engineering-lead roles. Third-person voice is maintained throughout with no padding.

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" — with comprehensive coverage.	5 / 5
Completeness	Explicitly answers both what (four advisory domains with concrete sub-capabilities) 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").	5 / 5
Trigger Term Quality	Natural trigger phrases a user would actually say — "sprint velocity is dropping", "eng hiring is broken", "team structure is unclear", "deciding when to add a tech-lead manager" — plus role synonyms (VP of Engineering, VPE).	5 / 5
Distinctiveness Conflict Risk	Explicit disambiguation — "NOT a CTO skill (which owns architecture) — VPE owns delivery operations and how the team ships" — carves a clear niche with minimal conflict risk.	5 / 5
	Total	20 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

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

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