Agent browser
Gives agents a browser automation CLI for navigating sites, filling forms, clicking, and capturing screenshots.
Skills for task automation.
18 skills
Gives agents a browser automation CLI for navigating sites, filling forms, clicking, and capturing screenshots.
Applies the Caveman agent workflow—lean, evidence-first habits—for coding sessions.
Deploys applications and sites to Vercel with the correct project and CLI workflows.
Configures EAS Workflows for CI/CD—builds, submits, and automation against Expo Application Services.
Creates a new Figma file via MCP with the correct project/team setup for agent workflows.
Mandatory guidance before use_figma MCP writes—Plugin API rules for creating/editing Figma nodes safely.
OpenClaw-oriented investigate workflow from gstack—public SKILL.md for ClawHub/OpenClaw agent use.
Compacts a conversation into a handoff document for another agent or coding session.
Creates and manages Linear issues, projects, and workflow updates from agent sessions.
Runs exploratory and production queries against MotherDuck/DuckDB with good agent workflows.
Automates browsers with Playwright for testing and agent-driven UI verification.
Operates Prisma Postgres across Console, create-db CLI, and Management API workflows.
Walks you through creating, improving, and evaluating Agent Skills (SKILL.md packages) so Claude/agents load specialized workflows correctly.
Saves your last gstack scrape as a reusable browser skill.
Builds and extends Stripe Apps that embed into the Stripe Dashboard and workflows.
Runs Tinybird CLI workflows—local dev, deployments, and datafile (.pipe/.datasource) operations.
Triages issues and external pull requests by categorizing, verifying, reviewing, and writing agent-ready tasks.
Explains how to use the Superpowers skill suite—when to invoke which workflow skills.
An agent skill is a portable pack of instructions that gives an agent specialized know-how for a task. In the open Agent Skills format (from Anthropic, now widely adopted), that pack is a folder with a SKILL.md file and optional scripts or references the agent can load when needed.
SKILL.md is the required main file in a skill folder. It starts with simple metadata (name and description) plus the instructions. Agents use the metadata to decide when a skill applies, then read the full file — and any linked files — only when the task needs them.
Open the listing and follow the source link — usually a GitHub SKILL.md. Install with your agent’s skill flow, or add the repo the way that product documents. When this site shows the skill text, Copy is on the page.
A prompt is paste-in text for one chat turn (or a short thread). A skill is a reusable file pack an agent can discover and load across a task, sometimes with code attached. Prompts live in the prompt directory; skills usually live on GitHub and we link out.
Each skill uses one sitewide category — the same set as the rest of the directory (Coding agent, Marketing, Document intelligence, and so on). Hops filter to categories that already have skills.
Yes. Submit with a public GitHub SKILL.md URL, or attach a skill as part of a method on a use case. An editor reviews it before it appears here.