📦

ui

Name: ui
Author: Chachamaru127

Content revision r1 Medium Risk ⚙️ External commands

Create Accessible UI Components and Feedback Forms

Teams need consistent UI components and feedback flows without rebuilding common patterns. This skill guides Claude, Codex, and Claude Code to generate accessible React-oriented UI.

Supports: Claude Codex Code(CC)

📊 70 Adequate

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

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

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/chachamaru127-ui.md Signed manifest GET /api/skills/chachamaru127-ui/manifest Signed lockfile GET /api/skills/chachamaru127-ui/lockfile

Test it

Using "ui". Create a SaaS pricing section with three plans.

Expected outcome:

A responsive pricing layout with plan names, feature lists, clear actions, accessible headings, and mobile-friendly spacing.

Using "ui". Add a bug report form to my app.

Expected outcome:

A feedback form flow with issue type, description, severity, contact option, validation messages, and success confirmation.

Using "ui". Make this contact form more accessible.

Expected outcome:

A revised form plan with linked labels, visible focus states, keyboard order, contrast checks, and screen reader friendly errors.

Security Audit

Medium Risk

v8 • 7/6/2026 Open versioned report

The static backtick and entropy findings are false positives after reviewing the listed files. No prompt injection, encoded payload, or direct command execution was found. A medium contextual risk remains because the community skill grants Bash and describes automatic package installation.

Files scanned

164

Lines analyzed

Review items

False positives ignored

Confirmed security concerns (1)

Medium

SKILL.md:4 component/doc.md:30

Broad Bash Permission for UI Generation

The skill allows Bash and documents automatic shadcn/ui installation. This can lead the assistant to run package manager commands during UI generation.

Bash permission and auto-install guidance are explicit. No concrete malicious command appears, so the concern is contextual rather than confirmed abuse.

Risk Factors

⚙️ External commands (3)

SKILL.md:39-60 SKILL.md:60-64 SKILL.md:64-75

Audited by: codex View Audit History →

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/chachamaru127-ui/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

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

HTML badge

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

Embed card

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

Academic citations (APA · BibTeX · CFF)

APA citation

Chachamaru127. (2026). ui security audit report (audit version 8) [Author version unspecified]. Skillstore. https://skillstore.io/skills/chachamaru127-ui/audits/8

BibTeX citation

@techreport{chachamaru127-chachamaru127-ui-2026,
  author = {Chachamaru127},
  title = {ui security audit report (audit version 8)},
  institution = {Skillstore},
  year = {2026},
  number = {8},
  url = {https://skillstore.io/skills/chachamaru127-ui/audits/8},
  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: "ui security audit report (audit version 8)"
version: "unspecified"
type: report
authors:
  - name: "Chachamaru127"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/chachamaru127-ui/audits/8"
identifiers:
  - type: other
    value: "skillstore:chachamaru127-ui:audit:8"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

Build Landing Page Sections

Create hero, pricing, features, header, footer, and contact sections that follow accessible UI patterns.

Add Product Feedback Forms

Generate feedback, bug report, feature request, or satisfaction form flows for an existing app.

Improve UI Accessibility

Use the checklist to add labels, focus states, keyboard support, contrast checks, and readable errors.

Try These Prompts

Create a Basic Section

Create a responsive hero section for my product page using accessible labels and clear call to action text.

Generate a Feedback Form

Add an in-app feedback form with rating, category, message, validation states, and accessible error messages.

Match Existing UI

Review the current UI patterns, then create a pricing section that matches spacing, colors, Tailwind usage, and accessibility standards.

Plan a Full Feedback Flow

Design a secure feedback collection flow, including UI states, confirmation messages, data fields, and review points before backend work.

Best Practices

Confirm the target component type and existing design system before generating UI.
Review every generated form for labels, focus states, keyboard access, and error handling.
Ask before running package installation or commands that modify project dependencies.

Avoid

Do not use this skill for authentication, database design, or unrelated backend logic.
Do not accept generated package commands without checking the exact dependency changes.
Do not rely on color alone to communicate errors, status, or required actions.