output/luckperms/SKILL.md
LuckPerms - Minecraft permission plugin for managing permissions, groups, and user access
npx skillsauth add Kling0012/MCRPG luckpermsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
LuckPerms is a permissions plugin for Minecraft servers. It allows server admins to control what features players can use by creating groups and assigning permissions.
This skill should be triggered when:
LuckPerms is:
LuckPerms works on:
net.luckperms:api) - Public, semantically versioned API for plugin integrationgit clone https://github.com/LuckPerms/LuckPerms.git
cd LuckPerms/
./gradlew build
Output jars are in loader/build/libs or build/libs.
<dependency>
<groupId>net.luckperms</groupId>
<artifactId>api</artifactId>
<version>5.4</version>
<scope>provided</scope>
</dependency>
LuckPerms loosely follows the Google Java Style Guide.
/lp user <player> permission set <permission> - Grant permission to user/lp group <group> permission set <permission> - Grant permission to group/lp user <player> parent add <group> - Add user to group/lp creategroup <group> - Create a new group/lp group <group> parent add <parent> - Set group inheritance/lp sync - Sync data across servers/lp editor - Open web editorThis skill includes comprehensive documentation in references/:
To refresh this skill with updated information:
tools
Skript-reflect addon for Skript - powerful reflection and element manipulation capabilities
tools
PlaceholderAPI - Minecraft plugin expansion system for placeholder text replacement
tools
Use when work should span one or more detached tasks but still behave like one job with a single owner context. TaskFlow is the durable flow substrate under authoring layers like Lobster, ACPX, plugins, or plain code. Keep conditional logic in the caller; use TaskFlow for flow identity, child-task linkage, waiting state, revision-checked mutations, and user-facing emergence.
tools
# Lobster Lobster executes multi-step workflows with approval checkpoints. Use it when: - User wants a repeatable automation (triage, monitor, sync) - Actions need human approval before executing (send, post, delete) - Multiple tool calls should run as one deterministic operation ## When to use Lobster | User intent | Use Lobster? | | ------------------------------------------------------ | --------------------------