New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

AppsFlyer Event Validation

by AppsFlyerSDK in AppsFlyerSDK/appsflyer-unity-plugin

Checks whether the AppsFlyer events and callbacks expected in a Unity app scenario actually fired, using logs, callback payloads and test evidence.

MITAuto-check passedTesting & QA

Install AppsFlyer Event Validation

skills CLI
$ npx skills add AppsFlyerSDK/appsflyer-unity-plugin --skill appsflyer-event-validation -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install AppsFlyerSDK/appsflyer-unity-plugin appsflyer-event-validation --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/AppsFlyerSDK/appsflyer-unity-plugin.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/appsflyer-event-validation .claude/skills/appsflyer-event-validation && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
appsflyer-event-validation
GitHub stars
178
Token cost
~332 tokens
SKILL.md length
145 words
Files
1
Skills in repo
7
Repo updated
First seen
Licence
MIT

At a glance

Checks whether the AppsFlyer events and callbacks expected in a Unity app scenario actually fired, using logs, callback payloads and test evidence.

  • Works in 6 steps: Identify the scenario under test. → Define the expected AppsFlyer events or… → Collect evidence from: Unity console… → …
  • Verifying AppsFlyer events after an end-to-end Unity test run
  • SKILL.md covers Goal, Workflow, Output Format and Rules
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

For a given scenario, the agent lists the AppsFlyer events or callbacks it expects, collects evidence from Unity console logs, Android logcat, iOS simulator logs and C# callback payloads, and matches the two. Each expected event is classed as confirmed triggered, missing, duplicate, unclear or blocked by environment.

The report returns the scenario, platform, expected, confirmed, missing and duplicate or unexpected events, the evidence, and a final status of passed, failed, inconclusive or blocked. Rules say not to assume an event fired because the app launched, to confirm only from logs, callbacks or assertions, to say needs more logging when evidence is thin, and to keep verified facts apart from assumptions.

When your agent uses it

  • Verifying AppsFlyer events after an end-to-end Unity test run
  • Finding missing or duplicate AppsFlyer callbacks in logs
  • Writing a pass or fail report for an SDK integration scenario

Example prompts

  • “Check the Android logcat from this run and tell me whether the in-app purchase event reached AppsFlyer.”
  • “Validate the AppsFlyer events for the first-launch scenario using the Unity console log.”
  • “Did the install conversion callback fire twice in this iOS simulator log?”

Requirements

  • Scenario logs or callback output, such as Unity console, Android logcat or iOS simulator logs

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Identify the scenario under test.
  2. Define the expected AppsFlyer events or callbacks for that scenario.
  3. Collect evidence from: Unity console logs, Android logcat, iOS simulator logs, C# callback payloads.
  4. Match expected events against actual evidence.
  5. Classify each expected event as: Confirmed triggered | Missing | Duplicate | Unclear | Blocked by environment.
  6. Summarize the result.

What it can do on your machine

Read from SKILL.md and the folder at commit 8756add. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

AppsFlyer Event Validation loads about 332 tokens when it runs. Until then it costs about 47 tokens; SKILL.md has 145 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~47
When it runs · the whole SKILL.md, loaded when a task matches
~332

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from AppsFlyerSDK/appsflyer-unity-plugin at commit 8756add, republished under its MIT licence (© AppsFlyerSDK). 145 words, ~332 tokens.

Download SKILL.mdSave it as .claude/skills/appsflyer-event-validation/SKILL.md (or your agent's skills folder).
name
appsflyer-event-validation
description
Validate that expected AppsFlyer SDK events and callbacks were triggered during an end-to-end Unity app scenario using logs, callback payloads, and test evidence.

AppsFlyer Event Validation

Use this skill when validating whether AppsFlyer-related events actually fired during an app scenario.

Goal

Compare expected AppsFlyer events against real evidence from logs, callbacks, or assertions.

Workflow

  1. Identify the scenario under test.
  2. Define the expected AppsFlyer events or callbacks for that scenario.
  3. Collect evidence from: Unity console logs, Android logcat, iOS simulator logs, C# callback payloads.
  4. Match expected events against actual evidence.
  5. Classify each expected event as: Confirmed triggered | Missing | Duplicate | Unclear | Blocked by environment.
  6. Summarize the result.

Output Format

Return:

  • Scenario
  • Platform
  • Expected AppsFlyer events
  • Confirmed triggered events
  • Missing events
  • Duplicate or unexpected events
  • Relevant evidence
  • Final status: Passed | Failed | Inconclusive | Blocked

Rules

  • Do not assume an event fired because the app launched.
  • Confirm events only from logs, callbacks, or assertions.
  • If logs are insufficient, say needs more logging.
  • Separate verified facts from assumptions.

© AppsFlyerSDK, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/appsflyer-event-validation of AppsFlyerSDK/appsflyer-unity-plugin.

Open the folder on GitHubat commit 8756add

Compare with similar skills

AppsFlyer Event Validation next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

AppsFlyer Event Validation compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
AppsFlyer Event Validation this skillAppsFlyerSDK/appsflyer-unity-plugin178—~332Automated safety check: PassMIT
BrowserStack Live Testinghandsontable/handsontable22k—~950Automated safety check: PassCustom licence
Teswiz Projectznsio/teswiz105—~977Automated safety check: PassMIT
MAUI Device Test Runnerdotnet/maui23k—~3.3kAutomated safety check: PassMIT
MAUI UI Test Writerdotnet/maui23k—~3kAutomated safety check: PassMIT
UI Kitten Showcase QAakveo/react-native-ui-kitten11k—~2.3kAutomated safety check: PassMIT

Similar skills

  • BrowserStack Live Testing

    handsontable/handsontable

    Opens a live BrowserStack session on a real Android, iOS or desktop browser for a local or public URL, tunneling localhost through Cloudflare when needed.

    22k GitHub stars~950 tokensUpdated today
    Testing & QAAuto-check passed

  • Teswiz Project

    znsio/teswiz

    A skill your agent uses when working in the znsio/teswiz repository to modify framework code, Cucumber/TestNG hooks, Applitools visual testing flows, configs/caps, or related docs/tests.

    105 GitHub stars~977 tokensUpdated today
    Testing & QAAuto-check passed

  • MAUI Device Test Runner

    dotnet/maui

    Official

    Builds and runs .NET MAUI device tests locally on iOS simulators, MacCatalyst, Android emulators or Windows, with optional category filtering.

    23k GitHub stars~3.3k tokensUpdated today
    Testing & QAAuto-check passed

  • MAUI UI Test Writer

    dotnet/maui

    Official

    Writes UI tests that reproduce a GitHub issue in .NET MAUI and keeps iterating until the tests actually fail, proving they catch the bug.

    23k GitHub stars~3k tokensUpdated today
    Testing & QAAuto-check passed

  • UI Kitten Showcase QA

    akveo/react-native-ui-kitten

    Drives the Expo showcase app in an iOS simulator with agent-device to sweep every UI Kitten component in all theme and mapping combinations, reporting regressions with evidence.

    11k GitHub stars~2.3k tokensUpdated 2 days ago
    MobileAuto-check passed

  • Mobile Automation with agent-device

    nuclearpasta/react-native-drax

    Drives iOS and Android devices and simulators from the command line: open apps, snapshot the UI tree, tap, type, scroll, take screenshots and read UI info.

    715 GitHub stars~1.4k tokensUpdated 4 days ago
    MobileAuto-check passed

More from AppsFlyerSDK/appsflyer-unity-plugin

  • AppsFlyer Unity Bridge Debugging

    AppsFlyerSDK/appsflyer-unity-plugin

    Traces a failing call or callback between C# and the native Android or iOS wrappers of the AppsFlyer Unity plugin to find the first broken link.

    178 GitHub stars~492 tokensUpdated 3 days ago
    Auto-check passed

  • AppsFlyer Unity Plugin API Change

    AppsFlyerSDK/appsflyer-unity-plugin

    Guides API changes in the AppsFlyer Unity plugin across the C# layer and the Android Java and iOS Objective-C bridges, ending with a compatibility-risk report.

    178 GitHub stars~514 tokensUpdated 3 days ago
    Auto-check passed

  • AppsFlyer Unity Plugin Release Check

    AppsFlyerSDK/appsflyer-unity-plugin

    Reviews the AppsFlyer Unity plugin before a release: version consistency, changelog, Android and iOS parity, billing variants and .unitypackage freshness.

    178 GitHub stars~470 tokensUpdated 3 days ago
    Auto-check passed

  • AppsFlyer Unity SDK Version Bump

    AppsFlyerSDK/appsflyer-unity-plugin

    Guides a consistent bump of the Android or iOS SDK wrapped by the AppsFlyer Unity plugin, keeping both billing library variants and release files in step.

    178 GitHub stars~789 tokensUpdated 3 days ago
    Auto-check passed

  • E2E Smoke Test

    AppsFlyerSDK/appsflyer-unity-plugin

    Run or review a basic end-to-end smoke test for the AppsFlyer Unity plugin on Android emulator or iOS simulator, covering startup, initialization, and basic event flow.

    178 GitHub stars~325 tokensUpdated 3 days ago
    Auto-check passed

  • Launch Log Analysis

    AppsFlyerSDK/appsflyer-unity-plugin

    Analyze logs for a specific app launch and determine whether AppsFlyer initialization, start flow, callbacks, and expected events occurred correctly in the Unity plugin.

    178 GitHub stars~314 tokensUpdated 3 days ago
    Auto-check passed

Works with

Categories

Questions about AppsFlyer Event Validation

What does AppsFlyer Event Validation do?

Checks whether the AppsFlyer events and callbacks expected in a Unity app scenario actually fired, using logs, callback payloads and test evidence. For a given scenario, the agent lists the AppsFlyer events or callbacks it expects, collects evidence from Unity console logs, Android logcat, iOS simulator logs and C# callback payloads, and matches the two. Each expected event is classed as confirmed triggered, missing, duplicate, unclear or blocked by environment.

When should I use AppsFlyer Event Validation?

AppsFlyer Event Validation fits situations like: verifying AppsFlyer events after an end-to-end Unity test run; finding missing or duplicate AppsFlyer callbacks in logs; writing a pass or fail report for an SDK integration scenario.

How do I install AppsFlyer Event Validation in Claude Code?

Run `npx skills add AppsFlyerSDK/appsflyer-unity-plugin --skill appsflyer-event-validation -a claude-code`. Or copy the skill folder (.claude/skills/appsflyer-event-validation in AppsFlyerSDK/appsflyer-unity-plugin) into .claude/skills/appsflyer-event-validation in your project. Claude Code loads it when a task matches its description.

How do I install AppsFlyer Event Validation in Codex?

Run `npx skills add AppsFlyerSDK/appsflyer-unity-plugin --skill appsflyer-event-validation -a codex`. Or copy the skill folder (.claude/skills/appsflyer-event-validation in AppsFlyerSDK/appsflyer-unity-plugin) into .agents/skills/appsflyer-event-validation in your project. Codex loads it when a task matches its description.

Can I use AppsFlyer Event Validation in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add AppsFlyerSDK/appsflyer-unity-plugin --skill appsflyer-event-validation -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/appsflyer-event-validation, .gemini/skills/appsflyer-event-validation, .github/skills/appsflyer-event-validation and .opencode/skills/appsflyer-event-validation in your project.

What does AppsFlyer Event Validation need to run?

SKILL.md names no scripts, command-line tools or credentials: AppsFlyer Event Validation is instructions for the agent only. Our summary lists: Scenario logs or callback output, such as Unity console, Android logcat or iOS simulator logs.

Does AppsFlyer Event Validation access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is AppsFlyer Event Validation safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does AppsFlyer Event Validation use?

AppsFlyer Event Validation is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does AppsFlyer Event Validation use?

About 332 tokens (SKILL.md is roughly 1.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to AppsFlyer Event Validation?

Skills that share tags, products or a category with AppsFlyer Event Validation: BrowserStack Live Testing (handsontable/handsontable, 22k stars), Teswiz Project (znsio/teswiz, 105 stars), MAUI Device Test Runner (dotnet/maui, 23k stars) and MAUI UI Test Writer (dotnet/maui, 23k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains AppsFlyer Event Validation?

AppsFlyerSDK (a GitHub organization) maintains it in AppsFlyerSDK/appsflyer-unity-plugin, which has 178 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 4, 2026.

Source: AppsFlyerSDK/appsflyer-unity-plugin on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.