Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →vp-engineering
VP Engineering perspective - org design (team topologies), process improvement, cross-team dependencies, engineering culture, OKRs, incident management maturity, platform strategy, DX optimization, release management at scale
Passed 16 of 22 test cases with the skill, and 11 of 22 without it.
and 7 more in the full report
6 fixed10 passed either way5 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
During a major SEV-1 production outage, how frequently should the Communications Lead publish internal updates, external status page updates, and executive updates?
| Checked | Without skill | With skill |
|---|---|---|
| Mandates internal updates every 15 minutes during a SEV-1 incident. | Missed | Passed |
| Mandates external status page updates every 30 minutes during a SEV-1 incident. | Missed | Passed |
The instructions your model reads when the skill loads.
| Type | Purpose | Characteristics | Size |
|---|---|---|---|
| Stream-aligned | Deliver user/business value | Full-stack, autonomous, owns entire feature slice | 5-8 |
| Platform | Reduce cognitive load for stream teams | Internal products, self-service APIs/tools | 3-6 |
| Enabling | Help teams adopt new capabilities | Coaching, not doing; temporary engagement | 2-3 |
| Complicated subsystem | Deep specialist expertise | ML, payments, security, real-time systems | 2-4 |
| Mode | Description | When to Use |
|---|---|---|
| Collaboration | Teams work together closely | New capability discovery, high uncertainty |
| X-as-a-Service | One team provides, other consumes | Well-defined API/platform capability |
| Facilitating | One team coaches another | Skill transfer, technology adoption |
## Engineering Organization: [Company Name]
### Team Map
Stream-aligned Teams:
├── Team Alpha: [product area] (5 people)
│ Owns: [service/feature list]
│ Stack: [tech stack]
├── Team Beta: [product area] (6 people)
│ Owns: [service/feature list]
│ Stack: [tech stack]
└── Team Gamma: [product area] (5 people)
Owns: [service/feature list]
Stack: [tech stack]
Platform Team:
test cases passed, vs 11 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.