Download for MacApple silicon, macOS 14+
Skill

fix-csp-compliance

@ui5 Updated 2026-10-20

Fix Content Security Policy (CSP) compliance issues that UI5 linter reports but cannot auto-fix. Use this skill when linter outputs: - `csp-unsafe-inline-script` with message "Use of unsafe inline script" Trigger on: inline JavaScript in HTML files, script tags without src attribute, onclick/onload handlers in HTML. Also use when user mentions 'security headers', 'inline script warning', 'CSP policy', 'unsafe-inline', or 'Content-Security-Policy'. Provides guidance on moving inline scripts to external files for CSP compliance.

claudedevelopmentopenui5pluginsapui5ui5

Install

With your agent

Install OMGSkills skill "ui5/plugins-coding-agents:plugins/ui5-modernization/skills/fix-csp-compliance" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.

Manual command

git clone https://github.com/UI5/plugins-coding-agents /tmp/plugins-coding-agents && ln -s /tmp/plugins-coding-agents/plugins/ui5-modernization/skills/fix-csp-compliance ~/.claude/skills/fix-csp-compliance

From README

Fix CSP Compliance - Unsafe Inline Scripts Key Rules NEVER delete inline script content. Always extract it to an external .js file and replace the inline ... with . Even trivial config objects, debug flags, or seemingly unused code must be externalized — removal is a functional regression. File naming: use a descriptive name matching the content's purpose (e.g., appConfig.js for configuration, init.js for initialization). This skill fixes Content Security Policy (CSP) compliance issues that the UI5 linter detects but cannot auto-fix because they require restructuring code into external files.