agentleFS
north-star-hqnorth-star-hq/agentlane/skills/drive/SKILL.md

drive

Skill2 starsChanged 33 days agoLicence not identifiedView on GitHub

Drive the app on this session's own lane - its simulator or emulator through the device tools (look, run, screenshot over MCP, or `agentlane look|run|screenshot` from a shell), its browser through the driver's own CLI under `agentlane exec` (playwright-cli or agent-browser) - and turn what works into proof and evidence. Use when seeing what is on a screen or page, clicking or typing in the web app, trying or repairing Maestro steps or a Playwright test, checking what an action did, reading a failed step, recording a video, trace or screenshot, or setting a device's location, permissions, appearance, push, clipboard or URL.

7 other projects use a version of this.

Adopted by

Most recently taken up by

The file

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.