Automated summary
A step-by-step troubleshooting guide for the sivtr command-line tool, covering binary verification, diagnostics, shell hooks, provider data, and configuration.
Strengths
- Ordered procedure with the exact commands to run at each step
- Symptom/fix lookup table for fast triage
- Covers frequent causes: binary missing from PATH, uninstalled shell hooks, empty provider sessions, clipboard access failures
Limitations
- Assumes sivtr is the failing tool; not reusable for diagnosing other CLIs
- Does not go beyond the listed checks (no raw log analysis or deep debugging)
- The mentioned providers (Codex, Claude Code, Pi, OpenCode) are specific to this tool
Use it when a sivtr command fails, is not found, or returns empty results.
Avoid it when you need usage documentation for sivtr or when the problem involves a tool other than sivtr.
Security analysis
SafeThe skill only runs diagnostic and installation commands for a specific tool (sivtr). It does not contain destructive commands, data exfiltration, obfuscation, or unsafe patterns. The most impactful action is 'cargo install sivtr' and 'sivtr clear --all', both benign and within the intended diagnostic scope.
No concerns found
How this analysis is madeExamples
Running `sivtr` gives me 'command not found'. Can you check my environment and tell me how to fix it?sivtr returns no AI session results in this workspace — run the diagnostics and figure out why.sivtr isn't capturing my terminal history. Check whether the shell hooks are installed and walk me through setting them up for zsh.description: Verify sivtr environment and diagnose issues. Run when sivtr commands fail or return empty results. allowed-tools: Bash
sivtr Environment Check
Diagnose why sivtr commands may not be working as expected.
Steps
1. Check binary
sivtr --version
If this fails, sivtr is not installed or not in PATH. Install with:
cargo install sivtr
2. Run diagnostics
sivtr doctor
This checks: binary version, config file, session log directory, shell hooks, provider sessions, clipboard.
3. Check shell hooks
If sivtr doctor shows hooks not installed:
sivtr init show
Install the hook for the current shell:
sivtr init bash # or zsh, powershell, nushell
Then restart the terminal (or source the profile).
4. Verify provider data
If provider searches return empty:
sivtr doctor
The "provider sessions" section shows how many sessions each provider has. If zero:
- The provider (Codex, Claude Code, Pi, OpenCode) may not have been used in this workspace
- The session data may be in a non-standard location
5. Check config
sivtr config show
If missing:
sivtr config init
Common Issues
| Symptom | Fix |
|---------|-----|
| sivtr not found | Install: cargo install sivtr |
| No terminal results | sivtr init bash + restart terminal |
| No AI session results | Provider may not have sessions in this workspace |
| Clipboard fails | sivtr doctor checks clipboard access |
| Stale results | sivtr clear --all resets session logs |
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/sivtr-environment-check-and-diagnostics-msh3utwm/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/sivtr-environment-check-and-diagnostics-msh3utwm' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/sivtr-environment-check-and-diagnostics-msh3utwm/download' --output '.skill-downloads/sivtr-environment-check-and-diagnostics-msh3utwm/SKILL.md.part' && mv '.skill-downloads/sivtr-environment-check-and-diagnostics-msh3utwm/SKILL.md.part' '.skill-downloads/sivtr-environment-check-and-diagnostics-msh3utwm/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
Tools declared by the author (check availability in your agent): Bash
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
This file does not provide a usable name/description header for this native procedure. It remains available to download and inspect; use the manual method below.
Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/sivtr-environment-check-and-diagnostics-msh3utwm/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.