Design monetization
Use when: designing pricing strategy, tiers, subscriptions, trials, perpetual licenses, usage-based billing, or catalog-ready offering plans; does not create catalog entities.From its SKILL.md
npx -y skills add Sidub-Inc/Monaiq.AI.Plugin --skill design-monetizationAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 2 stars2 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.
SKILL.md
7.7 KB, as published. Nobody here has run it
Also accepts from analyze-codebase (if chained directly):
- capabilities (optional): identified features to price
If invoked without upstream context, gathers requirements through conversation. </input-context>
<output-context> Provides to manage-catalog: - pricingPlan: { tiers: [{ name, classification, baseRate, currency, interval, features: [{ key, type, value }] }] } - productName: user's product nameDiscovery chain endpoint: design-monetization [pricingPlan] → manage-catalog (creates catalog entities from the plan) </output-context>
<execution_context>
Follows the skill layout and shared workflows in _shared/protocols.md. This skill contributes only catalog-ready pricing strategy and feature-assignment recommendations; catalog mutation belongs to manage-catalog.
</execution_context>
- Scenario provided, no existing offerings -> use scenario to inform tier design.
- No upstream context -> gather product, customer, and pricing-model constraints through conversation.
- Existing offerings -> show current pricing and offer refinement.
Gather Context
Determine design inputs from available context:
- If
scenario-advisorwas run: use the selected scenario (app type, chosen model, feature types) to inform tier structure - If
analyze-codebasewas run: use identified capabilities and their classifications - If neither: gather from conversation — ask what the product does, who the customers are, and what pricing model they want
Infer the appropriate number of tiers from: scenario-advisor output (if available), application complexity, identified feature count, and market norms for the application type.
Propose Tier Structure
Using pricing patterns from monaiq://patterns/pricing, propose a complete tier structure:
| Tier | Name | License Type | Price | Interval | Features Included |
|---|---|---|---|---|---|
| 1 | [e.g., Free] | Subscription | $0 | 1 Month | [list with access/rate-limit values] |
| 2 | [e.g., Pro] | Subscription | $X | 1 Month | [list with access/rate-limit values] |
| 3 | [e.g., Enterprise] | Subscription | $Y | 1 Month | [list with access/rate-limit values] |
For each feature in each tier, specify:
- Feature flags (Access features):
AllowedorDenied - Usage limits (RateLimit features): quota value and time window (e.g., "1000 per hour")
<!-- /SEM-01-stopgap -->Unlimited tiers. When calling the
feature_offeringMCP tool, set bothRateLimitandSampleSecondsto the string"unlimited"for an uncapped assignment. The tool maps that input to the domain's zero-as-unlimited representation internally. Paid capped tiers set explicit positive values (e.g.RateLimit = 1000withSampleSeconds = 3600for 1000/hour).
Explain the rationale: why this many tiers, why these price points relative to each other, and which pricing pattern from monaiq://patterns/pricing this follows.
Refine with User
Present the proposal and invite feedback. Common refinements:
- Adjust tier count (add/remove tiers)
- Change feature inclusion (move features between tiers)
- Modify pricing (change base rates, intervals)
- Change license type (switch from Subscription to Perpetual — called
LicenseClassificationin Monaiq) - Add consumption metering (layer on usage limits)
Iterate until the user approves the tier structure.
Output Catalog-Ready Summary
Produce a final structured summary table ready for manage-catalog input:
| Tier Name | Code | License Type | Price | Currency | Interval | Included Features (FeatureKey: Value) |
|---|---|---|---|---|---|---|
| [name] | [code] | [type] | [price] | [currency] | [interval] | [feature1: Allowed, feature2: 500/hr] |
This table contains all fields needed by the manage-catalog skill to create the catalog: product code, offering codes, feature keys with assignment values.
Route to Catalog
Suggest: "To create this catalog in Monaiq, run the manage-catalog skill with the specification above."
<success_criteria>
monaiq://patterns/pricingwas fetched and used for pattern knowledge- Tier count was inferred from context, not a fixed default
- Complete tier structure was proposed up front
- User refined and approved the design
- Final output is a catalog-ready summary table with all manage-catalog input fields
manage-catalogsuggested as next step </success_criteria>