Browse open-source agent skills from verified GitHub sources. Every entry links to the exact repository directory and includes practical setup notes, use cases, and prompts.
34
Skill guides
6
Workflow categories
16
Verified publishers
100%
GitHub linked
Why skills
Each listing points to a public source from its publisher, so you can inspect the actual files before installing or enabling anything in your agent.
Open the linked GitHub directory and review the skill files.
Follow the publisher-specific setup shown on the detail page.
Adapt an example prompt, then check the result before relying on it.
Curated library
Every listing includes its publisher, exact GitHub source, setup guidance, example prompts, and related skills.
Showing 34 skill guides
Turn descriptions of everyday machines into interactive, hand-inked isometric figures with working controls and cutaway views.
Typical outcome
Illustrate how everyday machines work.
Best for
Designers, educators, and creators building interactive explanations of everyday devices.
Create a Colorfigure of a kettle with a working switch and a cutaway showing its automatic shutoff.
Design and refine logos from brief to production-ready SVGs, with concept exploration, optical refinement, testing, and brand guidelines.
Typical outcome
Explore wordmarks, monograms, symbols, and combination marks.
Best for
Founders, designers, and teams creating or refreshing a product or company identity.
Design three distinct logo concepts for my AI tools directory. Present an overview and recommendation before creating the full kit.
Refactor React components with compound components, state lifting, and composition patterns that avoid boolean-prop sprawl.
Typical outcome
Replace components with too many boolean props.
Best for
React developers designing reusable component APIs and shared UI systems.
Refactor this component using composition patterns without changing its behavior.
Apply Vercel Engineering guidance to React and Next.js code, with emphasis on performance, rendering, and bundle efficiency.
Typical outcome
Find data-fetching waterfalls.
Best for
Frontend teams reviewing production React and Next.js applications.
Review these React changes against Vercel's React best practices.
Use Vercel's React Native guidance for architecture, performance, layout, animations, images, and platform behavior.
Typical outcome
Audit scrolling and rendering performance.
Best for
React Native and Expo developers building or reviewing mobile applications.
Audit this React Native screen for performance and platform issues.
Implement native-feeling page and component transitions with React's View Transition APIs and Next.js patterns.
Typical outcome
Add route transitions to Next.js.
Best for
React developers adding accessible, directional, or shared-element transitions.
Add an accessible shared-element transition between these routes.
Package and deploy web applications to Vercel, returning a preview URL and a claimable deployment when supported.
Typical outcome
Deploy a Next.js, React, or static site.
Best for
Developers and creators who need a repeatable Vercel deployment workflow.
Deploy this application to Vercel and return the preview URL.
Use Vercel CLI workflows with explicit token handling for authenticated project and deployment operations.
Typical outcome
Authenticate non-interactive CLI commands.
Best for
Developers automating Vercel operations in agents, CI, or scripts.
Use Vercel CLI with the provided token to inspect deployment status.
Audit a Vercel project for cost, performance, reliability, caching, function usage, and build efficiency.
Typical outcome
Investigate slow or expensive routes.
Best for
Teams operating production applications on Vercel.
Audit this Vercel project and rank cost and performance improvements.
Review web interfaces against Vercel's accessibility, performance, UX, interaction, and responsive-design guidance.
Typical outcome
Audit accessibility and focus behavior.
Best for
Designers and frontend developers reviewing production interfaces.
Review this interface against the web design guidelines.
Review documentation and product prose against Vercel's guidance for voice, structure, code samples, and readability.
Typical outcome
Review documentation voice and structure.
Best for
Technical writers, developer advocates, and product teams.
Review this documentation against Vercel's writing guidelines.
Turn an Agent Skills-compatible assistant into a local SEO specialist with 38 open-source skills for audits, Google Business Profile optimization, rankings, reviews, citations, reporting, and AI visibility.
Typical outcome
Audit a local business and prioritize search visibility issues.
Best for
Local SEO consultants, agencies, and multi-location marketing teams using Claude, Cursor, Codex, or another Agent Skills-compatible assistant.
Audit this local business and prioritize the issues blocking map pack visibility.
Run parallel, evidence-led SEO audits with 25 sub-skills and 18 specialist agents covering technical SEO, E-E-A-T, Schema.org, GEO, backlinks, local SEO, e-commerce, and international SEO.
Typical outcome
Run a full-site SEO audit and produce a prioritized, testable action plan.
Best for
SEO agencies, in-house search teams, and consultants using Claude Code for repeatable site audits and prioritized optimization plans.
/seo audit https://example.com
Use Rewamp UI's copy-paste React components and CLI to add highly interactive, Framer Motion-driven interface elements without depending on a wrapper package.
Typical outcome
Add an animated component directly to an existing React project.
Best for
React developers and design-focused teams building expressive interfaces with Tailwind CSS, Framer Motion, and optional Three.js effects.
Use Rewamp UI to add an animated theme toggle that matches this project's existing design tokens.
Create distinctive, production-grade frontend interfaces with deliberate typography, color, layout, and visual identity instead of generic AI-generated styling.
Typical outcome
Turn a product brief into a specific visual direction before coding.
Best for
Design engineers, frontend developers, and product teams building polished web pages and interfaces from a brief.
Design and build this landing page with a distinctive visual identity grounded in the product's subject matter.
Translate Apple's fluid-interface principles to the web with responsive feedback, interruptible motion, physical gestures, depth, typography, and reduced-motion support.
Typical outcome
Design fluid drag, swipe, sheet, and spring interactions.
Best for
Design engineers creating tactile web interactions, gesture-driven surfaces, sheets, drawers, and polished motion systems.
Make this bottom sheet feel fluid and interruptible using Apple-style motion principles.
Apply refined, layered shadows that give cards, controls, popovers, and hero surfaces clear depth without muddy or exaggerated effects.
Typical outcome
Replace blunt default shadows with layered elevation.
Best for
Frontend developers and designers polishing elevation, surface hierarchy, and visual depth in Tailwind interfaces.
Replace the generic shadows in this interface with a restrained elevation system.
Audit and improve web accessibility against WCAG 2.2, covering semantics, keyboard navigation, focus, contrast, forms, media, and assistive technologies.
Typical outcome
Run an evidence-led WCAG 2.2 accessibility audit.
Best for
Frontend teams, accessibility reviewers, and product engineers preparing inclusive production interfaces.
Audit this page against WCAG 2.2 and prioritize issues by user impact.
Run a sharp, prioritized critique of a URL, screenshot, or component across hierarchy, typography, spacing, color, motion, states, responsiveness, accessibility, and brand consistency.
Typical outcome
Review a screenshot, live page, or component implementation.
Best for
Designers, founders, and frontend teams looking for specific, ranked fixes before shipping an interface.
Review this landing page and rank the highest-impact design issues with specific fixes.
Build polished interfaces with Emil Kowalski's guidance on purposeful animation, responsive components, gestures, accessibility, and the small details that shape how a product feels.
Typical outcome
Decide whether an interaction needs animation and choose its purpose, easing, and duration.
Best for
Design engineers and frontend developers refining production interfaces, component behavior, and motion.
Review this interface using Emil Kowalski's design-engineering principles. Show specific before-and-after fixes for component feedback and motion.
Use a project-aware shadcn/ui workflow to search, add, compose, theme, and repair components with the correct CLI and implementation patterns.
Typical outcome
Inspect a project's shadcn configuration before adding components.
Best for
React and Next.js developers building product interfaces with shadcn/ui, Tailwind CSS, Radix, or Base UI.
Inspect this project's shadcn configuration and add the components needed for this settings page.
Adapt interfaces across breakpoints, devices, input methods, and platform constraints by rethinking the experience instead of merely scaling pixels.
Typical outcome
Rework a desktop interface for mobile and touch.
Best for
Product designers and frontend teams adapting desktop, mobile, tablet, print, or email experiences.
Adapt this desktop dashboard for mobile without hiding its core functionality.
Run a holistic, evidence-led interface review across accessibility, layout, UX writing, typography, color, visual polish, and motion.
Typical outcome
Review an interface across multiple design disciplines.
Best for
Design engineers and product teams that need a consolidated interface-quality review with ranked, actionable findings.
Run a holistic review of this interface and return one prioritized set of actionable findings.
Design and implement purposeful microinteractions, motion, transitions, loading states, gestures, and user feedback patterns that improve usability and delight.
Typical outcome
Add clear feedback to buttons, forms, loading states, and notifications.
Best for
Frontend developers and product designers building animated, stateful, and gesture-driven user experiences.
Design the microinteractions and feedback states for this workflow without over-animating it.
Audit a product flow or interface by capturing evidence first, then reporting usability, hierarchy, and interaction issues.
Typical outcome
Audit a product flow from screenshots.
Best for
Product teams reviewing onboarding, settings, checkout, and multi-step workflows.
Audit this onboarding flow and prioritize completion blockers.
Generate visual design directions and remixes from a product brief, reference, or existing interface.
Typical outcome
Explore visual directions.
Best for
Product designers and founders exploring alternatives before implementation.
Create three distinct visual directions for this dashboard brief.
Implement a selected screenshot, mockup, or generated design reference as a faithful responsive frontend.
Typical outcome
Build a page from a screenshot.
Best for
Frontend teams turning approved visual references into working interfaces.
Implement this reference as a responsive Next.js page.
Route product-design work to the right workflow for research, auditing, ideation, or implementation.
Typical outcome
Choose the right design workflow.
Best for
Teams that want a consistent entry point for varied product-design requests.
Choose the right product-design workflow for this request.
Clone a live URL into a runnable frontend-only local application with responsive behavior.
Typical outcome
Recreate a live page locally.
Best for
Frontend developers recreating an existing web experience with permission.
Recreate this URL as a responsive frontend-only app.
Create, inspect, and edit connected Google Docs while preserving document structure and requested scope.
Typical outcome
Create a document from structured content.
Best for
Teams collaborating on briefs, reports, proposals, and operational documents.
Create a Google Doc from this approved outline.
Read and manage comments on connected Google Drive files for focused review and follow-up workflows.
Typical outcome
Summarize unresolved feedback.
Best for
Teams coordinating feedback and approvals across shared Drive files.
Summarize unresolved comments and group them by owner.
Find, inspect, organize, and manage connected files and folders in Google Drive.
Typical outcome
Find files by metadata.
Best for
Teams using Drive as a shared source of truth for documents and project files.
Find the latest approved project brief and report its location.
Analyze and edit connected Google Sheets with precise ranges, formulas, formatting, and chart-aware workflows.
Typical outcome
Inspect formulas and ranges.
Best for
Operators and analysts working with shared data, models, and trackers.
Explain the current formulas and fix only the broken range.
Create and edit connected Google Slides presentations with deliberate structure, layout, and review boundaries.
Typical outcome
Create slides from an outline.
Best for
Teams preparing collaborative sales, training, project, and executive presentations.
Create a concise Google Slides deck from this approved brief.
Build a workflow
Start with a guide, adapt it to your tools and constraints, then keep the checks that make the result trustworthy for your team.
What each guide includes
A specific job and the people it helps.
Concrete use cases and adaptable prompts.
A short execution and verification checklist.
FAQs and links to related workflows.
