- Home
- Skills
- APIs & Backend
- csb inspector
Works with the AI Agents you already use
csb inspector
Inspect and audit Cocos Studio .csb binary files to extract node trees, properties, and asset dependencies.
$5
/moSubscription · cancel anytime
Secure checkout via Stripe
- Always the latest version
- Delivered live to your agent via MCP
- Cancel anytime, access ends at period end
csb inspector
Example session with this skill installed
I need to find a node named "btn_start" in res/ui/login.csb and see what image it uses for its normal state. Also check if it has a custom class.
- Read your context and instructions
- Compiled the csb inspector
The .csb file has been parsed. The node btn_start was located at path root/login_panel/btn_start. It uses a sprite sheet for its textures and does not have a customClassName defined.
Node Inspection: btn_start
| Property | Value |
|---|---|
| Name | btn_start |
| Class | Button |
| Custom Class | None |
| Position | (640.0, 120.0) |
| Size | (220.0, 80.0) |
| Normal State | ui/atlas_login.plist -> btn_green_n.png |
| Pressed State | ui/atlas_login.plist -> btn_green_p.png |
| Touch Enabled | True |
| Z-Order | 5 |
{
"classname": "Button",
"customClassName": "",
"options": {
"name": "btn_start",
"position": { "x": 640.0, "y": 120.0 },
"size": { "width": 220.0, "height": 80.0 },
"normalData": {
"path": "btn_green_n.png",
"plistFile": "ui/atlas_login.plist",
"resourceType": 1
},
"text": "START GAME",
"fontSize": 32,
"capInsets": { "x": 0, "y": 0, "w": 0, "h": 0 },
"scale9Enabled": false
}
}
Next steps
- Update your Lua controller to use
root:getChildByName("btn_start")if you haven't already. - Verify that
ui/atlas_login.plistis preloaded in your scene. - If the button alignment looks off, check the
anchorPointproperty in the full JSON output.
Subscription · always the latest version
- Secure checkout via Stripe
- Cancel anytime
- Delivered live via MCP
About this skill
Debugging Cocos Studio interface files is painful when you cannot see the underlying data structure. This skill provides a deep inspector for .csb binary files, allowing you to audit node trees, properties, and resources without opening the editor.
What it does
- Structure visualization of the full node hierarchy including positions, sizes, and visibility states.
- Property extraction for generic widgets and specific controls like Buttons, Text, ImageViews, and ScrollViews.
- Resource auditing to list all referenced images, plists, and fonts used within a specific interface.
- Node searching by name or path to verify Lua code bindings and resolve "node not found" errors.
- Batch processing to scan entire directories for resource usage or property consistency.
How it works
- Run the inspector script against a
.csbfile to output a human-readable node tree. - Use specific flags like
--findor--pathto locate a single node and view its full JSON property block. - Use the
--resourcesflag to generate a list of all asset dependencies for the file. - Export to JSON with
--jsonfor integration into other automated build or audit pipelines.
Frameworks & tools
This tool targets Cocos Studio 2.x binary files (FlatBuffers format). The core logic is written in Python 3 with no external dependencies, utilizing a custom schema for parsing binary headers.
Why this beats prompting it yourself
Parsing binary FlatBuffers manually via prompt is prone to offset errors and incorrect field mappings. This skill uses a pre-defined schema that correctly identifies nested widgetOptions and nodeOptions which vary by control type.
Use cases
- Validate that a UI node name matches the string used in Lua or C++ controllers.
- Check if a UI layout is using individual images instead of optimized sprite sheets.
- Debug layout issues by inspecting absolute positions and anchor points of hidden containers.
- Generate asset manifests for specific views to optimize loading sequences.
Known limitations
Does not support full animation timeline parsing by default. Old CocoLoader (1.x) formats return raw JSON instead of mapped properties. Schema modifications require strict field ordering.
Animation timelines are experimental. Cocos Studio 1.x files return generic nodes only. Binary schema is sensitive to field order.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Free forever
No account required to browse
Trust & safety
Security scan
Security scan passed 15 days ago