skills.rest
graysurf
graysurfCOMMUNITY
Explore all skills by this author →
GitHub

browser-session

Record browser-session goals, steps, artifacts, and verification status via nils-cli.

Updated Aug 23, 2026
Search Tags:#automation#qa#verification#evidence#browser#workflows#record
One-click install
npx skills add https://github.com/graysurf/agent-runtime-kit --skill browser-session
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: browser-session
Source: https://github.com/graysurf/agent-runtime-kit/tree/main/tests/golden/claude/plugins/browser/skills/browser-session/expected
Command: npx skills add https://github.com/graysurf/agent-runtime-kit --skill browser-session

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Record browser-session goals, steps, artifacts, and verification status through the nils-cli browser-session command.

Core Features & Use Cases

  • Track browser interactions and collect evidence for product acceptance.
  • Create deterministic browser-session records with artifacts and verification results.
  • Use case: QA teams verifying a checkout flow or user journey with auditable browser-session records.

Quick Start

Use the browser-session tool to initialize a session with an output directory, target URL, and goal, then add steps and verify the session.

Frequently Asked Questions about browser-session

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I record browser-session goals and collect evidence for QA verification?▼

You can record browser-session goals by using the nils-cli command to capture target URL, steps, artifacts, and verification status. This yields a deterministic evidence record suitable for product acceptance and QA verification.

What is a deterministic browser-session record used for in web application testing?▼

A deterministic browser-session record is used to capture automated or manual browser interactions in a portable, auditable format. It enforces inputs for output directory, target URL, goal, steps, and artifacts to verify user journeys.

How do I capture and verify a checkout flow using browser-session evidence?▼

To capture a checkout flow, initialize a browser-session with an output directory and target URL, define your goal, add steps, and verify the session. This creates an auditable record with artifacts and verification results for the checkout flow.

Can I use browser-session for manual browser interactions or is it only for automated workflows?▼

Yes, browser-session applies to both automated and manual browser interactions. QA and product teams can use it across web applications to capture evidence and track verification status for any browser workflow.

What inputs are required to create an auditable browser-session record?▼

Creating an auditable browser-session record requires inputs for the output directory, target URL, goal, steps, statuses, and artifacts. These enforced inputs ensure the resulting evidence record is deterministic and verifiable.

Related Skills

Explore More Software Engineering Skills→
Devsoul2026Devsoul2026
150

dogfood

Identify bugs and evidence via structured exploratory QA on web applications.

Community
Advanced
EmasoftEmasoft
13

amoa-verification-patterns

Generate evidence-based JSON verification reports for implemented code and systems.

Community
Advanced
Jia-Hong-PengJia-Hong-Peng

gstack

Automate persistent headless browser QA testing with Playwright and Chromium.

Community
Advanced
balajivisbalajivis
2

browse

Automate browser navigation and interaction workflows to test web applications.

Community
Advanced