Fload

Use when the user has Fload MCP tools available and asks about mobile app analytics, reviews, growth metrics, ad performance, anomalies, or app store optimiz...

Security Scan

The skill's description and tools align with a mobile analytics integration, but the packaged metadata omits required installation and credentials that the included instructions explicitly ask for, creating an incoherence and mild risk.

Purpose & Capability

Name/description match the declared tools: analytics, reviews, anomalies, ads, forecasts. The capabilities described (list_apps, get_metrics, approve_action, etc.) are coherent with a mobile analytics/management platform.

Instruction Scope

The SKILL.md and AGENTS.md instruct the agent to install and use an MCP server and to obtain a FLOAD_API_KEY from app.fload.app. Those runtime instructions go beyond the registry metadata (which lists no required env vars or install). The instructions also include action verbs (approve_action/reject_action) that imply the skill may act on the user's behalf in third-party systems — which requires clear credentialing and authorization but none is declared in the registry manifest.

Install Mechanism

Although the skill package itself has no install spec, AGENTS.md tells users to run an npx command to fetch @fload-ai/mcp. npx executes code pulled from the npm registry at runtime (moderate risk). The skill's registry entry provides no homepage or verified source to validate that package, increasing the risk of executing unreviewed third-party code.

Credentials

The registry declares no required environment variables, yet AGENTS.md and the instructions reference FLOAD_API_KEY and imply connectors to App Store Connect, Google Play, ad platforms, Stripe, RevenueCat, etc. Required credentials are not declared in the skill metadata, making it unclear what secrets the skill actually needs and how they will be used.

Persistence & Privilege

The skill is not marked always:true and does not request unusual platform privileges in the manifest. There is no indication it will modify other skills or force-install itself.

What to consider before installing

Before installing, note these inconsistencies and take precautions: (1) The skill metadata lists no install or credentials but the docs instruct you to run `npx @fload-ai/mcp` and create a FLOAD_API_KEY — ask the publisher to reconcile the manifest with the docs. (2) Treat any npx/npm install as potentially risky: verify the @fload-ai/mcp package on the npm registry and inspect its repository/source before running it (or run in an isolated sandbox). (3) Only provide a least-privilege API key (read-only if possible), rotate keys after testing, and monitor activity logs. (4) Confirm what actions the skill will perform on your behalf (e.g., approving review replies) and ensure you consent to that capability. (5) If the vendor has no homepage or verifiable source, prefer to test in a controlled environment or ask for a signed/package release you can audit. These gaps make the skill suspicious but not clearly malicious; requesting clarifying information from the publisher would reduce risk.

Fload — Mobile App Analytics via MCP

You have access to Fload MCP tools for mobile app analytics. Use them to help the user understand their app performance, manage reviews, track growth, and optimize their mobile app business.

What Is Fload?

Fload is a SaaS platform for mobile app publishers. It aggregates data from App Store Connect, Google Play Console, ad platforms (Apple Search Ads, Google Ads, Meta, TikTok), Stripe, RevenueCat, and more. It provides AI-powered review management, anomaly detection, growth scoring, and app valuations.

Available Tools

App Data

• list_apps — List all apps in the user's organization. Use first to discover what apps are available.
• get_app_details — Get detailed app info (metadata, valuation, platform). Accepts assetId or bundleId.

Reviews

• get_reviews — Get app reviews with filtering (rating, date range, replied status, platform). Essential for sentiment analysis and support workflows.

Metrics & Analytics

• discover_metrics — Discover what metrics are available for an app. Always call this first before querying data.
• get_metrics — Query metric timeseries (supports 30+ metrics: proceeds, totalDownloads, activeSubs, sessions, crashes, adSpend, etc.). Can query multiple metrics at once and break down by dimension.
• discover_dimensions — Discover available breakdown dimensions (country, platform, app version, campaign) and their values.

AI Agents

• list_agents — List Fload's AI agents (review, monitoring, forecasting, growth, ASO, ads, product, submission review).
• get_agent_details — Get agent configuration for a specific app.
• get_agent_run_history — Get execution history for an agent.

Anomalies

• get_anomalies — Get detected metric anomalies (surges/declines). Filter by severity, type, status, date range.

Ads

• get_ads_performance — Get ad campaign data across Apple Search Ads, Google Ads, Meta, TikTok.

Growth

• get_growth_audit — Comprehensive growth assessment synthesizing reviews, anomalies, valuations, and connector health.
• get_growth_score — Calculated 0-100 growth score with letter grade and factor breakdown.

Forecasting

• get_forecasts — Valuation-based forecasts with trend analysis and projections.

Dashboard

• get_dashboard_overview — Organization-wide portfolio overview with revenue, downloads, and connector health.

Actions

• list_pending_actions — List AI-generated review replies awaiting approval.
• approve_action — Approve a pending review reply (optionally edit first).
• reject_action — Reject and delete a pending review reply.

Common Workflows

"How is my app doing?"

1. list_apps to find the app
2. get_growth_score for a quick health check
3. discover_metrics to see what data exists, then get_metrics for revenue/downloads trends
4. get_anomalies for any recent issues

"Show me my reviews"

1. get_reviews with appropriate filters
2. For negative reviews: filter by rating 1-2
3. For unreplied: filter by replied=false
4. list_pending_actions to see AI-drafted replies

"What's happening with my ads?"

1. get_ads_performance — optionally filter by platform
2. Combine with get_metrics for downloads to calculate organic vs paid

"Give me a full business overview"

1. get_dashboard_overview for portfolio-level metrics
2. list_apps then get_growth_score for each app
3. get_anomalies for anything needing attention

"Help me understand this metric change"

1. get_metrics for the affected metric
2. get_anomalies to see if Fload detected it
3. get_growth_audit for broader context

Tips

• Always start with list_apps if you don't know the user's app IDs
• Use get_growth_score for a quick pulse check — it synthesizes multiple signals
• The get_growth_audit tool is the most comprehensive single-call assessment
• Review tools work across platforms (iOS + Android) simultaneously
• Anomaly detection covers: revenue, downloads, active subscriptions, trials, and more
• When presenting data, format numbers nicely (currency for revenue, comma separators for counts)
• Use discover_metrics before get_metrics to know what metrics are available for an app
• Use discover_dimensions to find breakdown options (country, platform, etc.) before using dimensional queries