用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt;运行前请先检查来源。
npx skills add https://github.com/diegosouzapw/awesome-omni-skill --skill analyze命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地?可下载 SkillsMP 当前能够提供的文件。
Token-efficient tracking for AI orchestration. CLI-first for status updates (~50 tokens), agent fallback for complex ops (~1KB). Use when: updating task status, querying blockers, creating progress files, validating phases.
AshAi extension guidelines for integrating AI capabilities with Ash Framework. Use when implementing vectorization/embeddings, exposing Ash actions as LLM tools, creating prompt-backed actions, or setting up MCP servers. Covers semantic search, LangChain integration, and structured outputs.
This skill should be used when solving hard questions, complex architectural problems, or debugging issues that benefit from GPT-5 Pro or GPT-5.1 thinking models with large file context. Use when standard Claude analysis needs deeper reasoning or extended context windows.
基于 SOC 职业分类
正在显示 SKILL.md
| name | analyze |
| description | Analyze Vela and liFS feature completeness compared to macOS/XNU, producing a completion scorecard |
| disable-model-invocation | true |
Perform a full feature completeness analysis of the Vela OS and liFS filesystem, comparing against macOS (XNU kernel + APFS). No argument is needed — always analyze both:
~/claude/vela/kernel/src/~/claude/lifs/lifs-core/src/Read the relevant source files before producing the report. Do not guess — check the actual code.
For each feature, read the file(s) and classify honestly:
unimplemented!(), or type definitions onlyCompare to: XNU VM subsystem (Mach VM, compressor, UPL, anonymous memory, file-backed mappings)
Compare to: BSD/Mach process model, pthreads, QoS classes
Compare to: XNU scheduler (mach timeshare + realtime + fixed priority)
Compare to: Mach ports, XPC, pipes, Unix domain sockets, signals
Compare to: Mach traps + BSD syscalls + commpage
Compare to: APFS (journaling, copy-on-write, snapshots, encryption, compression, clones)
Compare to: IOKit framework, Apple Silicon / Intel driver support
Compare to: SMEP/SMAP, SIP, Gatekeeper, code signing, Sandbox, TCC, KASLR
Compare to: BSD TCP/IP stack, Network Kernel Extensions, pf firewall
Compare to: IOPMrootDomain, ACPI, sleep/wake, P-states, T-states
Compare to: mach_absolute_time, gettimeofday, timers, commpage clock
Compare to: zsh (macOS default), launchd, dyld
Compare to: DTrace, kdebug, syslog, crash reporter, Instruments
Compare to: XNU SMP bringup, per-CPU data, IPI, CPU hotplug
For each category, print a subsection heading and a table:
| Feature | Status | Notes |
|---|---|---|
| Physical frame allocator | ✅ Complete | Buddy allocator, 13 orders, double-free detection |
| Copy-on-write | 🔧 In Progress | VmaBacking::Cow structure exists, no page fault handler |
After all categories, print:
A table:
| Category | Complete | In Progress | Stub | Missing | Score |
|---|---|---|---|---|---|
| Memory Management | 5 | 2 | 0 | 4 | 45% |
| ... | |||||
| Total | XX% |
Score formula per category: (Complete × 1.0 + InProgress × 0.4 + Stub × 0.1) / Total × 100
Then a single Overall Score: XX% line, weighted by category importance:
End with a Verdict paragraph: what Vela is today (research OS? daily-driver kernel? prototype?) and the top 3 features to complete next for maximum impact.