Uses a tool from inventory on a target object or location to perform a specific environmental interaction, such as digging, cutting, or measuring. Use this skill when a task requires modifying the environment or manipulating materials with a tool (e.g., using a shovel to dig soil, a thermometer to measure temperature, or an axe to cut wood). Takes the tool and target as inputs and outputs the result of the interaction.
Scanned 5/28/2026
Install via CLI
openskills install zjunlp/SkillNet---
name: scienceworld-tool-user
description: Uses a tool from inventory on a target object or location to perform a specific environmental interaction, such as digging, cutting, or measuring. Use this skill when a task requires modifying the environment or manipulating materials with a tool (e.g., using a shovel to dig soil, a thermometer to measure temperature, or an axe to cut wood). Takes the tool and target as inputs and outputs the result of the interaction.
---
# Skill: Tool User
## Purpose
Perform a physical action on the environment using a tool from your inventory. The core action is `use TOOL on TARGET`.
## When to Use
- A task requires modifying the environment (digging, cutting, heating).
- You need to measure a property of an object (temperature, conductivity).
- A tool-based interaction is the next step in your experiment workflow.
## Core Workflow
1. **Ensure Tool in Inventory:** The required tool (e.g., `shovel`, `thermometer`, `axe`) must be in your inventory. Use `pick up OBJ` if it is not.
2. **Identify Target:** Determine the exact target object or location name (e.g., `ground`, `tree`, `metal fork`).
3. **Execute:** `use TOOL on TARGET`.
4. **Interpret Result:** Read the observation output to determine the outcome (e.g., temperature reading, state change).
## Key Actions
| Action | Purpose |
|--------|---------|
| `pick up OBJ` | Acquire tool if not in inventory |
| `use OBJ on OBJ` | Perform tool interaction |
| `look around` | Confirm target identity and location |
## Example
**Task:** Measure the temperature of a metal fork using a thermometer.
1. `pick up thermometer` — ensure tool is in inventory
2. `use thermometer on metal fork`
3. Observation: "a thermometer, currently reading a temperature of 72 degrees celsius"
## Important Notes
* The tool must be in your inventory before use. The `pick up` action is a prerequisite.
* Use exact object names as they appear in the environment description.
* Some tools produce measurable outputs (thermometer readings); others produce state changes (shovel digs soil). Interpret accordingly.
No comments yet. Be the first to comment!
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
Use when a repo needs CodeGraph plus ast-grep for Codex MCP setup, exploration, impact analysis, structural search, or safe refactor planning.