Godot Engine 3d Developer
PassAudited by ClawScan on May 1, 2026.
Overview
This instruction-only Godot skill is coherent for game-development workflows, but it can create or update project records and enqueue builds through Tasking.tech, so users should be comfortable with those project changes.
This looks safe for its stated purpose as an instruction-only Godot development workflow. Before installing, make sure you trust the Tasking.tech workspace and workers, and that the agent should be allowed to create or update project tasks and start builds for the relevant game project.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
The agent may create or change project tasks and trigger builds when using the skill.
The skill documents tool-like workflows that can mutate project-management records and start build jobs. This is aligned with the game-development purpose, but users should notice the actions are not read-only.
Creates a task in the project management system. ... Applies partial updates. ... Enqueues a build job.
Install only in workspaces where the agent is allowed to make project-management updates and start build jobs; review requested task/build parameters before approving important changes.
The agent's actions may use whatever Tasking.tech or project permissions are available to it.
The workflows assume access to project/workspace resources and user handles. No credentials are declared, and this is expected for a project-management skill, but the effective permissions come from the runtime or platform account.
`project_id` (string, required) ... `assignee` (string, optional) – User id or handle. ... `task_id` (string, required).
Use least-privilege project access and avoid granting the agent broader workspace permissions than needed for the specific Godot project.
Build or test instructions, branch names, repo paths, and status results may be handled by external backend/worker infrastructure.
The skill describes a backend-to-worker job flow. This is expected for CI/build automation, but it means project job details may pass through Tasking.tech and worker systems.
The agent never accesses machines directly. It calls skills backend enqueues jobs workers execute and report back.
Confirm that Tasking.tech and any configured workers are trusted for the project data and branches the agent will reference.