ee-billing

Surface workflow for billing in Grida — Stripe (subscriptions) + Metronome (AI credit ledger). The stable contracts: `grida_billing.*` is not REST-exposed (views/RPCs only), `fn_billing_apply_*` are the single mutation points, webhook receivers are `GRIDA-SEC-001`, BYOK is the `GRIDA-SEC-003` carve-out. Use when touching `editor/lib/billing/`, `editor/scripts/billing/`, the `grida_billing` schema, the webhook receivers, or the entitlement gate. Companion to `ee`.

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An exemplary instruction-only surface skill: concise, concrete, with an explicit validation-gated workflow and disciplined progressive disclosure that points to docs and sibling skills instead of restating them. No meaningful weaknesses to address.

Dimension	Reasoning	Score
Conciseness	Lean and dense with specific contracts; assumes Claude's competence (never explains what Stripe/Metronome/subscriptions are) and every section earns its place with no padding.	3 / 3
Actionability	Provides copy-paste-ready commands (`pnpm tsx editor/scripts/billing/cli.ts setup:stripe`, the vitest E2E command) and exact function, file, and env-var names — fully actionable guidance.	3 / 3
Workflow Clarity	The 'Working on billing' section is a clear 6-step sequence with an explicit validation gate in step 5 (the E2E suite 'refuses to start unless every channel is demonstrably test-mode').	3 / 3
Progressive Disclosure	No bundle files exist; setup is delegated to docs ('cite it, don't restate it'), references are one-level-deep and clearly signaled to docs and sibling skills, and sections are well-organized for navigation.	3 / 3
	Total	12 / 12 Passed

Description

85%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A specific, well-scoped description that answers both what and when with explicit trigger guidance and a clear niche. The only weakness is that the trigger terms lean on technical file paths rather than natural-language phrasings a contributor would actually say.

Suggestions

Add natural-language trigger variants to the 'Use when' clause (e.g., 'subscriptions', 'AI credits', 'webhooks', 'entitlement gating') alongside the file paths so the skill surfaces for conversational billing requests, not just path-based ones.

Dimension	Reasoning	Score
Specificity	Names multiple concrete contracts and artifacts — `grida_billing.` not REST-exposed, `fn_billing_apply_` as the single mutation points, webhook receivers `GRIDA-SEC-001`, BYOK `GRIDA-SEC-003` — rather than vague language.	3 / 3
Completeness	Clearly answers what (surface workflow for Stripe subscriptions + Metronome credit ledger and its stable contracts) and when, via an explicit 'Use when touching ...' clause.	3 / 3
Trigger Term Quality	The natural term 'billing' appears alongside Stripe/Metronome, but the explicit 'Use when' triggers are technical file paths and schema names rather than common natural-language variations a user would say.	2 / 3
Distinctiveness Conflict Risk	A tightly scoped billing niche tied to exact file paths and marked 'Companion to `ee`', making it unlikely to trigger for the wrong skill.	3 / 3
	Total	11 / 12 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 8 suspicious	Warning

	Total	15 / 16 Passed

Repository: gridaco/grida
Path: .agents/skills/ee-billing/SKILL.md
Commit: 2e0d276

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.