skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
syncfusion/aspnetcore-ui-components-skills108 installs

syncfusion-aspnetcore-security

**CONTENT SECURITY POLICY (CSP) GUIDE** — Assist with configuring Syncfusion ASP.NET Core EJ2 components to work with strict Content Security Policy (CSP) headers. Use when: implementing CSP headers, generating and applying nonces to inline scripts/styles, configuring external font allowlists, or troubleshooting CSP violations.

How do I install this agent skill?

npx skills add https://github.com/syncfusion/aspnetcore-ui-components-skills --skill syncfusion-aspnetcore-security
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    The skill provides legitimate security guidance and code examples for implementing Content Security Policy (CSP) with Syncfusion ASP.NET Core components. No security risks were identified.

  • Socketpass

    No alerts

  • Snykpass

    Risk: LOW · No issues

What does this agent skill do?

Content Security Policy (CSP) — Syncfusion ASP.NET Core (Security)

Use this skill for high-level, Syncfusion-specific CSP guidance and references. Detailed code snippets and implementation examples live in the concern's references files.

When to Use

  • Implementing CSP headers for Syncfusion EJ2 controls
  • Running in strict CSP mode where inline scripts/styles are restricted
  • Adding nonces to inline scripts/styles for Syncfusion initialization
  • Allowlisting CDN resources or external fonts required by Syncfusion themes

Quick Checklist

  • Generate a cryptographically secure nonce per request
  • Add the nonce to the CSP header and to all Syncfusion script/style tags
  • Allow required CDN origins and font providers in CSP directives
  • Avoid unsafe-inline/unsafe-eval unless absolutely necessary
  • Verify behavior in browser DevTools and address CSP violations

Generic Guidelines (Summary)

  • Generate nonces early in the pipeline and store them in HttpContext for views
  • Use minimal, explicit CSP directives (prefer 'self', explicit hostnames, and 'nonce-<value>')
  • Prefer data binding over inline templates to avoid unsafe-eval requirements
  • Document your CSP policy and the reasons for any relaxations

References

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/syncfusion/aspnetcore-ui-components-skills/syncfusion-aspnetcore-security">View syncfusion-aspnetcore-security on skillZs</a>