Menu
Covers pricing frameworks and commercial patterns including usage-based, subscription, and hybrid models. Use when designing pricing tiers, migration strategies, or assessing commercial viability of features.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | commercial-models |
| description | Covers pricing frameworks and commercial patterns including usage-based, subscription, and hybrid models. Use when designing pricing tiers, migration strategies, or assessing commercial viability of features. |
| user-invocable | false |
This skill covers pricing frameworks and commercial patterns for Datum Cloud services.
Charge based on consumption:
| Model | Unit | Example |
|---|---|---|
| Per-request | API call | $0.001 per request |
| Per-resource-hour | Time × count | $0.05 per VM-hour |
| Per-unit | GB, CPU, etc. | $0.10 per GB |
Best for: Variable consumption, pay-as-you-go
Fixed recurring charge:
| Tier | Price | Includes |
|---|---|---|
| Free | $0 | Limited features, quota |
| Pro | $99/mo | Full features, higher quota |
| Enterprise | Custom | Everything + support |
Best for: Predictable revenue, committed customers
Subscription + usage overage:
Base: $99/month (includes 1000 requests)
Overage: $0.01 per request over 1000
Best for: Baseline predictability with growth flexibility
Purpose: Evaluation and adoption
Design principles:
Purpose: Production workloads
Design principles:
Purpose: Large organizations
Design principles:
Show the most expensive option first to anchor perception.
Frame price in terms of value, not cost:
Use round numbers for simplicity:
Consumers value bill predictability:
Keep existing customers on old pricing:
Move customers over time:
Switch everyone at once:
capability-quota — Quota implementationCovers GitHub conventions for pull requests, issues, and comments including linking, language style, formatting, and callout syntax. Use when creating PRs, writing issues, or posting comments on Datum Cloud repositories.
Turn raw engineering notes, PR/issue links, commit messages, or a one-line feature description into a changelog entry for Datum Cloud's GitHub Discussions Changelog category: a benefit-led title plus a markdown body, drafted for users and ready to hand off for final capture and publish. Use when someone says "write a changelog entry", "announce this in the changelog", or "post this to the changelog discussions" — this is the community-facing changelog POST, not the Keep a Changelog release file (that lives in `gtm-templates`).
Provides templates for go-to-market communications including blog posts, changelogs, social media, and enablement briefs. Use when writing launch announcements or marketing content.
Create a new GitHub release. Verifies CI is green on the release commit and refreshes the third-party NOTICE file before tagging, determines the next version from the latest tag, summarizes merged PRs since the last release, drafts release notes in the established style, and publishes via gh release create. Works for any datum-cloud service repository.
Scan a project repository for strict AGPL-3.0 license compliance across Go, Rust, and JavaScript/React codebases. Use this skill whenever the user asks to check, audit, verify, or enforce AGPL license compliance on a project, repo, or codebase. Triggers on phrases like "check agpl compliance", "audit license headers", "is this project agpl compliant", "scan for license headers", "check my license files", "agpl audit", or any request involving ensuring a project is properly licensed under AGPL. Always use this skill — don't wing AGPL compliance checks from general knowledge.
Covers producing weekly operational reports for the Datum AI Edge. Use when asked for an ops review, traffic report, latency analysis, provisioning report, or edge performance summary. Guides metric queries, anomaly detection, and publishing to datum-cloud/engineering.