SkillAgentSearch skills...

agent-experience

Audit the developer experience of a product, SDK, docs site, or SKILL.md by dropping multiple Claude subagents at it with only a tiny task prompt and real tools (WebFetch, Bash, Write).

Install / Use

npx skills add browserbase/skills --skill agent-experience

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

95/100

Supported Platforms

Claude Code

Tags

Our assessment of agent-experience

agent-experience scores 95/100 on our quality scale, 370th of 4,698 Development & Engineering skills we index (top 8%).

Its SKILL.md is 35 KB long, well organised into 20 sections with 5 code examples: a thorough specification that gives an agent plenty to work with.

With 3,731 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
30/30
Structure
20/20
Description
15/15
Adoption
15/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so agent-experience is actively maintained.
  • Our last check on 2026-11-16 found the source still online.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

Warning

Our scan of the whole file found 2 high-risk patterns. Read the lines below before installing agent-experience, and do not run it with automatic approvals. An AI review of the same text found nothing harmful.

  • highReads private keys or cloud credentialsline 140
    - macOS Keychain: `security find-generic-password -l "<expected-name>" -w` — try once with the most likely name (e.g. `BROWSERBASE_API_KEY`)…
  • highReads private keys or cloud credentialsline 158
    - Tier 3: `op read "op://<vault>/<item>/<field>"` or `security find-generic-password -l <NAME> -w`.

AI review by kimi-k2.7-code on 2026-09-29. Automated pattern scan on 2026-09-29. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

agent-experience compared with similar skills

All 4 of these similar skills score higher than agent-experience; compare them before choosing.

SkillScoreStarsUpdatedFormat
agent-experience (this skill)by browserbase953.7k2mo agoSKILL.md
taste-skillby Leonxlnx100116.8k8d agoCLAUDE.md
ai-job-searchby ai-job-search-dev10072.1ktodayCLAUDE.md
claude-howtoby luongnv8910047.3k2d agoCLAUDE.md
lobehubby lobehub10085.6ktodayMCP Server

Frequently asked questions

How do I install agent-experience?
Run npx skills add browserbase/skills --skill agent-experience. The install tabs above show the steps for each supported agent.
Which AI agents does agent-experience work with?
It is written for Claude Code, as a SKILL.md file. Other agents that read the same format can often use it too.
Is agent-experience safe to use?
Our scan of the whole file found 2 high-risk patterns. Read the lines below before installing agent-experience, and do not run it with automatic approvals. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is agent-experience still maintained?
The repository was last updated about 2 months ago, so agent-experience is actively maintained.

name: agent-experience description: "Audit the developer experience of a product, SDK, docs site, or SKILL.md by dropping multiple Claude subagents at it with only a tiny task prompt and real tools (WebFetch, Bash, Write). Agents must discover the docs themselves, install deps, ask for credentials if needed, and attempt real execution. The skill captures each agent's trace — tool calls, retries, wall time, errors — and scores on Setup Friction, Speed, Efficiency, Error Recovery, and Doc Quality, then emits an HTML report with an A–F grade and concrete fixes. Use when the user asks to audit agent experience, test a skill, audit docs for agents, check if a SDK is agent-friendly, validate a SKILL.md, measure agent DX, or benchmark how painful onboarding is for an AI agent. Triggers: 'audit agent experience', 'test this skill', 'audit docs for agents', 'is my SDK agent-friendly', 'run a DX audit', 'agent experience test', 'test my docs', 'how do agents do with my product'." compatibility: "Requires an agent harness with subagent (Agent tool), WebFetch, and Bash support, plus network access. No CLI install needed; audited products may require their own credentials at runtime." license: MIT metadata: author: jay-sahnan version: "1.4.0" allowed-tools: Read WebFetch Write Bash AskUserQuestion Agent

Audit Agent Experience

Evaluate how well a product/SDK/docs surface works when an AI agent actually tries to onboard and do a realistic task — starting from a short one-sentence prompt, with nothing pasted in. The agent must find the docs, install what it needs, and attempt real work. That's the only honest test of agent DX.

The skill spawns multiple subagents in parallel, captures each one's tool-call trace, and scores the experience using the same dimensions as the Skill Test Arena dashboard: Setup Friction, Speed, Efficiency, Error Recovery, Doc Quality.

Core principle

Do not spoonfeed. The subagent gets a tiny prompt like "Get started with {product} and {do its primary thing}". It must discover the docs, choose the path, and hit real failures. A good doc survives this; a bad doc does not.

Workflow

Execute these steps in order. Do not skip ahead.

Step 1 — Identify the target and define the abstract goal

Resolve what the user is asking to audit. The target may arrive in one of three forms:

  • URL — a docs site or product page (e.g., https://docs.example.com). This is the seed the subagents start from.
  • Repo / file path — for SKILL.md audits or SDK repos.
  • Product name — if the user is vague ("test my product"), ask via AskUserQuestion for the URL or repo.

This skill is product-agnostic. Never assume what the user wants to audit. Do not infer a target from environment signals (operator's email domain, git remote, repo name, recent files, memory, CLAUDE.md). Even if context strongly suggests a particular company, the user-facing question must NOT pre-fill or default to any specific product, URL, or company name. Ask open-endedly with neutral options only: e.g., "Paste a URL", "Paste a local path", "Type a product name". If the user did not name a target in their invocation, ask them — start fresh, no priors.

Research lightly after the user has named a target. 1 WebFetch max, enough to confirm: what is this product, and does it have a getting-started guide? You're identifying that there is a flow to follow, not extracting the steps. The whole point is to let the docs dictate the path.

Define ONE abstract goal, not a step-by-step checklist. The goal should be at the level of "complete the onboarding" or "make the product do its primary thing once" — NOT a list of specific actions.

Why: prescriptive checklists steer agents. If you tell them "navigate to example.com" but the docs' quickstart navigates to a different URL, the agent is torn between your instruction and the docs. That pollutes the test.

Examples of good abstract goals (the target product is supplied by the user — the examples below are illustrative only, not defaults):

  • A search API → "Complete the getting-started guide. Success = your code successfully calls the API and prints whatever the docs treat as a meaningful result."
  • A payments API → "Complete the getting-started flow for making a test charge. Success = you have a charge ID or equivalent confirmation."
  • A browser-automation SDK → "Complete the getting-started guide end-to-end. Success = you have code that runs a cloud browser session using whatever approach the docs recommend."
  • A SKILL.md → "Follow the skill's instructions and produce a successful outcome for its advertised job."

Examples of BAD goals (too prescriptive — don't do this):

  • ~~"Navigate to https://example.com"~~ (steers — the docs may pick a different URL)
  • ~~"Use Playwright"~~ (the docs may recommend Stagehand or Selenium)
  • ~~"Print the page title"~~ (the docs may print session ID, response body, anything)

The subagent will self-report against the abstract goal: did I complete the onboarding as the docs described? (yes / no / partial). The concrete sub-outcomes the agent actually achieved live in their trace under primary_outcome_achieved, not in a pre-defined checklist.

If the target has no clear getting-started flow (rare — even a README is a flow), ask the user what "done" means before continuing.

Step 2 — Gather audit config via AskUserQuestion

Use AskUserQuestion in a single call with 4 questions. Options: max 4 per question.

  1. Test depth (single-select, header: "Depth"):

    • 5 agents (Recommended) — balanced coverage
    • 3 agents — quick sanity check
    • 10 agents — thorough, higher cost
  2. Programming languages (multiSelect, header: "Languages"): pick up to 4 — Python, TypeScript, Go, Shell/Bash (let user deselect).

  3. Personas (multiSelect, header: "Personas"):

    • Standard (Recommended) — neutral baseline, no behavioral flavoring. Just "do the task." Best for unbiased measurement.
    • Pragmatic — just get it working, fastest path
    • Thorough — read the docs end-to-end before coding
    • Skeptical — verify claims the docs make
  4. Execution mode (single-select, header: "Exec mode"):

    • Allow Bash (Recommended) — subagents can run npm install, curl, etc. on your machine. Most realistic.
    • Draft-only — subagents may fetch docs and write code but won't execute anything. Safer.

After the user answers, gather one more question about model choice:

  1. Model (single-select, header: "Model"):
    • Sonnet (Recommended) — balanced cost/quality, default for most audits
    • Opus — strongest reasoning, highest cost; good for dense/ambiguous docs
    • Haiku — cheapest, fastest; good for checking if docs are agent-friendly to smaller models
    • Mixed comparison — split agents across Opus + Sonnet + Haiku so you can see how doc quality varies by model size. Useful for "are my docs robust even to weaker models?"

Pass the chosen model to each Agent invocation via the model parameter. If Mixed, distribute N agents roughly equally across the 3 models (round-robin by slot index) and record which model each agent used in the trace + report.

After the user answers, you have: depth (N), languages[], personas[], exec_mode, model.

If exec_mode = "Allow Bash", follow up with a second AskUserQuestion asking about credentials:

  • Credentials (single-select, header: "Credentials"):
    • Auto-discover (Recommended) — skill checks the user's env vars, common dotfiles, and credential managers; only prompts for paste if nothing found. Best for repeat use and for cases where another operator is running the audit.
    • None — let agents block (friction test) — agents hit the credential wall, counts as Setup Friction. Best for pure docs audits.
    • Paste manually — you paste keys directly; skill injects them. Use when you don't have keys stored locally yet.

If user picks Auto-discover, run Step 2.5 below before continuing. If Paste manually (or auto-discover falls back), AskUserQuestion asks for the credential values — not the names. The skill then writes them to each workspace .env using generic, product-agnostic names:

  • Primary credential → API_KEY
  • Secondary (e.g. project/org ID) → PROJECT_ID
  • Third (e.g. webhook secret) → SECRET

Do NOT use product-specific names like BROWSERBASE_API_KEY, EXA_API_KEY, STRIPE_SECRET_KEY. Those names steer the agent — they see BROWSERBASE_API_KEY in env and skip ever reading the docs to find out what env var the SDK actually expects. The generic name forces them to:

  1. Read the docs to discover the product's actual env var name (e.g. BROWSERBASE_API_KEY).
  2. Map the generic API_KEY value into whatever form the SDK requires — either re-export (export BROWSERBASE_API_KEY=$API_KEY) or pass inline in code (new Browserbase({ apiKey: process.env.API_KEY })).

If an agent fails to figure out the mapping, that's a doc quality signal — the docs weren't clear about credential naming.

Step 2.5 — Credential auto-discovery (only if user picked Auto-discover)

Run a tiered lookup. Stop at the first tier that produces a usable candidate. Never print credential values to chat — only names and source paths. The user picks by name; the skill internally maps name → value → workspace .env.

Derive the product slug from the target URL/repo to bias toward relevant matches. e.g. https://docs.browserbase.com → slug browserbase. Use lowercase substring match (case-insensitive) when ranking candidates.

Tier 1 — Already-exported env vars (free, zero side effects):

printenv | grep -iE '^[A-Z][A-Z0-9_]*_(API_KEY|TOKEN|SECRET|KEY)=' | cut -d= -f1

This returns names only. If any names contain the product slug, those are top candidates.

Tier 2 — Narrow dotfile scan (a hardcoded short list, NOT a recursive grep):

grep -hE '^[[:space:]]*export[[:space:]]+[A-Z][A-Z0-9_]*_(API_KEY|TOKEN|SECRET|KEY)=' \
  ~/.zshrc ~/.bashrc ~/.bash_profile ~/.zprofile ~/.env ./.env ./.envrc 2>/dev/null \
  | sed -E 's/^[[:space:]]*export[[:space:]]+([A-Z0-9_]+)=.*/\1/' \
  | sort -u

Files allowed: ~/.zshrc, ~/.bashrc, ~/.bash_profile, ~/.zprofile, ~/.env, ./.env, ./.envrc. Do NOT expand this list. Do NOT recurse. Do NOT scan ~/Library, ~/.config/, ~/Documents, etc. This is the entire allowlist; anything else is out of scope and risks leaking unrelated secrets.

For each match, record (NAME, source_path). Read the value lazily — only when the user has confirmed the choice — by re-grepping the specific source file for that exact name.

Tier 3 — Credential manager (only if op or security is on PATH AND tiers 1–2 had no good match):

  • 1Password CLI: skip unless op account list exits 0 (i.e. user is signed in). Don't trigger an interactive auth flow inside the skill.
  • macOS Keychain: security find-generic-password -l "<expected-name>" -w — try once with the most likely name (e.g. BROWSERBASE_API_KEY); silent failure means not stored.

If a credential manager produces hits, list them as candidates the same way as tiers 1–2.

Tier 4 — Fallback to paste: If all tiers above produced zero candidates, fall through to the manual paste flow described in Step 2.

Presenting candidates to the user. After tiers 1–3:

  • If exactly 1 candidate and its name contains the product slug → use it silently. Log a one-line confirmation in chat: Using BROWSERBASE_API_KEY from ~/.zshrc. (Name + source only — never the value.)
  • If multiple candidates, AskUserQuestion (single-select, header: "Use which credential?") with up to 4 options:
    • One option per top candidate, formatted <NAME> (from <source>)
    • Plus a Paste manually instead escape hatch
    • If >3 candidates, show the top 3 by slug-relevance and add a Show all option that re-asks with the rest.
  • **If

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars3.7k
CategoryDevelopment
Updated2mo ago
Forks241

Languages

JavaScript

Trust signals

88/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 medium
agent-experience — Claude Code Skill: Install & Safety Check | SkillAgent