Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →zzafergok/cto-advisor
Technical leadership guidance for engineering teams, architecture decisions, and technology strategy. Includes tech debt analyzer, team scaling calculator, engineering metrics frameworks, technology evaluation tools, and ADR templates.
Passed 13 of 22 test cases with the skill, and 12 of 22 without it.
3 fixed10 passed either way7 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
I am structuring my weekly schedule as an engineering executive. On Tuesdays, I usually hold general department updates and 1:1s. What specific recurring engineering governance and hiring activities belong on the Tuesday schedule?
| Checked | Without skill | With skill |
|---|---|---|
| Includes architecture review on Tuesday | Passed | Passed |
| Includes technical interviews on Tuesday | Missed | Passed |
The instructions your model reads when the skill loads.
Connect technical choices to business outcomes, delivery capacity, operational risk, and organizational constraints.
Clarify the company stage, product strategy, revenue or mission model, risk tolerance, funding horizon, regulatory context, team shape, and decision deadline. Separate immediate operational pressure from structural problems.
Create an evidence-backed inventory. Evaluate debt by customer impact, incident risk, delivery drag, security exposure, recurring operational cost, and cost of delay. Recommend a portfolio rather than a blanket cleanup: prevent new debt, contain critical risk, retire high-cost debt, and tolerate low-impact debt explicitly.
Align ownership boundaries with product and platform boundaries. Review cognitive load, decision latency, on-call burden, management span, skill concentration, and cross-team dependencies. Do not prescribe a reorganization without explaining transition cost and the behavior it is intended to change.
Use metrics to answer an operating question, not to rank individuals. Combine delivery flow, reliability, quality, security, customer outcomes, and team health. Define each metric, data source, cadence, owner, expected behavior, and gaming risk.
Evaluate functional fit, integration cost, security and compliance, data portability, service reliability, support, pricing sensitivity, exit cost, and roadmap alignment. Verify current vendor facts before relying on them.
Present options with tradeoffs and recommend a path proportionate to the evidence. Include assumptions, decision owner, near-term actions, longer-term implications, leading indicators, risks, and a review date. Distinguish strategic recommendations from architecture or implementation details that require deeper technical analysis.
test cases passed, vs 12 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.