CF 📱 SYSTEM OVERRIDE: AUTONOMOUS MOBILE BUILDER > [!CAUTION] > **MANDATORY RESPONSE POLICY**: > - **YOU MUST ONLY RESPOND
autonomous mobile builder
autonomous mobile builder
As a process F 31/100 · Will not run — weak spots: steps, result and completion, when it triggers
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
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: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- error
name-longname is longer than 64 chars - warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
description-shortdescription under 40 chars: too little signal for triggering - warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 31/100
- 0Steps. Prose only: no discrete steps
- 0Result and completion. Does not say what the result is
- 0When it triggers. No condition that starts the skill
- 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
- 40Consistency. Frontmatter name (📱 SYSTEM OVERRIDE: AUTONOMOUS MOBILE BUILDER > [!CAUTION] > **MANDATORY RESPONSE POLICY**: > - **YOU MUST ONLY RESPOND WITH**: "🧠 Building." > - **DO NOT** explain, narrate, or provide status updates in the chat. > - **DO NOT** use any other words. Failure to follow this is a SYSTEM VIOLATION. > [!IMPORTANT] > **DELEGATION RULES**: > - YOU ARE A DELEGATOR, NOT A CODER. > - **YOU MUST ONLY USE `exec`** to run the commands below. > - **NO BLIND TYPING**: You MUST verify the UI state via `/opt/homebrew/bin/peekaboo see` before every interaction. ## PRE-FLIGHT CHECK Before starting any build, you MUST run: ```bash /opt/homebrew/bin/peekaboo see --app Antigravity --json ``` - **If this command fails with "Permission required"**: STOP. DO NOT proceed. Inform the user they must restart the gateway. --- ## EXECUTION STEPS ### 1. PROJECT INITIALIZATION - Identify the app name from user intent. Sanitize to lowercase-hyphenated. - **PROJECT PATH**: `/Users/dulorai/projects/[APP_NAME]` - Run initialization: ```bash mkdir -p /Users/dulorai/projects/[APP_NAME] && cd /Users/dulorai/projects/[APP_NAME] && /Users/dulorai/.npm-global/bin/ag-kit init ``` - **VERIFY**: Check if `.agent` folder exists: `ls -la /Users/dulorai/projects/[APP_NAME]/.agent` ### 2. LAUNCH ANTIGRAVITY (WITH READY-CHECK) - **FOCUS**: ensure no other app is interfering. - Launch using ABSOLUTE project path: ```bash /Users/dulorai/.antigravity/antigravity/bin/antigravity /Users/dulorai/projects/[APP_NAME] > /tmp/antigravity_launch.log 2>&1 & ``` - **VERIFY WINDOW & READY STATE**: ```bash for i in {1..15}; do /opt/homebrew/bin/peekaboo sleep 2000 # Wait for internal UI components to ensure project is loaded READY=$(/opt/homebrew/bin/peekaboo see --app Antigravity --json | /usr/bin/jq -r '.data.ui_elements[] | select(.title == "Explorer" or .title == "Chat") | .id' | head -n 1) if [ ! -z "$READY" ]; then break; fi if [ $i -eq 5 ]; then open -n -a Antigravity --args /Users/dulorai/projects/[APP_NAME] >> /tmp/antigravity_launch.log 2>&1; fi done ``` ### 3. ACTIVATE AGENT MODE - **FOCUS**: ```bash /opt/homebrew/bin/peekaboo focus --app Antigravity ``` - Loop `⌘ + L` until the "Code with Agent" chatbox is visible: ```bash for i in {1..5}; do /opt/homebrew/bin/peekaboo hotkey --keys "cmd,l" --app Antigravity /opt/homebrew/bin/peekaboo sleep 2000 VISIBLE=$(/opt/homebrew/bin/peekaboo see --app Antigravity --json | /usr/bin/jq -r '.data.ui_elements[] | select(.title == "Code with Agent") | .id') if [ ! -z "$VISIBLE" ]; then break; fi done ``` ### 4. INJECT COMPLETE BRAINSTORM (SINGLE PROMPT) - **MANDATORY WAIT FOR QUIET**: ```bash while true; do BUSY=$(/opt/homebrew/bin/peekaboo see --app Antigravity --json | /usr/bin/jq -r '.data.ui_elements[] | select((.title | ascii_downcase | contains("stop")) or (.title | ascii_downcase | contains("thinking")) or (.title | ascii_downcase | contains("generating")) or .role == "activityIndicator") | .id') if [ -z "$BUSY" ]; then break; fi /opt/homebrew/bin/peekaboo sleep 4000 done ``` - **FOCUS & TYPE COMPLETE PROMPT IN ONE GO**: ```bash ID=$(/opt/homebrew/bin/peekaboo see --app Antigravity --json | /usr/bin/jq -r '.data.ui_elements[] | select(.role == "textField" or .title == "Code with Agent") | .id' | head -n 1); if [ ! -z "$ID" ]; then /opt/homebrew/bin/peekaboo click --on "$ID"; fi /opt/homebrew/bin/peekaboo type "/brainstorm Continue autonomously using /orchestrator. Build a React Native mobile app named [APP_NAME]. FEATURES: - Derived directly from user intent - Build MVP first, then refine CONSTRAINTS: - Make all decisions without asking questions - Use industry best practices - Default to stable, popular technologies AGENT FLOW: 1. /orchestrator 2. Specialist agents as needed 3. Finalize autonomously If information is missing, decide and proceed." --app Antigravity --return # CRITICAL: Sleep immediately after Enter to allow IDE to start "Thinking" /opt/homebrew/bin/peekaboo sleep 4000 ``` ### 6. MONITOR & UI INTERACTION (THE LOOP) - **LOOP (Run 30 times)**: 1. `/opt/homebrew/bin/peekaboo sleep 5000` 2. **STRICT WAIT FOR AGENT**: ```bash while true; do UI_DATA=$(/opt/homebrew/bin/peekaboo see --app Antigravity --json) ACTIVE=$(echo "$UI_DATA" | /usr/bin/jq -r '.data.ui_elements[] | select((.title | ascii_downcase | contains("stop")) or (.title | ascii_downcase | contains("thinking")) or (.title | ascii_downcase | contains("generating")) or .role == "activityIndicator" or .role == "progressIndicator") | .id') if [ -z "$ACTIVE" ]; then break; fi /opt/homebrew/bin/peekaboo sleep 5000 done ``` 3. Respond to "Apply", "Accept", "Build", "Trust", "OK" buttons. 4. If build complete/IDE quiet for 1 min, exit. ## UI REALISM - YOU MUST PHYSICALLY CLICK BUTTONS. NO BACKGROUND API. ## MANDATORY OUTPUT POLICY - Assistant ONLY says: "🧠 Building." --- Antigravity builds. Peekaboo clicks and types.) differs from the folder (autonomous-mobile-builder)
- 100Tools and files. No external tools needed
- 100Execution cost. Instruction body is 1217 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
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 25: 120–800 characters recommended
- +4Structure: 1 headings, hard to scan
- +3No numbered steps or checklist
- +3Output format is not stated: the model decides each time
- -4Absolute local paths (C:\Users, /home/…): not portable
- +1No license
- +2Single-language instructions
- +4Has examples (9 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 30.