Skill per agenti
Skill per Claude Code, Codex, Cursor e altri agenti dalla directory skills.sh: installazioni, stato dell'audit di sicurezza e il comando per aggiungere una skill.
Una skill non è legata a un solo agente: npx skills add la installa in qualsiasi agente supportato. Senza -a, la CLI trova gli agenti sul tuo computer e chiede dove aggiungerla.
Aggiornato · Fonti: skills.sh
Mostrate: 13 · trovate: 13 · su 10.000 nella directory
-
playwright-best-practices currents-dev/playwright-best-practices-skill
Use when writing Playwright tests, fixing flaky tests, debugging failures, implementing Page Object Model, configuring CI/CD, optimizing performance, mocking APIs, handling authentication or OAuth, testing accessibility (axe-core), file uploads/downloads, date/time mocking, WebSockets, geolocation, permissions, multi-tab/popup flows, mobile/responsive layouts, touch gestures, GraphQL, error handling, offline mode, multi-user collaboration, third-party services (payments, email verification), console error monitoring, global setup/teardown, test annotations (skip, fixme, slow), test tags (@smoke, @fast, @critical, filtering with --grep), project dependencies, security testing (XSS, CSRF, auth), performance budgets (Web Vitals, Lighthouse), iframes, component testing, canvas/WebGL, service workers/PWA, test coverage, i18n/localization, Electron apps, or browser extension testing. Covers E2E, component, API, visual, accessibility, security, Electron, and extension testing.
90.826 Non superato -
brand-landingpage wshobson/agents
Brand-first landing page designer — runs a brand-identity interview (colors, typography, shape language), then generates and iterates on a polished landing page via Stitch with deployment-ready HTML. Use when the user asks to create, design, or build a landing page, homepage, or marketing page and has no established visual direction. Skip when they have a design mockup, need a dashboard or app UI, are working at component level, building a multi-page app, or restyling with known design tokens — use frontend-design instead.
39.013 Non superato -
ckm:design nextlevelbuilder/ui-ux-pro-max-skill
32.495 Non superato -
scoutqa-test github/awesome-copilot
This skill should be used when the user asks to "test this website", "run exploratory testing", "check for accessibility issues", "verify the login flow works", "find bugs on this page", or requests automated QA testing. Triggers on web application testing scenarios including smoke tests, accessibility audits, e-commerce flows, and user flow validation using ScoutQA CLI. Use this skill proactively after implementing web application features to verify they work correctly.
9.949 Non superato -
stitch::manage-design-system google-labs-code/stitch-skills
Manage design systems in Stitch using MCP tools. Includes retrieval of assets, creating/updating design systems in Stitch, and applying them to screens.
9.269 Non superato -
stitch::code-to-design google-labs-code/stitch-skills
Convert frontend code (Vite, React, Angular, Vue, etc.) to a Stitch Design by chaining static HTML extraction, design system extraction, and file upload. **ALWAYS** use this skill when the user's intent is to move existing web apps or React/Angular/Vue components into Stitch (e.g., requests to "save", "migrate", or "upload"). You must use this skill even for simple "save" operations, as it is the only way to ensure the design system is extracted and assets are properly linked.
9.176 Non superato -
reka-ui onmax/nuxt-skills
Use when building with Reka UI (headless Vue components) - provides component API, accessibility patterns, composition (asChild), controlled/uncontrolled state, virtualization, and styling integration. Formerly Radix Vue.
7.204 Non superato -
baoyu-design jimliu/baoyu-design
Create polished design artifacts as self-contained HTML: UI mockups, interactive prototypes, wireframes, landing pages, dashboards, app screens, mobile apps, slide decks (a.k.a. PPT / PowerPoint presentations), documents and résumés, animations, 3D objects, research reports, HTML email, diagrams, fliers, and visual explorations. Use whenever the user asks to design, mock up, prototype, wireframe, visualize, explore, or make a PPT/deck for an interface, product screen, user flow, content layout, visual artifact, or pitch/deck concept, even if they do not say "design". Also use to export a deck built with this skill to PowerPoint (PPT/PPTX) — but only decks authored here (deck-stage / this skill's slide-structured HTML), NOT arbitrary HTML, so confirm the target is such a deck first. Also use for setting up, importing, or authoring reusable design systems, UI kits, brand tokens, or component libraries. Harness-agnostic for Claude Code, Cursor, Codex Agent, and similar file-capable agents.
5.870 Non superato -
ui-ux-pro-max sickn33/agentic-awesome-skills
Comprehensive design guide for web and mobile applications. Use when designing new UI components or pages, choosing color palettes and typography, or reviewing code for UX issues.
3.455 Non superato -
apify-brand-reputation-monitoring apify/agent-skills
2.518 Non superato -
understand-figma egonex-ai/understand-anything
Analyze a Figma file via the Figma REST API and generate an interactive design knowledge graph (pages, screens, components, component sets, instances, design tokens) with a kind:"design" dashboard.
1.473 Non superato -
21st-design-sync 21st-dev/skill
Look at the current project's design (its shadcn / Tailwind CSS variables and color tokens) and publish it to the 21st.dev community as a shareable theme, using `21st publish-theme`. Use when the user says "publish my theme", "share our design as a 21st theme", "sync my design to 21st", "turn my globals.css into a theme", "залей наш дизайн темой", "опубликуй тему". This is the 21st equivalent of design-sync: it reads the project's design tokens and syncs them into the public theme library.
1.356 Non superato -
ui-ux-pro-max likaia/nginxpulse
UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient.
1.329 Non superato
Le descrizioni sono degli autori, in inglese. Leggi il codice di una skill nel suo repository prima di installarla.
Che cos'è una skill
Una skill è una cartella con un file SKILL.md e, se serve, alcuni script: contiene istruzioni che un agente carica quando il compito corrisponde, per esempio come scrivere test in un certo framework o come preparare un rilascio. Questa directory raccoglie le skill di skills.sh per Claude Code, Codex, Cursor e altri agenti. Per ciascuna trovi nome, autore e repository, installazioni, stato dell'audit di sicurezza e il comando per aggiungerla, con il pulsante «Copia il comando».
Cosa mostra la pagina
- 10.000 skill ordinate per installazioni, sincronizzate ogni giorno da skills.sh;
- la vista «Di tendenza», basata sulle installazioni guadagnate negli ultimi 7 giorni;
- i filtri per argomento e per agente e una ricerca, con al massimo 100 skill per vista.
Le descrizioni sono quelle scritte dagli autori, in inglese, e non vengono tradotte.
Come leggere l'audit
Lo stato dell'audit viene dagli audit pubblicati da skills.sh e ha quattro valori: «Superato», «Avvisi», «Non superato» e «Non verificata». Un audit superato è un buon segnale, ma non una garanzia: una skill può eseguire script sul tuo computer, quindi leggi il codice nel repository su GitHub prima di installarla. Diffida delle skill che chiedono accessi non necessari al loro scopo.
Come aggiungere una skill
Trovata la skill che ti serve, controlla con quali agenti è compatibile, apri il repository e leggi il file SKILL.md per capire cosa fa. Poi copia il comando con il pulsante dedicato e lancialo nella cartella del progetto o nella configurazione del tuo agente. Dopo l'installazione, prova la skill su un compito semplice e verifica che l'agente la usi come previsto.
Da dove vengono i numeri
Le installazioni sono contate da skills.sh, non da noi: servono a capire cosa usano gli altri sviluppatori, non a giudicare la qualità. Il codice di ogni skill sta nel suo repository. Per scegliere l'agente a cui aggiungerle, consulta la pagina degli agenti di programmazione.