litespeed/get-optimization-settings reads the entire optimisation pipeline: minification, combination, deferral, font handling, the tuning exclusion lists and resource localisation.
This is the area most likely to break a theme, so reading comes first.
At a glance
| Ability | litespeed/get-optimization-settings |
| 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 settings read in this suite returns the same shape — key, current value, type, and whether the key is writable — and every settings write takes the same shape back: a map of key to value, applied as a patch. Keys are owned by exactly one area, and litespeed/list-settings-areas is the map of which area owns what.
The pipeline is a sequence, and the settings interact along it. Minification is nearly always safe; combination changes load order; deferral changes when scripts run; delay changes it again and more aggressively. A site can survive any one of those and break on two together.
Which is why the whole area reads in one call. Diagnosing a broken slider means knowing whether combine, defer and delay are all on, not just the one somebody remembers turning on last week.
The exclusion lists are part of the same read for the same reason: a script that is excluded from combining but not from deferring behaves differently from one excluded from both.
For what the pipeline has actually produced — as against what is configured — litespeed/get-optimization-status is the other half.
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:
How is LiteSpeed optimising CSS and JS here?
It resolves to one call:
{
"ability": "litespeed/get-optimization-settings",
"parameters": {}
}Worth knowing
- The settings interact. Read the whole area, not one key.
- Configuration only —
litespeed/get-optimization-statusreports what exists on disk. - The exclusion lists are part of the picture.
Related abilities
- Get Optimisation Status — configured versus working
- List Optimisation Exclusions — what is held back
- Update JS Settings — the riskiest part of the pipeline
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category