Flow Audit
Use when a client asks whether a Flow Builder flow is ready for production, wants it audited or checked, or asks something like "did I forget anything — triggers, products, variables?", "is this ready to publish?", or "check my paywall/flow". Answers one question — is this flow safe to put in front of paying users — with a verdict and ranked findings. Read-only: never writes to a flow. Complements `flow-generator` (which owns writes) and `paywall-teardown` (which owns conversion advice).
Install
/plugin marketplace add adaptyteam/adapty-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add adaptyteam/adapty-skills --skill flow-auditgit clone --depth 1 https://github.com/adaptyteam/adapty-skills.git /tmp/adapty-skills
mkdir -p ~/.claude/skills
cp -r /tmp/adapty-skills/plugin/skills/flow-audit ~/.claude/skills/flow-auditPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# flow-audit ## What this answers **Is this flow ready for production?** Not "here is a list of things about your flow" — a verdict: ready, or not ready and why, backed by ranked findings that each carry a concrete fix. A **blocker** is precisely a reason to answer no. This skill is **read-only**. It never calls `flows config update`, `products create`, or `flows create`. It cross-references the flow's config against the live dashboard (catalog, access levels) to catch what an offline checker structurally cannot — a bound product that does not exist, one with no store binding, a card whose copy claims a period the product does not have. When the user wants something fixed, hand it to `flow-generator`, which owns the backup, the approval gate, and the write. This skill does not implement transforms and does not touch the config on disk beyond the working copy it fetches to check. ## How you sound Every message, not only the report: - **A patient colleague who knows in-app purchases.** The user may be new to them. When they ask, answer plainly and use their own flow as the example. Friendly through patience, never through filler. - **"I" for what you do, "you" for what they do.** Lead with the answer; end on the one thing they need to do next. No opener, no recap, no "let me know if…". - **Plain words over raw values.** Show a value only when the user will type it or see it elsewhere — a placement ID, a builder label, a URL. Element ids, status codes and tool
Details
- Skill name
flow-audit- Repository
- adaptyteam/adapty-skills
- Path
plugin/skills/flow-audit/SKILL.md- License
- MIT
- Repo updated
- 18 November 2026
FAQ
What does the Flow Audit skill do?
Use when a client asks whether a Flow Builder flow is ready for production, wants it audited or checked, or asks something like "did I forget anything — triggers, products, variables?", "is this ready to publish?", or "check my paywall/flow". Answers one question — is this flow safe to put in front of paying users — with a verdict and ranked findings. Read-only: never writes to a flow. Complements `flow-generator` (which owns writes) and `paywall-teardown` (which owns conversion advice).
How do I install the Flow Audit skill?
Claude Code plugin: /plugin marketplace add adaptyteam/adapty-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Flow Audit popular?
It lives in adaptyteam/adapty-skills, which has 9 GitHub stars and 2 forks.
Related skills
Ab Tests
9adaptyteam/adapty-skills
Use when a user wants to run, check or end a regular A/B test of paywalls or flows through the Adapty CLI — plan it, create the draft, change it, start it, read its results, stop it with a winner, replace a running test with a changed one, archive it, or see which tests an app has. Triggers on "run an A/B test of these two paywalls", "test my new flow against the old one", "split traffic 50/50", "start the test", "stop the test, B wins", "end this experiment", "change the weights of my test", "which tests are running", "archive the old tests", "should I stop this test", "how did the test go",
Adapty Attribution
9adaptyteam/adapty-skills
Use when someone asks how their ad campaigns, channels, ad sets, ads, countries or keywords are performing in Adapty Attribution — ROAS, payback, CPI, cost per trial, installs, trial-to-paid, refunds, predicted revenue — which channel or campaign to scale or cut, where to move budget, why installs dropped, why Meta, TikTok or Google report different numbers than Adapty, or how to set up Adapty Attribution with Meta, TikTok, Google Ads, custom tracking links or a web funnel.
Adapty Docs
9adaptyteam/adapty-skills
Use when an Adapty question has no page already linked in the skill you are holding — how a product or dashboard feature behaves, what a setting does, a limit, store connections, Flow Builder, the Developer CLI, the server-side API, or an SDK method on any platform. Also use when you need a docs page and have no URL for it, or when a docs URL you tried returned 404. Not for making a change to an app's Adapty setup — connecting a store, or creating products, access levels or placements — which `adapty-integration` carries out through the Adapty CLI.
Flow Generator
9adaptyteam/adapty-skills
Use when a user wants to change an Adapty flow by editing its builder config JSON — add a locale, translate a paywall or onboarding, rewrite copy, add/remove/reorder screens, add tabs or plan pickers, wire quiz branching, or build an onboarding sequence — and also once a flow is published, to point a placement at it so an app can fetch it. Triggers on "edit my flow config", "add a language to my paywall", "translate my onboarding", "remove a screen from the flow", "add tabs to my paywall", "show the user's name or coin balance on my paywall", "add a Lottie animation, a map or a chart", "build
Convert State Machines to Actors
9kr4chinin/skills
Convert a database-backed implicit state machine to an actor, the one owner every writer of the persisted state goes through. Use when asked to put writers behind one owner, or to fix a race or lost update across several writers, such as a find-implicit-state-machines finding.
Project Building
9HOWILLMAKEIT/skills
建立和持续维护项目的工作方式与文档体系。用户要求创建 AGENTS.md、建立 docs、整理项目交接、沉淀开发或实验流程,或按已有项目规范推进工作时使用。编写或修改文档必须使用内置的 better-notes,核对来源、语言准确性和写作风格。适用于软件和研究项目;单纯概念问答、独立文件编辑或只读状态查询不因此自动触发项目文档写入。
Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.