Star200+

accessible-html

Revisar · 60
Indexado en Registry

Use whenever writing, editing, or reviewing markup or UI code — HTML, JSX/TSX, Vue/Svelte/Angular templates, web components, email HTML, or CSS that affects text size, color, focus, motion, layout order, or hit area. Also use when adding a button, link, form, input, modal, dropdo

Verified installs0
Estrellas39
Versión1.0.0
Calidad57/100 · Prometedor
Confianza60/100 · Solo sandbox
Auditoría72/100 · Requiere revisión

Perfil del activo

Diseño y producción creativa

Design assets, images, video, audio, multimodal media, presentation, and creative production skills.

Ver categoría

Escenario

Diseño y creatividad

I need my agent to produce design assets, UI directions, presentations, or creative media workflows.

Afinidad con Agent

Claude Code + Cursor + CLI

Funciona con Codex, Claude Code, Cursor, CLI o Agents personalizados.

Instalar

Listo

npx skills add AlemTuzlak/skills --skill accessible-html

Mantenimiento

Actual

3 días desde el último push

Riesgo

Requiere revisión

La licencia no está clara

Calidad de GitHub

39

57/100 Calidad · 68/100 Confianza

Etiquetas de cobertura

DiseñoDiseño y creatividadDiseño y creatividadagent-skill

Notas de revisión

La licencia no está clara · Permission surface may require sandboxing

Tarjeta de adopción del Agent

Confianza, auditoría y preparación de instalación de un vistazo

Estas puntuaciones combinan metadatos públicos del repositorio, señales de revisión de OpenAgentSkill, actualidad de mantenimiento y preparación de instalación. Sirven para preseleccionar; no sustituyen la revisión humana.

Calidad

Prometedor
57

Useful candidate, but compare it with alternatives before adopting.

Confianza

Solo sandbox
60

Candidata útil con señales de confianza incompletas o mixtas. Manténgala en un espacio aislado hasta que el ciclo de resultados demuestre el ajuste.

Auditoría

Requiere revisión
72

Revisión legible por máquina de la preparación de instalación, los metadatos de seguridad, el mantenimiento y el riesgo de adopción.

Trust Score de OpenAgentSkill v5

Revisión humana antes de instalar

Ejecute solo en un sandbox y compare alternativas cercanas antes de usarla en trabajo real.

CodexClaude CodeCursorOpenAgentSkill CLI

Estrellas

39 estrellas de GitHub

Actividad del repositorio

39 estrellas y 0 forks

Mantenimiento

3 días desde el último push

Licencia

Desconocido

Instalar

npx skills add AlemTuzlak/skills --skill accessible-html

Seguridad de instalación

Ruta estándar de paquete o instalación en tiempo de ejecución

Superficie de permisos

secrets or environment access, filesystem or document access

Resultados del Agent

Aún no hay datos de resultados del Agent

Documentación

Contexto sólido de README/SKILL.md

Resumen de riesgo

Revisar antes de producción

  • Repository license is unknown; no license file detected. This creates ambiguity about usage rights and redistribution.
  • La licencia no está clara
  • Low GitHub adoption signal
  • Quality score needs review

Preparación de instalación

Ruta de instalación disponible

  • La ruta de instalación está disponible
  • La evidencia del repositorio está disponible
  • La licencia no está clara
  • Aún no hay evidencia de resultados Agent-Proven

Metadatos legibles por Agent

Datos de decisión legibles por máquina para este skill.

Usa este bloque o el JSON integrado para decidir si un Agent debe instalar este skill, elegir una alternativa o pedir revisión humana primero.

Abrir JSON

Tareas adecuadas

  • flujos de GitHub automation
  • Equipos de Claude Code
  • builders willing to evaluate younger projects
  • Inspect repository metadata

Agents adecuados

CodexClaude CodeCursorOpenAgentSkill CLICLI

Decisión de instalación

Comando
npx skills add AlemTuzlak/skills --skill accessible-html
Política
Revisar
Revisión humana
Sí

Confianza y riesgo

Confianza
60/100
Auditoría
72/100
Nivel de riesgo
Requiere revisión

Ciclo de resultados

Endpoint
/api/agent/outcome
ID del evento
resolve
Resultados
5

Comando de instalación

npx skills add AlemTuzlak/skills --skill accessible-html
Auditoría públicaInforme de evaluaciónAPI ResolveTraspaso de instalación

No usar cuando

  • Equipos que necesitan un SLA con soporte del proveedor
  • production agents without a repository review
  • Low GitHub adoption signal
  • Repository license is unknown; no license file detected. This creates ambiguity about usage rights and redistribution.
  • La licencia no está clara

Skill alternativo

Frontend Design

171.1K Estrellas

npx skills add anthropics/skills --skill frontend-design

Skill alternativo

Taste Skill: Anti-Slop Frontend

79.4K Estrellas

npx skills add Leonxlnx/taste-skill --skill design-taste-frontend

Skill alternativo

Canvas Design

171.1K Estrellas

npx skills add anthropics/skills --skill canvas-design

Skill alternativo

Anthropic Brand Guidelines

171.1K Estrellas

npx skills add anthropics/skills --skill brand-guidelines

Seguridad de Agent v2

52/100 · Evitar instalación automática

ExperimentalRevisar

Sparse or mixed signals. Useful for discovery, but not for autonomous installation.

Test manually in an isolated workspace and compare against safer alternatives.

Resolver con API

Medio

Browser automation

Skill may drive a browser or interact with web pages.

Medio

Acceso a red

El skill probablemente consulta páginas remotas, API, repositorios o servicios externos.

Medio

Acceso al sistema de archivos

El skill puede leer o escribir archivos de proyecto, documentos, artefactos generados o estado local.

  • La licencia no está clara

Destinos de instalación

Instala este skill en tu flujo de Agent

Usa el endpoint público para obtener el comando, la lista de seguridad, prompts y enlaces canónicos.

skill install

OpenAgentSkill CLI

Resolve policy, run the source installer safely, and report a verified install receipt.

$ npx --yes https://github.com/Leon-Drq/openagentskill/releases/download/cli-v0.2.1/openagentskill-0.2.1.tgz install alemtuzlak-accessible-html

Plan de resolución de Agent

Deja que un Agent valide el ajuste antes de instalar.

La API Resolve devuelve la skill elegida, alternativas, política de seguridad, notas de auditoría, destino de instalación y un prompt listo para usar.

Abrir plan de texto

Abrir JSON

/api/agent/resolve?task=Use%20accessible-html%20for%20an%20agent%20workflow&agent=codex&max_risk=medium

Texto de Resolve

/api/agent/resolve?task=Use%20accessible-html%20for%20an%20agent%20workflow&agent=codex&max_risk=medium&format=text

Traspaso de instalación

/api/skills/alemtuzlak-accessible-html/install

Agent debe revisar

  • Task fit and alternatives from Resolve API.
  • Audit score, trust score, and safety policy warnings.
  • Install target compatibility for Codex, Claude Code, Cursor, or CLI.

Copiar prompt

Task: Use accessible-html in this workspace.
Resolve first: https://www.openagentskill.com/api/agent/resolve?task=Use%20accessible-html%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Review install handoff: https://www.openagentskill.com/api/skills/alemtuzlak-accessible-html/install
Install command: npx skills add AlemTuzlak/skills --skill accessible-html
Before running it, summarize audit warnings, required permissions, and the fallback skill if install is risky.

Traspaso de Agent

Da al Agent la ruta de instalación, no otro directorio.

Usa el endpoint público para obtener el comando, la lista de seguridad, prompts y enlaces canónicos.

Abrir API de instalación

Traspaso de instalación

/api/skills/alemtuzlak-accessible-html/install

Formato de texto LLM

/api/skills/alemtuzlak-accessible-html/install?format=text

Buscar alternativas

/api/skills/search?q=accessible-html&limit=3

Prompt de Agent

Use accessible-html for this task. Review https://www.openagentskill.com/api/skills/alemtuzlak-accessible-html/install, then install with: npx skills add AlemTuzlak/skills --skill accessible-html

Metadatos del Registry

Perfil legible por Agent para seleccionar skills automáticamente.

La API Registry expone señales de decisión, confianza, auditoría, casos de uso e instalación sin raspar la interfaz.

Abrir Manifest

Manifest

/api/registry/manifest/alemtuzlak-accessible-html

Texto LLM

/api/registry/manifest/alemtuzlak-accessible-html?format=text

Alias de instalación

/api/registry/install/alemtuzlak-accessible-html

Recomendar

/api/registry/recommend?task=Use%20accessible-html%20in%20an%20agent%20workflow&limit=3

Afinidad con Agent

59/100

GitHub automation

Etiquetas de uso

GitHub automationTesting and QABrowser automation

Plataformas

Claude Code, Cursor

Informe de auditoría

Requiere revisión · 72/100

Revisión legible por máquina de la preparación de instalación, los metadatos de seguridad, el mantenimiento y el riesgo de adopción.

Ver informe de auditoríaVer informe de evaluación

Panel de decisión de Agent

Fallback candidate for GitHub automation

Prototype with this skill first; keep a fallback candidate ready.

59
Preparación
Prototipo
Etapa

Rol en la pila

Candidata de respaldo

Ajuste principal

GitHub automation

Etiqueta de confianza

Prototipar primero

Ruta de instalación

Comando listo

Úsalo cuando

  • flujos de GitHub automation
  • Equipos de Claude Code
  • builders willing to evaluate younger projects

Evidencia

  • recent repository activity
  • install command or GitHub repo available
  • perfil de calidad 57/100
  • 7 eventos de interacción de OpenAgentSkill

revisar primero

  • Low GitHub adoption signal
  • Repository license is unknown; no license file detected. This creates ambiguity about usage rights and redistribution.

Ruta de implementación

  1. 1Instálalo en un Agent de sandbox y ejecuta una tarea de GitHub automation de principio a fin.
  2. 2Compare output quality, latency, and failure behavior against at least one alternative.
  3. 3Promote it into production only after reviewing repository permissions, license, and maintenance signals.

Perfil de confianza

Solo sandbox

Candidata útil con señales de confianza incompletas o mixtas. Manténgala en un espacio aislado hasta que el ciclo de resultados demuestre el ajuste.

60
Trust Score de OpenAgentSkill

Adopción en GitHub

Revisar

39 estrellas de GitHub

Actividad de stars/forks

Revisar

39 estrellas y 0 forks; la actividad de issues no está disponible en los metadatos actuales

Mantenimiento reciente

Aprobado

3 días desde el último push

Claridad de licencia

Revisar

Desconocido

Señales positivas

  • Revisión de IA aprobada
  • La ruta de instalación está disponible
  • La evidencia del repositorio está disponible
  • Repositorio mantenido recientemente
  • El comando de instalación no muestra un patrón de alto riesgo evidente
  • El ciclo de resultados está listo, pero necesita la primera ejecución real de Agent

Revisar antes de instalar

  • Repository license is unknown; no license file detected. This creates ambiguity about usage rights and redistribution.
  • La licencia no está clara
  • Low GitHub adoption signal
  • Quality score needs review
  • Permission surface needs review: secrets or environment access, filesystem or document access
  • GitHub adoption: 39 GitHub stars
  • Stars/forks activity: 39 stars, 0 forks; issue activity unavailable in current metadata
  • License clarity: Unknown
  • Permission surface: secrets or environment access, filesystem or document access
  • Aún no hay informes reales de resultados del Agent
  • Se requiere revisión humana antes de una instalación desatendida

Acción recomendada

Ejecute solo en un sandbox y compare alternativas cercanas antes de usarla en trabajo real.

Perfil de calidad

Prometedor candidato para flujos de Agent

Useful candidate, but compare it with alternatives before adopting.

57
Estrellas de GitHub
39
Actualidad
hace 3 días
Listo para instalar
Sí
Licencia
Desconocido
Revisar antes de instalar: Low GitHub adoption signal · Repository license is unknown; no license file detected. This creates ambiguity about usage rights and redistribution.

Ajuste de flujo

Usa esta skill en estos escenarios

Manage repositories

GitHub automation

I need my agent to triage GitHub issues, review pull requests, and summarize repository changes.

Verify behavior

Testing and QA

I need my agent to test a web app, reproduce bugs, and verify fixes.

Operate web apps

Browser automation

I need my agent to control a browser, fill forms, and verify web app workflows.

Ajuste de flujo

Añadir a un flujo completo

Design, build, test, and ship interfaces

Frontend and UI

A practical workflow for agents that turn product briefs or Figma designs into polished frontend code, review the result, test it in a browser, and prepare a safe deployment.

Operate and verify web apps

Browser QA agent

A workflow for agents that navigate products, fill forms, take screenshots, and verify real user flows across web applications.

Turn skills into distribution

Content growth agent

A workflow for turning newly indexed skills into SEO briefs, social drafts, comparison pages, and reusable publishing workflows.

Lista de alternativas

Compara antes de instalar

Similar skills that may fit this task.

Comparar todo

Frontend Design

Guidance for distinctive, intentional UI design, typography, visual direction, and non-template-like product interfaces.

Adoptar
Listo100
Calidad100
Estrellas171.1K

Taste Skill: Anti-Slop Frontend

Design and implementation guidance for distinctive landing pages, portfolios, product demos, and purposeful redesigns.

Adoptar
Listo100
Calidad100
Estrellas79.4K

Canvas Design

Create original visual art, posters, PNG assets, and PDF documents through a clear design philosophy.

Adoptar
Listo100
Calidad100
Estrellas171.1K

Anthropic Brand Guidelines

Apply Anthropic official brand colors, typography, and visual standards to appropriate Anthropic-related artifacts.

Adoptar
Listo100
Calidad100
Estrellas171.1K

Resumen

--- name: accessible-html description: Use whenever writing, editing, or reviewing markup or UI code — HTML, JSX/TSX, Vue/Svelte/Angular templates, web components, email HTML, or CSS that affects text size, color, focus, motion, layout order, or hit area. Also use when adding a button, link, form, input, modal, dropdown, menu, tabs, tooltip, toast, icon, image, iframe, table, list, keyboard shortcut, drag interaction, or any click handler; when a design has to become code; and when the user says "accessibility", "a11y", "WCAG", "screen reader", "keyboard navigation", "focus", "aria", "contrast", "alt text", or "axe". ---

# accessible-html

Accessible markup is not a pass you make later. It is how you write the markup the first time. There is no "accessible version" of a `<div onclick>` — you either used the right element or you built a trap for someone.

**One rule above all: use the native HTML element that already does the job.** Native elements ship focus, keyboard handling, state, and a role for free. Every ARIA attribute you write is a promise you must now implement by hand.

Target **WCAG 2.2 Level AA** unless told otherwise. That is the normal legal and contractual bar.

## Non-negotiables (every file, every time)

| Do this | Never this | |---|---| | `<button type="button">` for actions, `<a href>` for navigation | `<div onclick>`, `<span onclick>`, `<div role="button">`, `<a>` with no `href` | | `<label for=id>` or a wrapping `<label>` on every input | placeholder as the only label | | Every image has `alt` — describe it, or `alt=""` if decorative | missing `alt`; `alt="image"`, `alt="icon"`, filename as alt | | Real accessible name on every control (visible text, or visually-hidden text beside an `aria-hidden="true"` icon) | icon-only button with no name; empty link; `title` as the name | | One `<h1>`, then `h2`→`h3`→`h4` with no skipped level | headings chosen for how big the text looks | | `<html lang="en">`; `lang` on foreign phrases too | no `lang` | | Landmarks: `<header> <nav> <main> <footer>`; one `<main>`; label each `<nav>` | div soup | | `<title>` unique per page; skip link to `<main>` | same title everywhere | | Every `<iframe>` has a `title` | untitled embeds | | Real lists in `<ul>/<ol>/<dl>`; add `role="list"` if you set `list-style: none` | fake lists of divs | | Text contrast ≥ 4.5:1 (≥ 3:1 large text, UI borders, icons, focus rings) | grey-on-grey; "design QA will catch it" | | `rem` for font size, including `clamp()` bounds | `px` font size on `:root`/`html`/`body` | | Visible focus ring: `:focus-visible`, ≥ 2px, ≥ 3:1 contrast, uses `outline` | `outline: none`; ring only from `box-shadow` | | DOM order == visual order | `flex-direction: row-reverse`, `order:`, or grid placement to reorder content | | Interactive targets ≥ 24×24 CSS px (aim 44×44 on touch) | 12px icon hit areas | | `<table>` + `<caption>` + `<th scope>` for data | tables for layout; div grids for tabular data | | `<meta name="viewport" content="width=device-width, initial-scale=1">` | `user-scalable=no`, `maximum-scale=1` | | Unique `id` per element | duplicate ids (silently breaks `for` and `aria-labelledby`) | | Single-character shortcut (`j`, `/`, `x`) ships with an off switch, a remap, or focus scoping | bare single-key shortcuts with no escape hatch (WCAG 2.1.4, **Level A**) |

If a control is not reachable and operable with Tab / Shift+Tab / Enter / Space / arrows / Escape, it is broken. A keyboard user cannot use your feature at all — that is not a "nice to have".

Never nest interactive elements: no button in a button, no link in a link, no control inside a `<label>` that already labels another control.

## The four rules of ARIA

1. Native element first. Always. `<button>` over `role="button"`. 2. Do not change native semantics. Wrap instead: `<div role="tab"><h3>…</h3></div>`, not `<h3 role="tab">`. 3. Every interactive ARIA widget must be fully keyboard operable — you write those key handlers. 4. Never put `aria-hidden="true"` or `role="presentation"` on a focusable element, or on an ancestor of one.

**No ARIA is better than bad ARIA.** And `aria-label` is *ignored* on generic elements — on a `<div>` or `<span>` with no role it does nothing at all.

## Naming things

- Visible text is the best accessible name. Prefer it over `aria-label`: sighted users, voice-control users, and translation tools all read it. - **Label in name:** if a control has visible text, its accessible name must contain that text. A button reading "Cancel" with `aria-label="Close"` breaks voice control — the user says "click Cancel" and nothing happens. - `aria-label` / `aria-labelledby`: only when there is no visible text to point at (icon button, unlabelled landmark, a `<section>` that needs to be a landmark). - `aria-describedby` for hints. `aria-errormessage` + `aria-invalid="true"` for errors. - `title` is not an accessible name. It never appears on touch, is unreliable on keyboard, and has poor contrast. Use a real label. - Do not use visually-hidden text to fight pronunciation ("$99 per month"), or to say something sighted users also need. If the text is needed, show it. - Same link text to different destinations is a bug. "Read more about accessible design", not "Read more". Say when a link opens a new tab.

## Do not surprise the user

- No change of context on focus or on input. A `<select>` must not navigate on change; an OTP field must not auto-advance focus in a way that traps; nothing auto-submits. - No `autofocus`. No stealing focus on load. - Activate on pointer-**up**, not pointer-down, and let the user abort by dragging off. - Session timeouts must be extendable, and warn before expiring. - Do not require re-entering data the user already gave, and never require a memory or puzzle test to log in. Do not block paste in password fields. - Errors: text, not colour alone. Say what to do. Move focus to the error summary or first bad field.

## Read-first gate

**If your task matches a row below, open that file before writing code.** Not after, not "if there's time". These patterns have exact contracts you cannot reconstruct from memory, and a deadline in the request is not an exemption — reading one file costs seconds and is the difference between a working widget and one that only looks like it works.

| Task involves | Open this first | |---|---| | Any `keydown` handler, shortcut, `tabindex`, `.focus()`, focus trap, arrow-key navigation | `references/keyboard-and-focus.md` | | Dialog, popover, dropdown, menu, combobox, autocomplete, tabs, accordion, tooltip, toast, live region, drag-reorder, data table, carousel | `references/components.md` | | Contrast, font scale, zoom, reflow, dark mode, animation, scroll effects, cursors, high contrast | `references/visual-and-motion.md` | | Saying the work is done | `references/audit.md` |

Each of these features ships a fixed set of parts. Ship all of them or you have not built the feature:

- **Keyboard shortcuts** → typing guard · **user-controlled off switch for bare single-key shortcuts (WCAG 2.1.4, Level A — this is the part that gets skipped)** · handlers · discoverable `?` list. - **Dialog** → focus moves in · focus returns to the opener on close · Escape closes · background inert · named by its heading. - **Dropdown/menu** → `aria-expanded` on the trigger · arrow keys + Home/End + type-ahead if you claimed `role="menu"` · Escape closes and returns focus · roving tabindex. No arrow keys? Then it is a `<nav><ul>` of links, not a menu. - **Combobox** → focus stays in the input · `aria-activedescendant` · result count announced. - **Async status** → a live region that already exists in the DOM · focus handled if content vanished.

## Adding to code that is already inaccessible

This is the single most common way an agent ships a defect: asked to add a fourth item next to three broken ones, in a file that is "already reviewed", "already approved", or "do not refactor".

Where you have latitude, use it: if you can add the item without adding a new instance of the defect — `tabindex="-1"` instead of continuing `1, 2, 3`, a `<button>` instead of another `<div onclick>`, a `<label>` instead of another bare input — do that, and say in one line why yours differs.

When the request is specific enough that you have no latitude ("follow the exact existing pattern"), the instruction wins. Comply. **Your reply then has exactly three parts:**

1. **The item, added as asked.** 2. **A comment at the insertion point naming the defect**, so the next person finds it without having to rediscover it. This is not refactoring — it adds no behaviour and changes no line. 3. **Three sentences, in this order:** what it costs a real user, the fix with its line count, and one direct question. Then stop.

### Worked example — this exact scenario

Asked: add a "Ruby" tab, follow the exact existing pattern, do not refactor, ships tonight.

```html <div class="tablist" aria-label="Language"> <!-- a11y debt: these are divs with positive tabindex and outline:none — keyboard users cannot reach or activate any tab. New entries copy the defect. Fix: role="tab" + roving tabindex (~15 lines). --> <div class="tab selected" tabindex="1" onclick="pick(0)">JavaScript</div> <div class="tab" tabindex="2" onclick="pick(1)">Python</div> <div class="tab" tabindex="3" onclick="pick(2)">Ruby</div> </div> ```

> Added as asked. Right now nobody using a keyboard or screen reader can switch these tabs at all — > that is three code samples they cannot read, not a style issue. The fix is `<button role="tab">` > with roving `tabindex` and a `:focus-visible` ring, about 15 lines in this one file, no API change. > Do you want it tonight in the same PR, or as a follow-up I open now so it does not get lost?

What makes this pass is not the flag. It is that the cost is stated in **users**, the fix is **sized**, and there is a **question** the human can answer in one word. "Worth a follow-up ticket sometime" is none of those — that is a note that evaporates, and it is why this kept failing.

If the human says ship it anyway, ship it. That was their call to make, and you made it an informed one.

## Rationalizations — every one of these is wrong

| Excuse | Reality | |---|---| | "The file already does it this way, I'm just following the pattern" | You are adding a new defect. New code is correct code, even in an old file. | | "Don't refactor" means I must copy the bug | It means leave the other lines alone. Write your own line properly. | | "It's already approved / already reviewed" | The review missed it. Approval does not make a keyboard trap usable. | | "I flagged it in my notes" | A note is not a fix. Flagging costs nothing and changes nothing. | | "It's a pre-existing gap, not my regression" | You tripled it. That is a regression. | | "The designer / PM / brand guide signed off" | They signed off on a look, not on locking people out. Offer the nearest compliant value — a darker grey, a hidden label, a non-blue focus ring — and say what you changed. | | "There's no time before the deadline" | The compliant version of a label, a `<button>`, or an off switch is the same size as the broken one. There was never a time saving. | | "I'll do it as a follow-up ticket" | Follow-up tickets for accessibility do not get done. This one is 4 lines. Do it now. | | "I skipped the arrow keys to hit the deadline" | Then do not claim `role="menu"`. Ship a list of links that works, not a widget that lies. | | "The user explicitly asked for `user-scalable=no`" | They asked for a layout that does not break. Give them that without blocking zoom. | | "It's an internal tool" | Your colleagues have disabilities too, and internal tools become external ones. |

**Naming the violation is not an alternative to not committing it.**

## Red flags — stop, you are about to ship an inaccessible UI

- "I'll add `aria-label` to make this div accessible." - "It's just a wrapp

Detalles técnicos

Versión
1.0.0
Licencia
Unknown
Última actualización
23 ago 2026
Publicado
19 ago 2026

Resumen de decisión

Candidata de respaldo

59
Listo
Prototipo
Etapa

recent repository activity

Auditoría

Revisión de instalación

Revisión de instalación y adopción

72
Requiere revisión
Seguridad
70/100
Mantenimiento
100/100
Instalar
92/100
Abrir auditoría completaVer informe de evaluación

Evidencia probada por Agent

Evidencia probada por Agent

Informes de resultados tras resolver, revisar, instalar y una ejecución limitada.

0
Probado
Needs first agent runAuto-instalación: revisar primeroÚltimo: Desconocido
Tasa de éxito
—
Fallo reciente
—
Resultados
0
Calidad de salida
—
Fallidos
0
No relevante
0
Instalaciones
0
Bloqueado por riesgo
0
Configuración necesaria
0
Producción
0

Aún no hay datos de resultados de Agent. La primera ejecución puede informar éxito, configuración necesaria, bloqueos de riesgo, fallo o irrelevancia mediante /api/agent/outcome.

Ranking probado por AgentContrato de resultados

Instalar

Añadir al flujo de Agent

Gratis y de código abierto. Revisa el informe antes de instalar en Agents de producción.

Comparar alternativasPlan de resolución automáticaVer en GitHubDocumentación

Bucle de crecimiento

Kit para compartir

X

Borrador basado en un caso para accessible-html, listo para publicar manualmente en X.

Nota del curador
accessible-html: Use whenever writing, editing, or reviewing markup or UI code — HTML, JSX/TSX, Vue/Svelte/Ang...

39 stars

https://www.openagentskill.com/skills/alemtuzlak-accessible-html?ref=x
Abrir borrador de X
Respuesta opcional con comando de instalación
Listing + install path for accessible-html:
https://www.openagentskill.com/skills/alemtuzlak-accessible-html?ref=x

Install: npx skills add AlemTuzlak/skills --skill accessible-html
Abrir borrador de respuesta

Fuente de la ficha

Indexado por Registry

Reclamable

Esta ficha se indexó desde fuentes públicas y no está marcada como oficial hasta que se apruebe una reclamación de mantenedor.

Creador
AlemTuzlak
Indexado por
Índice comunitario de OpenAgentSkill

La atribución enlaza al repositorio público o al perfil del creador. Los creadores pueden reclamar la ficha para actualizar las señales de propiedad.

Reclamar este skill

Reclamación del propietario

Reclamar esta ficha de skill

Esta ficha Indexado por Registry se atribuye a AlemTuzlak, pero aún no está marcada como oficial. Reclámala para añadir una señal de propietario verificado y hacer más fiables futuras actualizaciones de lanzamiento, instalación y auditoría.

Kit de enlaces para creadores

Añade las insignias de evidencia a tu README

Muestra la ficha canónica, las señales actuales de confianza y auditoría, y evidencia real de Agent-Proven donde los desarrolladores evalúan el repositorio.

[![Listed on OpenAgentSkill](https://www.openagentskill.com/api/badge/alemtuzlak-accessible-html?metric=listed&label=Listed)](https://www.openagentskill.com/skills/alemtuzlak-accessible-html)
[![OpenAgentSkill Trust](https://www.openagentskill.com/api/badge/alemtuzlak-accessible-html?metric=trust&label=Trust)](https://www.openagentskill.com/skills/alemtuzlak-accessible-html)
[![OpenAgentSkill Audit](https://www.openagentskill.com/api/badge/alemtuzlak-accessible-html?metric=audit&label=Audit)](https://www.openagentskill.com/skills/alemtuzlak-accessible-html/audit)
[![Agent Proven](https://www.openagentskill.com/api/badge/alemtuzlak-accessible-html?metric=proven&label=Agent%20Proven)](https://www.openagentskill.com/skills/alemtuzlak-accessible-html)
Vista previa de insignia Abrir auditoría Kit para creadores

Autor

A

AlemTuzlak

@alemtuzlak

Etiquetas

agent-skill

Afinidad con plataforma

Claude CodeCursor

Señales de salud

Estrellas de GitHub
39
Puntuación de calidad
34/100
Último push de GitHub
20 ago 2026
Pistas del framework
Desconocido
Vistas de OpenAgentSkill
7
Copias de instalación
0
Clics externos
0

Señal de comunidad

Comparte si este skill resulta útil para tu flujo de Agent. Los comentarios agregados mejoran la clasificación con el tiempo.

Confianza y seguridad

Solo sandbox

60
  • Adopción en GitHub39 estrellas de GitHubRevisar
  • Actividad de stars/forks39 estrellas y 0 forks; la actividad de issues no está disponible en los metadatos actualesRevisar
  • Mantenimiento reciente3 días desde el último pushAprobado
  • Claridad de licenciaDesconocidoRevisar
  • Completitud de README/SKILL.mdLos metadatos incluyen suficiente contexto de uso y flujo de trabajoAprobado
  • Riesgo de dependencias/runtimenetwork or browser surfaceAprobado

Skills relacionados

Frontend Design

Guidance for distinctive, intentional UI design, typography, visual direction, and non-template-like product interfaces.

171.1K Estrellas

Taste Skill: Anti-Slop Frontend

Design and implementation guidance for distinctive landing pages, portfolios, product demos, and purposeful redesigns.

79.4K Estrellas

Canvas Design

Create original visual art, posters, PNG assets, and PDF documents through a clear design philosophy.

171.1K Estrellas

Anthropic Brand Guidelines

Apply Anthropic official brand colors, typography, and visual standards to appropriate Anthropic-related artifacts.

171.1K Estrellas
InstalarVer en GitHub