← AppLaunchFlowCONTENT HISTORY
WHAT CHANGED
changed
Update to AppLaunchFlow
Snapshot Nov 18, 2026 · 18:11 UTC · version 1.2.1
Collection source: downloaded plugin package.
Supporting file metadata differs
Supporting file metadata differs
Observed in package metadata. These changes alone do not establish a new customer-facing feature.
Save AppLaunchFlow and check future changes in Following.
Up to 3 plugins free · no card required.
All fields and original values.
Supporting files
Before
Oct 28, 2026 · 12:30 UTC
[{"relative_path":"references/tool-catalog.md","size_in_bytes":8156}]
After
Nov 18, 2026 · 18:11 UTC
[{"relative_path":"references/tool-catalog.md","size_in_bytes":7383}]
Compare saved observations
Download comparison JSONSKILL.md text changes
− removed · + added
No SKILL.md text changes between these observations.
Full technical diff · 1 changed fields
changed /included_files
BEFORE
[
{
"relative_path": "references/tool-catalog.md",
"size_in_bytes": 8156
}
]AFTER
[
{
"relative_path": "references/tool-catalog.md",
"size_in_bytes": 7383
}
]Full snapshot data
{
"description": "Draft, edit and localize AppLaunchFlow App Store and Google Play listing text while preserving existing languages, claims and store character limits.",
"included_files": [
{
"relative_path": "references/tool-catalog.md",
"size_in_bytes": 7383
}
],
"name": "applaunchflow-store-copy",
"skill_md_contents": "---\nname: applaunchflow-store-copy\ndescription: Draft, edit and localize AppLaunchFlow App Store and Google Play listing text while preserving existing languages, claims and store character limits.\n---\n\nCheck that the workflow's named tools are exposed by this host. If one is absent, use the matching AppLaunchFlow editor link and explain the specific step that needs the dashboard; don't claim the step completed.\n\n# Preserve product truth and scope\n\nResolve the project and linked store app with `get_project`. Separate the user's goal: listing copy, keyword discovery/rank monitoring, or publishing to a store. The audited MCP edits listing data and tracking; store publishing happens in the dashboard.\n\nFor existing copy, `get_store_listing` gives the saved source and languages. `update_store_listing` applies requested fields while preserving other languages and AI insights. `generate_store_listing` creates AI copy; use it for a requested draft rather than replacing copy for a small correction. Explicit replacement can retire a variant. `translate_store_listing` creates/refreshes localized copy; inspect existing languages before overwriting edited translations.\n\nKeep app capabilities and claims grounded in user/project input. Respect the tool's store-specific bounds: app name 30 characters, iOS subtitle 30 versus Play short description 80, iOS promotional text 170, descriptions 4000, iOS keyword field 100; release-note limits depend on store. A locale-specific correction should change that locale only.\n\nFor keyword research or monitoring, use the separate [keyword tracking skill](../applaunchflow-keywords/SKILL.md). Do not confuse changing the stored iOS keywords text field with adding tracked search terms.\n\nSee [the store-copy tool catalog](references/tool-catalog.md) for fields and language inputs. Preview exact proposed copy and character counts when a limit is close. Say that copy was saved in AppLaunchFlow, not published to a store.\n"
}SHA-256 of public snapshot: e7d1459160b809fd89051bb43759efea1fe39804c08b0e6b4ef067b6d0ba0452