mcpField
C
cawplan-product-insights

cawplan-product-insights

github.com/cawcutData & databases1142 installsUpdated 2d ago
Repository

About cawplan-product-insights

cawplan-product-insights is a skill for product teams reviewing CawPlan feedback trends and active critical issues. It verifies the product before fetching data and distinguishes available insights from retired adoption metrics.

Key features

  1. 01Resolve and confirm a product
  2. 02Fetch AI feedback categories and trends
  3. 03Review active critical issues
  4. 04Highlight shifts and outliers
  5. 05Identify retired adoption metrics

Use cases

  1. 01Summarize leading feedback categories
  2. 02Check active blockers and severity
  3. 03Spot notable changes in feedback

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/cawcut/skill-cawplan --skill cawplan-product-insights

After installing, type/cawplan-product-insightsin Claude Code to confirm it loaded.

Details

From the project README

CawPlan Product Insights

Bootstrap

cawplan skill check

Workflow

  1. Resolve product name to product_id:

    cawplan products list --search "<product name>"

    Continue only after one exact accessible product-name match (case-insensitive after trimming whitespace), one unique short-form/token-prefix match, or an explicit user confirmation of a candidate. If the user's stated product is absent or ambiguous, list the candidates and ask which product they mean; never silently choose a non-unique similarly named product. Do not fetch insight sources until the product is confirmed. Report NO_PERMISSION only for an explicit access-denied response.

  2. Fetch all insight sources in parallel:

    AI feedback analytics (feedback categories and trends):

    cawplan analytics get <product_id> --time_range 1m

    Critical issues (active blockers and incidents):

    cawplan critical list <product_id>

    There is no adoption/device-metrics source here anymore — the public endpoint behind cawplan metrics get (installations, crash rate, offline rate) has been retired. If the user specifically wants that data, tell them it's no longer available via CLI rather than silently omitting it or substituting something else.

Output

Structure the insights as:

  • User feedback: top feedback categories, notable shifts.
  • Critical issues: count and severity of active blockers.
  • Key takeaways: 2–3 bullet points on what needs attention.

Highlight notable shifts or outliers. Avoid overstating causality.

Decision Guide

  • For a business metric trend (subscriptions, CawPlan tickets, QA, workflow, tokens, API usage): use /cawplan-metrics. Device/app adoption metrics are no longer available via CLI at all.
  • For feedback categories only: use /cawplan-analytics.
  • For date-range activity report: use /cawplan-product-report.

References

  • references/CAWPLAN_OPEN_API.md

Comments

Markdown supported