mcpField
S
subscription-entitlement-review

subscription-entitlement-review

github.com/sylphxaiDevelopment153 installsUpdated today
Repository

About subscription-entitlement-review

subscription-entitlement-review is a skill for aligning billing events, product access, and support records. It helps teams model subscription states, channel precedence, audit events, risks, and acceptance checks, including paused, restored, and offline access.

Key features

  1. 01Subscription-state mapping
  2. 02Entitlement derivation review
  3. 03Channel precedence table
  4. 04Upgrade and renewal edge-case checks
  5. 05State machine and audit-event planning
  6. 06Acceptance checks and risk identification

Use cases

  1. 01Auditing entitlement behavior across billing channels
  2. 02Reviewing upgrade, cancellation, and refund paths
  3. 03Defining paused, restored, and offline access
  4. 04Preparing support traceability and acceptance checks

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/sylphxai/skills --skill subscription-entitlement-review

After installing, type/subscription-entitlement-reviewin Claude Code to confirm it loaded.

Bundled filesagents/openai.yamlreferences/subscription-entitlement-patterns.md

Details

From the project README

Subscription Entitlement Review

Use this skill to keep money movement, product access, and support truth aligned.

Workflow

  1. Identify billing model, platform/provider, product catalog, and entitlement surfaces.
  2. Read references/subscription-entitlement-patterns.md.
  3. Map subscription states, entitlement derivation, ledger events, support views, and user messaging.
  4. Build an explicit channel precedence table for web, App Store, Google Play, team invoice, family sharing, and manual support overrides.
  5. Check upgrades, downgrades, trials, grace, cancellation, refund, restore, offline access, duplicate events, and renewal failure paths.
  6. Model paused, restored, and offline entitlements as explicit states with entry/exit criteria, TTL/effective dates, user copy, and reconciliation behavior.
  7. Produce a state machine, audit events, risks, and acceptance checks.

When not to use

  • Do not use when the job belongs to saas-subscription-pricing — Defer when the job matches saas-subscription-pricing instead.
  • Do not use for generic advice the base model already handles without this skill's specific artifact contract.

Guardrails

  • Do not treat client UI state as the source of truth for durable access.
  • Do not mix cancellation, refund, failed renewal, and fraud into one state.
  • Preserve user trust with clear access consequences and support traceability.
  • Do not leave paused, restored, or offline access as vague events; name whether each grants, limits, resumes, or expires access.
  • Do not let a restore action create access until provider truth is verified and reconciled against existing ledger facts.

Output format

Billing model:
Provider/platform:
Entitlement surfaces:

State model:
- <state> -> <meaning and transition>

Paused/restored/offline states:
- paused:
- restored:
- offline_access:

Channel precedence:
| Source | Grants | Conflicts | Resolution |
| --- | --- | --- | --- |

Audit events:
- <event> <required fields>

Risks and fixes:
- <rule id> <risk> -> <fix>

Support/readiness checks:
- <check>

Comments

Markdown supported