Add usage-efficiency-audit to use case library - #112
Open
rezakhadjavi wants to merge 2 commits into
Open
Conversation
added 2 commits
June 2, 2026 18:36
Two skills (audit + setup) packaged for installation through the use case library. When the team crosses 80% of their plan in a billing cycle, Runneth pulls their cycle's conversation history, runs personalized pattern detection across re-pasted context, repeating workflows, skill mismatches, over-scoped threads, and re-derived knowledge, builds an openable HTML page with the highest-leverage recommendations, and posts a friend-voice note to Slack with the link. Fires once per cycle. Customer-facing copy guardrails enforced throughout: no dollar figures, no scarcity framing, no internal pricing terminology. Setup captures Slack channel, optional tags, and billing anniversary day. Daily watcher reminder schedules itself on install.
…month end Setup was rejecting days 29 through 31 to dodge the February edge case. That's wrong: real customer billing cycles land on those days all the time, and the right behavior is to clamp the anniversary to the last day of any month that doesn't contain that day (Feb 29 in non-leap years, Apr 31, etc), which is how Stripe handles it. Setup now accepts 1-31. Main skill cycle math uses safe_anniversary() that clamps to the last valid day of the target month. Validated against day 29 (the customer case) across leap-year and non-leap February, plus day 31 across April and Feb.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds the
usage-efficiency-audituse case to the library so it can be installed into customer sandboxes from the link.What this is
Two skills packaged behind one install:
usage-efficiency-audit(the watcher + audit). Runs daily, silent. When the customer crosses 80% of plan in the cycle, pulls their cycle's conversations from local Postgres, runs Claude-powered pattern detection across five categories (re-pasted context, repeating workflows, skill mismatches, over-scoped threads, re-derived knowledge), builds an openable HTML page, and posts a friend-voice note to Slack with the link. Fires once per cycle.setup-usage-efficiency-audit(the one-time install). Captures Slack channel, optional user tags, and billing anniversary day. Schedules the daily watcher reminder.Customer-facing copy guardrails
The customer never sees dollar figures, internal pricing tiers, or scarcity language. They only see percentage of plan used, days until reset, and (when usage trajectory warrants it) one optional line that the next tier 3x's their usage.
Files added
usage-efficiency-audit/use-case.jsonusage-efficiency-audit/marketing.mdusage-efficiency-audit/install-config.jsonusage-efficiency-audit/post-install-intro.mdusage-efficiency-audit/README.mdusage-efficiency-audit/SKILL.mdusage-efficiency-audit/setup-usage-efficiency-audit/SKILL.mduse-case-library-site/frontend/src/icons/bars-rising-filled.svg(new icon)use-case-library-site/frontend/src/Illustration.tsx(import + slug map).use-case-library/catalog.json(slug registered)Validation
All six required library files pass the validation checklist from
use-case-library-add: use-case.json has all six fields and a valid category, marketing.md has frontmatter + three standard sections, install-config.json changelog notes are strings, SVG is 24x24 with currentColor on paths, Illustration.tsx has both the import and the slug map entry, catalog.json has the slug registered.Not merging
Leaving for you to review and merge. Per Rabia's workflow rules, every merge to main needs explicit approval per change.