Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →refoundai/engineering-health
Help users build a sustainable engineering culture by measuring health through frameworks like Core 4, managing technical debt as leverage, and optimizing workflows with AI tools.
Passed 22 of 22 test cases with the skill, and 17 of 22 without it.
and 2 more in the full report
5 fixed17 passed either way0 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are trying to justify our AI coding assistant pilot. Most engineering managers say their devs save 2 hours a week, but our VP wants to know what target hours saved per week high-performing AI-forward engineering organizations typically report as a baseline. What baseline target should we set?
| Checked | Without skill | With skill |
|---|---|---|
| Identifies 8 to 10 hours saved per week as the baseline target reported by AI-forward engineering teams. | Missed | Passed |
The instructions your model reads when the skill loads.
Maintain high shipping velocity by balancing technical excellence with strategic developer investments.
Help the user with engineering health and productivity using insights from 18 guests and posts across Lenny's Podcast and Newsletter.
Chip Huyen: "It's really hard to measure productivity. So, I do ask people to ask their managers, "Would you rather give everyone on the team very expensive coding agent subscriptions or you get an extra head count?" Almost every one, the managers will say head count."
Compare the cost and output of AI tools against the value of additional headcount rather than just looking at raw productivity gains.
Inbal S: "The user of the AI tools to develop software needs to form a different thinking. You need to start figuring out how are you using these AI tools to help you be successful. And it's no longer just the actual code writing, it's really evolving your thinking to the big picture, to the connected experience, to connected systems."
Use AI to handle manual syntax so engineers can spend more time on high level system design and product understanding.
Mike Krieger: "We really rapidly became bottlenecked on other things like our merge queue. We had to completely re-architect it because so much more code was being written and so many more pull requests were being submitted. Over half of our pull requests are Claude Code generated."
Internal tools like merge queues must be re-architected to handle the massive increase in pull request volume generated by AI coding.
Nicole Forsgren: "So productivity, I think, is basically how much we can get done and how much we can do over time. And I think that's why it's so important to have this holistic measure because we can't just brute force it, right. And so that's why when my team and a bunch of my peers study productivity, we include this community effect because software is a team sport."
Avoid raw output metrics: instead, use a balanced view that includes team dynamics, sustainability, and workflow friction.
Sherwin Wu V2: "100% of our PRs are reviewed by Codex daily as well. So basically any code that goes into production that's merged in, Codex kind of has its eyes on and suggests improvements, suggests changes in the PRs."
As code volume increases, implement AI powered automated reviews to maintain quality without creating a manual bottleneck.
test cases passed, vs 17 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.