AdYour product here, seen by people installing AI tools every day Sponsor slots open: 12 of 12, from $249 a month

provider-naming vs frb-debugging

provider-naming and frb-debugging are both developer tools skills. frb-debugging scores higher (84 vs 78 out of 100). frb-debugging has more GitHub stars (5.5k), and frb-debugging was updated more recently (4 days ago). The table compares them side by side.

provider-namingfrb-debugging
Score78 / 10084 / 100
What it doesEnforces consistent naming for provider auxiliary functions in src/providers/. Use when creating, renaming, or reviewing provider modules or their tests.Use when generated code looks wrong, code generation fails, or you need to understand FRB internals
PublisherCommunity: microlinkhqCommunity: fzyzcjy
GradesMaintenance A, Licence A, Quality AMaintenance A, Licence A, Quality A
npm downloads a weekNot on npmNot on npm
RunsSkillSkill
Works withClaude Code, Claude appsClaude Code, Claude apps
GitHub stars1,4735,460
Last commit19 Oct 202619 Oct 2026
LicenceMITMIT
Listed since19 Oct 202620 Oct 2026
Install provider-namingInstall frb-debugging

Questions

Is provider-naming or frb-debugging more popular?

frb-debugging has more GitHub stars: 5,460.

Can I use provider-naming and frb-debugging together?

Yes. AI assistants can load several skills at once. Install both and the assistant picks the right one for each task.