Provide noscript fallback content
SkillWeb & browsingnoscript-tag is a skill for AI agents that reviews templates, rendered HTML, and shared components for noscript fallback content. It checks that pages work for users with JavaScript disabled, blocked, or failed to load, and that important content exists in the initial HTML rather than appearing only after hydration.
Available today. Use it from your connected AI after setup.
No other account needed.
Have an agent that can load skills and access the project's templates or rendered HTML.
Then ask your AI: use the Provide noscript fallback content skill
What your AI can do with it
- Review templates and shared components for missing <noscript> elements
- Flag pages where critical features lack alternative content for no-JS users
- Check that important content and pagination paths exist in the initial HTML
- Identify UA-sniffed behavior and suggest feature detection instead
- Explain how hydration mismatches break progressive enhancement
- Point to detailed rule guidance in references/rule.md
Getting started
- Have an agent that can load skills and access the project's templates or rendered HTML.
- Add the noscript-tag skill to the agent's available skills.
- Ask the agent to review a template, page, or component for noscript fallbacks.
- Review the flagged elements, attributes, and routes, then apply fixes.
- Consult references/rule.md for implementation details and code examples.
What this skill tells your AI
The instructions your AI receives, as published by thedaviddias/front-end-checklist in skills/noscript-tag/SKILL.md and read by ahel’s review.
Users with JavaScript disabled, blocked by corporate firewalls, or with failed script loads see blank pages without proper noscript fallbacks.
Quick Reference
- Add with helpful message for JS-dependent features
- Provide alternative content, not just 'Enable JavaScript'
- Use for critical features: analytics fallback, lazy-loaded images
- Consider progressive enhancement: content works without JS
- Important content should be present in the initial HTML, not fetched only after hydration
Check
Verify that this page provides appropriate noscript fallbacks for users with JavaScript disabled or unavailable, ensuring core functionality remains accessible. Confirm important content exists in the initial HTML and is not blocked on hydration.
Fix
Add noscript elements with alternative content or functionality for critical features that depend on JavaScript. Replace UA-sniffed behavior with feature detection and make sure the server-rendered HTML already contains the important content and pagination paths.
Explain
Explain why noscript fallbacks are important for accessibility, progressive enhancement, and ensuring your site works for all users regardless of their JavaScript support. Explain why feature detection is safer than UA sniffing and why hydration mismatches can break progressive enhancement.
Code Review
Review templates, server-rendered HTML, and shared components that output markup related to Provide noscript fallback content. Flag exact elements, attributes, and routes where the rendered HTML violates the rule.
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
Rule page: https://frontendchecklist.io/en/rules/html/noscript-tag
Signals
- GitHub stars
- 74k
- Forks
- 7k
- Last commit
- Aug 2026
Questions
- What does the skill check for?
- It verifies that pages provide noscript fallbacks for users with JavaScript disabled or unavailable, and that important content exists in the initial HTML rather than being blocked on hydration.
- When should the skill be used?
- When reviewing templates, rendered HTML, or shared components related to providing noscript fallback content. It validates the final browser-facing markup, not just the source framework abstraction.
Advanced
- Item type
- skill
- Key
noscript-tag- Source
- github.com/thedaviddias/front-end-checklist