القائمة
Use when checking Bricks' AI screen: the master Bricks abilities toggle, per-ability disable list, direct-tool fast path, `bricks-list-ability-status`, and error codes when an ability is off.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
Use when writing custom-element controls or debugging control behavior: "what control type for a color?", "conditional control visibility", "dynamic data on a custom control". Covers the ~40 control types, the `required` syntax, CSS-binding via `css` key, dynamic-data support, and default-value gotchas.
Use before writing or editing Bricks element JSON, settings, controls, globals, page settings, or template settings. Gives the runtime lookup order plus bundled full resolved schemas so you can check exact control keys and value shapes instead of guessing.
Use after every write through the Bricks MCP: set-page-elements, update-element, update-element-conditions, update-element-interactions, batch-update-elements, set-template-conditions, set-global-variables, create-theme-style, etc. Defines the verify-after-write loop: read back the change, render the affected post, check for silent failures (empty render, unknown tags, unbalanced braces, query:null). Catches the "tool returned success but the page broke" class of bugs.
Use when the Bricks skills update check reports BRICKS_SKILLS_UPDATE_AVAILABLE, or when the user asks to update the Bricks skills pack.
Use at the start of every Bricks session. Orientation rules: call get-design-context before any design-system write, verify mutations with get-page-elements / list-revisions, and never force same-named globals to duplicate.
Use when creating or updating design tokens: global classes, variables, color palettes, theme styles, components. Enforces uniqueness, scale-generator usage, and conditions on theme styles. Prevents system fragmentation.
استنادا إلى تصنيف SOC المهني
| name | bricks-ai-tab |
| description | Use when checking Bricks' AI screen: the master Bricks abilities toggle, per-ability disable list, direct-tool fast path, `bricks-list-ability-status`, and error codes when an ability is off. |
Requires: Bricks 2.4+ with the Abilities API enabled
Run first when filesystem tools are available:
_BS_UPDATE_CHECK=""
for _CAND in "$HOME/.bricks/skills/bricks-skills/scripts/bricks-skills-update-check" "$PWD/scripts/bricks-skills-update-check" "$HOME/.claude/skills/bricks-skills/scripts/bricks-skills-update-check" "$HOME/.codex/skills/bricks-skills/scripts/bricks-skills-update-check"; do
[ -f "$_CAND" ] && _BS_UPDATE_CHECK="$_CAND" && break
done
[ -n "$_BS_UPDATE_CHECK" ] && sh "$_BS_UPDATE_CHECK" || true
If it prints BRICKS_SKILLS_UPDATE_AVAILABLE <old> <new> <tag>, load bricks-skills-update before continuing. If it prints BRICKS_SKILLS_JUST_UPDATED <old> <new>, mention the new version and continue.
Bricks exposes its abilities to MCP clients through Bricks > AI. This screen is the admin control panel for Bricks abilities. MCP clients cannot change these settings. The screen affects which Bricks abilities are callable.
bricks-list-ability-status are absent.bricks-list-ability-status and adapter get-info/discovery, but execution returns bricks_ability_disabled.Do not treat tools/list as the complete Bricks ability list.
Current Bricks source keeps only high-frequency abilities on the default MCP server as direct tools (includes/abilities/manager.php). The rest are enabled abilities but must be called through:
mcp-adapter-execute-ability
ability_name: "bricks/<ability-name>"
parameters: { ... }
So a missing direct tool can mean either:
bricks_ability_disabled, orCheck status before concluding the ability does not exist.
The storage option bricks_mcp_settings is shaped:
{
"enabled": true,
"disabledAbilities": [ "bricks/delete-post", "bricks/upload-media" ],
"enabledAbilities": [ "bricks/list-builder-permissions" ]
}
disabledAbilities opts out of default-on abilities. enabledAbilities opts into default-off abilities. Permission-management tools are default off because they can change builder access for WordPress roles.
Call:
bricks-list-ability-status
Example response shape (includes/abilities/meta.php):
{
"abilities": [
{ "name": "bricks/add-element", "enabled": true, "defaultEnabled": true, "category": "bricks-elements", "destructive": false },
{ "name": "bricks/set-builder-role-access", "enabled": false, "defaultEnabled": false, "category": "bricks-permissions", "destructive": false }
],
"total": 122,
"enabled": 121,
"disabled": 1
}
If enabled: false, a site admin either disabled the ability or has not opted into a default-off group. You cannot route around it. The fix is for a human to enable it under Bricks > AI.
Also call:
bricks-get-mcp-version
Current response shape:
{
"bricksVersion": "2.3.4",
"bricksAbilitiesVersion": "1.0.0",
"adapterVersion": null,
"wordpressVersion": "6.8",
"abilitiesApiActive": true,
"disabledAbilityCount": 1
}
There is no abilityCount field in get-mcp-version; use list-ability-status.total when you need the count.
bricks_ability_disabled: the dispatcher or a diagnostic path reached an ability name that the admin disabled. Do not retry. Call bricks-list-ability-status to confirm state.bricks/* abilities register at all. Tell the user to enable Bricks abilities under Bricks > AI.bricks_setting_excluded / bricks_setting_unknown: these come from the settings registry, not the AI screen. See the bricks-settings skill.The AI screen is an exposure deny-list, not a role editor:
bricks_ability_disabled.These are not toggleable by MCP and should stay human-admin tasks:
apiKey*, apiSecretKey*, or license*, plus access tokens and template passwords, are excluded from Bricks settings abilities. Use bricks-list-credential-status to check whether a credential is configured without reading its value. Other provider settings, such as adobeFontsProjectId, are only writable if bricks/list-settings-schema exposes them.executeCodeEnabled, executeCodeCapabilities, codeSignaturesLocked, codeExecutionMode, and htmlExecutionMode are excluded from Bricks settings abilities (includes/abilities/settings.php).If a task requires one of these, surface the requirement to a human. Do not try to find another MCP route.
# Expected bricks/delete-global-class but it is not in tools/list.
bricks-list-ability-status
-> { abilities: [ ..., { name: "bricks/delete-global-class", enabled: false, category: "bricks-design" } ], ... }
# Admin disabled it. Tell the user:
# "The site owner has disabled delete-global-class on this Bricks install.
# Re-enable it under Bricks > AI."
list-ability-status when an expected ability is missing.bricks_ability_disabled. The deny-list is explicit.bricks_mcp_settings directly. The UI is the contract.tools/list entry means the ability is disabled. Many enabled Bricks abilities are dispatcher-only.