You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
π Skills from any public GitHub repository. In Tools β Skills, paste the address of a repository, one of its folders, or a SKILL.md kept in the open Agent Skills format (Unity's official skills, the lists the community maintains, a repository of your own) and press See what it holds. Nothing is installed yet: the panel lists every skill the address holds with its description, folder, files and size, and what each one carries β source code (installed as read-only text, never run), scripts, a terminal expected, a name you already have, or why it cannot be installed β plus the repository's license, or that none is declared. View opens a skill in full before you decide: origin (repository, branch, commit, folder), license, the safety scan, the files left out and why, and each file as text. Pick the ones you want and install them at once; a name taken by a skill from elsewhere is replaced only after you confirm.
π Skills from GitHub remember where they came from and can be updated. Opening the Skills view asks GitHub, once per repository, whether the folder moved on; when it has, the row says so, and Update reinstalls it from the same place after the safety scan runs again. HydraOps redistributes nothing: each skill comes from its author's repository, under the license the repository and the skill declare.
π€ Reading a repository is thrifty with GitHub's limit (60 API requests an hour per computer without a token): a preview spends three, and viewing or installing what was just previewed spends none, because the answers are kept for a few minutes.
π¦ Two dependencies are raised past reported vulnerabilities: hono (reached through the MCP SDK; HydraOps serves nothing through its static handler) and http-cache-semantics (build tooling only, never shipped with the app).