New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Vpe Advisor

by borghei in borghei/Claude-Skills

VP of Engineering advisor on org design, productivity, quality, delivery, and capacity planning.

MITAuto-check passedDevOps & Cloud

Install Vpe Advisor

skills CLI
$ npx skills add borghei/Claude-Skills --skill vpe-advisor -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install borghei/Claude-Skills vpe-advisor --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/c-level-advisor/vpe-advisor .claude/skills/vpe-advisor && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
vpe-advisor
GitHub stars
881
Token cost
~2.3k tokens
SKILL.md length
1,018 words
Files
7 (incl. scripts, references)
Skills in repo
349
Repo updated
First seen
Licence
MIT

At a glance

VP of Engineering advisor on org design, productivity, quality, delivery, and capacity planning.

  • Works in 3 steps: Pull current state across 6 dimensions… → Run eng_org_health_scorer.py against the… → Translate prioritized gaps into a…
  • Scoring engineering org health
  • SKILL.md covers When to use this skill, Inputs the advisor expects, Workflows and Decision frameworks, plus 5 more sections
  • Runs Python scripts from its folder; calls python3

What it does

Vpe Advisor is an agent skill from borghei/Claude-Skills. VP of Engineering advisor on org design, productivity, quality, delivery, and capacity planning. Use when scoring engineering org health, designing the eng org, planning capacity, or building the productivity dashboard.

Its SKILL.md is about 2.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files, including scripts and reference files (for example `references/eng-productivity-and-quality.md`, `references/eng-strategy-and-roadmap.md` and `references/engineering-org-design.md`).

It sits in DevOps & Cloud, covering Operations and SOPs, Site reliability engineering and Platform engineering. The repository describes itself as: 385 AI skills, 77 expert agents, and 900 stdlib Python tools for every team: engineering, PM, marketing, C-level, compliance, business ops, research, and a LinkedIn toolkit… The licence is MIT.

When your agent uses it

  • Scoring engineering org health
  • Designing the eng org
  • Planning capacity
  • Building the productivity dashboard

Example prompts

  • “/vpe-advisor”

Requirements

  • Python 3

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. Pull current state across 6 dimensions (structure, delivery, quality,
  2. Run eng_org_health_scorer.py against the populated JSON.
  3. Translate prioritized gaps into a quarterly OKR for engineering.

What it can do on your machine

Read from SKILL.md and the folder at commit 4a698e8. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 3 files in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • python3

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Vpe Advisor loads about 2.3k tokens when it runs, and up to ~9.1k if it reads all its reference files. Until then it costs about 58 tokens; SKILL.md has 1,018 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~58
When it runs · the whole SKILL.md, loaded when a task matches
~2.3k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~9.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from borghei/Claude-Skills at commit 4a698e8, republished under its MIT licence (© borghei). 1,018 words, ~2,289 tokens.

Download SKILL.mdSave it as .claude/skills/vpe-advisor/SKILL.md (or your agent's skills folder). This skill also uses 6 other files; get the full folder from GitHub.
name
vpe-advisor
description
VP of Engineering advisor on org design, productivity, quality, delivery, and capacity planning. Use when scoring engineering org health, designing the eng org, planning capacity, or building the productivity dashboard.
license
MIT + Commons Clause
metadata.version
1.0.0
metadata.author
borghei
metadata.category
executive-leadership
metadata.domain
c-level-advisor
metadata.updated
2026-05-27
metadata.tags
engineering, vpe, leadership, productivity, dora, space, capacity, hiring, retention

VP of Engineering Advisor

The agent acts as a fractional VP of Engineering, focused on the people / process / delivery half of engineering leadership. Where the CTO is accountable for technical strategy and architecture, the VPE is accountable for the engineering organization that ships it.

Grounded in modern productivity frameworks (DORA + SPACE + DevEx), engineering management research (Camille Fournier, Will Larson, modern staff-eng tracks), and the operational realities of scaling engineering teams.

When to use this skill

  • Scoring engineering organization health across structure, productivity, quality, delivery, culture, talent
  • Designing or restructuring the engineering org: squads, platform, embedded, matrixed
  • Planning engineering capacity for the next 2–4 quarters
  • Building or refreshing the engineering productivity dashboard (DORA / SPACE / DevEx)
  • Defining the delivery model: agile, kanban, scrum, shape-up, hybrid
  • Planning the hiring pipeline and the performance management approach
  • Preparing the engineering section of the board deck (delivery, quality, talent, asks)

Inputs the advisor expects

  • Company stage, sector, headcount in engineering
  • Current org structure (squads, platform teams, embedded model)
  • Delivery metrics (DORA: deploy frequency, lead time, MTTR, change-fail rate)
  • Quality / reliability metrics (uptime, error rates, incident count)
  • Talent metrics (open req count, time-to-hire, regrettable attrition)
  • Spend posture (eng comp budget, tooling, cloud)
  • Top frictions (CEO, CPO, CTO, customers)

Workflows

Workflow 1 — Score engineering org health
  1. Pull current state across 6 dimensions (structure, delivery, quality, productivity, culture, talent).
  2. Run eng_org_health_scorer.py against the populated JSON.
  3. Translate prioritized gaps into a quarterly OKR for engineering.
bash
python3 vpe-advisor/scripts/eng_org_health_scorer.py \
  --input eng_state.json --format markdown
Workflow 2 — Build the productivity dashboard (DORA + DevEx)
  1. Capture latest delivery + experience metrics per team.
  2. Run eng_productivity_dashboard.py to classify each team (elite / high / medium / low) and surface top intervention candidates.
  3. Use output for the weekly engineering review and the board section.
bash
python3 vpe-advisor/scripts/eng_productivity_dashboard.py \
  --input team_metrics.json --format markdown
Workflow 3 — Plan capacity for the next 2–4 quarters
  1. Inventory teams, current headcount, attrition assumption, hiring plan, planned investment splits (run-the-business vs grow vs transform).
  2. Run eng_capacity_planner.py to project usable capacity and highlight bottleneck teams.
  3. Reconcile against product roadmap commitments.
bash
python3 vpe-advisor/scripts/eng_capacity_planner.py \
  --input capacity_inputs.json --format markdown

Decision frameworks

CTO vs VPE — where the line is

A common pattern at Series B+:

FunctionCTOVPE
ArchitectureOwnsConsults
Build-vs-buyOwnsConsults
Tech stack decisionsOwnsConsults
Infra strategyOwnsConsults
Org structureConsultsOwns
Hiring + retentionConsultsOwns
Delivery (how)ConsultsOwns
Productivity metricsConsultsOwns
Engineering cultureJointJoint
Roadmap deliveryJoint with CPOJoint with CPO

If you don't have both roles, the founder/CEO usually plays one of them implicitly. Make the split explicit before adding the second role.

Org shapes
ShapeFits whenBreaks when
Functional (FE, BE, infra)< 30 engineers, single productCross-team feature work; bottlenecks
Squad-based30–300 engineers, multi-productSquads too small (<5) or too rigid
Platform + product squads50+ engineersPlatform team becomes blocker
Matrix (capability + product)Large org with shared specialistsReporting confusion
Embedded in productStrong product-led cultureStandards drift across teams

The advisor will default to platform + product squads for ≥ 50 engineers. Squad target size: 4–8 engineers; smaller is fragile, larger sub-fragments naturally.

Delivery model — which one
  • Scrum — when work is stable, externally committed, deploy cycles are larger
  • Kanban — when work is reactive, unpredictable (platform, infra, support)
  • Shape-up / Basecamp-style — when product team is small, opinionated, and shippable cycles work
  • Hybrid — most production engineering teams default here

Don't enforce one model across all teams. Different teams need different shapes.

When to invest in platform engineering

Indicator: developer experience drag (slow CI, fragile dev env, weeks-long service onboarding) consumes >20% of engineering time on tax work.

Counter: platform engineering team building golden paths, self-service infra, internal developer portal, eval automation.

Start the platform team at ~30 engineers; size it ~10–15% of total engineering at scale.

Common engagements

Show full SKILL.md (416 more words)Show less
"We're shipping less than we used to. Why?"
  1. Pull DORA metrics — is it deploy frequency, lead time, or change-fail rate?
  2. Look at team-level numbers; "engineering is slow" usually means 2–3 specific teams.
  3. Check WIP — too much in-flight is the most common cause.
  4. Check on-call burden and incident frequency.
  5. Triangulate with DevEx survey (developer-reported friction).
"Help me plan engineering hiring for next year"
  1. Pull product roadmap commitments and translate to capacity (use eng_capacity_planner.py).
  2. Subtract current capacity (headcount × utilization × attrition).
  3. Identify the bottleneck capabilities (full-stack, ML, platform, security).
  4. Build the hire plan with stage gates.
"Our top engineers are leaving"
  1. Tag attrition: regrettable vs not.
  2. Pull exit interview themes for the last 6 months.
  3. Look at: comp band relative to market, manager quality, scope, autonomy.
  4. Prioritize the 2–3 root causes; design interventions and measure.
"Help me build the engineering section of the board deck"
  1. Delivery: DORA metric trends; top wins; top misses.
  2. Quality / reliability: uptime, incidents (count + severity), SLO posture.
  3. Talent: headcount, hires, regrettable attrition, key hires planned.
  4. Investment posture: run/grow/transform mix vs target.
  5. Asks: usually one budget, one organizational, one product-priority.

Anti-patterns to avoid

  • VPE without budget authority. Becomes a glorified scrum master.
  • DORA metrics as a stick. Use them as compass; never as employee performance.
  • Hiring without retention focus. Attrition is more expensive than slow hiring.
  • One delivery model across all teams. Platform and product teams have different shapes.
  • Promoting the strongest engineer to manager. Career ladder needs both IC and EM tracks.
  • Org redesign every 6 months. Stability wins; resist the urge.
  • Squad-of-three model at scale. Below 4 engineers, bus risk + on-call burden are unsustainable.
  • Engineering culture defined by perks. Real culture is in promotion criteria, hiring bar, incident response, code review norms.

References

  • references/engineering-org-design.md — org shapes, role definitions, hiring sequence
  • references/eng-productivity-and-quality.md — DORA + SPACE + DevEx, SLOs, on-call, quality programs
  • references/eng-strategy-and-roadmap.md — capacity planning, investment buckets, roadmap alignment
  • c-level-advisor/cto-advisor — technical strategy + architecture (peer to VPE)
  • c-level-advisor/cpo-advisor — product partnership
  • c-level-advisor/chro-advisor — talent / comp / hiring partnership
  • c-level-advisor/chief-data-officer-advisor — data team interface
  • c-level-advisor/chief-ai-officer-advisor — AI / ML team interface
  • engineering/observability-designer — SLO / SLI / error budgets
  • engineering/incident-commander — incident response practice
  • engineering/feature-flags-architect — safe deployment practice
  • engineering/chaos-engineering — reliability practice
  • engineering/senior-architect — technical decision making

Output expectations

When the advisor runs, you should walk away with:

  1. A clear point of view
  2. 2–4 concrete next actions with owners and timelines
  3. Open questions that materially change the recommendation
  4. References to scripts and reference docs that deepen the analysis

© borghei, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 6 other files (scripts, references) in c-level-advisor/vpe-advisor of borghei/Claude-Skills.

  • SKILL.md
  • references/eng-productivity-and-quality.md
  • references/eng-strategy-and-roadmap.md
  • references/engineering-org-design.md
  • scripts/eng_capacity_planner.py
  • scripts/eng_org_health_scorer.py
  • scripts/eng_productivity_dashboard.py

Open the folder on GitHubat commit 4a698e8

Compare with similar skills

Vpe Advisor next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Vpe Advisor compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Vpe Advisor this skillborghei/Claude-Skills881—~2.3kAutomated safety check: PassMIT
Knowledge Opsalirezarezvani/claude-skills28k—~4.1kAutomated safety check: PassMIT
Capacity And Cost Engineeringmagnus919/agent-skills113—~4.7kAutomated safety check: PassMIT
Release Engineeringmagnus919/agent-skills113—~3.9kAutomated safety check: PassMIT
Nw Platform Engineering FoundationsnWave-ai/nWave617—~1.1kAutomated safety check: PassMIT
Operationstravisjneuman/.claude101—~3.4kAutomated safety check: PassMIT

Similar skills

  • Knowledge Ops

    alirezarezvani/claude-skills

    A skill your agent uses when a Head of Ops, Knowledge Manager, or TPM-Internal needs to author, validate, or clean up company SOPs and internal runbooks (procurement intake, vendor offboarding…

    28k GitHub stars~4.1k tokensUpdated 1 mo ago
    DevOps & CloudAuto-check passed

  • Capacity And Cost Engineering

    magnus919/agent-skills

    Model technical capacity, unit cost, and budget constraints connected to demand, performance, and reliability decisions.

    113 GitHub stars~4.7k tokensUpdated yesterday
    DevOps & CloudAuto-check passed

  • Release Engineering

    magnus919/agent-skills

    Design, automate, and operate end-to-end software releases: release process models and pipelines (trunk-based development, CD stages, release trains), progressive delivery and feature flags…

    113 GitHub stars~3.9k tokensUpdated yesterday
    DevOps & CloudAuto-check passed

  • Nw Platform Engineering Foundations

    nWave-ai/nWave

    Foundational platform engineering knowledge from key references -- Continuous Delivery, SRE, Accelerate, Team Topologies, Chaos Engineering, and Secure Delivery.

    617 GitHub stars~1.1k tokensUpdated 21 days ago
    DevOps & CloudAuto-check passed

  • Operations

    travisjneuman/.claude

    Operations excellence expertise for supply chain optimization, process improvement (Lean, Six Sigma), capacity planning, vendor management, quality assurance, and operational efficiency.

    101 GitHub stars~3.4k tokensUpdated yesterday
    SecurityAuto-check passed

  • Money Ops

    iamzifei/show-me-the-money

    24/7 autonomous business operations orchestrator with business health scoring, canary monitoring, and safety guardrails.

    1k GitHub stars~3.8k tokensUpdated 1 mo ago
    DevOps & CloudAuto-check passed

More from borghei/Claude-Skills

All 349 skills in this repo

  • Agents In The Team

    borghei/Claude-Skills

    Run delivery when AI coding and ops agents take tickets. An agent skill from borghei/Claude-Skills.

    881 GitHub stars~4.2k tokensUpdated today
    Auto-check passed

  • AI Content Disclosure

    borghei/Claude-Skills

    Check AI-generated marketing content and reviews for required disclosures under the EU AI Act, FTC rules and platform AI-label policies.

    881 GitHub stars~3.4k tokensUpdated today
    Auto-check passed

  • AI Prototyping

    borghei/Claude-Skills

    Idea to AI-generated prototype to customer validation to engineering handoff.

    881 GitHub stars~3.6k tokensUpdated today
    Auto-check passed

  • Analytics Engineer

    borghei/Claude-Skills

    Analytics engineering across data modeling, dbt, transformation, and semantic layers.

    881 GitHub stars~3.4k tokensUpdated today
    Auto-check passed

  • Ansoff Matrix

    borghei/Claude-Skills

    Ansoff Matrix — 4-quadrant framework for growth options: market penetration, market/product development, and diversification.

    881 GitHub stars~2.2k tokensUpdated today
    Auto-check passed

  • Brainstorm Okrs

    borghei/Claude-Skills

    OKR brainstorming and validation using the Radical Focus framework — outcome objectives, measurable key results, counter-metrics.

    881 GitHub stars~1.4k tokensUpdated today
    Auto-check passed

Categories

Questions about Vpe Advisor

What does Vpe Advisor do?

VP of Engineering advisor on org design, productivity, quality, delivery, and capacity planning. Vpe Advisor is an agent skill from borghei/Claude-Skills. VP of Engineering advisor on org design, productivity, quality, delivery, and capacity planning.

When should I use Vpe Advisor?

Vpe Advisor fits situations like: scoring engineering org health; designing the eng org; planning capacity; building the productivity dashboard.

How do I install Vpe Advisor in Claude Code?

Run `npx skills add borghei/Claude-Skills --skill vpe-advisor -a claude-code`. Or copy the skill folder (c-level-advisor/vpe-advisor in borghei/Claude-Skills) into .claude/skills/vpe-advisor in your project. Claude Code loads it when a task matches its description.

How do I install Vpe Advisor in Codex?

Run `npx skills add borghei/Claude-Skills --skill vpe-advisor -a codex`. Or copy the skill folder (c-level-advisor/vpe-advisor in borghei/Claude-Skills) into .agents/skills/vpe-advisor in your project. Codex loads it when a task matches its description.

Can I use Vpe Advisor in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add borghei/Claude-Skills --skill vpe-advisor -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/vpe-advisor, .gemini/skills/vpe-advisor, .github/skills/vpe-advisor and .opencode/skills/vpe-advisor in your project.

What does Vpe Advisor need to run?

Going by SKILL.md and its folder, Vpe Advisor needs Python for the scripts in its folder and the command-line tools its instructions call (python3). Our summary lists: Python 3.

Does Vpe Advisor access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Vpe Advisor safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Vpe Advisor use?

Vpe Advisor is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Vpe Advisor use?

About 2.3k tokens (SKILL.md is roughly 9.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 6.8k tokens, read only when the agent opens those files.

What are the alternatives to Vpe Advisor?

Skills that share tags, products or a category with Vpe Advisor: Knowledge Ops (alirezarezvani/claude-skills, 28k stars), Capacity And Cost Engineering (magnus919/agent-skills, 113 stars), Release Engineering (magnus919/agent-skills, 113 stars) and Nw Platform Engineering Foundations (nWave-ai/nWave, 617 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Vpe Advisor?

borghei (a GitHub user) maintains it in borghei/Claude-Skills, which has 881 GitHub stars. The repository holds 349 skills in this directory. The repository was last updated on October 7, 2026.

Source: borghei/Claude-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.