SKILLEMALL.ai

BF android-flyverify-integration

Interactive guide for integrating MobTech FlyVerify (SecVerify) into Android projects with 5-step workflow. Use when user says "我要在app中增加一键登录", "秒验集成", "FlyVerify集成", "Android一键登录", or asks about FlyVerify setup, Gradle configuration, pre-verification, one-click login, custom UI, or privacy compliance. Supports step-by-step interactive integration with user confirmation at each step.

ClawHub Agent Skills author: MobSupport v2.0.0 MIT-0 5 files · 1 script body ≈ 3 231 tokens Open the sourceclawhub.ai↗ analyzed 6 d ago

Interactive guide for integrating MobTech FlyVerify (SecVerify) into Android projects with 5-step workflow.

As a process F 31/100 · No process to follow — References files that are not bundled: assets/FlyVerify_Config_Template.xlsx

IntegrationExcelSecuritySoftware developmentPersonal productivitytype and topics are labelled automatically from the skill text
JSON
Technical rating
B
92/100
safety, quality, tests
Safety 60%
100
Quality 40%
79
Run on models
none yet
Process rating
F
31/100
No process to follow
References files that are not bundled: assets/FlyVerify_Config_Template.xlsx
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
0
the three weakest of ten parameters · all ten

How to improve

  1. The text references files that are not there: add them or drop the references.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 0

✓ No critical or high findings

Files scanned: 5. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: assets/FlyVerify_Config_Template.xlsx

Process rating: all ten parameters 31/100

Will not run. References files that are not bundled: assets/FlyVerify_Config_Template.xlsx
  • 0Tools and files. 1 referenced file(s) missing: assets/FlyVerify_Config_Template.xlsx
  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 40Consistency. Frontmatter name (android-flyverify-integration) differs from the folder (andorid-flyverify-integration)
  • 100Steps. 44 steps
  • 100Execution cost. Instruction body is 3231 tokens
  • 100Running it twice. No mutating operations

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • -4Absolute local paths (C:\Users, /home/…): not portable
  • +1No license
  • +2Single-language instructions
  • +5Description quotes 3 example trigger phrases
  • +3Description length 386: enough signal without eating the budget
  • +4Structure: 45 headings
  • +3Step-by-step instructions: 44 items
  • +4Has examples (37 code blocks)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 79.

External checks

ClawHub: suspicious
The skill is aimed at Android FlyVerify setup, but it asks the agent to handle app secrets, edit build scripts, and run Gradle with unverified dynamic dependencies in ways users should review carefully.
LLM: suspicious (high) · VirusTotal: · 16 Sept 2026