local-test

Automate local Jekyll build validation with Playwright MCP and capture screenshots.

1|Updated Nov 5, 2021
One-click install
npx skills add https://github.com/talmolab/lab-website --skill local-test
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: local-test
Source: https://github.com/talmolab/lab-website/tree/main/.claude/skills/local-test
Command: npx skills add https://github.com/talmolab/lab-website --skill local-test

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @playwright/mcp.

What problem does it solve?

Manually checking website changes across multiple pages and screen sizes is tedious and error-prone. This Skill automates local site testing and visual validation, ensuring your website looks perfect before deployment.

Core Features & Use Cases

  • Automated Browser Testing: Uses Playwright MCP to start a local Jekyll server, navigate to key pages, and capture full-page screenshots.
  • Visual Regression & Validation: Helps identify layout issues, broken elements, or missing content by providing visual evidence of how pages render.
  • Use Case: Before deploying a new feature or content update, use this Skill to automatically generate screenshots of the homepage, team page, and a sample member profile, then review them to confirm everything renders as expected.

Quick Start

Test the local Jekyll build and capture screenshots of the main website pages.

Frequently Asked Questions about local-test

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate visual testing of my Jekyll site locally?

Visual testing automates screenshot capture and validation of Jekyll pages during development. This Skill starts your local Jekyll server, navigates core pages, and captures full-page screenshots using Playwright to verify layout, rendering, and content before deployment.

Can I use Playwright to test my Jekyll website automatically?

Yes. Playwright MCP powers automated browser navigation and visual validation of Jekyll sites. This Skill launches the development server, waits for readiness, visits key pages, captures screenshots, and verifies page structure and titles to catch rendering issues early.

What pages does local Jekyll testing check automatically?

This Skill validates core pages: homepage, team page, research page, publications page, and member profiles. It captures full-page screenshots of each, verifies page titles and DOM structure, and reports any rendering health issues or errors found during the test run.

How do I catch layout and rendering bugs before deploying Jekyll changes?

Automated visual validation captures screenshots of your site across key pages and screens. This Skill generates visual evidence of how content renders after local changes, letting you review rendered output and identify broken elements or layout issues before going live.

Do I need to manually start my Jekyll server to run visual tests?

No. This Skill handles server startup automatically, launching your Jekyll development server in the background, waiting for it to be ready, then navigating and testing pages. You only run the Skill; it manages the entire test workflow.

What's the difference between visual regression testing and manual site review?

Visual regression testing automates screenshot capture and page structure validation across multiple pages at once, catching inconsistencies and rendering errors systematically. Manual review is slower and error-prone; automation ensures consistent validation before each deployment.