Automated summary

Flags only demo-breaking visual issues—layout collapse, content cutoff, broken interactions—while ignoring cosmetic tweaks and edge cases.

Strengths

Focuses exclusively on issues that could embarrass during a live demo
Checks multiple viewport widths (375px, 768px, 1024px, 1440px)
Ignores subjective improvements and non-critical edge cases

Limitations

Only covers visual stability, not functional or performance bugs
May miss accessibility or responsiveness issues in niche scenarios
Requires manual setup of viewport sizes for testing

When to use it

Use when preparing for a live demo or final pre-deploy review to ensure visual stability.

When not to use it

Do not use when you need comprehensive UI polish or when functional testing is more important than visual consistency.

Security analysis

Safe

Quality score85/100

The skill provides non-executable guidance for reviewing demo visual stability; no dangerous or unexpected operations are described.

No concerns found

How this analysis is made

Examples

Check demo stability at common viewports

Analyze the app's layout at 375px, 768px, 1024px, and 1440px for any content cut off, layout collapse, or broken interactions that could embarrass during a live demo. Ignore minor alignment or spacing issues.

Verify demo-critical paths

Review the main user flow of this app (login → dashboard → key action) for any visual breakage or missing fallbacks that would be obvious in a demo.

Pre-deploy stability review

Run a stability check on the current build. Flag only issues that cause layout overflow, unreadable text, or broken interactions at any viewport. Skip cosmetic suggestions.

name: demo-stability-checker description: Prioritize visual stability over perfection. Flag only issues that could cause embarrassment during a live demo. Use when preparing for demos, final pre-deploy review, or verifying demo-critical paths.

Demo Stability Checker

Name: Demo Stability Checker
Author: Skills Guide Bot

Instructions

Flag only demo-breaking issues:
- Layout collapse or overflow at 375px, 768px, 1024px, 1440px
- Content cut off or unreadable
- Broken interactions or missing fallbacks
Ignore:
- Cosmetic tweaks (minor alignment, spacing)
- Subjective improvements
- Edge cases unlikely in demo flow
Priority: Visual stability > perfection.

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/demo-stability-checker-mma3jsri/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/demo-stability-checker-mma3jsri' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/demo-stability-checker-mma3jsri/download' --output '.skill-downloads/demo-stability-checker-mma3jsri/SKILL.md.part' && mv '.skill-downloads/demo-stability-checker-mma3jsri/SKILL.md.part' '.skill-downloads/demo-stability-checker-mma3jsri/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code

test -f '.skill-downloads/demo-stability-checker-mma3jsri/SKILL.md' && test -s '.skill-downloads/demo-stability-checker-mma3jsri/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/demo-stability-checker' && cp -R '.skill-downloads/demo-stability-checker-mma3jsri' '.claude/skills/demo-stability-checker'

Cursor

test -f '.skill-downloads/demo-stability-checker-mma3jsri/SKILL.md' && test -s '.skill-downloads/demo-stability-checker-mma3jsri/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/demo-stability-checker' && cp -R '.skill-downloads/demo-stability-checker-mma3jsri' '.cursor/skills/demo-stability-checker'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation

openskills install './.skill-downloads/demo-stability-checker-mma3jsri'

openskills read 'demo-stability-checker-mma3jsri'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/demo-stability-checker-mma3jsri/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.