Avoid inline JavaScript
SkillWeb & browsingjavascript-inline is a skill for AI agents that reviews web pages for inline JavaScript issues. It inspects both the source code and the browser execution path, so fixes target the real bottleneck or bug rather than a symptom. Use it when reviewing scripts, client components, bundles, or runtime behavior related to avoiding inline JavaScript.
Use Avoid inline JavaScript in Claude, ChatGPT or Ahel Desktop
Free. Sign in, add Avoid inline JavaScript and connect your AI. About a minute.
Also: Claude Code · Cursor · Codex
Then ask your AI: use the Avoid inline JavaScript skill
Details
Instructions available. Your AI can read the instructions. Execution depends on the setup they require.
Account requirements not reviewed. Check the skill instructions before use; ahel provides instructions and does not run this skill.
No other account needed.
Have an AI agent that can load skills.
What your AI can do with it
- Review scripts, client components, and bundles for inline JavaScript issues
- Inspect source code to locate inline JavaScript
- Trace the browser execution path to find runtime behavior problems
- Identify the real bottleneck or bug behind an inline JavaScript issue
Getting started
- Have an AI agent that can load skills.
- Add the javascript-inline skill to the agent's available skills.
- Ask the agent to review a page, script, or bundle for inline JavaScript issues.
- Apply the fixes the agent suggests, which target the source code and the browser execution path.
What this skill tells your AI
The instructions your AI receives, as published by thedaviddias/front-end-checklist in skills/javascript-inline/SKILL.md and read by ahel’s review.
Inline JavaScript breaks browser caching, violates Content Security Policy (CSP), and creates unmaintainable spaghetti code mixing markup with behavior.
Quick Reference
- Move onclick/onmouseover handlers to external JS files
- Use addEventListener instead of inline event handlers
- Exception: critical above-the-fold JS can be inlined
- External files enable browser caching across pages
Check
Verify that JavaScript code is not mixed with HTML markup using external script files and proper separation of concerns for better maintainability and performance.
Fix
Move inline JavaScript to external files, implement proper event handling, and use modern JavaScript patterns for DOM interaction.
Explain
Explain why separating JavaScript from HTML improves maintainability, enables caching, reduces security risks, and follows best practices for separation of concerns.
Code Review
Review scripts, client components, and browser execution paths related to Avoid inline JavaScript. Flag exact imports, event handlers, runtime side effects, or blocking operations that violate the rule, and state how the change should be verified in the browser.
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
Rule page: https://frontendchecklist.io/en/rules/javascript/javascript-inline
Signals
- GitHub stars
- 74k
- Forks
- 7k
- Last commit
- Oct 2026
Questions
- When should this skill be used?
- Use it when reviewing scripts, client components, bundles, or runtime behavior related to avoiding inline JavaScript.
- What does the skill inspect?
- It inspects both the source code and the browser execution path, so fixes target the real bottleneck or bug.
- Does it fix the code automatically?
- The item description only says it helps review pages and identify issues; whether it applies fixes automatically is not stated.
Advanced
- Item type
- skill
- Key
javascript-inline- Source
- github.com/thedaviddias/front-end-checklist
github.com/thedaviddias/front-end-checklist
Related picks
Skill · thedaviddias
The pick for JavaScriptmodern-javascript-patterns
Skill · wshobson
The pick for JavaScriptowasp-security
Skill · davila7
The pick for Web (OWASP)security-and-hardening
Skill · addyosmani
The pick for Web (OWASP)browser-use
Skill · browser-use
More in Web & browsingwebapp-testing
Skill · anthropics
More in Web & browsing