360 Secure SkillHub
360 安全技能中心

search

该 Skill 通过 AppFollow 搜索应用(只读,任意套餐可用),列出候选并检查是否已跟踪;经用户确认后可创建或复用集合、添加应用到跟踪,并输出包含已添加、已存在和未添加引用的 JSON。写入受套餐限制时会降级为仅报告候选,供反馈分析与 ASO 分析 Skill 继续使用。

AppFollow
热度 0.00
最近更新 2026-10-19 07:44:55
分类:营销依赖:第三方 API应用场景:市场分析 / 研究 / 工作流

安装技能

复制下面的话术发给你的 Agent,它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill: npx secure-skills-cli add appfollow/appfollow-ai-toolkit/search
Metadata
name
search
description
Find an app on the App Store / Google Play and start tracking it in AppFollow, then hand structured app references to the feedback-analysis and aso-analysis skills. Read-only search + dedupe works on any plan; the add step degrades gracefully when the plan does not allow writes. Trigger on "find app X", "track our app", "add <app> to AppFollow".

search — find + track apps

Read using-appfollow first (session opening, write ritual, error codes).

Inputs

  • query: app name (free-text search keywords).
  • store: as (App Store), gp (Google Play), ms, am (Amazon).
  • country (default us), collection (name; created if new), locale.

Flow

  1. Session: whoami (see using-appfollow).
  2. Normalize input. Search takes free-text keywords only — the ASO search endpoints do not accept a store URL or an ext_id. Trim the query to the app name (strip any pasted URL down to the app name/title before searching).
  3. Search (read-only, any plan). Call aso_search_results (optionally aso_search_suggestions, 5 cr). Present numbered candidates. Auto-pick only a single exact-title match; otherwise the user picks.
  4. Resolve collection. list_collections. If the target collection is new, run add_collection_preview → user approval → add_collection.
  5. Dedupe (read-only). list_apps; if the app is already tracked, record it under skipped_existing and skip the add.
  6. Add (write — may be plan-gated). add_app_preview → explicit user approval → add_app with identical args. Valid stores: as, gp, ms, am.
  7. Verify. list_apps again; confirm the app now appears; capture its apps_id.
  8. Emit the JSON block (below).

Read-only degrade path (plan-gated writes)

add_app and add_collection require an Advanced API / Custom plan, and those routes carry no feature gate — so a plan block does not arrive as FEATURE_DISABLED. It can surface as AUTH_REQUIRED, VALIDATION_ERROR, or UPSTREAM_ERROR. Therefore:

  • Always complete search + dedupe (read-only — works on any plan).
  • Attempt the add_* confirm.
  • On any error code from the add, do not assert a specific code. Report the candidate refs you found, state plainly that the add could not be completed (likely a plan limitation), and list the found refs under not_added so the report skills can still target them (they may already be tracked).

Output (fenced JSON)

{
  "added": [{"store": "as", "ext_id": "389801252", "apps_id": 12345, "collection": "Core apps", "locale": "en-US", "title": "Example App"}],
  "skipped_existing": [],
  "not_added": [],
  "collection_created": null,
  "credits_spent_estimate": 2
}