Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Applica regole di sicurezza (hardening) ogni volta che si costruisce, modifica o revisiona un sito web o un'app. Copre security headers, CSP, HTTPS, validazione input, cookie, CORS, upload, gestione errori e OWASP Top 10. Trigger - "crea un sito", "costruisci un'app", "metti in sicurezza", "proteggi il sito", "hardening", "security headers", "build a website".
.claude/skills/ccplugins-hardening-siti/SKILL.md| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-01 | ✗→✓ | ▲ Improved | 59% | 0% |
| case-02 | ✗→✓ | ▲ Improved | 123% | 0% |
| case-03 | ✗→✓ | ▲ Improved | 37% | 0% |
| case-04 | ✗→✓ | ▲ Improved | 46% | 0% |
| case-11 | ✗→✓ | ▲ Improved | 16% | 0% |
Quando si costruisce o si modifica un sito/app, applicare SEMPRE queste regole di sicurezza senza che l'utente debba chiederlo. Segnalare nel riepilogo finale quali protezioni sono state applicate.
Applicare su ogni risposta HTML:
Strict-Transport-Security: max-age=31536000; includeSubDomains
X-Content-Type-Options: nosniff
X-Frame-Options: DENY
Referrer-Policy: strict-origin-when-cross-origin
Permissions-Policy: camera=(), microphone=(), geolocation=()
Content-Security-Policy: default-src 'self'; script-src 'self'; object-src 'none'; base-uri 'self'; frame-ancestors 'none'In Node/Express usare helmet(). In Django attivare SECURE_* settings. Su hosting statico (Netlify/Vercel/GitHub Pages) usare il file headers della piattaforma. Adattare la CSP alle risorse reali del sito (CDN, font, analytics) — mai usare unsafe-inline per gli script; preferire nonce o hash.
innerHTML, eval, attributi evento o URL senza sanitizzazione.path.basename + directory fissa.HttpOnly; Secure; SameSite=Lax (o Strict per azioni sensibili).Access-Control-Allow-Origin: * su endpoint autenticati. Whitelist esplicita di origin..env in .gitignore..gitignore con .env, node_modules, credenziali.npm audit / pip-audit (vedi skill sicurezza-github per l'automazione).Prima di consegnare un sito/app, verificare: headers presenti, query parametrizzate, validazione server, cookie sicuri, CSRF, niente segreti nel codice, errori generici, .gitignore corretto. Elencare all'utente le protezioni applicate e gli eventuali punti che richiedono configurazione sul suo hosting.
| Case | Status | Duration (ms) | Turns | Tokens | Tool calls | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Without | With | Δ | Without | With | Δ | Without | With | Δ | Without | With | Δ | ||
case-01 | fail→pass | 27,791 | 38,759 | +39% | 1 | 1 | 0% | 4,993 | 7,932 | +59% | 0 | 0 | — |
case-02 | fail→pass | 25,144 | 26,788 | +7% | 1 | 1 | 0% | 2,620 | 5,837 | +123% | 0 | 0 | — |
case-03 | fail→pass | 32,075 | 31,600 | -1% | 1 | 1 | 0% | 5,164 | 7,094 | +37% | 0 | 0 | — |
case-04 | fail→pass | 31,710 | 16,782 | -47% | 1 | 1 | 0% | 2,721 | 3,976 | +46% | 0 | 0 | — |
case-05 | pass→pass | 17,695 | 16,859 | -5% | 1 | 1 | 0% | 3,283 | 4,036 | +23% | 0 | 0 | — |
case-06 | pass→pass | 16,673 | 14,933 | -10% | 1 | 1 | 0% | 2,704 | 3,556 | +32% | 0 | 0 | — |
case-07 | fail→fail | 13,185 | 13,695 | +4% | 1 | 1 | 0% | 2,357 | 3,179 | +35% | 0 | 0 | — |
case-08 | pass→pass | 16,099 | 16,634 | +3% | 1 | 1 | 0% | 2,567 | 3,971 | +55% | 0 | 0 | — |
case-09 | pass→pass | 13,194 | 12,660 | -4% | 1 | 1 | 0% | 2,202 | 3,012 | +37% | 0 | 0 | — |
case-10 | pass→pass | 20,474 | 19,383 | -5% | 1 | 1 | 0% | 3,402 | 4,167 | +22% | 0 | 0 | — |
case-11 | fail→pass | 19,325 | 17,593 | -9% | 1 | 1 | 0% | 3,383 | 3,908 | +16% | 0 | 0 | — |
case-12 | pass→pass | 16,817 | 17,844 | +6% | 1 | 1 | 0% | 2,475 | 3,735 | +51% | 0 | 0 | — |
case-13 | pass→pass | 15,516 | 15,078 | -3% | 1 | 1 | 0% | 2,203 | 3,213 | +46% | 0 | 0 | — |
case-14 | pass→pass | 16,182 | 18,402 | +14% | 1 | 1 | 0% | 2,501 | 4,039 | +61% | 0 | 0 | — |
case-15 | pass→pass | 16,011 | 15,404 | -4% | 1 | 1 | 0% | 2,497 | 3,220 | +29% | 0 | 0 | — |
case-16 | pass→pass | 20,742 | 23,143 | +12% | 1 | 1 | 0% | 3,864 | 4,909 | +27% | 0 | 0 | — |
case-17 | fail→fail | 12,467 | 9,836 | -21% | 1 | 1 | 0% | 1,842 | 2,404 | +31% | 0 | 0 | — |
case-18 | pass→pass | 15,420 | 18,912 | +23% | 1 | 1 | 0% | 2,449 | 3,955 | +61% | 0 | 0 | — |
case-19 | pass→pass | 24,597 | 27,777 | +13% | 1 | 1 | 0% | 3,982 | 5,896 | +48% | 0 | 0 | — |
case-20 | pass→pass | 14,293 | 15,373 | +8% | 1 | 1 | 0% | 2,196 | 3,458 | +57% | 0 | 0 | — |
case-21 | pass→pass | 13,706 | 16,165 | +18% | 1 | 1 | 0% | 2,065 | 3,574 | +73% | 0 | 0 | — |
case-22 | pass→pass | 17,363 | 15,020 | -13% | 1 | 1 | 0% | 3,379 | 3,428 | +1% | 0 | 0 | — |
case-23 | pass→pass | 15,751 | 18,139 | +15% | 1 | 1 | 0% | 2,794 | 3,870 | +39% | 0 | 0 | — |
DecimalAI ran this skill against gemini-3.6-flash twice over the same eval suite — once with the skill loaded and once without — and compared the two runs case by case. 23 cases were attempted. The headline lift of +22 percentage points is the difference between those two pass rates over the 23 comparable cases. 1 case got worse with the skill loaded, and it is included in that figure.
Without the skill loaded, the model failed this case. With it loaded, the same prompt on the same model passed. This is one improved case from the latest verified run; every case, including any that regressed, is in the table above.
Other measured skills in the registry, with their headline benchmark lift.