菜单
Minimal-fix coding philosophy. Use when writing or reviewing any code change -- favors deletions, hard line/file/PR limits, and elegance over cleverness.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/Kevin-Liu-01/Agent-Machines --skill agent-ethos命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
How Agent Machines work -- providers (Dedalus, E2B, Sprites), agent runtimes (Hermes, OpenClaw, Claude Code, Codex), MCP catalog, bootstrap, and closed-loop verification. Use when asked about the runtime, scaling, sleep/wake, destroy, or inspecting this environment.
Build landing page sections, hero blocks, and marketing surfaces in the Reticle/Sigil engineering-instrument-grid aesthetic. Use when creating new landing sections, hero components, marketing pages, or when the user says "reticle", "hero", "landing page", "new section", "instrument panel", "grid cell", or wants to match the existing Agent Machines visual language.
Declarative web framework for building browser-based 3D, VR, and AR experiences using HTML and entity-component architecture. Use this skill when creating WebXR applications, VR experiences, AR experiences, 360-degree media viewers, or immersive web content with minimal JavaScript. Triggers on tasks involving A-Frame, WebXR, VR development, AR development, entity-component-system, declarative 3D, or HTML-based 3D scenes. Built on Three.js with accessible HTML-first approach.
基于 SOC 职业分类
正在显示 SKILL.md
| name | agent-ethos |
| description | Minimal-fix coding philosophy. Use when writing or reviewing any code change -- favors deletions, hard line/file/PR limits, and elegance over cleverness. |
| version | 1.0.0 |
| author | Kevin Liu |
| license | MIT |
| metadata | {"agent-machines":{"tags":["philosophy","code-quality","minimalism","hard-limits"],"related_skills":["empirical-verification","plan-mode-review"]}} |
You are a surgeon, not a painter. Your job is the minimal, correct intervention.
Fewer lines, not more. No speculative code: do not add abstractions, helpers, or flexibility for hypothetical future use. Build what is needed now.
Match the surrounding style. Read the file before editing it. If the file uses factories, use factories. If it avoids them, avoid them.
| Limit | Value |
|---|---|
| Function length | 70 lines |
| File length | 500 lines (excluding tests) |
| Nesting depth | 3 levels |
| Argument count | 5 |
| PR size | 200 changed LOC |
If a function name contains "and", split it.
Elegant is not clever. Can you debug this at 3 AM with a breakpoint on each logical step? Can a new engineer understand it without asking anyone? Does removing any part break something? Is every branch an explicit, named case?
If the reader says "obviously correct," you have achieved it.
Every deletion is a net positive unless it removes something needed. Writing more code to fix a bug may hide the bug further. The fix that deletes lines is almost always the right one.
