Hive Axyl
ChatGPT pluginBuild and operate games
Hive Axyl helps teams develop and operate games by providing SDK integration, service configuration, live operations, and analytics capabilities through one platform. It helps reduce repetitive work and tool switching, so teams can focus more on building and improving their games.
- Featured
- No
not on the featured shelf
Movement
From our daily snapshots over the last 30 days.
Rank by placement
Rank in Developer tools
In its category
How this plugin compares with others in the same category. Positions are counted within the category, not across the whole directory.
Developer tools681st of 742 by placement
| # | Plugin | Position | 7d |
|---|---|---|---|
| 679 | #7864 | — | |
| 680 | #7891 | 1,013places down | |
| 681 | #7893 | — | |
| 682 | #7915 | — | |
| 683 | #7918 | — |
Example prompts
- “Add login and logout to my game using Hive Axyl.”
- “Retrieve store products and implement in-app purchases using Hive Axyl.”
- “Show daily new user counts for the last 10 days and identify the country with the most new users using Hive Axyl.”
Skills
axyl-analytics-common
Common rules that all skills using the Hive Analytics tools of the Hive Axyl MCP server must follow. Read it as a prerequisite alongside skills such as axyl-drill-down-metrics. Use it on its own when a request calls the Hive Analytics tools directly and no other Hive Analytics skill covers it. TRIGGER when: - Always load this together when a Hive Analytics skill such as axyl-drill-down-metrics is activated. - A request uses the Hive Analytics tools directly and no other Hive Analytics skill covers it: a simple metric lookup (for example, last week's DAU), organization or workspace management (for example, creating an organization), or Analytics configuration (excluded users, metric start dates, metric filters, currency). DO NOT TRIGGER when: - The request is development work unrelated to Hive Analytics.
axyl-auto-login
Restores a Hive Axyl session at Unity app restart from saved access/refresh tokens. Use for auto login, per-call token validation, refresh recovery and credential-preservation decisions when no session is live. Does not implement guest-token login or a live refresh loop.
axyl-console-access
Common rules for operating the Hive Axyl Console through the hive-axyl MCP server: session, company scope, menu access and action permission, prerequisites, write confirmation, and where the per-feature Console guides live. The per-feature operations — project/app, app meta, login settings, security key, usage restriction, user lookup, TCB settings — are served by the hive-axyl MCP itself (its tools plus its documentation guides), so read the matching MCP-served guide with these rules (TCB: also the axyl-tcb-function skill). TRIGGER when: - Any Hive Axyl Console operation or lookup is requested through the hive-axyl MCP server — project/app, app meta, login settings, security key, usage restriction, user lookup, TCB settings, and the like. DO NOT TRIGGER when: - The request does not touch the Hive Axyl Console — e.g. SDK feature implementation (see the axyl-developer-guide skill) or Analytics workflows (see the analytics skills).
axyl-consumable-purchase
Composes a new Hive Axyl consumable purchase in Unity across the selected market: checkout, record, game-server verification and delivery, and close. Use for the shared purchase lifecycle or multi-market orchestration; interrupted purchases use recovery and recurring products use subscription.
axyl-create-content
Creates and saves Hive Analytics chart, ranking, funnel, or retention content, and can assemble approved content into a dashboard. Follow axyl-analytics-common first. TRIGGER when: - The user asks to build and save a chart, ranking, funnel, or retention - The user asks to create a dashboard with an already finalized composition - The user asks to bundle specified metrics or charts into one dashboard - The user asks to recreate an existing dashboard or a dashboard template in another project or workspace of the same company DO NOT TRIGGER when: - The dashboard composition is undecided or needs recommendation/readiness assessment → axyl-design-dashboard - The request is read-only analysis → axyl-analytics-common, axyl-detect-anomaly, or axyl-drill-down-metrics - The request creates a user segment or snapshot → axyl-create-segment - The request is development work unrelated to analytics
axyl-create-segment
Designs Hive Analytics segment conditions, estimates the matching user count, saves the segment, and optionally extracts a point-in-time snapshot. It also lists existing segments/snapshots and refreshes snapshots. Follow axyl-analytics-common first. TRIGGER when: - The user asks to create a segment (for example, "create a segment of paying iOS users") - The user asks how many users meet certain conditions (simulation only, no save) - The user asks to list existing segments/snapshots or take or refresh a snapshot DO NOT TRIGGER when: - The request is a metric breakdown by dimension or a user ranking → axyl-drill-down-metrics - The request is to create chart, funnel, retention, or dashboard content → axyl-create-content - The request is only to send a push; this skill stops at segments and snapshots - The request is development work unrelated to analytics
axyl-custom-login
Implements Hive Axyl Custom login in Unity using an app-server one-time grant key through PKCE, token exchange and session installation. Use for grant-key login and fresh-key recovery; the client does not obtain server credentials.
axyl-design-dashboard
Recommends dashboards for a Hive Analytics project's genre, BM, purpose, and audience, and assesses whether each content item is implementable from the available metrics, events, dimensions, and recent ingestion state. TRIGGER when: - The user asks for a dashboard or content composition recommendation or design - The user asks for a dashboard tailored to an audience or purpose - The user asks to create a dashboard without a finalized composition - The user asks what can be built from current data or which logs are missing DO NOT TRIGGER when: - The composition is settled and only saving and assembly remain → axyl-create-content - The request is read-only: use axyl-analytics-common for a value, axyl-detect-anomaly for anomaly judgment, or axyl-drill-down-metrics for dimensional contributor analysis - Game client log send code is being implemented → axyl-integrate-analytics-log - The request is to create a segment → axyl-create-segment
axyl-detect-anomaly
Detects unusual changes in Hive Analytics metrics with a conservative heuristic over raw values returned by preview_chart or preview_retention. It compares a completed target interval with same-position historical points, reports the numerical deviation, and suggests causes to verify without claiming causality. TRIGGER when: - The user asks whether a metric has spiked, dropped, or looks unusual - The user asks to scan several metrics for unusual changes - The user asks whether a metric change is unusual and what to verify next DO NOT TRIGGER when: - The request is only for a metric value → use axyl-analytics-common (preview_chart) - The change is already established and the request is only to break down contributors by dimension → use axyl-drill-down-metrics - The user asks to save a chart or dashboard → use axyl-create-content
axyl-developer-guide
Use when implementing an Axyl feature that is not covered by a more specific skill; verify the official Axyl developer guide before coding uncovered login, payment, push, mailbox, TCB Connector, account/auth, or service access control behavior.
axyl-drill-down-metrics
Breaks Hive Analytics metrics down by dimensions through preview_chart and ranks users through preview_chart_rank. This is read-only contributor analysis, not defining or saving a user segment. Follow axyl-analytics-common first. TRIGGER when: - The user asks to break down any metric by OS, country, market, product, or another confirmed dimension - The user asks which segments contributed to an already identified metric spike or drop - The user asks for a list of whale users or top-paying users DO NOT TRIGGER when: - The request asks whether a change is anomalous or scans metrics for anomalies → use axyl-detect-anomaly - The request is a simple metric figure lookup → use axyl-analytics-common (preview_chart) - The request investigates one specific user's activity, purchases, or logins → use axyl-inspect-user - The request is to create and save a segment or take a snapshot → axyl-create-segment - The request is development work unrelated to analytics
axyl-guest-login
Implements first-run or returning guest login in Unity with the Hive Axyl SDK, through token exchange and session installation. Use for guest creation/restoration and retaining guest recovery credentials after failure. Does not implement saved access/refresh-token auto login.
Show all 34Show fewer
axyl-inspect-user
Investigate one individual user's activity history and latest state. This covers CS inquiry checks, report verification, and confirmation of a specific user's purchases or logins. Identifying the user to investigate is also part of this skill's job. Follow the common rules of axyl-analytics-common as a prerequisite. TRIGGER when: - The user asks to check a specific user's activity, history, or state - Verifying "what this user actually did" based on a CS inquiry or report - Selecting and investigating one user matching a condition such as whale, dormant, or new DO NOT TRIGGER when: - Breaking a metric down by dimension (OS/country/market) → axyl-drill-down-metrics - Determining whether a metric is anomalous → axyl-detect-anomaly - The goal is to define and save a segment → axyl-create-segment - Dozens of users or more must be handled in a batch (this skill investigates one user at a time)
axyl-integrate-analytics-log
Analyzes a game client repository to recommend events for games using Hive SDK v4 or the Hive Axyl SDK, then implements and verifies the SDK send code. TRIGGER when: - Adding or modifying Hive Analytics event send code in a game repository - Scanning a game repository to recommend events to collect - Designing how to enrich an SDK auto-collected event with game properties DO NOT TRIGGER when: - Querying or analyzing already-ingested analytics data - Integrating only non-analytics SDK features such as Hive authentication, payments, push, or ads - Implementing code that sends logs directly from a server over HTTP or Fluentd - Requesting a Hive console configuration change
axyl-link-provider
Links a provider account to the signed-in Hive Axyl player in Unity. Use for guest-to-provider linking, acquisition, ownership conflicts and post-link reconciliation while preserving the current account. Does not implement provider login or account merging.
axyl-logout
Implements user-requested Hive Axyl logout in Unity, including outcome-specific local cleanup, stored credentials and protection against clearing a replacement session. Does not implement account withdrawal, provider sign-out or automatic cleanup after login failure.
axyl-provider-login
Exchanges already-acquired provider credentials for a Hive Axyl session in Unity. Use when the app already has the provider ID, token or ticket and user ID and needs the Axyl login/token/session join. Provider credential acquisition belongs to the selected route skill.
axyl-provider-login-apple
Implements native Sign in with Apple through a Hive Axyl session in Unity on iOS/macOS. Use for Apple addon acquisition, nonce state, IdentityToken/UserIdentifier handoff, token exchange and session installation.
axyl-provider-login-credential-manager
Implements Google sign-in through Android Credential Manager and a Hive Axyl session in Unity. Use for the native Google account picker, web client ID/raw nonce, GoogleIdToken and Axyl handoff. Browser Google OAuth uses the WebAuth route.
axyl-provider-login-gpg
Implements Google Play Games sign-in through a Hive Axyl session in Unity on Android. Use for IsAuthenticated, SignIn, serverAuthCode acquisition and provider exchange with the web OAuth client's registered redirect URI. Ordinary Google account sign-in uses another route.
axyl-provider-login-steam
Implements native Steam ticket login through a Hive Axyl session in Unity on Windows/macOS. Use for Steam client prerequisites, ticket validation lifetime, ReleaseTicket and Axyl token/session handoff. Steam browser OpenID uses WebAuth.
axyl-provider-login-webauth
Implements browser provider login through a Hive Axyl session in Unity: Google/X OAuth, Sign in with Apple on Android/Windows/WebGL and Steam OpenID. Use for WebAuth callbacks, redirect/loopback/state, the Axyl relay, provider exchange and Axyl handoff. Native Apple on iOS/macOS, Credential Manager, GPG and Steam tickets use their native routes.
axyl-purchase-market-apple
Implements Hive Axyl Apple StoreKit payments in Unity on iOS/macOS. Use when Apple consumable checkout, unfinished-purchase recovery or subscription startup is requested, including JWS handoffs and original-transaction finish. Apple sign-in uses the authentication skill.
axyl-purchase-market-google
Implements Hive Axyl Google Play Billing in Unity on Android. Use for Google consumables, unconsumed-purchase recovery or subscription startup, including per-launch product/offer queries, purchase callbacks, receipt handoffs, post-then-consume and device acknowledgement. Google sign-in is a separate flow.
axyl-purchase-market-pg
Implements Hive Axyl hosted PG consumable checkout, browser resume and purchase recovery in Unity. Use for payment URLs, OrderRequestOs and quantity inputs, restored-order correlation, game-server verification and delivery, and finalize, including ambiguous same-product orders and WebGL page opening. No PG client addon is required.
axyl-purchase-market-steam
Implements Hive Axyl Steam microtransaction consumables and recovery in Unity. Use for Steam catalog/init, authorization callbacks, the game-server verification that charges, delivery and finalize. Steam authentication tickets and subscription flows are outside this skill.
axyl-purchase-recovery
Composes shared or multi-market recovery of unfinished Hive Axyl consumables in Unity: discover, hand to the game server as a recovery and close after its delivery confirmation. Use after crashes or incomplete delivery/close when the market is unspecified or several markets are involved. Does not start checkout.
axyl-push
Use for shared or multi-platform push preparation, language/consent changes and app-policy-driven account binding in Hive Axyl Unity. Native APNs/FCM details are bundled; sending campaigns and local notifications are outside this skill.
axyl-push-apns
Implements Hive Axyl APNs push in Unity on iOS/macOS: preparation, native forwarding and actual environment, language/consent changes, and app-policy-driven account binding. Use for Apple push integration; does not send campaigns.
axyl-push-fcm
Implements Hive Axyl Android FCM push in Unity: Firebase/permission preparation, token renewal, language/consent changes, and app-policy-driven account binding. Use for Android push integration; does not send campaigns or cover Apple APNs.
axyl-setup
Sets up the Hive Axyl SDK in a Unity application: UPM package selection, bootstrap, capability and auth addon registration, service resolution, and automatic token refresh wiring. Use for installing or configuring Axyl, missing services, or initialization issues; login composition is handled by the relevant login flow skill.
axyl-subscription
Composes shared Apple/Google subscription startup in Hive Axyl Unity: pre-record, acquisition, save, game-server verification and entitlement, and confirmation. Use for multi-market or unspecified-market subscription flows and common receipt/post invariants; does not implement server renewal jobs.
axyl-tcb-function
Build, deploy, test, and operate Hive Axyl TCB Connector serverless functions with the hive-axyl MCP server: start_tcb_workflow, its TCB documents, and the Console TCB settings tools. TRIGGER when: - Creating, changing, deploying, invoking, or testing a Hive Axyl TCB Connector function or project. - The project's TCB credential, Secret Key, API ID (SecretId), or its change history in the Console (with the axyl-console-access gates). DO NOT TRIGGER when: - Calling TCB from the game client through the Hive Axyl SDK (see the axyl-developer-guide skill). - Tencent CloudBase work unrelated to Hive Axyl TCB Connector. - Other Console menus (see the axyl-console-access skill) or Analytics work (see the analytics skills).
axyl-username-login
Implements Hive Axyl username/password login and app-requested login-or-signup in Unity, including password transformation, restricted signup fallback, PKCE and session installation.
- Categories
- Made by
- Com2uS Platform · Website
- Sign-in
- On Install
- Capabilities
- Interactive, Read, Write
- Availability
- Available
- Version
- 2.1.0
- Keywords
- hive, game-development, liveops, sdk, game-analytics
- Created
- October 12, 2026
- More info
- Sponsorship
- Promote this plugin