← AppLaunchFlowCONTENT HISTORY

Update to AppLaunchFlow

Snapshot Oct 28, 2026 · 12:30 UTC · version 1.1.0

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save AppLaunchFlow and check future changes in Following.

Up to 10 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Research and track AppLaunchFlow App Store or Google Play keywords, rank history and competitor apps; distinguish suggestions, tracked terms and listing metadata.",
  "included_files": [
    {
      "relative_path": "references/tool-catalog.md",
      "size_in_bytes": 12542
    }
  ],
  "name": "applaunchflow-keywords",
  "skill_md_contents": "---\nname: applaunchflow-keywords\ndescription: Research and track AppLaunchFlow App Store or Google Play keywords, rank history and competitor apps; distinguish suggestions, tracked terms and listing metadata.\n---\n\n# Resolve the linked app and market\n\nUse `get_project` to identify the linked App Store ID or Google Play package, then `list_keywords` and `list_keyword_competitors` for existing tracking. The tool resolves store/app context from that project; don't invent an app identifier or silently switch markets. Resolve country/language only when needed for the question. Linking or changing the store app requires the dashboard.\n\nCheck that each named tool is exposed by this host. If it is absent, give the relevant dashboard link and the specific limitation instead of inventing a call.\n\n# Research versus tracking\n\n`suggest_keywords` and `suggest_keyword_competitors` propose options; they do not add tracking. Ground recommendations in the actual app features and the user's target audience. State whether a value is observed data, a suggestion or your judgment. Do not promise a ranking gain.\n\nUse `add_keywords` or `add_keyword_competitors` only when the user wants those items tracked. Inspect duplicates first. Respect `get_plan_usage` and returned limit recovery; repeated additions cannot fix a full allowance.\n\nUse `remove_keywords` and `remove_keyword_competitors` only for the selected requested removals. Keyword text can match several country/store rows: scope precisely or use returned tracked IDs. Do not clean up other markets as a side effect of removing one term.\n\n# Report actual performance\n\n`get_keyword_history` provides historical rankings, not guaranteed attribution to a copy change. State app, store, country/language, time range, tracked term and missing data. Missing rank is not automatically zero. Do not turn one observation into a trend or compare incompatible markets.\n\nThe iOS keywords field belongs to [store copy](../applaunchflow-store-copy/SKILL.md); adding a tracked keyword does not edit that field or publish metadata. Alerts, competitor gap analysis and CSV export remain dashboard workflows unless the live capability catalog says otherwise.\n\nSee [the complete keyword tool catalog](references/tool-catalog.md) for scope/filter fields and supported history inputs.\n"
}

SHA-256 of public snapshot: 2785c64b4ffc8f6b23ec0f15cd2b018751032fb632124eddbd515c50e3becb90