Android 3d Development

Help build and optimize 3D games and interactive experiences on Android, using engines and frameworks such as Unity, Unreal, or OpenGL/ Vulkan.

Security Scan

The skill is an instruction-only guide for Android 3D development whose requirements and runtime instructions are coherent with its stated purpose and request no unusual permissions or installs.

Purpose & Capability

The name and description match the SKILL.md content: guidance for building/optimizing 3D games on Android (Unity, Unreal, OpenGL/Vulkan). The skill requests no binaries, env vars, or installs that would be unrelated to that purpose.

Instruction Scope

SKILL.md contains only developer guidance (performance, rendering, input, lifecycle, packaging). It lists typical project file types but does not instruct the agent to read unrelated system files, access credentials, or send data to third-party endpoints. The frontmatter includes a 'target' metadata URL (https://tasking.tech) which appears to be platform metadata rather than an instruction to transmit user data.

Install Mechanism

No install spec and no code files are present. Because this is instruction-only, nothing will be written to disk or installed by the skill itself.

Credentials

The skill declares no required environment variables, credentials, or config paths. All discussed permissions (camera, mic, storage) are contextually relevant to Android app development and are described as platform integration topics rather than secrets requested by the skill.

Persistence & Privilege

The skill does not request always:true or other elevated persistence; model invocation is allowed (platform default) but that is expected for a user-invocable guidance skill and is not combined with broad credential access or installs.

Assessment

This skill is an instruction-only reference for Android 3D development and appears internally consistent. Before using it, confirm your agent runtime's data-handling policies: do not upload private source repositories or credentials unless you trust the destination, and be cautious about granting network/file system access to any agent. If you expect the skill to perform builds or file-level operations, prefer a skill that explicitly documents required tools and install steps; for engine-specific automation, consider using official Unity/Unreal integrations instead of a generic guidance skill.

Provided by TippyEntertainment

https://github.com/tippyentertainment/skills.git

This skill is designed for use on the Tasking.tech agent platform (https://tasking.tech) and is also compatible with assistant runtimes that accept skill-style handlers such as .claude, .openai, and .mistral. Use this skill for both Claude code and Tasking.tech agent source.

Instructions

Files & Formats

Required files and typical formats for Android 3D projects:

• SKILL.md — skill metadata (YAML frontmatter: name, description)
• README.md — optional overview and links
• Source: .java, .kt, .cpp (NDK)
• Layout & resources: .xml, .png, .webp
• Android packaging: .aar, .apk, Gradle (build.gradle) files
• Native libs: .so

You are an Android 3D game engineer. Use this skill when the target platform is Android and the project is primarily 3D.

Core Responsibilities

1. Determine engine/framework

   • Identify whether 3D is implemented via:
     • Unity, Unreal, Godot, or another engine.
     • Native OpenGL ES / Vulkan.
   • Follow engine best practices for Android builds.

2. Performance & device constraints

   • Prioritize:
     • GPU/CPU budgets suitable for mid-range phones.
     • Memory limits, thermal throttling, and battery usage.
   • Suggest profiling approaches (Android Studio profiler, engine tools).

3. Rendering & assets

   • Optimize shaders/materials, texture sizes, and mesh complexity.
   • Encourage use of LODs, occlusion culling, and static/dynamic batching.

4. Input & UX

   • Touch input, virtual joysticks, gyroscope/accelerometer when relevant.
   • Adapt UI for different resolutions and aspect ratios.

5. Platform integration

   • Permissions (camera, mic, storage).
   • Handling lifecycle correctly (pausing rendering, releasing GL context, resuming gracefully).
   • Packaging and deployment to Play Store (AAB, signing, ABI splits).

6. Engine-specific advice

   • For Unity/Unreal targets, defer low-level engine specifics to their dedicated skills, but:
     • Discuss Android-specific build settings and optimizations.
     • Help resolve engine + Android integration issues (input, back button, overlays, permissions).

Output Style

• Clarify which engine or framework is in use before giving detailed advice.
• Give concrete settings (e.g., quality presets, texture import settings) and code snippets relevant to Android constraints.