← ClonerrrCONTENT HISTORY
WHAT CHANGED
Update to Clonerrr
Snapshot Oct 24, 2026 · 13:42 UTC · version 1.0.0
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save Clonerrr and check future changes in Following.
Up to 10 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Audit an app's App Store or Google Play listing against its competitors with Clonerrr's App audit and turn the findings into a prioritised plan. Use when the user asks for an app store optimisation (ASO) review, why their listing is not converting, feedback on their title, keywords or screenshots, or what their recent reviews say.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 406
}
],
"name": "audit-app-listing",
"skill_md_contents": "---\nname: audit-app-listing\ndescription: Audit an app's App Store or Google Play listing against its competitors with Clonerrr's App audit and turn the findings into a prioritised plan. Use when the user asks for an app store optimisation (ASO) review, why their listing is not converting, feedback on their title, keywords or screenshots, or what their recent reviews say.\n---\n\n# Audit an app's store listing\n\nClonerrr's App audit reads a public App Store or Google Play listing, finds the apps it competes with, and grades the listing, keywords, screenshots, recent reviews and paid ads against them.\n\nWhat the user asks for comes first. If they only want one section, or a shorter answer, give that.\n\n## Steps\n\n1. **Get the store link.** The audit needs the app's App Store or Google Play link. If the user gave only a name, ask for the link; do not guess one.\n2. **Run it.** Call `run_app_audit` with `store_url`. A new audit takes a minute or two and is worked through a few steps per call:\n - While `status` is `running`, call `run_app_audit` again with the same `store_url`. Tell the user once that it takes a minute or two.\n - If it is still running after eight calls, stop, give the user `report_url` and say the report finishes filling in on its page.\n - An audit finished in the last three days comes back at once; `audited_on` says when the listing was read.\n3. **Answer from the findings** once `status` is `done`:\n - The store score and each section's score, then the `headline`.\n - The `priorities`, in the order given, each with what to change and why.\n - A link to `report_url`, where every section is laid out in full with the competitors side by side.\n4. **Go deeper on request.** Each entry under `sections` has the detail: the listing's checks with a grade and a fix, the searches with today's rank, the screenshots' first three to test, the complaints in recent reviews, and ad ideas. Useful follow-ups you can write yourself: a new title and subtitle from `title_to_test` and `subtitle_to_test` (30 characters each on the App Store), a rewritten description opening, screenshot captions. For an ad idea, call `get_ad_template` with its `built_on.id` and write the script.\n\n## What not to infer\n\n- Ranks come only from `searches`. A search with no `rank` means the app was not in the results read (`looked_at_top`), not that it can never rank.\n- Use only the numbers in the result. Do not estimate downloads, revenue or conversion rates.\n- The paid ads section reads Clonerrr's library, which is a sample. Never say a competitor does not advertise; say none of its ads are in the library.\n- A score is a comparison with the competitors found for this audit, not an absolute grade.\n\n## When it cannot run\n\n- The link is not an App Store or Google Play listing: say the audit covers those two stores only.\n- The tool says the day's limit is reached: tell the user and suggest trying tomorrow. Do not retry in a loop.\n"
}SHA-256 of public snapshot: a6c54c6c8d798d8ac46b66228161794fe86532b864bf9d6b1429c39b8dafbaa5