ui-styling Skill
Guide for the visual style, structure, and shared building blocks used by Semantic Link Labs interactive UI tools (HTML widgets and anywidget-based widgets). Use this when adding a new interactive UI, modifying an existing one, or adding shared visual components. Published by microsoft in semantic-link-labs.
Decision snapshot
Is this a fit?
Design and media, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
2 months ago · MIT license
No specific cautions were detected. Review the source and requested permissions before installing.
What is ui-styling Skill?
Guide for the visual style, structure, and shared building blocks used by Semantic Link Labs interactive UI tools (HTML widgets and anywidget-based widgets). Use this when adding a new interactive UI, modifying an existing one, or adding shared visual components. Published by microsoft in semantic-link-labs. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Design and media
- Design and media use cases
Declared skill metadata
- Source file: .claude/skills/ui-styling/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use ui-styling Skill
- Use it for design and media.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/semantic-link-labs
- Skill file: .claude/skills/ui-styling/SKILL.md
What it does
Guide for the visual style, structure, and shared building blocks used by Semantic Link Labs interactive UI tools (HTML widgets and anywidget-based widgets). Use this when adding a new interactive UI, modifying an existing one, or adding shared visual components.
Skill instructions
UI Styling for Interactive Tools This skill describes the styling conventions, shared building blocks, and architectural patterns used by all interactive UI tools in Semantic Link Labs so that every tool has a consistent, elegant design. When to Use This Skill Use this skill when you need to: - Add a new interactive UI function to the library. - Modify an existing interactive UI (e.g. vertipaqanalyzer, deltaanalyzer, perspectiveeditor). - Add new shared visual components (icons, theme variables, headers, etc.) that should be reused across tools. - Decide between a static-HTML widget and an anywidget-based widget. --- The Two UI Patterns Semantic Link Labs has exactly two supported patterns for interactive UI tools. Always pick one based on whether the UI needs to call back into Python after the initial render. | Pattern | When to use | Reference implementations | |---------|-------------|---------------------------| | Static-HTML widget (the Vertipaq style) | The UI is fully driven by
Verified compatibility and discovery
Frequently asked questions
What is ui-styling?
ui-styling is a open-source AI agent skill with Copy skill directory. Guide for the visual style, structure, and shared building blocks used by Semantic Link Labs interactive UI tools (HTML widgets and anywidget-based widgets).
Who is ui-styling best for?
ui-styling is best for reusing agent instructions, scripts, and references, design and media workflows.
How do I install ui-styling?
Install or run ui-styling using Copy skill directory. Check ui-styling for the latest setup command.
Is ui-styling actively maintained?
ui-styling may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
