# Manage tzst Archives from the CLI

Archive workflows can fail when flags, filters, or conflict rules are unclear. This skill gives focused tzst CLI guidance for safe extraction, automation, and installation.

## Install

```bash
npx skillstore add xixu-me/tzst
```

## Metadata

- Status: approved
- Slug: xixu-me-tzst
- Skillstore revision: r1
- Version status: missing
- Tree hash: 11c8efbc65fd6d6c0d13cf6e61ff243e2dc4781562d2d311df27d84ce81b769c
- Author: xixu-me
- GitHub username: xixu-me
- License: MIT
- Repository: https://github.com/xixu-me/skills/tree/main/skills/tzst/
- Ref: 64ca8af0f54a325752f08bd54e52151061ea659a
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network
- Quality score: 76
- Public page: https://skillstore.pages.dev/skills/xixu-me-tzst
- Manifest: https://skillstore.pages.dev/api/skills/xixu-me-tzst/manifest

## Capabilities

- Choose tzst subcommands for creating, extracting, listing, and testing archives.
- Recommend safe extraction filters, including data, tar, and fully\_trusted modes.
- Prepare JSON-friendly command patterns for scripts and pipelines.
- Explain conflict-resolution choices for interactive and automated extraction.
- Guide installation through uv, pip, or official release binaries.
- Troubleshoot exit codes and command placement for global flags.

## Use Cases

- Safe Backup Extraction: Choose extraction commands, filters, and conflict rules for restoring archives without flattening paths by mistake.
- Scriptable Archive Checks: Prepare machine-readable list or test workflows with stable exit-code handling and non-interactive conflict choices.
- tzst Install Support: Guide users through uv, pip, or release binary setup before running version and help checks.

## Prompt Templates

### Check a tzst Archive

```
List the contents of backup.tzst and explain whether I should use normal or flat extraction.
```

### Extract Safely

```
Extract backup.tzst into restore/ using safe defaults and preserve the original directory structure.
```

### Automate JSON Output

```
Create a non-interactive command to list backup.tzst as JSON without banner text for a pipeline.
```

### Plan Trusted Extraction Policy

```
Compare data, tar, and fully_trusted filters for this archive source, then recommend the safest command and conflict policy.
```

## Limitations

- It covers the tzst CLI, not the Python API or generic tar and zip tools.
- It cannot verify archive contents without access to the files.
- It does not replace user review before installing packages or binaries.
- It relies on the installed tzst version for final flag behavior.

## Best Practices

- List an archive first when member names or structure are uncertain.
- Use the data extraction filter unless the archive source is fully trusted.
- Set a non-interactive conflict policy for scripts and scheduled jobs.

## Anti Patterns

- Using flat extraction when the user expects directory structure to remain.
- Combining machine-readable output with interactive conflict prompts.
- Recommending fully trusted extraction for unknown archive sources.

## Security Audit

- Audited at: 2026-07-08T10:05:39.476\+00:00
- Summary: All static findings were adjudicated as false positives. The flagged external-command patterns are Markdown code spans and CLI guidance for a named archive tool, not embedded shell execution. No prompt injection, data exfiltration, or unauthorized network intent was found.

## Stats

- Views: 84
- Downloads: 11
- Favorites: 0
- Popularity score: 0