一键导入
just
Use this skill when working with just command runner, Justfiles, or build recipes. Helps list, run, create, modify, and debug just recipes and Justfile syntax.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Use this skill when working with just command runner, Justfiles, or build recipes. Helps list, run, create, modify, and debug just recipes and Justfile syntax.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Manage the full WebAssembly component lifecycle with the `component` CLI tool — init projects, install dependencies, build, run, compose, publish, pull, search, and inspect components against OCI registries (GHCR, Docker Hub, ACR) and meta-registries. Covers the WebAssembly Component Model and WASI Preview 2.
Build a single WebAssembly component in multiple languages (Rust, Python, JavaScript, Go) from a single prompt. Generates parallel implementations with language-suffixed directories so you can compare output, size, and behavior across toolchains. Defaults match wasm-build — Rust + Python on WASI 0.3 RC, JavaScript + Go on WASI 0.2.
Build WebAssembly components from Rust, Python, JavaScript/TypeScript, or Go using the Component Model. Defaults to WASI 0.3 (RC) for Rust and Python (native async / stream / future), and WASI 0.2 for JavaScript and Go (whose toolchains don't yet ship a p3 path). Covers scaffolding, language-specific toolchain setup (wit-bindgen, componentize-py, jco / componentize-js, tinygo), compilation, WIT binding generation, validation, and size/startup optimization.
Upstream Bytecode Alliance utilities for WebAssembly — `wkg` (OCI push/pull with full annotation control, WIT-package authoring via `wkg wit fetch/build/publish`, GHCR/Docker auth) and `wasm-tools` (validate, inspect, embed, extract, compose, print, dump, metadata). Includes a curated catalog of useful pre-built components for discovery.
Run, debug, and profile WebAssembly components and core modules with the `wasmtime` runtime. Covers `run`, HTTP `serve`, `--invoke` with WAVE syntax for direct export calls, AOT `compile` to .cwasm, `wizer` snapshotting, and the inspection commands `objdump` / `explore` / `settings`. Supports WASIp2 and WASIp3.
Use this skill when running untrusted code in hardware-isolated sandboxes, registering host tools for guest code, working with Hyperlight micro-VMs, or using the hyperlight-sandbox Python SDK. Covers sandbox creation, code execution, tool dispatch, file I/O, network allowlisting, and snapshot/restore.
| name | just |
| description | Use this skill when working with just command runner, Justfiles, or build recipes. Helps list, run, create, modify, and debug just recipes and Justfile syntax. |
| allowed-tools | Bash, Read, Write, Edit, Glob, Grep |
You are a specialized assistant for working with just command runner and Justfiles.
just is a command runner similar to make but simpler and more focused. It uses Justfiles to define recipes (commands) that can be executed.
When this skill is invoked, you should help users:
just --list or just -l to show all available recipes in the Justfilejust --show RECIPE to display the contents of a specific recipejust RECIPE_NAME [ARGS]just --list - List all recipesjust --summary - List recipes in a single linejust --show RECIPE - Show a recipe's contentsjust RECIPE - Run a recipejust --evaluate VARIABLE - Evaluate a variablejust --variables - List all variablesjust --choose - Interactively choose a recipe to runjust --dump - Print entire JustfileRecipes are defined like:
recipe-name arg1 arg2:
command to run
another command
Variables:
variable := "value"
IMPORTANT: Before running any just commands, you must determine which binary to use:
scripts/just exists in this skill's directory (.agents/skills/just/scripts/just)just binaryExample setup:
# Determine which just binary to use
SKILL_DIR=".agents/skills/just"
if [ -x "$SKILL_DIR/scripts/just" ]; then
JUST="$SKILL_DIR/scripts/just"
else
JUST="just"
fi
# Then use $JUST for all commands
$JUST --list
You should set up this binary detection at the start of your workflow and use the determined path consistently.
scripts/just binary first, fall back to system binaryjust --list (with the correct binary) to understand available recipessh -cu by default@ prefix to suppress echoing a command- prefix to ignore command failuresrecipe: dependency1 dependency2When invoked, start by checking for a Justfile and listing available recipes unless the user asks for something specific.