メニュー
Verify claims against primary sources before writing code or docs. Read the actual API, run the actual command, check the actual docs. Do not guess. Do not assume. Do not ship until verified.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/Kevin-Liu-01/Agent-Machines --skill rtfmコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？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 | rtfm |
| description | Verify claims against primary sources before writing code or docs. Read the actual API, run the actual command, check the actual docs. Do not guess. Do not assume. Do not ship until verified. |
When you think you know how an API, tool, or system works, you are wrong until you have verified it against the source. This skill exists because workarounds for nonexistent limitations are worse than the problems they claim to solve.
Every time you:
The actual code, API docs, or type signature. Not a summary. Not a blog post. Not your memory.
| Claim type | Where to look |
|---|---|
| "crate X doesn't support Y" | docs.rs/X, GitHub source, Cargo.toml features |
| "API doesn't accept parameter Z" | OpenAPI spec, SDK type definition, --help |
| "kernel doesn't support mode M" | kernel.org/doc/html/, Documentation/ tree |
| "service doesn't offer feature F" | official product docs, changelog, pricing page |
| "protocol doesn't allow operation O" | RFC, spec PDF, reference implementation |
Official examples, changelogs, migration guides.
Community evidence that people are doing the thing you think is impossible.
If the claim is about runtime behavior, write a minimal test. Five lines. Compile it. Run it. See what happens. Do not theorize about what the compiler, runtime, or service will do. Ask it.
After steps 1-4, you may say "X doesn't support Y." Not before.
If you skipped any step, go back. The five minutes you spend reading docs saves the five hours you spend building and debugging a workaround for a limitation that does not exist.
If you have not read the docs, you have not earned the right to say it cannot be done. Read first. Decide second. Code third.
