metadata-audit
Audit and Improve App Store Metadata
App store listings can meet character limits while still using unclear copy or weak keywords. This skill combines ASOScan scores, recommendations, and change history with specific rewrites and localized drafts.
自分のエージェントでインストール
このリクエストをエージェントにコピーしてください。正規の Skill ページとマニフェストが含まれています。
Review the Skillstore skill "metadata-audit" from https://skillstore.io/skills/asoscan-metadata-audit.md and its manifest at https://skillstore.io/api/skills/asoscan-metadata-audit/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.エージェントは引き続き計画を提示し、セキュリティポリシーで必要な確認を求める必要があります。
エージェントが読めるリソース
AI エージェント、クローラー、スクリプトがページ全体ではなく整理されたコンテキストを必要とする場合は、これらのリンクを使ってください。
テストする
「metadata-audit」を使用しています。 Illustrative request: Rewrite a task planner listing with clear benefits and Apple character limits.
期待される結果:
- Suggested title: Focus List: Daily Planner. Character count: 25/30.
- Suggested subtitle: Plan tasks and stay focused. Character count: 27/30.
- Reason: The title identifies the product category, and the subtitle describes its practical benefit.
- Confirm that these statements match the app before submitting the text.
「metadata-audit」を使用しています。 Illustrative request: Explain why a metadata score of 25/25 does not mean the listing copy is optimal.
期待される結果:
- Metadata score: 25/25. This indicates completeness and character-limit compliance, not persuasive or relevant copy.
- Next review: Check whether the title uses a relevant search term and the subtitle states a clear benefit.
- Conversion scores may be estimates and cannot judge screenshot content.
セキュリティ監査
安全All 33 static findings are false positives: Markdown formatting and documented ASOScan operations do not demonstrate vulnerabilities. API authentication targets ASOScan over HTTPS, and the skill prohibits printing credentials. Paid AI calls and data changes require approval; no evidence found of prompt injection, credential exfiltration, or unrelated execution.
リスク要因
⚙️ 外部コマンド (30)
🌐 ネットワークアクセス (2)
🔑 環境変数 (1)
このレポートを共有・引用
バージョン付き評価レポート、中立的なバッジ、埋め込みカード、引用を共有できます。Skillstore は証拠を報告しますが、この Skill が安全かどうかは判断しません。
レポートリンクをコピー
https://skillstore.io/skills/asoscan-metadata-audit/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdownバッジ
[](https://skillstore.io/skills/asoscan-metadata-audit?utm_source=security_passport_badge)HTMLバッジ
<a href="https://skillstore.io/skills/asoscan-metadata-audit?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/asoscan-metadata-audit/security.svg" alt="Skillstore security assessment" loading="lazy"></a>埋め込みカード
<iframe src="https://skillstore.io/embed/skills/asoscan-metadata-audit.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>学術引用 (APA · BibTeX · CFF)
APA形式の引用
asoscan. (2026). metadata-audit security audit report (audit version 1) [Author version 1.3.7]. Skillstore. https://skillstore.io/skills/asoscan-metadata-audit/audits/1BibTeX形式の引用
@techreport{asoscan-asoscan-metadata-audit-2026,
author = {asoscan},
title = {metadata-audit security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/asoscan-metadata-audit/audits/1},
note = {Author version 1.3.7}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "metadata-audit security audit report (audit version 1)"
version: "1.3.7"
type: report
authors:
- name: "asoscan"
date-released: "2026-11-15"
url: "https://skillstore.io/skills/asoscan-metadata-audit/audits/1"
identifiers:
- type: other
value: "skillstore:asoscan-metadata-audit:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore スコア
このスコアの理由 証拠の信頼度: 中作成できるもの
Improve an independent app listing
Review an Apple listing, identify weak fields, and draft concise title, subtitle, and keyword changes with character counts.
Prioritize Google Play copy changes
Combine ASOScan recommendations, score limitations, and metadata history to prioritize accurate short and full description improvements.
Prepare localized listing drafts
Review saved locale drafts and request new variants after confirming costs, then compare character counts before manual store submission.
これらのプロンプトを試す
Audit [app name] on [platform] in [country]. Show ASOScan scores with denominators and suggest three specific metadata improvements.
Review [app name] on [platform]. Rewrite its title and subtitle or short description using [target keywords]. Include exact character counts and reasons.
Review metadata history and current ASOScan recommendations for [app name] in [country]. Prioritize field changes without claiming that history proves ranking effects.
Check saved [locale] drafts for [app name] first. Before generating or saving a new draft, explain the costs and wait for approval.
ベストプラクティス
- Confirm the app, platform, country, and current metadata before drafting changes.
- Use ASOScan scores with denominators and explain where completeness checks or conversion proxies limit interpretation.
- Keep credentials private and obtain approval before paid AI calls or data changes. Verify decision-critical platform limits against official documentation.
回避
- Treating a perfect completeness score as proof that listing copy or screenshots are optimal.
- Repeating Apple keywords, stuffing Google descriptions, or adding unsupported awards and ranking guarantees.
- Generating paid localization drafts without approval or presenting saved drafts as published store updates.