agentsclimarketplace

Ui control

Skill yarlson/yarstack/plugins/yarstack/skills/ui-control

Verify graphical browser, desktop, or Electron behavior through the actual interface. Use when screenshot, accessibility, console, network, trace, or browser-driven evidence is required; exclude terminal-hosted interfaces.From its SKILL.md

Install
npx -y skills add yarlson/yarstack --skill ui-control

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.5 KB, 249 tokens by cl100k_base, as published. Nobody here has run it

UI Control

Gather reproducible evidence from the actual graphical surface without changing production behavior.

Workflow

  1. Identify the target surface, build or session, and observable contract.
  2. Reuse the authorized running or authenticated surface when it is the target. Start a local app only when necessary and authorized.
  3. Prefer existing repository harnesses and locate controls by stable roles, labels, identifiers, or application markers.
  4. Perform only actions needed for the requested behavior or a concrete risk.
  5. Capture the smallest relevant screenshot, accessibility output, console entry, network evidence, or trace.
  6. Check loading, empty, error, keyboard, focus, responsive, and cleanup states only when material to the contract.
  7. Clean up only servers, profiles, sessions, and artifacts created by this workflow.

Keep verification read-only unless the parent task separately authorizes implementation. Use behavior-implement for fixes, phase-validate for contract acceptance, and test-gap-review for evidence sufficiency.

Do not add automation dependencies for a one-off probe, retain sensitive evidence, use stale selectors, or terminate user-owned resources.

Finish with the surface tested, actions, observed result, retained evidence, and blockers or limitations.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 326,736. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.