Every scene is a path you can run: which skills to use, how to install, how to prompt, and what traps to avoid.
Pick a scene to start
Personal efficiency is not "busier" — it's offloading fragments to a reliable system: capture → consolidate → plan → review. Let AI do note cleanup, knowledge merge, planning breakdown; you only judge "keep or not, what's next", leaving your head for what truly needs thinking.
The biggest lever in social content is the topic — communities widely agree "topic decides 60%+ of a post's success". Have AI mine last-7-day hits for direction first, then run topic → script → image/video → multi-platform → review. Far better than staring at a blank page.
A workflow that actually runs is not "one bot sells for you". It splits sourcing → copy → video → listing → review into repeatable steps, AI drafts each, you make the key calls. Community consensus: build the minimum viable chain first, then automate deeper.
AI writes fast, but the quality gate matters more. Community consensus in three: reverse TDD (AI writes tests, then minimal impl), zero-warning gate (`--max-warnings=0`, warnings silently become the new baseline), review as a gate (every change through the same gate). Make AI output verifiable and g
Fastest way to regret AI code: "it writes fast but you dare not merge". Core: give it coding standards, then review and refactor; you make the merge call, not hand over the keyboard.
Browser-automation pain is "brittle scripts, break on any change". The point of AI: give a clear goal and a done-criteria, let it walk and self-verify, not hardcode XPath and maintain forever.
The biggest value of testing isn't "high coverage" — it's "catching the paths that actually break". The point of AI-generated tests: give it the implemented code or a clear behavior contract, then have it add edge cases. Don't let it invent the thing under test; a test that passes on a fake object p
The scare with doc-writing is "AI sounds right but the API name is invented". The discipline: have AI write from real code / real docs, then match each paragraph to source. Don't let it invent APIs from memory.
The classic failure mode is twenty "suggestions" where eighteen are style preferences. A useful review contains only two kinds of information: what will break, and what will confuse the next reader. So the job is not to make AI say more. It is to forbid everything else.
browser-use/browser-use/skills/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.
heygen-com/hyperframes/skills/pr-to-video
Turn a GitHub pull request (a PR URL, owner/repo#N, or 'this PR' in a checked-out repo) into a code-change explainer video — changelog, feature reveal, fix, or refactor walkthrough built from the diff, commits, and files: the input is a code change, not a website. Not a product promo (/product-launch-video) or a no-PR topic explainer (/faceless-explainer). Unclear → /hyperframes.
heygen-com/hyperframes/.agents/skills/seam-craft
Render-correctness doctrine for scene-to-scene seams in HyperFrames launch videos — the prerequisites that make transitions composite correctly on the master timeline. Load when assembling the master timeline / index.html, when a white flash appears at a cut or crossfade seam (especially on dark films), when reasoning about why a transition opacity dip shows through, or when verifying the render-side mechanics of how overlapping scene wrappers blend. Covers the opaque stage-ground (#root background) white-flash guard and how the injector overlaps wrappers, holds final frames, ping-pongs tracks, and stamps lint-clean template code onto the master timeline. Does NOT contain the per-transition catalog — see the transition registry for individual transition entries.
get-convex/agent-skills/skills/convex-backup
Set up Convex backups and run a restore DRILL that proves recovery — snapshot, restore into a throwaway preview, assert the data came back — plus a schedule matched to your RPO and a gated recovery runbook.
get-convex/agent-skills/skills/convex-launch-readiness
Run every Convex audit (authz, reviewer, advisor, insights) into one scored, deduped readiness report with an ordered fix plan — Lighthouse for your backend.
get-convex/agent-skills/skills/convex-cost
Preview Convex spend — rank functions by bytes/documents-read × call-volume from insights, project each cost driver's growth curve, name the cheapest fix; confirm-cost for paid actions.
get-convex/agent-skills/skills/convex-expert
Convex backend specialist. Use this agent for any code inside a `convex/` directory — function definitions, schemas, indexes, queries, mutations, actions, HTTP endpoints, cron jobs, file storage, auth wiring, and component installation. Knows the object-form function syntax, validator patterns, resource limits, and component ecosystem that generic Claude routinely gets wrong.
get-convex/agent-skills/skills/convex-migrate-rehearse
Rehearse a live-app schema change + backfill on a snapshot-seeded preview deployment, verify, then promote the proven change to prod with the snapshot as rollback.