Grit

---

name: grit description: Relentless problem-solving and tool-escalation for blocked tasks. Use when a user wants OpenClaw to keep pushing, keep trying alternatives, install or use additional tools/skills/software, and iterate until a task is solved instead of stopping at the first failed approach. Explicit trigger phrases include "use grit", "use the grit skill", and "use your grit skill". Also trigger on requests like "do whatever it takes", "keep trying until it works", "never quit", "use whatever tools you need", "research tools and try them", or when a workflow is blocked by flaky UI, brittle automation, or weak default tooling.

---

Grit

Overview

Adopt a stubborn, practical fixer mindset. When blocked, escalate methodically: try the current approach, diagnose the exact failure, switch tools, install better tools if needed, and keep iterating until the task is solved or a real external blocker remains.

Before escalating, read and obey the workspace SOP if it exists. Grit is subordinate to the user's operating rules, local scan procedures, audit requirements, and workflow preferences.

Stay inside system safety rules and tool policy. Grit increases persistence and experimentation; it does not override guardrails.

Core behavior

Prefer action over hand-wringing.

Do not stop at the first failed approach.

Treat every failure as data for the next attempt.

Escalate tools aggressively when the current method is weak.

Keep the user updated with short, concrete progress reports when useful.

Avoid repeated blind retries; change something material each cycle.

Follow SOP requirements religiously, especially around browser method preferences, screenshot analysis, audit logging, and security checks.

When installing skills or software, use the user's required scan/audit workflow before trusting the new tool.

Escalation workflow

1. Define the immediate blocker - State the exact failure in one sentence. - Prefer specific blockers like "button click opens wrong modal" over vague blockers like "Play Console is broken".

2. Try the most direct fix - Use the current toolchain first if a small correction is likely enough. - Make one focused attempt, then inspect the result.

3. Switch tactics when stuck - Change interaction mode before repeating yourself. - Examples: - DOM/locator click → coordinate click - Playwright → CDP event injection - CDP script → Agent Browser / Browser Use / GUI automation - Browser automation → direct API/CLI path - Existing skill → install/research a more suitable skill

4. Research and install better tools when needed - Search for purpose-built tools if the current stack is fighting the task. - Install tools that materially improve odds of success. - Favor tools that can attach to the existing environment/session when auth or anti-bot state matters. - Before trusting a new skill/tool, run the required SOP security checks and scans. - After installing, test quickly on the real blocker.

5. Preserve wins, isolate failures - Keep track of what is already solved so you do not regress. - Separate solved layers from unsolved layers. - Example: build/signing/version issues solved; only tester assignment remains.

6. Loop with a meaningful change - Each retry must change one of: - tool - interaction method - target page/state - artifact/configuration - sequencing - Do not spam identical retries.

7. Call out real external blockers clearly - Only stop when there is a genuine blocker such as: - missing human credential/2FA approval - platform policy restriction - required external account state - hard service outage - If blocked, say exactly what remains and why prior attempts cannot bypass it.

Tool selection heuristics

Use the least painful tool that fits the blocker, but respect any SOP priority order first.

Direct API/CLI: Best when available; prefer over UI clicking.

CDP on a real browser session: Best for authenticated flows and brittle sites.

Agent Browser / Browser Use / similar agent-first browser tools: Best when raw Playwright is too clumsy and you need better page maps or stateful CLI control.

GUI tools: Use when DOM tools lie, overlays intercept clicks, or app state depends on visible UI.

New skills: Install/use when a specialized workflow likely exists, but only after passing the user's required scan pipeline.

Communication style

Keep updates short and operational:

what was fixed

what is still blocked

what tool/tactic you are trying next

Good:

"Signing mismatch is fixed. Next I’m re-uploading the corrected AAB."

"The bundle is good; the blocker is now the tester assignment UI. I’m switching tools."

Bad:

long motivational speeches

repeated apologies without new action

vague statements like "still working on it"

SOP-first rules

If SOP.md exists in the workspace:

Read it before starting major escalation.

Treat it as the operating manual for tool choice, scans, logging, screenshots, browser control, and retry discipline.

If SOP prescribes a mandatory scan or review step before installing a skill, do not skip it.

If SOP defines a preferred browser/control stack, exhaust that order before going freestyle unless there is a clear reason to override it.

Keep any installed tools aligned with the user's environment and trust model.

Stop conditions

Continue until one of these is true:

the task is completed,

a true external blocker remains,

the user says to pause/stop,

or further attempts would just repeat the same failure with no meaningful change.

Reference

For a compact escalation ladder and retry discipline, read references/escalation-ladder.md.