00PrabalK00/app-store-metadata-builder
skills/app-store-metadata-builder/SKILL.md
Draft app titles, descriptions, changelogs, and keyword sets for app-store releases. Use when preparing App Store or Play Store metadata.
development
Updated Mar 23, 2026
$ install --global
skillsauthnpx skillsauth add 00PrabalK00/claude-skills app-store-metadata-builderInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
4 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
4
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Mar 23, 2026, 11:32 PM81.5s2 files scanned
SKILL.md
- name:
- app-store-metadata-builder
- description:
- Draft app titles, descriptions, changelogs, and keyword sets for app-store releases. Use when preparing App Store or Play Store metadata.
App Store Metadata Builder
Overview
Draft app titles, descriptions, changelogs, and keyword sets for app-store releases.
Core Workflow
- Gather the source material, existing conventions, templates, and destination format before drafting.
- Extract the information that matters most for the intended audience and discard low-signal noise.
- Structure the output so it matches repo, team, or domain expectations instead of starting from a blank generic outline.
- Draft the artifact, then surface any missing facts or decisions that still need human input.
Deliver
- A ready-to-edit draft in the expected structure and tone.
- The main sections, decisions, or states the artifact should include.
- Open questions or missing facts that would improve the final output.
Guardrails
- Do not invent facts, metrics, approvals, or guarantees that are not supported by the inputs.
- Prefer existing repo or team conventions over generic formatting.
- Keep the output useful and specific rather than padded.
- Prefer repository evidence, command output, and nearby tests over vague intuition.
Related Skills
00PrabalK00/vendor-evaluation-scorecard
tools
VerifiedTrustedCommunity
Compare vendors or tools using weighted criteria, tradeoffs, risks, and recommendation logic. Use when selecting platforms or partners.
SKILL.mdUpdated Mar 23, 2026
00PrabalK00/user-interview-synthesizer
data-ai
VerifiedTrustedCommunity
Extract needs, pain points, quotes, and behavioral patterns from user interviews. Use when synthesizing qualitative research.
SKILL.mdUpdated Mar 23, 2026
00PrabalK00/user-feedback-clusterer
databases
VerifiedTrustedCommunity
Group user feedback into themes, bugs, requests, sentiment, and confusion points. Use when analyzing feedback corpora.
SKILL.mdUpdated Mar 23, 2026
00PrabalK00/test-writer-coverage-closer
testing
VerifiedTrustedCommunity
Find missing coverage, design useful unit or integration tests, add fixtures or mocks, and explain remaining edge cases. Use when a feature lacks tests, a bug needs regression coverage, or coverage gaps block confidence.
SKILL.mdUpdated Mar 23, 2026