agentleFS
lynx-communitylynx-community/skills/skills/lynx-recorder/SKILL.md

lynx-recorder

Skill28 starsChanged 8 months agoApache-2.0View on GitHub

Record Lynx page interactions into a TestBench replay file using agent-lynx. Use when asked to start or stop a recording, capture page interactions for replay, or troubleshoot recording capture. For inspecting or editing an existing fixture, use lynx-recorder-fixture.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Start before opening the page: Run recorder start. Capture must begin *before* the target page loads so the recording includes loadTemplate.

    line 54
  2. Very specific:

    Stop and save: Run recorder end --output ./my-recording.json.

    line 57
  3. Very specific:

    The target must be a recorder build: If start reports Recording.start is not implemented, the app/engine was built without …

    line 63

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Lynx Recorder

Record Lynx page interactions and produce a TestBench replay file. The saved .json file may contain base64(zlib(JSON)); use lynx-recorder-fixture to inspect or edit its contents.

agent-lynx CLI

This skill contains no scripts. Recording is the recorder subcommand of the public agent-lynx CLI:

agent-lynx recorder start [options]
agent-lynx recorder end [options]

The agent-lynx CLI is normally available on PATH. If command -v agent-lynx fails, use pnpx, for example:

pnpx agent-lynx recorder start [options]

The agent-lynx CLI on PATH and the pnpx command are the supported execution forms. This skill does not provide a local scripts/index.mjs entry.

Commands

recorder start

agent-lynx recorder start [--client <clientId>]
  • -c, --client <clientId> (optional) — Target client. If omitted, the first available client is used.

recorder end

agent-lynx recorder end [--client <clientId>] [--output <path>]
  • -c, --client <clientId> (optional) — Target client. If omitted, the first available client is used.
  • -o, --output <path> (optional) — Output file or directory. If omitted, defaults to ~/.lynx-devtool/files/lynxrecorder/recording-<clientId>-<timestamp>.json.

Workflow

  1. Start before opening the page. Run recorder start. Capture must begin before the target page loads so the recording includes loadTemplate.
  2. If start reports restartRequired: true, enable_debug_mode was just enabled — restart the app and run recorder start again (see Notes).
  3. Open and interact. Open (or reload) the target Lynx page and perform the interactions to capture.
  4. Stop and save. Run recorder end --output ./my-recording.json. Report the absolute path(s) returned in savedFiles to the user.

Notes

  • A replayable recording requires loadTemplate. Open or reload the target page after recorder start. A recording started against an already-open page still captures interactions but cannot be replayed.
  • First-time enable_debug_mode may need a restart. start enables enable_debug_mode if it is off; when the platform persists that switch, start returns { success: false, restartRequired: true }. Restart the app, then run start again.
  • The target must be a recorder build. If start reports Recording.start is not implemented, the app/engine was built without ENABLE_TESTBENCH_RECORDER (not a dev/recorder build). Use a recorder-capable build.
  • One client by default. Omitting --client picks the first available client. When multiple devices or apps are connected, pass --client explicitly.

Output

end prints a single JSON object on success:

{
  "success": true,
  "message": "Recording ended successfully.",
  "savedFiles": ["/abs/path/recording.json"],
  "diagnostics": [
    {
      "file": "/abs/path/recording.json",
      "fileSizeBytes": 12345,
      "healthy": true,
      "actions": 42,
      "hasTemplate": true,
      "functionDistribution": { "loadTemplate": 1, "SendTouchEvent": 12 },
      "verdict": "Valid recording — includes template load and interaction data"
    }
  ]
}

diagnostics.verdict classification:

  • hasTemplate: true → valid, replayable.
  • Touch events present but no loadTemplate → useful for analyzing interactions, not replayable.
  • Actions present but no loadTemplate → useful for inspecting JSB calls / data updates, not replayable.
  • 0 actions → empty recording; nothing was captured.
  • Cannot parse → the file is not a valid TestBench recording.

Troubleshooting

SymptomCauseAction
start returns restartRequired: trueenable_debug_mode was just enabled and persistedRestart the app, then run recorder start again
start errors Recording.start is not implementedNot a dev/recorder build (no ENABLE_TESTBENCH_RECORDER)Use a recorder-capable build of the app/engine
Recording has no loadTemplate (not replayable)Page was already open, or not reloaded after startRe-record: run start first, then open/reload the page
Empty recording (0 actions)No page activity between start and endEnsure the page is opened and interacted with during recording
end times outDevice disconnected, or start was never calledVerify the connection; ensure start ran first
No available clientsDevice not connected or app not runningConnect the device via USB and open the DevTool-enabled app

Download now (ZIP)

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.