oil-ui
Explore and Refine Interface Designs
Interface projects often need clear visual direction before implementation. Oil UI guides design exploration, preview comparison, and evidence-based refinement.
インストール前に停止して確認を求めてください。
計画を確認し、ファイルを変更する前にユーザーの明示的な同意を得てください。
自分のエージェントでインストール
このリクエストをエージェントにコピーしてください。正規の Skill ページとマニフェストが含まれています。
Review the Skillstore skill "oil-ui" from https://skillstore.io/skills/oil-oil-oil-ui.md and its manifest at https://skillstore.io/api/skills/oil-oil-oil-ui/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.エージェントは引き続き計画を提示し、セキュリティポリシーで必要な確認を求める必要があります。
エージェントが読めるリソース
AI エージェント、クローラー、スクリプトがページ全体ではなく整理されたコンテキストを必要とする場合は、これらのリンクを使ってください。
テストする
「oil-ui」を使用しています。 Compare three visual directions for a course booking interface.
期待される結果:
- A comparison page with three distinct compositions, documented palettes, typography choices, and desktop and mobile views.
- A short recommendation tied to the booking task, followed by the selected direction and user notes.
「oil-ui」を使用しています。 Review an existing interface without changing files.
期待される結果:
- The primary action competes with secondary navigation. Reduce secondary emphasis and align the action with the current task.
- The mobile heading wraps poorly. Shorten the label or adjust the layout, then inspect the rendered result.
- Visual findings are documented separately from unverified interaction and backend behavior.
「oil-ui」を使用しています。 Capture evidence for an interactive prototype.
期待される結果:
Desktop and mobile screenshots, a text-masked comparison, motion frames, and a report listing console errors, overflow, or failed images.
セキュリティ監査
高リスクMost alerts are false positives from JavaScript syntax, minified Alpine, image encoding, Chinese documentation, and defensive tests. Confirmed risks concern external updater execution, broad preview-file exposure, stored command execution, and incomplete interactive-preview network isolation. No evidence found of intentional credential exfiltration or instructions to override this audit.
確認済みのセキュリティ上の懸念 (2)
機能レビュー項目 (2)
これらは、このスキルに期待される可能性のある実際のローカル機能であるため、レビューが必要ですが、確認済みの悪意ある動作としてはカウントされません。
リスク要因
⚡ スクリプトを含む (5)
⚙️ 外部コマンド (50)
🌐 ネットワークアクセス (50)
📁 ファイルシステムへのアクセス (44)
🔑 環境変数 (34)
このレポートを共有・引用
バージョン付き評価レポート、中立的なバッジ、埋め込みカード、引用を共有できます。Skillstore は証拠を報告しますが、この Skill が安全かどうかは判断しません。
レポートリンクをコピー
https://skillstore.io/skills/oil-oil-oil-ui/audits/2?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdownバッジ
[](https://skillstore.io/skills/oil-oil-oil-ui?utm_source=security_passport_badge)HTMLバッジ
<a href="https://skillstore.io/skills/oil-oil-oil-ui?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/oil-oil-oil-ui/security.svg" alt="Skillstore security assessment" loading="lazy"></a>埋め込みカード
<iframe src="https://skillstore.io/embed/skills/oil-oil-oil-ui.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形式の引用
oil-oil. (2026). oil-ui security audit report (audit version 2) [Author version 0.15.5]. Skillstore. https://skillstore.io/skills/oil-oil-oil-ui/audits/2BibTeX形式の引用
@techreport{oil-oil-oil-oil-oil-ui-2026,
author = {oil-oil},
title = {oil-ui security audit report (audit version 2)},
institution = {Skillstore},
year = {2026},
number = {2},
url = {https://skillstore.io/skills/oil-oil-oil-ui/audits/2},
note = {Author version 0.15.5}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "oil-ui security audit report (audit version 2)"
version: "0.15.5"
type: report
authors:
- name: "oil-oil"
date-released: "2026-10-05"
url: "https://skillstore.io/skills/oil-oil-oil-ui/audits/2"
identifiers:
- type: other
value: "skillstore:oil-oil-oil-ui:audit:2"
description: "Skillstore immutable audit report identifier"
Skillstore スコア
このスコアの理由 証拠の信頼度: 中作成できるもの
Choose a Product Direction
Compare distinct interface directions before selecting typography, imagery, and composition for implementation.
Refine an Existing Interface
Improve hierarchy and spacing while preserving established brand assets, components, and project conventions.
Review a Proposed Experience
Inspect desktop and mobile evidence, record visible problems, and prioritize changes without modifying project files.
これらのプロンプトを試す
Review this screen for hierarchy, spacing, typography, and readability. Keep files unchanged and distinguish visible defects from style preferences.
Explore three distinct directions for this product. Keep the audience, content, and main action consistent, then create a comparison page.
Recreate this reference at its documented viewport. Add a mobile layout and label assumptions where the reference does not show behavior.
Refine this workflow using existing components. Capture key states and motion evidence, request an independent visual review, and report remaining gaps.
ベストプラクティス
- Define the audience, main action, actual content, target viewport, and deliverable before exploring directions.
- Inspect actual-size desktop and mobile renders; record unverified behavior and keep screenshots tied to the current version.
- Use trusted candidates in a dedicated preview directory, approve saved commands, and authorize updates separately.
回避
- Treating a static screenshot or scaled preview as proof of working interaction or mobile reflow.
- Executing stored manifest commands or external updates without reviewing their source and scope.
- Previewing untrusted scripts beside private files or claiming interactive previews cannot make external requests.