nanoclaw-repl

Run a zero-dependency, session-aware NanoClaw v2 REPL with markdown-backed sessions.

Updated Mar 1, 2026
One-click install
npx skills add https://github.com/derekhu0002/ai4pb-orchestrator --skill nanoclaw-repl-derekhu0002
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nanoclaw-repl
Source: https://github.com/derekhu0002/ai4pb-orchestrator/tree/main/skills/nanoclaw-repl
Command: npx skills add https://github.com/derekhu0002/ai4pb-orchestrator --skill nanoclaw-repl-derekhu0002

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a zero-dependency, session-aware NanoClaw v2 REPL that enables repeatable experimentation and extensible scripting without requiring external runtimes.

Core Features & Use Cases

  • persistent markdown-backed sessions
  • model switching with /model
  • dynamic skill loading with /load
  • session branching with /branch
  • cross-session search with /search
  • history compaction with /compact
  • export to md/json/txt with /export
  • session metrics with /metrics

Quick Start

Open a new session and load a skill script with /load to begin interactive testing.

Frequently Asked Questions about nanoclaw-repl

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a zero-dependency REPL for interactive model testing?

Use the /branch command to split your current session state into a new isolated path. This enables parallel experimentation with different models or prompts while keeping the original session intact.

Can I switch models dynamically during a REPL session?

Yes, you can switch models dynamically during a REPL session by using the /model command. This allows you to test different models within the same isolated, persistent environment.

How do I save and share my interactive REPL session history?

You can save and share your REPL session history by using the /export command to output results as markdown, JSON, or text files. Sessions are persisted using markdown-backed storage.

What is the best way to manage long REPL conversation histories?

The best way to manage long REPL conversation histories is using the /compact command to compress session history. This maintains context while reducing token load for continued interaction.

How do I branch a session to test different prompts in isolation?

Use the /branch command to split your current session state into a new isolated path. This enables parallel experimentation with different models or prompts while keeping the original session intact.