phase-1-schema
|
phase-2-convention
|
phase-3-mockup
|
phase-4-api
|
phase-5-design-system
|
phase-6-ui-integration
|
phase-7-seo-security
|
phase-8-review
|
phase-9-deployment
|
plan-plus
|
pm-discovery
|
qa-phase
|
rollback
|
skill-create
|
skill-status
|
sprint
|
starter
|
zero-script-qa
|
dynamic
|
enterprise
|
audit
|
bkend-auth
|
bkend-cookbook
|
bkend-data
|
bkend-quickstart
|
bkend-storage
|
bkit-rules
|
bkit-templates
|
unsplash
Search and fetch photos from Unsplash with proper attribution. Use when users need images for content, want photos by keyword, need random images for variety, or ask for stock photos. Automatically provides attribution required by Unsplash guidelines.
company-admin
Access and update company administrative information stored in Notion
debug prod issues
Debug production issues on Vercel using logs, database inspection, and proper deployment waiting
self-improve
Update skill documentation and extend OpenCode capabilities based on learnings
skill-authoring
Create and register new OpenCode skills in this repo
skill-creator
Create new OpenCode skills with valid SKILL.md frontmatter.
skill-reinforcement
Always and Automatically improve skills after each use by capturing learnings and anti-patterns
test-staging-branch
Test feature branches on Vercel preview deployments using Chrome automation and Gmail OTP
testability
Make features testable by design. Testing pyramid from fast (local) to slow (UI). Expose APIs securely for testing.
workspace-guide
Workspace guide to introduce OpenWork and onboard new users.
0-finance-cli
Keep the 0 Finance CLI aligned with product capabilities.
browser-automation
Reliable, composable browser automation using minimal OpenCode Browser primitives.
character-sprite
>
desk-accessory
>
office-sprite
>
speak
Provides concise spoken alerts and digests through the mcp-tts MCP server. It should be selected proactively for significant AI and DevOps transitions: a substantial plan is ready, a long build/test/deploy/release/monitoring phase changes state, a major task completes, a terminal blocker or exhausted retry budget needs attention, user approval/authentication/manual action is required, or a lengthy final result needs a short audible summary. Do not use for routine progress or ordinary short replies.
qa
QA-test a website or web app and return a 1-5 quality score (5 = flawless, 1 = broken) with evidence. Use when the user wants to test, QA, evaluate, score, or "check how good" a site, page, flow, or app — including a local dev server (e.g. "qa test localhost:5173", "does the checkout work?", "rate this landing page"). Drives a real Browser Use cloud browser, tunneling localhost automatically.
remote-browser
Controls an isolated Browser Use Cloud browser from a sandboxed machine with the current Browser Use CLI.
x402
Set up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key. Two setups it works out up front — "just use it" (set up a wallet so you or Claude Code can run cloud browser tasks paid from the wallet — Claude writes and runs throwaway scripts, nothing touches your codebase) or "build it in" (install the SDK and write the key + code into your project). Walks through wallet setup, funding, .env, and a ~$1 test run. Use when the user asks about x402, pay-per-use, USDC payments, or wants Browser Use Cloud without an API key. For the free-tier signup (reverse-CAPTCHA → API key), use `browser-use cloud signup` or the `cloud` skill instead.
browser-use
Direct browser control via CDP for web interaction: automation, scraping, testing, screenshots, and site/app work.
cloud
>
open-source
>
Page 97 of 1687 · 84306 results