skills/mojo-tools/SKILL.md
Use when editing Mojo code, .mojo files, fire emoji files, SIMD kernels, Python-Mojo interop, GIL-free parallelism, C FFI, hatch-mojo build hooks, or packaging Mojo extensions.
npx skillsauth add cofin/flow mojo-toolsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
For comprehensive support for modern Mojo syntax, project initialization, and GPU programming, we highly recommend installing the official Modular agent skills:
Installation:
npx skills add modular/skills
The patterns below focus on project integration and build hooks.
The hatch-mojo plugin allows seamless compilation of Mojo source files during the standard Python build process.
Key Configuration (pyproject.toml):
[tool.hatch.build.targets.wheel.hooks.mojo]
# Configuration for mojo compilation
</workflow>
<guardrails>
## Guardrails
owned, borrowed, and inout to manage data flow and avoid unnecessary copies.SIMD for performance-critical logic -- Mojo excels at vectorization; always consider SIMD when processing large arrays.[tool.hatch.build.targets.wheel.hooks.mojo]
dependencies = ["hatch-mojo"]
path = "src/my_extension.mojo"
</example>development
Use when tracing execution paths, mapping dependencies, understanding unfamiliar code, following data flow, investigating end-to-end behavior, debugging call chains, or deciding which files to read next.
development
Use when reviewing authentication, authorization, user input, secrets, API keys, database queries, file uploads, session management, external API calls, OWASP risks, or data handling attack surface.
testing
Use when analyzing tradeoffs, comparing approaches, weighing options, assessing risks, stress-testing conclusions, identifying blind spots, or applying multiple viewpoints to a decision.
development
Use when reviewing hot paths, slow code, database queries, N+1 risks, memory usage, loops, I/O, caching strategy, concurrency, latency-sensitive paths, or resource efficiency.