build-afm Skill
description: Build AFM from scratch, including submodules, patches, WebUI assets, and the Swift package build.
Want an agent-native computer in the browser? Try HappyCapy.
Cloud sandbox for AI agents · No setup · Run autonomous workflows from your browser
Affiliate link — we may earn a commission at no extra cost to you.
Why use this skill
build-afm is most useful when you want an agent workflow that is more structured than an ad-hoc prompt. Instead of restating the same expectations every time, a dedicated SKILL.md file gives the assistant a repeatable brief. In this case, the core value is clarity: the repo already frames the workflow around frontend skills tasks, and the skill source gives you a portable starting point you can evaluate, adapt, and reuse. The inferred platform for this skill is OpenClaw Skills, which helps you judge whether it is likely to feel native in your current agent ecosystem or whether it is better treated as a general reference.
That matters because AI assistants are better when the operating context is explicit. A good skill turns hidden team expectations into visible instructions. It can name preferred tools, describe failure modes, define what “done” looks like, and reduce the amount of corrective prompting you need after the first draft. For developers exploring the wider SKILL.md ecosystem, this page helps answer the practical question: is this skill specific and maintained enough to be worth trying?
How to evaluate and use it
Start with the source repo and the preview below. The preview tells you whether the instructions are actionable or just aspirational. Strong skills usually describe triggers, recommended tools, steps, and known pitfalls. Weak skills tend to stay generic. This one lives in scouzi1966/maclocal-api, which gives you a concrete repo context, update history, and direct ownership trail.
Once you confirm the scope looks right, test it on a small task before making it part of a larger workflow. If it improves consistency, keep it. If it is too broad, outdated, or conflicts with your own process, treat it as a reference rather than a drop-in rule. That is the healthiest way to use directory-discovered skills: not as magic plugins, but as reusable operational knowledge that still deserves judgment.
SKILL.md preview
Previewing the source is one of the fastest ways to judge whether a skill is truly useful. This snippet comes from the public file in the linked repository.
--- name: build-afm description: Build AFM from scratch, including submodules, patches, WebUI assets, and the Swift package build. user_invocable: true --- # Build AFM Use this skill when the user wants a fresh AFM build or a clean rebuild from the current checkout. ## Usage - `/build-afm` - `/build-afm debug` - `/build-afm release` ## Workflow ### 1. Validate prerequisites Check the local environment before building: ```bash uname -m sw_vers -productVersion brew --version xcode-select -p swift --version git --version node --version npm --version ``` Expected baseline: - Apple Silicon (`arm64`) - macOS version compatible with `Package.swift` - full Xcode selected, not standalone Command Line Tools - Swift toolchain compatible with the package manifest - Node.js and npm available for the vendored WebUI build If prerequisites are missing, stop and tell the user exactly what failed. ### 2. Run the build Default to release unless the user explicitly asks for debug. ```bash ./Scripts/build-from-scratch.sh ./Scripts/build-from-scratch.sh --debug ``` Do not add skip flags. This workflow is for full builds. ### 3. Report the result After a successful build, report: - build configuration - full path to the `afm` binary - version output from `afm --version` ### 4. Failure hints If the build fails, check: - Xcode selection and license acceptance - Node.js/npm availability - submodule initialization - patch application failures