Uses an appliance to change the state of an object (cooling, heating, or cleaning). Use when the task requires altering an object's temperature or cleanliness using a specific device (e.g., cooling with a fridge, heating with a microwave, cleaning with a sinkbasin). Takes the object, target state, and appliance as inputs and executes the corresponding modifier action.
Scanned 5/28/2026
Install via CLI
openskills install zjunlp/SkillNet---
name: alfworld-object-state-modifier
description: Uses an appliance to change the state of an object (cooling, heating, or cleaning). Use when the task requires altering an object's temperature or cleanliness using a specific device (e.g., cooling with a fridge, heating with a microwave, cleaning with a sinkbasin). Takes the object, target state, and appliance as inputs and executes the corresponding modifier action.
---
# Instructions
Change an object's state (cool, heat, or clean) using a household appliance. You must be holding the target object before executing the state change.
## Workflow
1. **Navigate to appliance:** `go to {appliance}` (e.g., `go to fridge 1`)
2. **Prepare if closed:** If observation says appliance is closed, execute `open {appliance}` -- verify it opens
3. **Execute state change:** `{action} {obj} with {appliance}` -- verify observation confirms the change
4. **Proceed:** Continue with the next task step (e.g., placing the modified object)
## Action Mapping
| State Change | Action | Typical Appliance |
|---|---|---|
| Cool | `cool {obj} with {appliance}` | `fridge 1` |
| Heat | `heat {obj} with {appliance}` | `microwave 1`, `stoveburner 1` |
| Clean | `clean {obj} with {appliance}` | `sinkbasin 1` |
## Error Recovery
- "Nothing happened": Check (1) you are holding the object, (2) appliance is open/ready, (3) object and appliance names are correct
- Appliance occupied: remove existing items first with `take {item} from {appliance}`
## Example
**Scenario:** You need to cool a tomato using the fridge.
```
Thought: I'm holding tomato 1 and need to cool it. I'll go to the fridge.
Action: go to fridge 1
Observation: The fridge 1 is closed.
Action: open fridge 1
Observation: You open the fridge 1. The fridge 1 is open. In it, you see a lettuce 1.
Action: cool tomato 1 with fridge 1
Observation: You cool the tomato 1 using the fridge 1.
```
**Result:** The tomato is now in a cooled state. Proceed with the next task step (e.g., placing it on a countertop).
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.