skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
tabooharmony/roblox-brain1k installs

roblox-tooling

Use when configuring Roblox tooling such as Rojo, Wally, pesde, Selene, StyLua, Lune, Rokit, luau-lsp, or CI/CD.

How do I install this agent skill?

npx skills add https://github.com/tabooharmony/roblox-brain --skill roblox-tooling
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    The roblox-tooling skill provides a comprehensive and security-conscious guide for managing Roblox development environments. It covers essential tools like Rojo, Wally, and Lune while emphasizing best practices such as using CI secret stores for credentials and verifying the provenance of third-party packages. The external sources and community tools mentioned are reputable and standard within the Roblox ecosystem. No malicious patterns or security risks were detected.

  • Socketpass

    No alerts

  • Snykpass

    Risk: LOW · No issues

What does this agent skill do?

roblox tooling

When to Load

Load for filesystem workflows, tool/package pins, linting, sourcemaps, and CI.

Quick Reference

  • Use Rojo when the source of truth should live in files and sync or build into Studio.
  • Use Wally only when the project wants package manifests and a lockfile; keep package scope and server/client placement explicit.
  • Pin tools with the project's existing manager; for a new project lead with Rokit (Aftman is archived, but Rokit reads existing aftman.toml projects).
  • Run Selene and StyLua in check mode in CI. Do not let a formatter rewrite a contributor's branch silently.
  • Use Lune for standalone Luau scripts or test helpers when its standard libraries fit the task.
  • Generate a Rojo sourcemap for editor tooling when the project needs Roblox-aware navigation.
  • CI must check test results and expected counts, not merely exit codes. Separate logic, file/HTTP, and engine suites; see full.md.

Source-of-truth first. Identify Studio vs files before editing; never assume they match. rojo syncback pulls saved-place edits, not live two-way sync; preview with dry-run/list. Follow existing tooling; do not impose optional tools. TestEZ is archived: keep where used, not as a new default. See full.md §§1b–1c.

Need the details? Load references/full.md for setup, file layout, and CI examples.

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/tabooharmony/roblox-brain/roblox-tooling">View roblox-tooling on skillZs</a>