📦

html

Name: html
Author: shreyam1008

콘텐츠 리비전 r1 안전 ⚙️ 외부 명령어

Build Accessible, Semantic HTML

Inconsistent markup causes accessibility, usability, and search problems. This skill guides you toward semantic structure, resilient forms, and useful document metadata.

지원: Claude Codex Code(CC)

🥉 78 브론즈

Maintain this Skill? Claim it 🥉 78 브론즈

내 에이전트로 설치

이 요청을 에이전트에 복사하세요. 공식 Skill 페이지와 매니페스트가 포함되어 있습니다.

에이전트 요청

Review the Skillstore skill "html" from https://skillstore.io/skills/shreyam1008-html.md and its manifest at https://skillstore.io/api/skills/shreyam1008-html/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

에이전트는 계속해서 계획을 표시하고 보안 정책에서 요구하는 확인을 요청해야 합니다.

에이전트가 읽기 쉬운 리소스

AI 에이전트, 크롤러, 스크립트가 전체 페이지 대신 정리된 컨텍스트만 필요할 때 이 링크를 사용하세요.

Markdown 상세 GET /skills/shreyam1008-html.md 서명된 manifest GET /api/skills/shreyam1008-html/manifest 서명된 lockfile GET /api/skills/shreyam1008-html/lockfile

테스트해 보기

"html" 사용 중입니다. How should a product page organize its main regions?

예상 결과:

Use one main landmark with a descriptive heading. Place site navigation in a nav landmark, supporting content in an aside, and related page content in sections or articles.

"html" 사용 중입니다. What should I check on a newsletter signup form?

예상 결과:

Give the email field a visible label and use the email input type.
Add autocomplete for email, native required validation, and an error message connected with an accessible description.
Use a submit button and preserve a visible focus state.

보안 감사

안전

v1 • 2026. 10. 2. 버전별 보고서 열기

All 21 static findings are false positives caused by Markdown inline backticks and fenced HTML examples in SKILL.md. No Ruby or shell execution, prompt injection, network access, or data-exfiltration behavior is evidenced.

스캔된 파일

분석된 줄 수

검토 항목

오탐 무시됨

위험 요인

가장 최근에 완료된 정적·의미론적 감사에서 확인된 보안 발견 사항이 감지되지 않았습니다. 이는 스킬에 부작용이 없음을 증명하지 않습니다.

감사자: codex

이 보고서 공유 및 인용

버전이 지정된 평가 보고서, 중립 배지, 임베드 카드 및 인용을 공유하세요. Skillstore는 근거를 보고하지만 이 Skill의 안전 여부를 판단하지 않습니다.

버전별 보고서 열기

보고서 링크 복사

https://skillstore.io/skills/shreyam1008-html/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown 배지

[![Skillstore security assessment](https://skillstore.io/badges/skills/shreyam1008-html/security.svg)](https://skillstore.io/skills/shreyam1008-html?utm_source=security_passport_badge)

HTML 배지

<a href="https://skillstore.io/skills/shreyam1008-html?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/shreyam1008-html/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

임베드 카드

<iframe src="https://skillstore.io/embed/skills/shreyam1008-html.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

학술 인용 (APA · BibTeX · CFF)

APA 인용

shreyam1008. (2026). html security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/shreyam1008-html/audits/1

BibTeX 인용

@techreport{shreyam1008-shreyam1008-html-2026,
  author = {shreyam1008},
  title = {html security audit report (audit version 1)},
  institution = {Skillstore},
  year = {2026},
  number = {1},
  url = {https://skillstore.io/skills/shreyam1008-html/audits/1},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "html security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
  - name: "shreyam1008"
date-released: "2026-10-02"
url: "https://skillstore.io/skills/shreyam1008-html/audits/1"
identifiers:
  - type: other
    value: "skillstore:shreyam1008-html:audit:1"
    description: "Skillstore immutable audit report identifier"

Skillstore 점수

이 점수의 이유 증거 신뢰도: 중간

아키텍처

유지보수성

콘텐츠

커뮤니티

사양 준수

만들 수 있는 것

Start a new page

Generate a semantic document skeleton with landmarks, headings, metadata, and accessible content structure.

Improve a form

Review fields, labels, input types, grouping, validation, and error associations for a more usable form.

Audit markup quality

Inspect existing HTML for semantic, accessibility, metadata, and performance-aware markup improvements.

이 프롬프트를 사용해 보세요

Create a page structure

Create a semantic HTML structure for a page about [topic]. Include landmarks, a logical heading order, and accessible navigation.

Build an accessible form

Design the HTML for a [form type]. Include labels, suitable input types, autocomplete values, field grouping, native validation, and accessible error references.

Review existing markup

Review this HTML for semantic structure and accessibility. List each issue, explain its user impact, and propose a specific markup correction: [paste HTML].

Optimize document metadata

Audit the document head for [page type]. Recommend title, description, language, viewport, canonical, social metadata, structured data, image dimensions, and script loading improvements.

모범 사례

Prefer native HTML elements before adding ARIA roles or custom interaction.
Give every control a clear label, suitable type, and predictable keyboard behavior.
Keep document structure, metadata, and resource loading aligned with the page purpose.

피하기

Do not use clickable div elements when a button or link provides the required behavior.
Do not use placeholders as the only form labels or skip heading levels for visual styling.
Do not add aggressive alerts, unnecessary preload hints, or metadata without a clear purpose.

자주 묻는 질문

Does this skill create CSS?

No. It focuses on semantic markup, native behavior, accessibility, forms, metadata, and performance-aware HTML.

Can it design accessible forms?

Yes. It covers labels, input types, autocomplete, fieldsets, legends, native validation, and error associations.

Does it replace an accessibility audit?

No. It provides markup guidance, but automated checks and manual testing remain necessary.

Can it improve SEO markup?

Yes. It can recommend titles, descriptions, canonical links, social metadata, structured data, and semantic content structure.

Should I use ARIA everywhere?

No. Prefer native semantics and add ARIA only when it fills a genuine accessibility gap.

Can it review existing HTML?

Yes. Provide the markup and context, and it can identify structural, form, metadata, and accessibility improvements.

개발자 세부 정보

작성자

shreyam1008

라이선스

MIT

Skillstore 리비전

버전 안내

작성자가 버전을 선언하지 않았습니다.

리포지토리

https://github.com/shreyam1008/shre-skills/tree/ba9787f41c2fe1be1062eeb6322bc339a1026383/skills/html

참조

bbec03cf10354f3aaccd6dd24eda4ac9ceeceac5

유지보수 최신성

2026. 10. 2.

사용량

0 다운로드 · 0 조회

파일 구조

📄 SKILL.md