Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
aliyun avatar

Alibabacloud Emas Apm Query

aliyun/alibabacloud-aiops-skills

  • 111 installs
  • 208 repo stars
  • Updated August 4, 2026
  • aliyun/alibabacloud-aiops-skills

alibabacloud-emas-apm-query is a Claude skill that queries Alibaba Cloud EMAS APM crash/ANR/lag issues and maps stack samples to mobile app source code to suggest fixes.

About

This skill troubleshoots mobile app issues reported to Alibaba Cloud EMAS APM. It calls the 4 read-only emas-appmonitor OpenAPIs to do Top-N aggregation, sample stack drill-down, and dimension breakdowns across crash, ANR, lag, and memory issue types, then maps stacks to app source to suggest fixes. A developer uses it to investigate mobile crashes and ANRs.

  • Queries EMAS APM crash, ANR, lag, and memory issues via 4 read-only OpenAPIs
  • Top-N aggregation, sample stack drill-down, and dimension breakdowns
  • Maps stacks to app source code across Android, iOS, HarmonyOS, Flutter, Unity

Alibabacloud Emas Apm Query by the numbers

  • 111 all-time installs (skills.sh)
  • Ranked #554 of 1,039 Mobile Development skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
At a glance

alibabacloud-emas-apm-query capabilities & compatibility

Requires Alibaba Cloud credentials; EMAS APM query APIs are read-only

Capabilities
debugging
Works with
aws
Use cases
debugging
Runs
Runs locally
Pricing
Bring your own API key
From the docs

What alibabacloud-emas-apm-query says it does

Alibaba Cloud EMAS APM (mobile Application Performance Monitoring) issue troubleshooting skill.
SKILL.md
Client coverage: native Android / iOS / HarmonyOS, Flutter, Unity
SKILL.md
npx skills add https://github.com/aliyun/alibabacloud-aiops-skills --skill alibabacloud-emas-apm-query

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs111
repo stars★ 208
Last updatedAugust 4, 2026
Repositoryaliyun/alibabacloud-aiops-skills ↗

What it does

Troubleshoot mobile app crash, ANR, and lag issues from Alibaba Cloud EMAS APM and map stacks to source.

Who is it for?

Investigating mobile app crashes, ANRs, and lag reported to Alibaba Cloud EMAS APM

Skip if: H5 apps (out of scope) or writing new APM data (read-only APIs)

When should I use this skill?

A developer needs to analyze a mobile app crash, ANR, or memory issue from EMAS APM

What you get

Produces root-cause analysis and fix suggestions mapping APM stacks to file:line in the app source.

  • Top-N issue aggregation and sample stacks
  • Root-cause analysis and fix suggestions mapped to source

By the numbers

  • 4 read-only OpenAPIs
  • 6 supported issue types (crash/anr/lag/custom/memory_leak/memory_alloc)

Files

SKILL.mdMarkdownGitHub ↗

alibabacloud-emas-apm-query

1. Scenario Description & Architecture

After a mobile app integrates Alibaba Cloud EMAS APM, the crash / anr / lag / custom / memory_leak / memory_alloc events it produces every day are aggregated and reported by the SDK to the backend. A typical troubleshooting workflow is:

1. Figure out which Issues are most worth fixing: sort by error rate / error count → pick Top 3~5 2. Inspect what a specific Issue looks like: fetch its aggregated metrics and affected versions 3. Find several representative samples: across different devices / versions / networks 4. Read the stack + business log in a sample: find actionable clues 5. Compare against the app source code and propose a fix

This skill stitches the 5 steps above into a single CLI pipeline. The entire process only calls the 4 read-only APIs of `aliyun emas-appmonitor`, and depends on no database / log service:

GetIssues  → GetIssue → GetErrors → GetError
   ↓
(optional) stack ↔ user APP source → precise file:line + fix diff

Supported BizModules: crash / anr / lag / custom / memory_leak / memory_alloc Supported OS: android / iphoneos / harmony (harmony does not have anr / memory_*)

2. Prerequisites

ItemRequirementSelf-check command
Aliyun CLI version>= 3.3.3aliyun version
Pluginaliyun-cli-emas-appmonitoraliyun emas-appmonitor --help
jqany version (required by scripts)jq --version

Full installation steps: `references/cli-installation-guide.md`. Recommended: enable auto plugin installation once:

aliyun configure set --auto-plugin-install true
aliyun plugin update

3. Credential Pre-check

Do NOT print AK/SK values; just verify that an available profile exists:

aliyun configure list

The expected output contains a current profile whose Mode / RegionId are non-empty. If not, configure one of AK / OAuth / StsToken / RamRoleArn per `references/cli-installation-guide.md#Configuration`.

This skill never reads or forwards AK / SK field values themselves during its whole lifecycle.

4. AI-mode Lifecycle

Start (before the skill runs):

aliyun configure ai-mode enable
aliyun configure ai-mode set-user-agent --user-agent "AlibabaCloud-Agent-Skills/alibabacloud-emas-apm-query"

End (after troubleshooting completes):

aliyun configure ai-mode disable

5. RAM Permissions

This skill only needs the 4 read-only emasha:View* actions (ViewIssues / ViewIssue / ViewErrors / ViewError). EMAS AppMonitor's RamCode is emasha and does not support resource-level authorization, so Resource is fixed to "*".

For the full least-privilege JSON policy, the equivalent system policies (AliyunEMASAppMonitorReadOnlyAccess / AliyunEMASAppMonitorFullAccess), and common permission-error troubleshooting, see `references/ram-policies.md`.

[MUST] Permission Failure Handling: When any command or API call fails due to permission errors at any point during execution, follow this process:
1. Read references/ram-policies.md to get the full list of permissions required by this SKILL
2. Use ram-permission-diagnose skill to guide the user through requesting the necessary permissions
3. Pause and wait until the user confirms that the required permissions have been granted

6. Parameter Confirmation

IMPORTANT: Parameter Confirmation — Before executing any command or API call,
ALL user-customizable parameters (e.g., RegionId, instance names, CIDR blocks,
passwords, domain names, resource specifications, etc.) MUST be confirmed with the
user. Do NOT assume or use default values without explicit user approval.
ParameterRequiredTypeDescriptionDefault
app-keyYesint64EMAS APP Key (typically 9+ digits). Prefer to infer from SDK initialization code in the current workspace (see the 6 rule families in `references/appkey-detection.md`); if exactly one match is found, echo it and wait for user confirmation; if multiple, list candidates and let the user pick; on miss, ask the user to provide it manually.None (default: probed from workspace)
osYesenumandroid / iphoneos / harmony (H5 goes to h5, which is out of scope). Inferred together with `app-key` from the project type: build.gradle / AndroidManifest.xml → android; *.xcodeproj / Podfile → iphoneos; module.json5 + ets/ → harmony. For cross-platform Flutter / Unity projects, the user MUST pick one (android / iphoneos).None (default: probed from project type)
time-rangeYesobject`StartTime=<ms> EndTime=<ms> Granularity=1 GranularityUnit=<HOUR\DAY>`
biz-moduleNolistIf omitted, all 6 modules are scanned; if specified, only that module is analyzedAll 6
digest-hashNostringIf the user already knows a specific Issue, skip the Top-N stage and drill down directlyNone
top-nNointNumber of Top issues5
filter-jsonNostringFurther narrow down (specific version / device model / region ...), a JSON stringNot applied

Timestamp unit: every API uses Unix milliseconds. If the user passes a value in seconds (< 1e12), the scripts will automatically multiply by 1000.

`biz-module` pitfall: the CLI --help lists the legacy enum (exception / crash / lag / custom / h5JsError / h5WhiteScreen); however, `anr / memory_leak / memory_alloc` are actually forwarded to the backend and work. This skill scans all 6 modules requested by the user by default; see `references/biz-module-reference.md`.

`time-range` pitfall: in some environments Granularity=60 GranularityUnit=MINUTE is rejected by the backend (returns Code: 200, Message: "unknown error"). Always prefer Granularity=1 GranularityUnit=DAY or GranularityUnit=HOUR.

`--os` pitfall: the CLI --help marks --os as optional, but in practice omitting it returns an empty list without error (Model.Items=[], Total=0). All 4 APIs must pass --os explicitly.

`--did` pitfall: get-error's --did is also marked optional in --help, but is implicitly required by the backend. Omitting it returns Code: 100011 Parameter Not Enough. Take it from get-errors' Items[*].Did (already handled by dig_issue.sh; when calling aliyun emas-appmonitor get-error manually, pass it explicitly).

Dual semantics of `DigestHash`: get-errors returns Items[*].DigestHash, which is the hash of a single event, different from the aggregated --digest-hash you passed in. When calling get-error next, still use the aggregated hash (the one you used in get-issues / get-issue); do not switch to the single-event hash.

Reuse `biz-module`: whichever bizModule was used to obtain a Top Issue from get-issues must be reused for the next three steps (get-issue / get-errors / get-error); otherwise the response will be empty (the same DigestHash exists under only one bizModule). list_top_issues.sh already attaches a bm field to each row so it can be reused.

7. Core Workflow

flowchart TD
    Start[User request] --> DetectCtx{Workspace can infer AppKey+OS?}
    DetectCtx -- single match --> ConfirmCtx[Echo for user confirmation]
    DetectCtx -- multiple matches --> PickCtx[List candidates, let user pick]
    DetectCtx -- miss --> AskCtx[Ask user for AppKey + OS]
    ConfirmCtx --> HasHash
    PickCtx --> HasHash
    AskCtx --> HasHash
    HasHash{digestHash provided?}
    HasHash -- yes --> SingleIssue[get-issue: fetch single Issue metadata]
    HasHash -- no --> ParallelIssues[Parallel get-issues over 6 bizModules]
    ParallelIssues --> TopN[Sort by errorRate, take Top 3-5]
    TopN --> IterateTop[Iterate Top Issues]
    IterateTop --> SingleIssue
    SingleIssue --> GetErrors[get-errors: latest 3-5 samples]
    GetErrors --> PickSample["Sample policy: latest / hot device / latest affected version"]
    PickSample --> GetError[get-error: stack/threads/logs/dimensions]
    GetError --> HasCode{CWD has APP source?}
    HasCode -- yes --> CodeMatch[stack -> file + line -> diff]
    HasCode -- no --> CliReport[CLI-only diagnostic report]
    CodeMatch --> Report[Final report: issue list + root cause + fix]
    CliReport --> Report
    Report --> CallFailed{Any CLI call failed?}
    CallFailed -- yes --> CliSelfDiag["CLI self-diagnose: --log-level debug / --cli-dry-run / configure list / plugin update"]
    CallFailed -- no --> endNode[Done]
    CliSelfDiag --> endNode

7.0 Runtime locate the Skill directory ($SKILL_DIR)

The Skill's own path is known to the Agent at the time SKILL.md is loaded (see the fullPath / path field under <available_skills> in the context). Before running any bash command that needs to read bundled resources from this Skill (scripts/ / assets/ / references/), the Agent MUST first export the directory of SKILL.md to SKILL_DIR exactly once:

# The Agent fills in the absolute path of SKILL.md into the placeholder, then exports once
export SKILL_DIR="$(cd "$(dirname "<ABSOLUTE_PATH_OF_SKILL.md>")" && pwd)"

# Self-check: all three directories must exist
[[ -d "$SKILL_DIR/scripts" && -d "$SKILL_DIR/assets" && -d "$SKILL_DIR/references" ]] \
  || { echo "[ERROR] SKILL_DIR does not point to the root of this Skill: $SKILL_DIR" >&2; exit 1; }

Rules:

1. Do not hardcode `~/.cursor/skills-cursor/...` or `~/.claude/skills/...`: this Skill can be distributed in the repository (.agent/skills/alibabacloud-emas-apm-query/) or at the user level, and the absolute path varies with the host. 2. Do not rely on `cd` into the Skill directory to use relative paths: the scripts drop artifacts into the current working directory (the user's APP source root); cd would break this semantic. 3. The bash scripts have a fallback: scripts/list_top_issues.sh and scripts/dig_issue.sh auto-detect their own location via BASH_SOURCE at the top, so they can locate $SKILL_DIR even if it was not exported. Other inline jq / rg commands inside SKILL.md still require the Agent to export $SKILL_DIR first.

7.1 Stage A: Top N (when digest-hash is not provided)

Use scripts/list_top_issues.sh to scan the 6 biz_modules in parallel:

bash "$SKILL_DIR/scripts/list_top_issues.sh" \
  --app-key <AppKey> \
  --os <iphoneos|android|harmony> \
  --start-time <startMs> \
  --end-time <endMs> \
  --top-n 5 \
  --order-by ErrorRate

The output is a merged Top-N table, each row containing {bm, digestHash, ec, er, edc, edr, name, type, reason}. To add a Filter (e.g. "only version 3.5.x"), append --filter-json '{"Key":"appVersion","Operator":"in","Values":["3.5.0","3.5.1"]}'; see `references/filter-reference.md`.

7.2 Stage B: Drill into a single Issue

Use scripts/dig_issue.sh:

bash "$SKILL_DIR/scripts/dig_issue.sh" \
  --app-key <AppKey> \
  --os <iphoneos|android|harmony> \
  --biz-module <crash|anr|lag|custom|memory_leak|memory_alloc> \
  --digest-hash <13-char Base36> \
  --start-time <startMs> --end-time <endMs> \
  --sample-size 3

Output directory:

emas-apm-dig-<AppKey>-<DigestHash>-<epoch>/
  01-get-issue.json
  02-get-errors.json           (contains the ClientTime/Uuid/Did triples)
  samples/<Uuid>.json          (complete JSON per sample, includes Backtrace/EventLog etc.)
  report.md                    (structured markdown report)

7.3 Stage C: Code mapping + diff (if the CWD contains APP source)

Follow `references/troubleshoot-workflow.md`:

1. Determine the platform (Android / iOS / Harmony / RN / Flutter / Web) 2. Model.Backtrace → keep APP user frames → grep the source → locate file:line 3. Enrich the timeline using EventLog + Controllers + Threads + CustomInfo 4. Emit the smallest diff (≤ 20 lines + one sentence of "why")

If the CWD does not contain the source: emit only a CLI diagnostic report (Issue overview, sample dimension comparison, representative stack), and append a hint that "switching to the APP source directory enables code-level localization".

7.4 Failure handling (CLI only)

When any aliyun emas-appmonitor call fails, run the following self-checks in order:

aliyun configure list                                   # 1. current profile / mode / region
aliyun plugin update                                    # 2. latest plugin
aliyun emas-appmonitor <cmd> ... --cli-dry-run          # 3. parameter serialization check
aliyun emas-appmonitor <cmd> ... --log-level debug      # 4. HTTP body + RequestId

Do not guide the user to query any server-side data source.

8. Success Verification

The full 6-step CLI self-verification (with runnable commands and pass/fail criteria for each step) is in `references/verification-method.md`. The correct-vs-incorrect CLI pattern matrix is in `references/acceptance-criteria.md`. Core criteria:

1. Reachable: get-issues dry-run prints the HTTP body successfully 2. Non-empty: some biz_module has Model.Total >= 1 3. Stable: two calls with identical parameters return the same Top 5 DigestHash 4. Filter works: after adding a filter, Total is strictly <= the full count 5. Three-level chain: issues → issue → errors → error can pull a Stack end to end 6. Diagnosable: on induced errors, the output includes RequestId and ErrorCode

9. Cleanup

This skill is read-only; it does not create any cloud resources that need cleanup.

Tear-down is only two things:

aliyun configure ai-mode disable

# (optional) delete the local JSON directories produced by dig_issue.sh
rm -rf ./emas-apm-dig-*

10. Best Practices

1. Probe first, ask later: before entering the main flow, grep SDK initialization code from the user's workspace per `references/appkey-detection.md` to infer app-key / os; confirm with the user only after a hit, rather than asking upfront. 2. Top first, then drill: do not run dig_issue.sh against every Issue from the start — first use list_top_issues.sh to aggregate the Top N, then drill into each of them. The total number of CLI calls is O(N) rather than O(all). 3. Always pass `--os`: --os on all 4 APIs is marked optional in --help, but omitting it returns empty results silently. Always specify android / iphoneos / harmony explicitly. 4. `get-error` MUST carry `--did`: marked optional in --help but implicitly required by the backend; take it from Items[*].Did in the get-errors response. 5. Reuse `biz-module`: the next get-issue / get-errors / get-error calls must use the same bizModule that produced the Issue in get-issues; switching will return empty. 6. Shrink the time window from "wide" to "narrow": start diagnosis with 24h / Granularity=1 GranularityUnit=DAY; once a specific version / device is located, shrink to 1~4 hours with GranularityUnit=HOUR. 7. Filters are JSON strings: the entire --filter value must be a single JSON string; build nested SubFilters with jq -cn to avoid manual escape errors (see `references/filter-reference.md`). 8. Multi-account scenarios: confirm the profile via aliyun configure list and pass --profile <name> explicitly rather than relying on implicit env-var switching. 9. Persist `get-error`: this API response can be from hundreds of KB to several MB; do not truncate JSON with head / tail. Write to > /tmp/emas-error-XXX.json first and then process with jq. 10. Android obfuscation: when you see class names like a.a.a.b.c, ask the user for mapping.txt before attempting code mapping rather than guessing. 11. iOS not symbolicated: when Model.SymbolicStatus=false, the Stack contains many raw addresses; only emit conclusions at device / version dimensions, and re-analyze after dSYM is uploaded. 12. Parallel QPS control: list_top_issues.sh has a built-in sleep 0.3s to avoid throttling; scanning 6 biz_modules takes 2~3 seconds in total and does not need extra concurrency. 13. Empty `biz-module` results are not errors: anr / memory_* under harmony or very-low-traffic AppKeys returning Total=0 is normal and should not be retried. 14. Do not reverse-use this skill to write data: all 4 APIs are Get* / View*. If the user wants to "update Issue status" or "mark as fixed", that falls under write APIs like UpdateIssueStatus and is out of scope.

11. Reference Links

DocumentPurpose
`references/cli-installation-guide.md`Aliyun CLI installation / configuration / plugins / credentials
`references/appkey-detection.md`Identify AppKey and OS from the user's workspace across Android / iOS / Harmony / Flutter / Unity / H5
`references/ram-policies.md`Least-privilege JSON + Permission Failure Handling
`references/get-issues.md`GetIssues parameters / response / ordering
`references/get-issue.md`GetIssue parameters / response
`references/get-errors.md`GetErrors parameters / response
`references/get-error.md`GetError parameters / response
`references/filter-reference.md`--filter structure / operators / SubFilters / dry-run validation
`references/biz-module-reference.md`6 biz_modules x platforms x available filterCode list
`references/troubleshoot-workflow.md`Full flow for stack -> source -> diff
`references/related-commands.md`Cheat sheet for all aliyun emas-appmonitor commands + skill boundary
`references/verification-method.md`6-step runnable CLI verification with pass/fail criteria
`references/acceptance-criteria.md`Correct vs incorrect CLI pattern matrix (for review / self-check)
`assets/system-filters/index.json`Index of 14 static filter snapshots (biz_module x platform)

Related skills

firebaseXcode Project SetupAutomatically create and configure a new Xcode project with Swift Package Manager dependencies for iOS or macOS agent projects.74.7k392expoExpo Tailwind SetupInstantly configure Tailwind CSS v4 with NativeWind v5 and react-native-css inside an Expo project for universal styling.46.7k2.3kexpoExpo Dev ClientCreate custom development clients for Expo React Native apps that need native modules or Apple-specific targets.45.9k2.3kavdleeSwiftui Expert SkillGet expert guidance when writing, reviewing, or refactoring SwiftUI views, state, performance, and modern iOS/macOS APIs.27.6k3.3kflutterFlutter Apply Architecture Best PracticesEnforce clean layered architecture when creating or refactoring a Flutter mobile application.25.4k2.7kexpoExpo ModuleCreate custom config plugins that safely modify native Android and iOS projects generated by Expo prebuild.25k2.3k

FAQ

Which issue types and clients are covered?

Crash, ANR, lag, custom, memory_leak, and memory_alloc across Android, iOS, HarmonyOS, Flutter, and Unity; H5 is out of scope.

Does it modify data?

No. It only calls the 4 read-only APIs get-issues, get-issue, get-errors, and get-error.

Mobile Developmentmonitoring
Browse by category
AI & AgentsFrontend & DesignBackend & DataDev ToolsAutomationTesting & ReviewSecurityMonitoring & CloudDocs & Planning
Design & frontend
Design systemsAnimation & motionAccessibility (a11y)CSS & TailwindUI designUXDesign to codeshadcn/uiLanding pagesBest design skills
Most searched skills
find-skillscavemanfrontend-designbrainstormingsystematic-debuggingstop-slopemil-design-engui-ux-pro-maxkarpathy-guidelinesweb-design-guidelinesreact-best-practicesgrill-meimprovemicrosoft-foundryagent-browser
Browse all listings
All agent skillsAll MCP serversAll marketplacesAll plugins

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.