Star200+

accessible-html

Revoir · 60
Indexé dans 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
Stars39
Version1.0.0
Qualité57/100 · Prometteur
Confiance60/100 · Sandbox uniquement
Audit72/100 · Revue nécessaire

Profil de l’actif

Design et production créative

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

Voir la catégorie

Scénario

Design et créativité

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

Adéquation Agent

Claude Code + Cursor + CLI

Compatible avec Codex, Claude Code, Cursor, CLI ou des Agents personnalisés.

Installer

Prêt

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

Maintenance

À jour

2 jours depuis le dernier push

Risque

Revue nécessaire

La licence est ambiguë

Qualité GitHub

39

57/100 Qualité · 68/100 Confiance

Tags de couverture

DesignDesign et créativitéDesign et créationagent-skill

Notes de revue

La licence est ambiguë · Permission surface may require sandboxing

Carte d’adoption Agent

Confiance, audit et préparation à l’installation en un coup d’œil

Ces scores combinent les métadonnées publiques du dépôt, les signaux de revue OpenAgentSkill, la fraîcheur de maintenance et la préparation à l’installation. Ils servent à présélectionner et ne remplacent pas la revue humaine.

Qualité

Prometteur
57

Useful candidate, but compare it with alternatives before adopting.

Confiance

Sandbox uniquement
60

Candidate utile avec des signaux de confiance incomplets ou mixtes. Gardez-la dans un espace isolé jusqu’à ce que la boucle de résultats confirme son adéquation.

Audit

Revue nécessaire
72

Revue lisible par machine de la préparation à l’installation, des métadonnées de sécurité, de la maintenance et du risque d’adoption.

Trust Score OpenAgentSkill v5

Revue humaine avant installation

Exécutez uniquement dans un sandbox et comparez les alternatives proches avant usage réel.

CodexClaude CodeCursorOpenAgentSkill CLI

Stars

39 stars GitHub

Activité du dépôt

39 stars et 0 forks

Maintenance

2 jours depuis le dernier push

Licence

Inconnu

Installer

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

Sécurité d’installation

Chemin d’installation standard de package ou runtime

Surface de permissions

secrets or environment access, filesystem or document access

Résultats Agent

Pas encore de données de résultats Agent

Documentation

Contexte README/SKILL.md solide

Résumé des risques

Revoir avant production

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

Préparation à l’installation

Chemin d’installation disponible

  • Le chemin d’installation est disponible
  • La preuve du dépôt est disponible
  • La licence est ambiguë
  • Pas encore de preuve de résultat Agent-Proven

Métadonnées lisibles par Agent

Données de décision lisibles par machine pour ce skill.

Utilisez ce bloc ou le JSON intégré pour décider si un Agent doit installer ce skill, choisir une alternative ou demander d’abord une revue humaine.

Ouvrir JSON

Tâches adaptées

  • workflows GitHub automation
  • Équipes Claude Code
  • builders willing to evaluate younger projects
  • Inspect repository metadata

Agents adaptés

CodexClaude CodeCursorOpenAgentSkill CLICLI

Décision d’installation

Commande
npx skills add AlemTuzlak/skills --skill accessible-html
Politique
Revoir
Revue humaine
Oui

Confiance et risque

Confiance
60/100
Audit
72/100
Niveau de risque
Revue nécessaire

Boucle de résultat

Endpoint
/api/agent/outcome
ID d’événement
resolve
Résultats
5

Commande d’installation

npx skills add AlemTuzlak/skills --skill accessible-html
Audit publicRapport d’évaluationAPI ResolveRelais d’installation

Ne pas utiliser quand

  • Équipes qui nécessitent un SLA soutenu par le fournisseur
  • 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 licence est ambiguë

Skill alternatif

Frontend Design

170.9K Stars

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

Skill alternatif

Taste Skill: Anti-Slop Frontend

79.0K Stars

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

Skill alternatif

Canvas Design

170.9K Stars

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

Skill alternatif

Anthropic Brand Guidelines

170.9K Stars

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

Sécurité Agent v2

52/100 · Éviter l’installation automatique

ExpérimentalRevoir

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

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

Résoudre via API

Moyen

Browser automation

Skill may drive a browser or interact with web pages.

Moyen

Accès réseau

La skill récupère probablement des pages distantes, API, dépôts ou services externes.

Moyen

Accès au système de fichiers

La skill peut lire ou écrire des fichiers de projet, documents, artefacts générés ou l’état local de l’espace de travail.

  • La licence est ambiguë

Cibles d’installation

Installer ce skill dans votre workflow Agent

Utilisez le point de terminaison public pour récupérer la commande, la checklist, les prompts et les liens canoniques.

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 résolution Agent

Laissez un Agent vérifier la pertinence avant l’installation.

L’API Resolve renvoie la skill sélectionnée, des alternatives, la politique de sécurité, les notes d’audit, la cible d’installation et un prompt prêt à l’emploi.

Ouvrir le plan texte

Ouvrir JSON

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

Texte Resolve

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

Relais d’installation

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

L’Agent doit vérifier

  • 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.

Copier le 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.

Relais Agent

Donnez à l’Agent le chemin d’installation, pas un autre annuaire.

Utilisez le point de terminaison public pour récupérer la commande, la checklist, les prompts et les liens canoniques.

Ouvrir l’API d’installation

Relais d’installation

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

Format texte LLM

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

Trouver des alternatives

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

Prompt 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

Métadonnées Registry

Profil lisible par Agent pour la sélection automatique de skills.

L’API Registry fournit les signaux de décision, confiance, audit, cas d’usage et installation sans analyser l’interface.

Ouvrir Manifest

Manifest

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

Texte LLM

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

Alias d’installation

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

Recommander

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

Adéquation Agent

59/100

GitHub automation

Tags de cas d’usage

GitHub automationTesting and QABrowser automation

Plateformes

Claude Code, Cursor

Rapport d’audit

Revue nécessaire · 72/100

Revue lisible par machine de la préparation à l’installation, des métadonnées de sécurité, de la maintenance et du risque d’adoption.

Voir le rapport d’auditVoir le rapport d’évaluation

Panneau de décision Agent

Fallback candidate for GitHub automation

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

59
Préparation
Prototype
Étape

Rôle dans la pile

Candidate de secours

Pertinence principale

GitHub automation

Libellé de confiance

Prototyper d’abord

Chemin d’installation

Commande prête

À utiliser lorsque

  • workflows GitHub automation
  • Équipes Claude Code
  • builders willing to evaluate younger projects

Preuves

  • recent repository activity
  • install command or GitHub repo available
  • profil qualité 57/100
  • 7 événements OpenAgentSkill

revoir d’abord

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

Chemin d’implémentation

  1. 1Installez-le dans un Agent en sandbox et exécutez une tâche de GitHub automation de bout en bout.
  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.

Profil de confiance

Sandbox uniquement

Candidate utile avec des signaux de confiance incomplets ou mixtes. Gardez-la dans un espace isolé jusqu’à ce que la boucle de résultats confirme son adéquation.

60
Trust Score OpenAgentSkill

Adoption GitHub

Vérifier

39 stars GitHub

Activité stars/forks

Vérifier

39 stars et 0 forks; l’activité des issues n’est pas disponible dans les métadonnées actuelles

Maintenance récente

Validé

2 jours depuis le dernier push

Clarté de licence

Vérifier

Inconnu

Signaux positifs

  • Revue IA approuvée
  • Le chemin d’installation est disponible
  • La preuve du dépôt est disponible
  • Dépôt maintenu récemment
  • La commande d’installation ne présente aucun motif de haut risque évident
  • La boucle de résultats est prête mais nécessite la première exécution réelle de l’Agent

Réviser avant installation

  • Repository license is unknown; no license file detected. This creates ambiguity about usage rights and redistribution.
  • La licence est ambiguë
  • 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
  • Pas encore de rapports de résultats Agent réels
  • Une revue humaine est requise avant une installation sans surveillance

Action recommandée

Exécutez uniquement dans un sandbox et comparez les alternatives proches avant usage réel.

Profil qualité

Prometteur candidat pour les workflows Agent

Useful candidate, but compare it with alternatives before adopting.

57
Stars GitHub
39
Actualité
il y a 2 jours
Prêt à installer
Oui
Licence
Inconnu
Réviser avant installation: Low GitHub adoption signal · Repository license is unknown; no license file detected. This creates ambiguity about usage rights and redistribution.

Adéquation au workflow

Utilisez cette skill dans ces scénarios

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.

Adéquation au workflow

Ajouter à un workflow complet

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.

Liste d’alternatives

Comparer avant installation

Similar skills that may fit this task.

Tout comparer

Frontend Design

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

Adopter
Prêt100
Qualité100
Stars170.9K

Taste Skill: Anti-Slop Frontend

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

Adopter
Prêt100
Qualité100
Stars79.0K

Canvas Design

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

Adopter
Prêt100
Qualité100
Stars170.9K

Anthropic Brand Guidelines

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

Adopter
Prêt100
Qualité100
Stars170.9K

Vue d’ensemble

--- 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

Détails techniques

Version
1.0.0
Licence
Unknown
Dernière mise à jour
20 août 2026
Publié
19 août 2026

Instantané de décision

Candidate de secours

59
Prêt
Prototype
Étape

recent repository activity

Audit

Revue d’installation

Revue d’installation et d’adoption

72
Revue nécessaire
Sécurité
70/100
Maintenance
100/100
Installer
92/100
Ouvrir l’audit completVoir le rapport d’évaluation

Preuves validées par Agent

Preuves validées par Agent

Rapports après resolve, revue, installation et une exécution limitée.

0
Validé
Needs first agent runAuto-installation: revoir d’abordDernier: Inconnu
Taux de réussite
—
Échec récent
—
Résultats
0
Qualité de sortie
—
Échecs
0
Non pertinent
0
Installations
0
Bloqué par le risque
0
Configuration requise
0
Production
0

Aucune donnée de résultat Agent pour l’instant. La première exécution peut signaler succès, besoin de configuration, blocage de risque, échec ou non-pertinence via /api/agent/outcome.

Classement Agent-ProvenContrat de résultat

Installer

Ajouter au workflow Agent

Gratuit et open source. Examinez le rapport avant l’installation dans des Agents de production.

Comparer les alternativesPlan de résolution autoVoir sur GitHubDocumentation

Boucle de croissance

Kit de partage

X

Brouillon guidé par scénario pour accessible-html, prêt pour une publication manuelle sur X.

Note du curateur
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
Ouvrir le brouillon X
Réponse facultative avec commande d’installation
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
Ouvrir le brouillon de réponse

Source de la fiche

Indexé par Registry

Revendiable

Cette fiche a été indexée à partir de sources publiques et n’est pas marquée officielle tant qu’une revendication de mainteneur n’est pas approuvée.

Créateur
AlemTuzlak
Indexé par
Index communautaire OpenAgentSkill

L’attribution renvoie au dépôt public ou au profil du créateur. Les créateurs peuvent revendiquer la fiche pour mettre à jour les signaux de propriété.

Revendiquer ce skill

Revendication du propriétaire

Revendiquer cette fiche de skill

Cette fiche Indexé par Registry est attribuée à AlemTuzlak, mais n’est pas encore marquée officielle. Revendiquez-la pour ajouter un signal de propriétaire vérifié et rendre les futures mises à jour de lancement, d’installation et d’audit plus fiables.

Kit de backlinks créateur

Ajoutez les badges de preuve à votre README

Affichez la fiche canonique, les signaux actuels de confiance et d’audit, ainsi que de vraies preuves Agent-Proven là où les développeurs évaluent le dépôt.

[![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)
Aperçu du badge Ouvrir l’audit Kit créateur

Auteur

A

AlemTuzlak

@alemtuzlak

Tags

agent-skill

Adéquation plateforme

Claude CodeCursor

Signaux de santé

Stars GitHub
39
Score de qualité
34/100
Dernier push GitHub
20 août 2026
Indications de framework
Inconnu
Vues OpenAgentSkill
7
Copies d’installation
0
Clics sortants
0

Signal de communauté

Indiquez si ce skill semble utile à votre workflow Agent. Les retours agrégés améliorent le classement au fil du temps.

Confiance et sécurité

Sandbox uniquement

60
  • Adoption GitHub39 stars GitHubVérifier
  • Activité stars/forks39 stars et 0 forks; l’activité des issues n’est pas disponible dans les métadonnées actuellesVérifier
  • Maintenance récente2 jours depuis le dernier pushValidé
  • Clarté de licenceInconnuVérifier
  • Complétude README/SKILL.mdLes métadonnées incluent suffisamment de contexte d’usage et de workflowValidé
  • Risque dépendances/runtimenetwork or browser surfaceValidé

Skills associés

Frontend Design

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

170.9K Stars

Taste Skill: Anti-Slop Frontend

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

79.0K Stars

Canvas Design

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

170.9K Stars

Anthropic Brand Guidelines

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

170.9K Stars
InstallerVoir sur GitHub