litespeed/list-optimization-exclusions reads the optimisation exclusion lists: which files, URIs and roles are held back from the CSS and JS pipeline.
It is the first place to look when a script breaks after enabling combine or defer — and the first place to look when one mysteriously did not break.
At a glance
| Ability | litespeed/list-optimization-exclusions |
| Toolset | LiteSpeed Cache — toolset/litespeed |
| Group | LiteSpeed Cache › CSS, JS & HTML |
| Requires | LiteSpeed Cache, active on the site |
| Capability | manage_options |
| Safety | Read-only — changes nothing |
| Repeatable | Idempotent — running it twice leaves the same result |
| Ships in | AcrossAI Abilities Manager 0.0.34 and later |
How it works
Every exclusion is a piece of history: something broke, somebody excluded it, and the reason is not recorded anywhere. Reading the list is reading the site’s accumulated incidents with the explanations removed.
That makes it useful in both directions. A script that is failing may need adding; a list that has grown to thirty entries is a sign the optimisation settings are more aggressive than this site can support, and dialling them back may be better than maintaining the exclusions.
The lists are separate by kind — skip combining, skip deferring, skip delaying, skip everything — and a script can be on one and not another. That distinction is where most of the confusion lives: a script excluded from combining is still being deferred.
Input
This ability takes no input.
What comes back
| Name | Type | What it is |
|---|---|---|
settings | array | One row per setting: its key, its current value, its type, and whether this suite can write it. |
count | integer | How many settings the area holds. |
success | boolean | Whether the call completed. |
message | string | A one-line summary of what happened, suitable for showing a human. |
error_code | string | Present only on failure — a stable machine-readable reason, such as a missing field, a wrong field type or an unmet confirmation. |
Example
Ask your assistant:
What scripts are we already excluding from optimisation?
It resolves to one call:
{
"ability": "litespeed/list-optimization-exclusions",
"parameters": {}
}Worth knowing
- Exclusion from combining is not exclusion from deferring. The lists are separate.
- A long list suggests the settings are too aggressive for this site.
- Nothing records why an entry was added. Read it as history.
Related abilities
- Update Optimisation Exclusions — change one list
- Get Optimisation Settings — what the exclusions protect against
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category