We’re a dev team at ZEP and we had a problem: we rolled out Claude Code with a bunch of custom skills, but nobody was using them. Skill usage was sitting at around 6%. Devs had Claude Code, they just weren’t using the skills that would actually make them productive. The core issue was what we started calling the “Intention-Action Gap”: skills existed but were buried in docs nobody read, best practices stayed locked in the heads of a few power users, and there was no way to surface the right skill at the right moment. So we built an internal system (now open-sourced as Zeude) with three layers:
- Sensing: measure what’s actually happening We hooked into Claude Code’s native OpenTelemetry traces and piped everything into ClickHouse. For the first time we could see who’s using which skills, how often, and where people were doing things manually that a skill could handle.
- Delivery: remove all friction We built a shim that wraps the claude command. Every time a dev runs Claude Code, it auto-syncs the latest skills, hooks, and MCP configs from a central dashboard. No manual setup, no “did you install the new skill” Slack messages.
- Guidance: nudge at the right moment This was the game changer. We added a hook that intercepts prompts before Claude processes them and suggests relevant skills based on keyword matching. Someone types “send a message to slack” -> they get a nudge: “Try /slack-agent!” The right skill, surfaced at exactly the moment they need it. Results: skill usage went from 6% to 18% in about 2 weeks. 3x increase, zero mandates, purely driven by measurement and well-timed nudges. We open-sourced the whole thing: https://github.com/zep-us/zeude Still early (v0.9.0) but it’s been working for us. Anyone else dealt with the “we have the tools but nobody uses them” problem? submitted by /u/Lopsided_Yak9897
Originally posted by u/Lopsided_Yak9897 on r/ClaudeCode
You must log in or # to comment.