app store optimization

v1.0.0

App Store Optimization (ASO) specialist skill for mobile apps. Use this skill whenever the user mentions ASO, app store ranking, keyword optimization for app...

0· 212·1 current·1 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The name/description (App Store Optimization) matches the runtime instructions and included references (keyword research, metadata, visuals, competitive analysis, full strategy). All reference files are relevant to ASO and the deliverables described. There are no unrelated requirements (no cloud creds, no unrelated binaries).
Instruction Scope
SKILL.md prescribes an interactive, two-step workflow (extract context, present diagnosis and ask for confirmation) and only loads local reference files on demand. It does not instruct reading system files, environment variables, or sending data to external endpoints. It will ask users for app-specific data (metrics, assets) which is appropriate for the stated purpose.
Install Mechanism
No install spec and no code files beyond local reference docs — the skill is instruction-only, so nothing is written to disk or downloaded during install.
Credentials
The skill declares no environment variables, credentials, or config-path access. References mention third-party ASO tools (AppTweak, Sensor Tower, etc.) as optional data sources, but the skill does not require those credentials.
Persistence & Privilege
Flags show default behavior (always:false, agent-invocable), so it does not force persistent inclusion. The skill does not request to modify other skills or system-wide settings.
Assessment
This skill appears coherent and safe as an instruction-only ASO advisor. Before using it: (1) don't paste sensitive credentials (App Store Connect, Play Console, or third-party ASO API keys) in chat — if you must connect tools, prefer limited API keys and explicit integration channels; (2) expect the skill to ask for app metrics, example screenshots, or current metadata — share only what you're comfortable disclosing; (3) treat outputs as expert recommendations that you should validate with your ASO tooling and analytics (keyword volumes, ranking data) before making store changes; (4) note the skill enforces a mandatory confirmation checkpoint before producing full reports — this prevents unsolicited long exports. If you need the skill to fetch live ranking or download data, that will require external tool credentials or exports, which is outside the skill's current declared scope.

Like a lobster shell, security has layers — review code before you run it.

latestvk9763sp6vegde1zxx7w0z4c4b982r9mg

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments