Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    (unofficial) RuneLite plugin developer

    1

    Expert Java 11 development, compliance auditing, and API implementation for RuneLite external plugins.

    Free

    Security scanned
    (unofficial) RuneLite plugin developer

    (unofficial) RuneLite plugin developer

    Example session with this skill installed

    I want a basic plugin that displays the players health around its true tile.

    • Read your context and instructions
    • Compiled the unofficial runelite plugin

    The following is a complete example response illustrating the skill’s output. It describes a proposed implementation; no plugin code or tests have been run.


    I’ve translated your idea into a minimal plugin design: a health indicator drawn around the local player’s true tile, with a small Hitpoints label nearby.

    Deliverable: True Tile Health plugin design

    The tile border acts as a health meter. At full health, the entire border is filled. As health drops, the filled portion shrinks clockwise, leaving a faint background outline so the tile remains visible.

    ElementBehavior
    PositionAnchored to the player’s true tile, following discrete tile movement
    Health borderFilled proportionally to current Hitpoints divided by maximum Hitpoints
    Health labelDisplays current and maximum Hitpoints, such as 72 / 99
    Boosted healthKeeps the border full and displays the actual boosted value, such as 115 / 99
    ColoursGreen above 50%, orange from 26–50%, red at 25% or below
    ConfigurationToggle the label and adjust border thickness and colours
    Unavailable dataHides the indicator when player data or tile projection is unavailable
    Plugin lifecycleRegisters the overlay on enable and removes it on disable

    The implementation should use RuneLite’s player location, skill values, and tile projection APIs, verified against the project’s dependency version. Health calculations belong in a small helper that can be tested independently. Rendering should draw the projected tile border and label without scanning the scene or performing network requests.

    Before coding, I would check existing RuneLite and Plugin Hub implementations for overlap, confirm relevant feature restrictions, and inspect the repository’s Java version and build conventions.

    Next steps

    1. Implement the plugin, overlay, configuration, and health calculation helper.
    2. Test partial health, boosted health, zero health, and invalid maximum values; run the repository’s build checks.
    3. Validate the appearance manually while standing, walking, running, taking damage, healing, hopping worlds, and toggling the plugin.

    Automated checks can verify the calculations. In-game confirmation is still needed to establish that the indicator follows the correct tile and remains readable across camera angles.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Building RuneLite plugins requires navigating strict Java 11 constraints, Jagex compliance rules, and complex game state APIs. This skill manages the end-to-end development lifecycle for Old School RuneScape external plugins, ensuring your code is performant enough for the render loop and compliant enough for the Plugin Hub.

    What it does

    • API implementation handles net.runelite.api game state, events, widgets, item containers, and menu entries.
    • Compliance checking validates features against Jagex third-party client guidelines and RuneLite rejected feature lists.
    • Resource optimization audits render-path efficiency, memory allocations, and network payload sizes for Party data.
    • UI development builds overlays, Swing plugin panels, and widget sprite overrides using standard RuneLite patterns.
    • Hub preparation generates Plugin Hub manifests, estimates PR size buckets, and manages runelite-plugin.properties metadata.

    How it works

    1. Research phase searches RuneLite core and existing Hub plugins for prior art and OSRS Wiki mechanics.
    2. Implementation phase writes Java 11 compatible code, injecting services like ClientThread, Gson, and OkHttpClient.
    3. Verification phase runs Gradle test workflows and performs passive event capture/replay fixture testing.
    4. Preflight phase executes Plugin Hub compliance checks and prepares the 40-character commit hash for submission.

    Frameworks & tools

    Java 11, Gradle, RuneLite API, OSRS Wiki, Lombok, Gson, OkHttpClient, and RuneLite Plugin Hub packager workflows.

    Why this beats prompting it yourself

    Generic AI often suggests modern Java features (records, switch expressions) that break RuneLite's Java 11 environment. This skill is grounded in specific RuneLite architecture patterns, preventing common rejections like manual Gson instantiation or inefficient scene scanning.

    Use cases

    • Adding a new overlay that tracks specific NPC animations or projectile timers.
    • Refactoring a plugin to use event-driven tracking instead of per-tick scene scanning.
    • Debugging ambiguous game interactions using ASCII interaction diagrams and event logs.
    • Preparing a compliant submission for the RuneLite Plugin Hub repository.

    Known limitations

    Does not support Java features introduced after version 11. Cannot automate OSRS gameplay or bypass Jagex account security requirements for the development client.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Game Development.

    Strictly Java 11 only. No support for records, text blocks, or sealed classes. Cannot automate gameplay or interact with the client via browser-based tools.

    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 buying a skill.

    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 to use

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 22 days ago

    • Free with an Agensi account

    Accounts
    GitHub
    Software
    Git

    Permissions

    Terminal / Shell
    Read Files
    Write Files
    Network Access

    Allowed Hosts

    api.github.com
    Listed22 days ago

    What's inside

    Frequently Asked Questions

    This skill ensures your plugin code adheres strictly to Java 11 constraints and Jagex's Third-Party Client guidelines, preventing common Hub rejection reasons like using modern Java features or prohibited automation features.

    The skill is optimized for LLMs with access to Java development environments and can be integrated into any AI agent capable of generating and auditing Gradle-based project structures.

    Yes, the skill can analyze existing codebases to identify performance bottlenecks in the render loop or refactor inefficient per-tick scene scanning into event-driven patterns.

    The skill is updated to reflect the latest RuneLite API changes and Jagex compliance policy shifts, ensuring you don't use deprecated methods or implement newly banned features.

    The skill focuses on UI overlays, game state tracking, and API implementation; it specifically excludes any functionality that bypasses Jagex security or automates gameplay, as these violate RuneLite's core principles.

    New in Game Development

    Free