agentsclimarketplace

Building saas products

Skill VKK-00/agentic-project-lifecycle/plugins/agentic-project-lifecycle/skills/building-saas-products

Codex plugin for governing large software projects from discovery through release and operations.

Install
npx -y skills add VKK-00/agentic-project-lifecycle --skill building-saas-products

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 16 days oldThe repository was created 16 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when a hosted subscription product involves tenants or workspaces, pricing plans, entitlements, billing, activation, retention, churn, customer support, account lifecycle, or SaaS unit economics.

The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.1 KB, as published. Nobody here has run it

Building SaaS Products

Treat SaaS as product, business model, tenancy system, billing state machine, and continuously operated service—not merely hosted software.

Validate the business boundary

  • RULE-SAAS-01: Distinguish primary user, buyer, administrator, approver, and ideal customer segment. Define the painful workflow, willingness-to-pay assumption, acquisition motion, and first value event before expanding scope.
  • RULE-SAAS-02: Specify tenant ownership, membership, invitations, role-based authorization, plan entitlements, data isolation, export, retention, deletion, and ownership transfer. Keep identity, authorization, and entitlements separate.

Make money and access deterministic

  • RULE-SAAS-03: Model the complete subscription lifecycle: trial, checkout, activation, upgrade, downgrade, proration, failed payment, retries, grace period, suspension, cancellation, refund, reconciliation, and webhook idempotency. Assign a source of truth for subscription state.
  • RULE-SAAS-04: Define metric contracts for activation, time-to-value, retention, churn, expansion, revenue, support load, and quality guardrails. Each metric needs a formula, population, window, source, owner, baseline, and target.
  • RULE-SAAS-05: Track unit economics and cost-to-serve by tenant or core workflow. Set review thresholds for infrastructure, vendor, support, and AI costs before committing pricing.
  • RULE-SAAS-06: Do not open beta or GA without tested account deletion/export, support ownership, privacy handling, billing recovery paths, observability, and rollback.

Read discovery and economics, tenancy and billing, and activation and operations when those decisions are active.

Gives 0 of the 12 instructions most analytics metrics skills give

Counted across 368 of the 369 authors here whose files we hold, read 2026-08-06

  • read product marketing context before asking questionsin 18 of 368, across 12 files
  • use lowercase with underscores for event namesin 16 of 368, across 6 files
  • track events for decisions not vanity metricsin 15 of 368, across 5 files
  • use object-action format for event namesin 15 of 368, across 8 files
  • produce a tracking plan documentin 14 of 368, across 4 files
  • Call RUBE_SEARCH_TOOLS first to get current schemasin 13 of 368, across 2 files
  • establish consistent event naming conventions before implementingin 10 of 368, across 4 files
  • Verify dimension and metric compatibility before reportingin 9 of 368, across 2 files
  • Encrypt data at rest and in transitin 9 of 368, across 3 files
  • use snake_case for event namesin 9 of 368, across 5 files
  • monitor technical health during the testin 9 of 368, across 5 files
  • use consistent property namesin 8 of 368, across 4 files

Said here and by no other author read

  • Define user, buyer, and administrator roles before expanding
  • Specify tenant ownership, membership, and data isolation rules
  • Model the complete subscription and billing lifecycle
  • Define metric contracts for activation, churn, and revenue
  • Track unit economics and cost-to-serve per tenant
  • Keep identity, authorization, and entitlements separate

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.