Skip to content
TrustedSkillsbeta
Back to all skills

Game Tools Workflows

Checked
pluginagentmarketplace·vlatest·productivity

Automates complex game development tasks by creating and executing custom workflows for streamlined asset management & repetitive processes.

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add pluginagentmarketplace/custom-plugin-game-developer --skill game-tools-workflows -a claude-code
  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

pluginagentmarketplace

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned pluginagentmarketplace/custom-plugin-game-developer at aa7edfe267.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Scanned
4 files, 263 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill automates complex game development tasks by creating and executing custom workflows. It streamlines asset management, repetitive processes, and enforces best practices across a wide range of tools commonly used in game development including Unity, Unreal Engine, Godot, Visual Studio, Blender, Maya, Wwise, FMOD, Jira, Notion, Slack, Discord, and more. The skill facilitates consistent Git branching strategies, LFS configuration, commit message formatting, and build automation processes.

When to use it

  • To enforce a standardized Git workflow for game development teams using branches like main, develop, feature/*, fix/*, and release/*.
  • When needing to automate repetitive tasks such as building game projects across different platforms (e.g., Windows, macOS, Linux).
  • For ensuring consistent commit message formatting with prefixes like feat, fix, art, audio, etc.
  • To manage large asset files using Git LFS for common file types like PSD, FBX, WAV, MP3, PNG, TGA and ZIP.

Key capabilities

  • Git Workflow Automation: Enforces branching strategies (main, develop, feature/, fix/, release/*).
  • LFS Configuration: Automates Git LFS configuration for common game asset file types.
  • Commit Convention Enforcement: Ensures commit messages follow a specific format with defined prefixes.
  • Build Automation: Executes build scripts using Unity (and potentially other engines) in batch mode, generating builds with version numbers.

Example prompts

  • "Create a Git branch named 'feature/new-character' for developing a new character."
  • "Run the build script for Windows in release configuration."
  • "Enforce commit message formatting using prefixes like 'feat', 'fix', or 'art'."
  • “Configure Git LFS to track .psd files.”

Tips & gotchas

  • The skill requires familiarity with common game development tools and workflows.
  • Build automation relies on a pre-existing build script, as demonstrated in the provided example using Unity. The path to your Unity installation is required for building.
  • This skill focuses on automating processes within a defined tool stack; it does not provide direct integration with all possible game development software.