AsmdefSAFE
AI automation skills specifically designed for Unity
Overview
AI automation skills specifically designed for Unity
7635012e8e68OBSERVED · 2026-10-10What it tells the agent
The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.
--- name: unity-asmdef description: Advise on Unity assembly definitions (asmdef) --- > **Before calling any skill in this module:** if you are about to call a skill with parameters guessed from its name or description, STOP — read this file (or fetch its schema via `GET /skills/recommend?includeSchema=true`) first. If you already have the parameter definitions from recommend/schema, you may proceed straight to dryRun. ## Triggers - Planning asmdef layout - Untangling assembly dependencies - Speeding up compilation - Splitting editor/runtime/test code - 规划 asmdef 结构、理顺程序集依赖、加速编译、拆分编辑器/运行时代码 # Unity asmdef Advisor Use this skill when the project is large enough that compile boundaries and dependency direction matter. ## Recommend Only When Worth It `asmdef` is usually worth discussing when: - the project has multiple domains/systems - editor code and runtime code are mixed - compile times are becoming noticeable - tests should be isolated cleanly ## Output Format - Whether `asmdef` is justified now - Proposed assemblies - Allowed dependency direction - Editor/runtime/test split - Migration steps - Risks or churn to avoid ## Default Guidance - Prefer a few meaningful assemblies over many tiny ones. - Split editor code from runtime first. - Keep the dependency graph directional and shallow. ## Guardrails > **Mode**: Documentation only — no REST skills to gate; load freely under any operating mode (Approval / Auto / Bypass). - Do not introduce `asmdef` fragmentation for a tiny prototype. - Do not create circular dependencies or force everything through a shared dumping-ground assembly.
Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | NA |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- none-observed
- Shell
- none-observed
- Dependencies
- pinned
- Secrets in source
- none-found
Findings (0)
No findings outside the package's declared scope.
Gates applied: no_behavioural_pass.
7635012e8e68full audit observations/trust-audit/skill/besty0728__asmdef.json · Report an issue / request a re-scanAudit history
Every audit this skill has had.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-10 | 7635012e8e68 | SAFE | B | 89 | first audit |
Questions
What does the Asmdef skill do?
AI automation skills specifically designed for Unity
Is Asmdef safe to install?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean skill reads B.
What can Asmdef access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
How current is this page?
The grade is for one exact copy of the source (7635012e8e68), read on 2026-10-10. The repository is watched, and a new audit runs when it changes — this is the first audit.