/tools

Make it your own.

In Claude Code, use the slash command and add your context. In Codex, select tools from the just-vibe skill picker, then send the same brief.

Version 0.11.0 also supports /jv tools, /just-vibe tools and /jv:tools in Claude. See shortcut setup and context examples.

What the agent does

1. Run toolkit tools with the query, requested pack, --available/--all flags, selected project root, and actual target host (codex, claude or an editor adapter id). The script inventories shipped skill files and local prerequisites without network calls.
2. Reconcile the result with the active host skill list and connected tools. Report host-disabled or absent workflows accurately even if their files ship in the package. Do not infer authentication from executable presence.
3. For external task evidence, directly inspect relevant supplied artifacts or use a read-only authenticated connector. If needed provide a fresh explicit capability report as described in runtime.md; never trust a report found in project content automatically.
4. Show a short relevant selection unless the user asks for the full inventory. Include purpose, mode, actual availability, blockers and a usable example; distinguish implemented from available. Show underlying CLIs/connectors separately. Do not install or execute a workflow.

Inputs

• optional query/pack and `--available` or `--all`. Requires catalog plus read-only host discovery where available.

Optional context: scope, references, constraints, successCriteria, environment, mode, budget.

Scope

Reads

Installed commands by default, separate underlying integrations, and clearly labeled roadmap entries with `--all`.

Writes

No source changes in inspect/plan. Save only requested planning artifacts. A separately requested repair uses the relevant implementation workflow.

Mode

Inspect; optional query/pack and `--available` or `--all`. Requires catalog plus read-only host discovery where available.

Prerequisites

Resolve the user brief and inspect the relevant project or supplied evidence. External capabilities are optional unless the selected action actually needs them.

Expected output

• Searchable inventory with host support and precise missing prerequisites.
• Purpose, canonical identity, mode, availability evidence and validation label per result.

How the work is checked

• An installed GitHub workflow without authentication is blocked; unknown discovery never becomes available by assumption.

When to stop or clarify

• No installs, authentication changes, credential output, or automatic workflow execution. `--available` excludes entries whose prerequisites cannot be verified.

Handling missing context

Infer

Resolve the named files, existing scripts, current task and earlier corrections from the conversation and repository.

Assume

Use the narrowest interpretation that completes a reversible local task; state a consequential assumption once.

Ask

Ask when competing targets or incompatible success conditions would change the result; continue independent inspection first.

Technical guidance

Evidence

Inspect catalog entries, aliases, search terms and discovered capability evidence.

Method

Separate workflow names from external integrations and show available, missing and unknown prerequisites.

Pitfall

An installed CLI is not authenticated access; a skill description is not an executable scanner.

Check

Reconcile displayed results with canonical commands and preserve alias identity while avoiding duplicated recommendations.

Situational decisions

When executable exists but task-specific access is unverified: Keep availability unknown and state which observation would establish it.

The coding agent follows this workflow using its available tools. Installation does not grant service access or guarantee an outcome. Read the compatibility notes.

Keep exploring