visual-test Skill
Visually verify a component by launching its Storybook story and taking a screenshot with playwright-cli. Use after making visual changes to a component. Published by microsoft in fluentui.
Decision snapshot
Is this a fit?
Browser automation, Testing, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Filesystem access, Shell access
Copy skill directory
2 months ago · NOASSERTION license
Access note: Local files. Access note: Shell access.
What is visual-test Skill?
Visually verify a component by launching its Storybook story and taking a screenshot with playwright-cli. Use after making visual changes to a component. Published by microsoft in fluentui. 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
- Browser automation
- Testing
- Browser automation use cases
- Testing use cases
Declared skill metadata
- Source file: .agents/skills/visual-test/SKILL.md
Allowed tools declared by source
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
- Local files
- Shell access
Requirements and access
Security and permissions
Review permissions before connecting any MCP server to an agent. Pay special attention to whether it can read local files, write data, call external services, or perform destructive actions.
When to use visual-test Skill
- Use it for browser automation.
- Use it for testing.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/fluentui
- Skill file: .agents/skills/visual-test/SKILL.md
What it does
Visually verify a component by launching its Storybook story and taking a screenshot with playwright-cli. Use after making visual changes to a component.
Skill instructions
Visual Test a Component Visually verify $ARGUMENTS by launching Storybook and capturing a screenshot with playwright-cli. Prerequisites Run playwright-cli via npx so nothing is installed globally on the user's box. The first invocation downloads @playwright/cli@0.1.1 into the npx cache; subsequent calls are cached. Every command below uses this form: bash npx -y @playwright/cli@0.1.1 <command Critical: use the per-component Storybook only Always boot the per-component stories package (react-<component-stories) via nx storybook target, which only imports its own component's stories and dependencies. Steps 1. Find the component's stories package. Each v9 component has a dedicated stories package named react-<component-stories: bash yarn nx show project react-<lowercase-component-name-stories --json If nx returns nothing with output of Could not find project react-<component-stories, the component doesn't have its own stories package — check for a preview package (react-<component-preview
Verified compatibility and discovery
Frequently asked questions
What is visual-test?
visual-test is a open-source AI agent skill with Copy skill directory. Visually verify a component by launching its Storybook story and taking a screenshot with playwright-cli. Use after making visual changes to a component.
Who is visual-test best for?
visual-test is best for reusing agent instructions, scripts, and references, browser automation workflows, testing workflows.
How do I install visual-test?
Install or run visual-test using Copy skill directory. Check visual-test for the latest setup command.
Is visual-test actively maintained?
visual-test 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.
