agentleFS
syamanersyamaner/roastpilot-agent/.claude/skills/capture/SKILL.md

capture

Skill2 starsChanged 22 days agoMITView on GitHub

Drive the replay harness + SPA and capture a screenshot of a named page state (dashboard-live, dashboard-recovery, dashboard-fault, roast-detail, roast-detail-selected, history, history-empty) — for ui-reviewer, debugging, or the E12 demo rig. Uses the Playwright MCP; scripted Playwright fallback. (E10+: needs web/ + the replay harness.)

60 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use weekly, ingest and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • gaiaaiagentSkill

    weekly

    Generate a weekly digest rolling up dailies into higher-level pattern analysis

    Also in 4 projects that use this

  • JaimeGBASkill

    ingest

    Digest an external source (article, paper, transcript, URL, book chapter) and integrate its content into the knowledge base

    Also in 9 projects that use this

  • AnthropicSkill

    brief

    Generate contextual briefings for legal work — daily summary, topic research, or incident response. Use when starting your day and need a scan of legal-relevant items across email, calendar, and contracts, when researching a specific legal question across internal sources, or when a developing situation (data breach, litigation threat, regulatory inquiry) needs rapid context.

    Also in 6 projects that use this

  • dubwoahSkill

    ask

    Answer questions about the codebase without generating or modifying any code. Use when the user wants to understand how something works, find where something is defined, or explore the project structure. Invoked with /ask.

    Also in 5 projects that use this

  • QuixiAISkill

    weekly-review

    Review the past week across goals, tasks, calendar, journal, and commitments, then propose the next week

    Also in 5 projects that use this

  • termdockSkill

    recall

    Retrieves cross-session memories about past decisions, lessons, and patterns. Use when user asks about prior work, past decisions, or mentions a feature. Triggers include check memory, what did we decide, how did we solve.

    Also in 6 projects that use this

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 58 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Start replay at speed ≥ 10× (or step deterministically for an exact frame).

    line 33

“Common” is measured: kept by at least 6 in 10 of the 58 edited versions of this file we could read. “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

Capture a deterministic screenshot of one SPA page state, driven by the replay harness (never real hardware). Pass the state name as the argument (default: dashboard-live).

Prerequisites (E10+)

  • The replay harness exists (roastpilot-agent --replay <export> — E10-S1) and a fixture under tests/fixtures/replay/ that produces the target state.
  • The SPA is built/served (Vite dev server proxying /api, or the built web/).
  • The Playwright MCP (@playwright/mcp, wired in .mcp.json) is available, or scripted Playwright via Bash as a fallback.

State → fixture/route map

StateHow to reach it
dashboard-live/ during preheating — charge guidance band visible
dashboard-recovery/ in operator_recovery_required → recovery modal
dashboard-fault/ after a pre-T0 overrun fault → fault banner + safety trail
roast-detail/roasts/:id of a completed run — curve, timeline, trace
roast-detail-selectedsame, with a CLAMP trace row selected → curve marker
history / history-empty/roasts populated / empty

Pick (or step the replay to) a fixture that produces the requested state.

Capture

  1. Start replay at speed ≥ 10× (or step deterministically for an exact frame).
  2. Via the Playwright MCP: browser_navigate to the route, browser_wait_for the state to settle (e.g. the phase badge / banner / modal), then browser_take_screenshot. (Scripted Playwright via Bash is the fallback.)
  3. Save to web/test-results/captures/<state>.png (or the path the caller asks for). For chrome-only shots that exclude the flaky uPlot canvas, mask the canvas region (D24) — pixel-correctness of the chart is asserted via data, not screenshots.

Output

The screenshot path(s) + a one-line note on what state was captured. This is a capture utility — it does not judge (that's ui-reviewer) and is not the CI gate (that's the scripted toHaveScreenshot() suite, D24).

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.