mirror

Mirror a gopher-cli source namespace into the vault with recursive dump.

Updated Feb 21, 2026
One-click install
npx skills add https://github.com/penserai/gopher-cli --skill mirror
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mirror
Source: https://github.com/penserai/gopher-cli/tree/main/.claude/skills/mirror
Command: npx skills add https://github.com/penserai/gopher-cli --skill mirror

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Mirror a gopher-cli source namespace into the vault, enabling secure, auditable backups and cross-environment replication.

Core Features & Use Cases

  • Mirror a source namespace into vault to create a mirrored copy of structure and documents.
  • Validate and preview the source with browse commands, then perform a recursive dump to vault/mirrors/[source-name].
  • Plan for verification by browsing the destination to ensure structure and content match expectations.

Quick Start

Use the mirror skill to copy a source namespace into vault/mirrors/[source-name], then verify the mirror with a browse command.

Frequently Asked Questions about mirror

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

FAQPage Schema
How do I back up a namespace to a vault using a recursive dump?

To back up a namespace to a vault, you use a recursive dump workflow to copy items while preserving the original structure. This creates a secure, auditable mirrored copy in the destination.

What is namespace mirroring for cross-environment synchronization?

Namespace mirroring is the process of copying a source namespace into a vault to create an identical, structured copy. It enables secure cross-environment replication and synchronization of documents.

Can I preview a source namespace before performing a vault backup?

Yes, you can validate and preview the source namespace using browse commands before executing the recursive dump. This ensures the source structure matches expectations before copying.

Do I need a destination path to mirror a source namespace into the vault?

You need a source namespace, but the destination path is optional. If not specified, the mirror workflow defaults to copying the source into the vault/mirrors/[source-name] directory.

How do I verify a namespace backup after copying it to the vault?

You verify a namespace backup by browsing the destination path in the vault to ensure the structure and content match the source. This confirms the recursive dump was successful.