agentleFS
o1xhacko1xhack/CodexBar-Mobile/.agents/skills/qa-test/SKILL.md

qa-test

Skill76 starsChanged 15 days agoMITView on GitHub

CodexBar live QA/e2e testing: run provider usage matrix checks, validate real app config, use Peekaboo for menu proof, use Browser Use/official docs for API spec or logged-in dashboard checks, and handle 1Password credentials safely.

  • Reads credentials

2 other projects use a version of this; 1 new project in the last 4 weeks, against 0 the 4 before.

Adopted by

Surging: 1 new project took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 1 new projectWeek of Nov 1: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 1 in all, so this is a hint, not a trend.

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 2

    1. steipete/CodexBar★ 23k100% same
    2. Richard-Yang0130/vibe-island★ 4100% same

    Edited · 0

    None found.

    Wrote their own version · 0

    None found.

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository6 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

12 rules. About 0 are common, 5 are distinctive, and 7 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 7

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use for live provider testing, release smoke tests, menu verification, or debugging “provider works/fails” reports.

    line 8
  2. Very specific:

    Use the packaged CLI first: CodexBar.app/Contents/Helpers/CodexBarCLI.

    line 13
  3. Very specific:

    Do not use CodexBar.app/Contents/MacOS/codexbar.

    line 14
  4. Very specific:

    Never run broad env, set, or secret regex dumps.

    line 15
  5. Very specific:

    Use $one-password for secrets: all op commands inside one persistent tmux session, service account first, no raw secret output.

    line 16
  6. Very specific:

    Treat browser-cookie/keychain flows as prompt-risky.

    line 17
  7. Distinctive:

    Run the bundled script:

    line 22
  8. Distinctive:

    Before editing config, make a backup:

    line 63
  9. Distinctive:

    Use Peekaboo after CLI checks:

    line 72
  10. Very specific:

    Verify visually with view_image.

    line 89
  11. Very specific:

    Use $browser-use only when a logged-in dashboard, API key page, or provider docs need browser/profile state.

    line 93
  12. Distinctive:

    If Browser Use is unavailable, say so and use web search for public official docs.

    line 103

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

CodexBar Live QA

Use for live provider testing, release smoke tests, menu verification, or debugging “provider works/fails” reports.

Rules

  • Work from the CodexBar repo checkout.
  • Use the packaged CLI first: CodexBar.app/Contents/Helpers/CodexBarCLI.
  • Do not use CodexBar.app/Contents/MacOS/codexbar; that is the app binary and may appear to hang as a CLI.
  • Never run broad env, set, or secret regex dumps.
  • Use $one-password for secrets: all op commands inside one persistent tmux session, service account first, no raw secret output.
  • Treat browser-cookie/keychain flows as prompt-risky. Prefer CLI/API-token checks and KeychainNoUIQuery-safe tests unless the user explicitly requested live UI.
  • For current API behavior, browse official provider docs only.

CLI Matrix

Run the bundled script:

.agents/skills/qa-test/scripts/live_provider_matrix.sh --enabled

Useful modes:

.agents/skills/qa-test/scripts/live_provider_matrix.sh --provider all
.agents/skills/qa-test/scripts/live_provider_matrix.sh --providers openai,zai,deepseek
.agents/skills/qa-test/scripts/live_provider_matrix.sh --default

Interpretation:

  • --enabled asks CodexBarCLI config providers for enabled providers, honoring CODEXBAR_CONFIG and default toggles.
  • --default runs the app-facing default command with no provider override.
  • --provider all forces every registered provider and is expected to fail for providers without sessions/keys.
  • A green app config needs --enabled and --default clean; --provider all is a discovery/triage tool.

Config QA

Validate config:

CodexBar.app/Contents/Helpers/CodexBarCLI config validate
stat -f '%Lp %N' "$HOME/.codexbar/config.json"

Redact config shape:

jq '(.providers // []) |= map(.apiKey = (if .apiKey then "<redacted>" else .apiKey end) |
  .secretKey = (if .secretKey then "<redacted>" else .secretKey end) |
  .cookieHeader = (if .cookieHeader then "<redacted>" else .cookieHeader end) |
  (if .id == "stepfun" and has("region") then .region = "<redacted>" else . end) |
  .tokenAccounts = (if .tokenAccounts then (.tokenAccounts | .accounts = (.accounts | map(.token = "<redacted>"))) else .tokenAccounts end))' \
  "$HOME/.codexbar/config.json"

Before editing config, make a backup:

cp "$HOME/.codexbar/config.json" "$HOME/.codexbar/config.pre-qa-$(date +%Y%m%d%H%M%S).json"
chmod 600 "$HOME/.codexbar"/config.pre-qa-*.json

Live Menu QA

Use Peekaboo after CLI checks:

pkill -x CodexBar || pkill -f 'CodexBar.app/Contents/MacOS/CodexBar' || true
open -n "$PWD/CodexBar.app"
peekaboo menu list-all --json | rg -i 'codexbar'
peekaboo menu click-extra --title codexbar-merged --json
screencapture -x /tmp/codexbar-live-menu.png

Crop top-right menu if needed:

sips --cropToHeightWidth 900 340 --cropOffset 20 2650 /tmp/codexbar-live-menu.png \
  --out /tmp/codexbar-live-menu-crop.png >/dev/null

Verify visually with view_image. Confirm provider tabs/rows match enabled config and no failing provider dominates the first screen.

Browser Use

Use $browser-use only when a logged-in dashboard, API key page, or provider docs need browser/profile state.

Existing Chrome path:

mcporter call chrome-devtools.list_pages --args '{}' --output text
mcporter call chrome-devtools.navigate_page --args '{"url":"https://provider.example"}' --output text
mcporter call chrome-devtools.take_snapshot --args '{}' --output text

If Browser Use is unavailable, say so and use web search for public official docs; do not substitute isolated Playwright for login/profile-dependent pages.

Fix Triage

  • Missing auth/session: configure key/session if available; otherwise leave provider disabled or report blocked auth.
  • Wrong provider API/spec: inspect official docs, then patch fetcher/settings/tests.
  • Provider key exists but live API rejects it: keep key stored if useful, disable provider if the menu would show a persistent error.
  • User-facing behavior changes need CHANGELOG.md.
  • Code fixes need focused tests, make check, $autoreview, and live CLI proof before landing.

Known CodexBar QA Notes

  • OpenAI Admin API key is the useful usage provider key. Project OPENAI_API_KEY values can fail legacy credit-balance fallback with 403.
  • Deepgram usage requires a key/project with Management API permissions; transcription-only keys can return 403.
  • Groq usage uses the Prometheus metrics API, not ordinary inference endpoints.
  • MiniMax pay-as-you-go API keys and Token Plan/Coding Plan keys are different; wrong key kind can leave usage unavailable.

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.