accessible-html

Tinjau · 60
Diindeks di 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
Star39
Versi1.0.0
Kualitas57/100 · Menjanjikan
Kepercayaan60/100 · Hanya sandbox
Audit72/100 · Perlu ditinjau

Profil aset

Desain dan produksi kreatif

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

Lihat kategori

Skenario

Desain dan kreatif

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

Kecocokan Agent

Claude Code + Cursor + CLI

Cocok untuk Codex, Claude Code, Cursor, CLI, atau Agent khusus.

Pasang

Siap

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

Pemeliharaan

Terkini

2 hari sejak push

Risiko

Perlu ditinjau

Lisensi tidak jelas

Kualitas GitHub

39

57/100 Kualitas · 68/100 Kepercayaan

Tag cakupan

DesainDesain dan kreatifDesain dan kreatifagent-skill

Catatan ulasan

Lisensi tidak jelas · Permission surface may require sandboxing

Kartu adopsi Agent

Kepercayaan, audit, dan kesiapan pemasangan dalam sekali lihat

Skor ini menggabungkan metadata repositori publik, sinyal ulasan OpenAgentSkill, kebaruan pemeliharaan, dan kesiapan pemasangan. Ini adalah sinyal shortlist, bukan pengganti peninjauan manusia.

Kualitas

Menjanjikan
57

Useful candidate, but compare it with alternatives before adopting.

Kepercayaan

Hanya sandbox
60

Kandidat berguna dengan sinyal kepercayaan yang kurang atau bercampur. Gunakan di ruang kerja terisolasi hingga loop hasil membuktikan kecocokan tugas.

Audit

Perlu ditinjau
72

Tinjauan yang dapat dibaca mesin tentang kesiapan pemasangan, metadata keamanan, pemeliharaan, dan risiko adopsi.

Trust Score OpenAgentSkill v5

Tinjauan manusia sebelum pemasangan

Jalankan hanya dalam sandbox dan bandingkan alternatif terdekat sebelum digunakan untuk kerja nyata.

CodexClaude CodeCursorOpenAgentSkill CLI

Star

39 star GitHub

Aktivitas repositori

39 star dan 0 fork

Pemeliharaan

2 hari sejak push

Lisensi

Tidak diketahui

Pasang

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

Keamanan pemasangan

Jalur pemasangan paket atau runtime standar

Cakupan izin

secrets or environment access, filesystem or document access

Hasil Agent

Belum ada data hasil Agent

Dokumentasi

Konteks README/SKILL.md kuat

Ringkasan risiko

Tinjau sebelum produksi

  • Repository license is unknown; no license file detected. This creates ambiguity about usage rights and redistribution.
  • Lisensi tidak jelas
  • Low GitHub adoption signal
  • Quality score needs review

Kesiapan pemasangan

Jalur pemasangan tersedia

  • Jalur pemasangan tersedia
  • Bukti repositori tersedia
  • Lisensi tidak jelas
  • Belum ada bukti hasil Agent-Proven

Metadata yang dapat dibaca Agent

Data keputusan yang dapat dibaca mesin untuk skill ini.

Gunakan blok ini atau JSON tersemat untuk memutuskan apakah Agent perlu memasang skill ini, memilih alternatif, atau meminta tinjauan manusia terlebih dahulu.

Buka JSON

Tugas yang sesuai

  • alur kerja GitHub automation
  • Tim Claude Code
  • builders willing to evaluate younger projects
  • Inspect repository metadata

Agent yang sesuai

CodexClaude CodeCursorOpenAgentSkill CLICLI

Keputusan pemasangan

Perintah
npx skills add AlemTuzlak/skills --skill accessible-html
Kebijakan
Tinjau
Tinjauan manusia
Ya

Kepercayaan dan risiko

Kepercayaan
60/100
Audit
72/100
Tingkat risiko
Perlu ditinjau

Lingkar hasil

Endpoint
/api/agent/outcome
ID event
resolve
Hasil
5

Perintah pemasangan

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

Jangan gunakan ketika

  • Tim yang membutuhkan SLA dengan dukungan vendor
  • 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.
  • Lisensi tidak jelas

Keamanan Agent v2

52/100 · Hindari pemasangan otomatis

EksperimentalTinjau

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

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

Selesaikan via API

Sedang

Browser automation

Skill may drive a browser or interact with web pages.

Sedang

Akses jaringan

Skill kemungkinan mengambil halaman jarak jauh, API, repositori, atau layanan eksternal.

Sedang

Akses sistem file

Skill dapat membaca atau menulis file proyek, dokumen, artefak yang dihasilkan, atau status workspace lokal.

  • Lisensi tidak jelas

Target pemasangan

Pasang skill ini di alur Agent Anda

Gunakan endpoint publik untuk mengambil perintah, checklist keamanan, prompt target, dan tautan kanonis.

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

Rencana resolusi Agent

Biarkan Agent memverifikasi kecocokan sebelum memasang.

API Resolve mengembalikan skill utama, alternatif, kebijakan keamanan, catatan audit, target pemasangan, dan prompt siap pakai.

Buka rencana teks

Agent harus memeriksa

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

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

Serah-terima Agent

Berikan jalur pemasangan kepada Agent, bukan direktori lain.

Gunakan endpoint publik untuk mengambil perintah, checklist keamanan, prompt target, dan tautan kanonis.

Buka API pemasangan

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

Metadata Registry

Profil yang dapat dibaca Agent untuk pemilihan skill otomatis.

API Registry menyediakan sinyal keputusan, kepercayaan, audit, use case, dan pemasangan tanpa mengikis UI.

Buka Manifest

Kecocokan Agent

59/100

GitHub automation

Platform

Claude Code, Cursor

Laporan audit

Perlu ditinjau · 72/100

Tinjauan yang dapat dibaca mesin tentang kesiapan pemasangan, metadata keamanan, pemeliharaan, dan risiko adopsi.

Lihat laporan auditLihat laporan evaluasi

Panel keputusan Agent

Fallback candidate for GitHub automation

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

59
Kesiapan
Prototipe
Tahap

Peran di stack

Kandidat cadangan

Kecocokan utama

GitHub automation

Label kepercayaan

Buat prototipe dulu

Jalur pemasangan

Perintah siap

Gunakan saat

  • alur kerja GitHub automation
  • Tim Claude Code
  • builders willing to evaluate younger projects

Bukti

  • recent repository activity
  • install command or GitHub repo available
  • profil kualitas 57/100
  • 7 event interaksi OpenAgentSkill

tinjau dulu

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

Jalur implementasi

  1. 1Pasang di Agent sandbox dan jalankan satu tugas GitHub automation dari awal hingga akhir.
  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 kepercayaan

Hanya sandbox

Kandidat berguna dengan sinyal kepercayaan yang kurang atau bercampur. Gunakan di ruang kerja terisolasi hingga loop hasil membuktikan kecocokan tugas.

60
Trust Score OpenAgentSkill

Adopsi GitHub

Periksa

39 star GitHub

Aktivitas star/fork

Periksa

39 star dan 0 fork; aktivitas issue tidak tersedia dalam metadata saat ini

Pemeliharaan terbaru

Lulus

2 hari sejak push

Kejelasan lisensi

Periksa

Tidak diketahui

Sinyal positif

  • Tinjauan AI disetujui
  • Jalur pemasangan tersedia
  • Bukti repositori tersedia
  • Repositori yang baru dipelihara
  • Perintah pemasangan tidak memiliki pola berisiko tinggi yang jelas
  • Loop hasil siap tetapi membutuhkan eksekusi Agent nyata pertama

Tinjau sebelum memasang

  • Repository license is unknown; no license file detected. This creates ambiguity about usage rights and redistribution.
  • Lisensi tidak jelas
  • 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
  • Belum ada laporan hasil Agent nyata
  • Tinjauan manusia diperlukan sebelum pemasangan tanpa pengawasan

Tindakan yang disarankan

Jalankan hanya dalam sandbox dan bandingkan alternatif terdekat sebelum digunakan untuk kerja nyata.

Profil kualitas

Menjanjikan kandidat untuk alur kerja Agent

Useful candidate, but compare it with alternatives before adopting.

57
Star GitHub
39
Keterkinian
2 hari lalu
Siap dipasang
Ya
Lisensi
Tidak diketahui
Tinjau sebelum memasang: Low GitHub adoption signal · Repository license is unknown; no license file detected. This creates ambiguity about usage rights and redistribution.

Kecocokan alur kerja

Gunakan skill ini pada skenario berikut

Kecocokan alur kerja

Tambahkan ke alur kerja lengkap

Daftar alternatif

Bandingkan sebelum memasang

Similar skills that may fit this task.

Bandingkan semua

Ringkasan

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

Detail teknis

Versi
1.0.0
Lisensi
Unknown
Pembaruan terakhir
20 Agu 2026
Diterbitkan
19 Agu 2026

Ringkasan keputusan

Kandidat cadangan

59
Siap
Prototipe
Tahap

recent repository activity

Audit

Tinjauan pemasangan

Tinjauan pemasangan dan adopsi

72
Perlu ditinjau
Keamanan
70/100
Pemeliharaan
100/100
Pasang
92/100
Buka audit lengkapLihat laporan evaluasi

Bukti tervalidasi Agent

Bukti tervalidasi Agent

Laporan hasil setelah resolve, tinjau, pasang, dan satu eksekusi terbatas.

0
Terbukti
Needs first agent runPasang otomatis: tinjau duluTerakhir: Tidak diketahui
Tingkat sukses
Kegagalan terbaru
Hasil
0
Kualitas output
Gagal
0
Tidak relevan
0
Pemasangan
0
Diblokir risiko
0
Perlu penyiapan
0
Produksi
0

Belum ada data hasil Agent. Eksekusi pertama dapat melaporkan keberhasilan, kebutuhan setup, blok risiko, kegagalan, atau tidak relevan melalui /api/agent/outcome.

Pasang

Tambahkan ke alur Agent

Gratis dan sumber terbuka. Tinjau laporan sebelum memasang pada Agent produksi.

Siklus pertumbuhan

Kit berbagi

X

Draf berbasis skenario untuk accessible-html, siap untuk posting manual di X.

Catatan kurator
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
Buka draf X
Balasan opsional dengan perintah pemasangan
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
Buka draf balasan

Sumber listing

Diindeks Registry

Dapat diklaim

Listing ini diindeks dari sumber publik dan belum ditandai resmi hingga klaim pemelihara disetujui.

Kreator
AlemTuzlak
Diindeks oleh
Indeks komunitas OpenAgentSkill

Atribusi menautkan ke repositori publik atau profil kreator. Kreator dapat mengklaim listing untuk memperbarui sinyal kepemilikan.

Klaim skill ini

Klaim pemilik

Klaim listing skill ini

Listing Diindeks Registry ini dikaitkan dengan AlemTuzlak, tetapi belum ditandai resmi. Klaim untuk menambahkan sinyal pemilik terverifikasi dan membuat pembaruan peluncuran, pemasangan, serta audit berikutnya lebih tepercaya.

Kit backlink kreator

Tambahkan badge bukti ke README Anda

Tampilkan listing kanonis, sinyal kepercayaan dan audit saat ini, serta bukti Agent-Proven nyata di tempat pengembang mengevaluasi repositori.

[![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)

Penulis

A

AlemTuzlak

@alemtuzlak

Kecocokan platform

Sinyal kesehatan

Star GitHub
39
Skor kualitas
34/100
Push GitHub terakhir
20 Agu 2026
Petunjuk framework
Tidak diketahui
Tampilan OpenAgentSkill
7
Salinan pemasangan
0
Klik keluar
0

Sinyal komunitas

Bagikan apakah skill ini bermanfaat untuk alur kerja Agent Anda. Masukan gabungan meningkatkan peringkat dari waktu ke waktu.

Kepercayaan & keamanan

Hanya sandbox

60
  • Adopsi GitHub39 star GitHubPeriksa
  • Aktivitas star/fork39 star dan 0 fork; aktivitas issue tidak tersedia dalam metadata saat iniPeriksa
  • Pemeliharaan terbaru2 hari sejak pushLulus
  • Kejelasan lisensiTidak diketahuiPeriksa
  • Kelengkapan README/SKILL.mdMetadata memuat konteks penggunaan dan alur kerja yang cukupLulus
  • Risiko dependensi/runtimenetwork or browser surfaceLulus