Skip to content
Back to skills

Mc Place Until Supported

ASecurity

Create reliable footing by placing blocks until observed support becomes provably solid. Absorbs placement uncertainty and never exposes 'accepted but ineffective' outcomes

  • 10 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added June 6, 2026
testingpythonperformance

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned June 6, 2026

npx -y skills add bdambrosio/Cognitive_workbench --skill mc-place-until-supported --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Mc Place Until Supported?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Mc Place Until Supported
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/bdambrosio-mc-place-until-supported/badge)](https://www.skillsdirectory.com/skills/bdambrosio-mc-place-until-supported)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: mc-place-until-supported
type: python
description: "Create reliable footing by placing blocks until observed support becomes provably solid. Absorbs placement uncertainty and never exposes 'accepted but ineffective' outcomes"
---

# Minecraft Place Until Supported Tool

Creates reliable footing by placing blocks until observed support becomes provably solid. Absorbs placement uncertainty and never exposes 'accepted but ineffective' outcomes.

## Purpose

Reliable footing creation for safe movement and construction. Uses observation-verification loop to ensure blocks are actually placed and provide support, handling asynchronous placement uncertainty.

## Input

- `value`: Item/block name (preferred, optional - auto-selects from inventory if not provided)
- `item`: Item/block name (alternative to value, optional)
- `placement_policy`: One of `{"underfoot", "forward-underfoot", "lateral"}` (default: `"underfoot"`)
- `max_attempts`: Integer maximum placement attempts (default: `3`)
- `verify_delay`: Float seconds to wait before re-observation (default: `0.0`)

## Output

Returns uniform_return format with:
- `value`: Text summary with outcome and attempt count
- `data`: Structured data dict (machine-readable). Key fields:
  - `outcome`: `"SUPPORTED"` | `"NO_PLACEABLE_TARGET"` | `"PLACEMENT_IMPOSSIBLE"` | `"INVENTORY_EXHAUSTED"` | `"SUPPORT_AMBIGUOUS"`
  - `attempts_made`: Integer
  - `max_attempts`: Integer
  - `placement_policy`: String
  - `item`: String

## Behavior & Performance

- Observation-verification loop: Places block, observes, verifies support
- Retries up to max_attempts if support not achieved
- Handles asynchronous placement uncertainty
- Auto-selects item from inventory if not specified

## Guidelines

- Use for creating reliable footing before movement
- `SUPPORTED` outcome indicates solid footing achieved
- `NO_PLACEABLE_TARGET` indicates no valid placement location
- `INVENTORY_EXHAUSTED` indicates no more blocks available
- `SUPPORT_AMBIGUOUS` indicates uncertain support state - may need retry

## Usage Examples

Place until supported with defaults:
```json
{"type":"mc-place-until-supported","value":"dirt","placement_policy":"underfoot","max_attempts":3,"out":"$place"}
```

Place forward-underfoot:
```json
{"type":"mc-place-until-supported","item":"cobblestone","placement_policy":"forward-underfoot","out":"$place"}
```

Files in this skill

  • Skill.md2.3 KB
  • tool.py12.6 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…