Skip to content
TrustedSkillsbeta
Back to all skills

Oiloil Ui Ux Guide

Checked
oil-oil·vlatest·frontend·Apache-2.0

Helps with UI components, UX design as part of agent workflows workflows.

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add oil-oil/ui-ux-guide --skill oiloil-ui-ux-guide -a claude-code
  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

oil-oil

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned oil-oil/oiloil-ui-ux-guide at f32bc2bd21.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Scanned
22 files, 2,396 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The Oiloil UI/UX Guide skill assists AI agents in providing style-neutral UI and UX consultations. It functions as a patient interviewer, prioritizing user preferences and constraints before offering suggestions. The skill adapts its approach based on the project's stage of development, from initial design to complex legacy systems, always aiming to understand the user’s goals before making recommendations.

When to use it

  • Design System Definition: When establishing or refining a design system (e.g., selecting colors and fonts).
  • Component Guidelines: To generate rules for specific UI components like settings pages or dashboards.
  • Screen Review: For reviewing existing screen designs, either through direct visual input or pasted screenshots.
  • Project Assessment: When needing an initial assessment of a project's current design state and direction.
  • Design Direction Exploration: To explore different approaches to UI/UX challenges within a project.

Key capabilities

  • Mode-based operation: Offers distinct modes: design (default), guide, and review.
  • Project Stage Assessment: Automatically assesses the stage of a project (Blank, Half-finished, Mature, Complex Legacy, Uncertain) to tailor its approach.
  • Code Analysis: Analyzes code files like tailwind.config, theme.ts, globals.css, and package.json to understand existing UI frameworks and token usage.
  • Prioritized Listening: Focuses on understanding user needs and constraints before offering opinions or recommendations.
  • Fact-based Descriptions: Communicates observations about a project's state using factual descriptions rather than subjective assessments.

Example prompts

  • "Can you give me some guidance on the design of our settings page?"
  • "Please review this screenshot of my dashboard." (followed by pasting an image)
  • "Let’s pick colors and fonts for our new application."

Tips & gotchas

  • Initial Code Review: The skill prioritizes a brief code review before offering any suggestions. This helps it understand the existing project context.
  • Mode Awareness: Be explicit about the desired mode (design, guide, or review) to ensure accurate results. If ambiguous, the skill will default to "design" and announce this mode.
  • User Preference is Key: The skill prioritizes user taste and constraints; be prepared to articulate your preferences for best results.