New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Uloop Verify Project

by hatayama in hatayama/unity-cli-loop

Check a Unity project's files without starting Unity: missing or orphaned .meta files, invalid or duplicate GUIDs, leftover merge conflict markers, and a broken Packages/manifest.json.

MITAuto-check passedGame Development

Install Uloop Verify Project

skills CLI
$ npx skills add hatayama/unity-cli-loop --skill uloop-verify-project -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install hatayama/unity-cli-loop uloop-verify-project --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/hatayama/unity-cli-loop.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/uloop-verify-project .claude/skills/uloop-verify-project && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
uloop-verify-project
GitHub stars
577
Token cost
~1.5k tokens
SKILL.md length
842 words
Files
1
Skills in repo
11
Repo updated
First seen
Licence
MIT

At a glance

Check a Unity project's files without starting Unity: missing or orphaned .meta files, invalid or duplicate GUIDs, leftover merge conflict markers, and a broken Packages/manifest.json.

  • Tasks that involve Git workflow
  • SKILL.md covers When to use, Usage, Checks and What is checked, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Uloop Verify Project is an agent skill from hatayama/unity-cli-loop. Check a Unity project's files without starting Unity: missing or orphaned .meta files, invalid or duplicate GUIDs, leftover merge conflict markers, and a broken Packages/manifest.json. Use after adding, moving, renaming, deleting, or merging assets, and before committing.

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Game Development, covering Git workflow. The repository describes itself as: Let AI Drive Unity, from Editor to Play Mode. The licence is MIT.

When your agent uses it

  • Tasks that involve Git workflow

Example prompts

  • “/uloop-verify-project”

What it can do on your machine

Read from SKILL.md and the folder at commit b05bd95. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Uloop Verify Project loads about 1.5k tokens when it runs. Until then it costs about 73 tokens; SKILL.md has 842 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~73
When it runs · the whole SKILL.md, loaded when a task matches
~1.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from hatayama/unity-cli-loop at commit b05bd95, republished under its MIT licence (© hatayama). 842 words, ~1,455 tokens.

Download SKILL.mdSave it as .claude/skills/uloop-verify-project/SKILL.md (or your agent's skills folder).
name
uloop-verify-project
description
Check a Unity project's files without starting Unity: missing or orphaned .meta files, invalid or duplicate GUIDs, leftover merge conflict markers, and a broken Packages/manifest.json. Use after adding, moving, renaming, deleting, or merging assets, and before committing.

uloop verify-project

Check the project's files the way Unity reads them on its next import, without starting Unity. When Unity opens a project with these problems, it silently gives assets new GUIDs and deletes orphaned .meta files, which breaks references in ways that cannot be undone. Run this first and fix what it finds while the old GUIDs still exist.

When to use

  • After adding, moving, renaming, copying, or deleting assets, especially from a script or another branch
  • After a merge or rebase that touched Assets/, Packages/, or ProjectSettings/
  • Before committing
  • Before opening the project in Unity

Usage

bash
uloop verify-project
uloop verify-project --project-path <path>

Exit codes:

  • 0: nothing found
  • 1: problems found (the report is still printed on stdout), or the check could not run (an error envelope on stderr and nothing on stdout)

Checks

CheckMeaningHow to fix
CONFLICT_MARKERA merge conflict block (<<<<<<<, =======, >>>>>>>) is left in a fileResolve the conflict and remove the markers; Unity cannot load or compile a file that contains them
MANIFEST_INVALIDPackages/manifest.json is missing, is not a valid JSON object, has a malformed dependencies object, or has a file: dependency that does not point to a package folderRestore the manifest from version control, or fix or remove the dependency the message names
GUID_DUPLICATETwo or more .meta files declare the same GUIDKeep the .meta file of the original asset and delete the copies' .meta files so Unity assigns them new GUIDs
GUID_INVALIDA .meta file has no valid guid: line (32 hexadecimal characters, not all zero)Restore the .meta file from version control; otherwise Unity assigns a new GUID, which breaks references to the asset
META_MISSINGAn asset has no .meta file next to itBring its .meta file along from the branch or folder it came from; if you just created the asset, let Unity import it (for example with uloop compile) and commit the generated .meta file
META_ORPHANA .meta file has no matching assetIf the asset was moved or renamed, move the .meta file with it to keep the GUID; if the asset was deleted, delete the .meta file too

What is checked

  • .meta files under Assets/, under every embedded package (a folder directly under Packages/ with a package.json file), and under every local package the manifest lists as file: (a relative path is resolved from Packages/). A folder inside another of these is checked once.
  • Names Unity hides are skipped and need no .meta file: names starting with ., names ending with ~, cvs in any case, and files with a .tmp extension in any case.
  • Plugin folders ending in .bundle, .framework, .xcframework, .plugin, or .androidlib (any case) need their own .meta file, but nothing inside them is checked: Unity imports such a folder as one plugin, so the files inside are not checked whether they have .meta files or not.
  • Symbolic links need a .meta file but are never followed.
  • A .meta file pairs with its asset by exact name, letter case included, so the result is the same on every OS. An orphaned .meta file is not checked further, because Unity deletes it.
  • Conflict markers are searched in every file of those folders (.meta files included), every file under ProjectSettings/, and Packages/manifest.json and Packages/packages-lock.json. Only the first block of each file is reported. A file with a NUL byte in its first 8000 bytes is treated as binary and skipped.
Show full SKILL.md (284 more words)Show less

Output

JSON on stdout:

  • Success: true when nothing was found
  • ProjectRoot: the checked project
  • FindingCount: every problem found, including those left out of Findings
  • CountsByCheck: the count for each of the six checks, always all six
  • Findings: each with Check, Path, and Message, plus Line for CONFLICT_MARKER and GUID and RelatedPaths for GUID_DUPLICATE. Path is /-separated and relative to the project, or absolute for a local package outside it. Sorted in the order of the table above, then by path. At most 100 findings of each check are listed.
  • Truncated: true when a check had more than 100 findings
  • ScannedRoots: the folders whose .meta files were checked
  • MetaFileCount: how many .meta files were checked
  • Message: one-line summary

Notes

  • A file you just created has no .meta file until Unity imports it. Run uloop compile first, or treat META_MISSING on brand-new files as expected.
  • After a fresh clone, an empty folder that git does not track leaves its folder .meta file as META_ORPHAN. Delete that .meta file, or add a file to the folder so git tracks it.
  • Run it while Unity is idle. Files Unity is writing at that moment can be reported, and a file Unity deletes during the check makes the command fail; run it again once Unity is idle.
  • Not checked: GUID collisions with packages in Library/PackageCache, folders hidden only by the Windows hidden attribute (they are reported as META_MISSING), and package folders under Packages/ that are symbolic links.
  • It only reads files and works whether Unity is open or closed.
  • If uloop answers that verify-project is an unknown command, or that it "is handled by the global uloop dispatcher", the installed uloop is older than this command: run uloop update.

© hatayama, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/uloop-verify-project of hatayama/unity-cli-loop.

Open the folder on GitHubat commit b05bd95

Compare with similar skills

Uloop Verify Project next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Uloop Verify Project compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Uloop Verify Project this skillhatayama/unity-cli-loop577—~1.5kAutomated safety check: PassMIT
Godot Project Foundationsthedivergentai/GD-Agentic-Skills816—~3.1kAutomated safety check: PassLGPL-3.0
Emergency Hotfix WorkflowDonchitos/Claude-Code-Game-Studios26k—~2.9kAutomated safety check: NotesMIT
Player-Facing Patch NotesDonchitos/Claude-Code-Game-Studios26k—~2.5kAutomated safety check: NotesMIT
Finishing a Development Branchobra/superpowers297k5 repos~1.9kAutomated safety check: PassMIT
Code Design Rationale Investigatorcursor/plugins10k9 repos~2.6kAutomated safety check: PassNone

Similar skills

  • Godot Project Foundations

    thedivergentai/GD-Agentic-Skills

    Expert blueprint for Godot 4 project organization (feature-based folders, naming conventions, version control).

    816 GitHub stars~3.1k tokensUpdated 1 mo ago
    Game DevelopmentAuto-check passed

  • Emergency Hotfix Workflow

    Donchitos/Claude-Code-Game-Studios

    Runs an emergency fix process for severe bugs: a severity check, a written hotfix record, and a branch cut from the shipped release rather than main.

    26k GitHub stars~2.9k tokensUpdated yesterday
    DevelopmentAuto-check: notes

  • Player-Facing Patch Notes

    Donchitos/Claude-Code-Game-Studios

    Writes player-facing patch notes from git history and changelogs, filtering out framework and maintenance commits and rewriting developer wording for players.

    26k GitHub stars~2.5k tokensUpdated yesterday
    DevelopmentAuto-check: notes

  • Finishing a Development Branch

    obra/superpowers

    Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    297k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed

  • Code Design Rationale Investigator

    cursor/plugins

    Official

    Digs into why code is shaped the way it is by checking git history, pull requests and connected tools in parallel, then reporting a cited read on the tradeoffs.

    10k GitHub starsUsed in 9 repos~2.6k tokens
    DevelopmentAuto-check passed

  • Git Guardrails Claude Code

    fossasia/eventyay-interpretation

    Set up Claude Code hooks to block dangerous git commands (push, reset --hard, clean, branch -D, etc.) before they execute.

    1.6k GitHub starsUsed in 12 repos~578 tokens
    AI & LLM EngineeringAuto-check passed

More from hatayama/unity-cli-loop

All 11 skills in this repo

  • Uloop Pause Point

    hatayama/unity-cli-loop

    Breakpoint-like: pause Unity at a source file:line without editing code or recompiling, and get the locals, parameters, and fields there.

    577 GitHub stars~2k tokensUpdated today
    Auto-check passed

  • Uloop Record Video

    hatayama/unity-cli-loop

    Record the Game View or any Editor window (Scene, Inspector, ...) to an .mp4 or .webm video.

    577 GitHub stars~1.7k tokensUpdated today
    Auto-check passed

  • Uloop Hot Reload

    hatayama/unity-cli-loop

    Apply C edits to the running Editor without a compile or domain reload, keeping Play Mode state.

    577 GitHub stars~2k tokensUpdated today
    Auto-check passed

  • V3 CLI Invocation Migration

    hatayama/unity-cli-loop

    Migrate only uloop V2 CLI option syntax in agent skills, Markdown, POSIX shell scripts, and PowerShell scripts to V3 syntax.

    577 GitHub stars~1.2k tokensUpdated today
    Auto-check passed

  • Uloop Get Project Info

    hatayama/unity-cli-loop

    Get Unity project information via uloop CLI. An agent skill from hatayama/unity-cli-loop.

    577 GitHub stars~228 tokensUpdated today
    Auto-check passed

  • Uloop Hello World

    hatayama/unity-cli-loop

    Sample uloop hello-world tool. An agent skill from hatayama/unity-cli-loop.

    577 GitHub stars~321 tokensUpdated today
    Auto-check passed

Categories

Questions about Uloop Verify Project

What does Uloop Verify Project do?

Check a Unity project's files without starting Unity: missing or orphaned .meta files, invalid or duplicate GUIDs, leftover merge conflict markers, and a broken Packages/manifest.json. Uloop Verify Project is an agent skill from hatayama/unity-cli-loop.json.

When should I use Uloop Verify Project?

Uloop Verify Project fits situations like: tasks that involve Git workflow.

How do I install Uloop Verify Project in Claude Code?

Run `npx skills add hatayama/unity-cli-loop --skill uloop-verify-project -a claude-code`. Or copy the skill folder (.agents/skills/uloop-verify-project in hatayama/unity-cli-loop) into .claude/skills/uloop-verify-project in your project. Claude Code loads it when a task matches its description.

How do I install Uloop Verify Project in Codex?

Run `npx skills add hatayama/unity-cli-loop --skill uloop-verify-project -a codex`. Or copy the skill folder (.agents/skills/uloop-verify-project in hatayama/unity-cli-loop) into .agents/skills/uloop-verify-project in your project. Codex loads it when a task matches its description.

Can I use Uloop Verify Project in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add hatayama/unity-cli-loop --skill uloop-verify-project -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/uloop-verify-project, .gemini/skills/uloop-verify-project, .github/skills/uloop-verify-project and .opencode/skills/uloop-verify-project in your project.

What does Uloop Verify Project need to run?

SKILL.md names no scripts, command-line tools or credentials: Uloop Verify Project is instructions for the agent only.

Does Uloop Verify Project access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Uloop Verify Project safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Uloop Verify Project use?

Uloop Verify Project is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Uloop Verify Project use?

About 1.5k tokens (SKILL.md is roughly 5.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Uloop Verify Project?

Skills that share tags, products or a category with Uloop Verify Project: Godot Project Foundations (thedivergentai/GD-Agentic-Skills, 816 stars), Emergency Hotfix Workflow (Donchitos/Claude-Code-Game-Studios, 26k stars), Player-Facing Patch Notes (Donchitos/Claude-Code-Game-Studios, 26k stars) and Finishing a Development Branch (obra/superpowers, 297k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Uloop Verify Project?

hatayama (a GitHub user) maintains it in hatayama/unity-cli-loop, which has 577 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on October 9, 2026.

Source: hatayama/unity-cli-loop on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.