AF auth0-expo
Use when adding authentication to Expo (React Native) mobile apps — login, logout, user sessions, protected routes, biometrics, or token management. Integrates react-native-auth0 SDK with Expo Config Plugin for native iOS/Android builds. Trigger for any Expo project needing Auth0, including app.json plugin config, custom scheme setup, or credential management. Do NOT use for bare React Native CLI projects (use auth0-react-native), React web apps (use auth0-react), Next.js (use auth0-nextjs), or backend APIs.
As a process F 59/100 · Will not run — References files that are not bundled: /auth0-quickstart, /auth0-react-native, /auth0-mfa
How to improve
- The text references files that are not there: add them or drop the references.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 2
✓ No critical or high findings
Medium and low: 2
-
low Exfiltration
exfil-secret-in-urlreferences/integration.md:376Credential passed in a URL query string (normal for some APIs — verify the host is the intended service) (placeholder value)const webAppUrl = `https://your-web-app.com/login?session_transfer_token=…
placeholder -
low Dangerous commands
cmd-pipe-to-shell-known-hostscripts/utils/validation.mjs:25Pipe-to-shell installer from a well-known host (still executes remote code) (string literal in code, not executed)" Linux: curl -sSfL https://raw.githubusercontent.com/auth0/auth0-cli/main/install.sh | sh\n" +
code literal
Files scanned: 15. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: /auth0-quickstart - warning
missing-refreference to a missing file: /auth0-react-native - warning
missing-refreference to a missing file: /auth0-mfa - warning
missing-refreference to a missing file: /auth0-cli
Process rating: all ten parameters 59/100
- 0Tools and files. 4 referenced file(s) missing: /auth0-quickstart, /auth0-react-native, /auth0-mfa
- 0Result and completion. Does not say what the result is
- 50When it triggers. No condition that starts the skill
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 18 steps
- 100Failures and branches. 16 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3150 tokens
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- medium 1 test cases, all positive: not one "should refuse" or "should ask first"
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
- +5Description has no quoted example phrases that should trigger the skill
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 513: enough signal without eating the budget
- +4Structure: 17 headings
- +3Step-by-step instructions: 18 items
- +4Has examples (8 code blocks)
- +4Reference files are cited in the instructions (3 of 3)
- +3All 1 scripts are documented
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.