Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    csb inspector

    1

    Inspect and audit Cocos Studio .csb binary files to extract node trees, properties, and asset dependencies.

    $5

    /mo

    Subscription · cancel anytime

    Secure checkout via Stripe

    • Always the latest version
    • Delivered live to your agent via MCP
    • Cancel anytime, access ends at period end
    Security scanned
    csb inspector

    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

    PropertyValue
    Namebtn_start
    ClassButton
    Custom ClassNone
    Position(640.0, 120.0)
    Size(220.0, 80.0)
    Normal Stateui/atlas_login.plist -> btn_green_n.png
    Pressed Stateui/atlas_login.plist -> btn_green_p.png
    Touch EnabledTrue
    Z-Order5
    {
      "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

    1. Update your Lua controller to use root:getChildByName("btn_start") if you haven't already.
    2. Verify that ui/atlas_login.plist is preloaded in your scene.
    3. If the button alignment looks off, check the anchorPoint property in the full JSON output.
    $5/mo

    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

    1. Run the inspector script against a .csb file to output a human-readable node tree.
    2. Use specific flags like --find or --path to locate a single node and view its full JSON property block.
    3. Use the --resources flag to generate a list of all asset dependencies for the file.
    4. Export to JSON with --json for 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. 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. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 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

    Permissions

    Terminal / Shell
    Read Files
    Write Files
    Listed15 days ago

    What's inside

    Frequently Asked Questions

    This skill decodes the binary FlatBuffer format used by Cocos Studio, providing a human-readable map of node hierarchies, properties, and asset dependencies that are otherwise inaccessible without the original editor files.

    It is compatible with any AI agent or environment capable of running Python 3 scripts, making it easy to integrate into LLM-driven development workflows or automated CI/CD pipelines.

    Yes, the inspector can extract a complete list of all images, .plist files, and fonts referenced in a .csb, which is essential for identifying missing assets or unoptimized textures.

    The purchase includes the core Python-based inspector script, the custom parsing schema for Cocos Studio binary headers, and documentation for CLI usage and JSON export.

    While it primarily targets Cocos Studio 2.x FlatBuffers, it can return raw data for older 1.x CocoLoader formats; however, it does not currently support full animation timeline playback or keyframe interpolation.

    No external libraries are required; the skill is built with vanilla Python 3 to ensure maximum portability across different operating systems and developer environments.

    New in APIs & Backend