skills
Tool to verify your sivtr installation, configuration, and environment, and diagnose common issues.
Install
mkdir -p .claude/skills/skills-ariestar && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/11884" && unzip -o skill.zip -d .claude/skills/skills-ariestar && rm skill.zipInstalls to .claude/skills/skills-ariestar
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Verify sivtr environment and diagnose issues. Run when sivtr commands fail or return empty results.Key capabilities
- →Check if `sivtr` binary is installed and in PATH
- →Run `sivtr doctor` for complete diagnostics
- →Verify and install shell hooks for the current shell
- →Check provider sessions for data presence
- →Display and initialize `sivtr` configuration
How it works
The skill diagnoses `sivtr` environment issues by checking binary installation, running diagnostics, verifying shell hooks, and inspecting provider session data and configuration.
Inputs & outputs
When to use skills
- →Diagnose why sivtr commands fail
- →Check provider sessions
- →Verify sivtr configuration
- →Install shell hooks
About this skill
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 |
When not to use it
- →When `sivtr` commands are working as expected
- →When manual debugging of `sivtr` issues is preferred
- →When shell hooks are already correctly installed
Limitations
- →The skill is specific to diagnosing `sivtr` environment issues.
- →Installation of `sivtr` binary is a prerequisite if not found.
- →Shell hook installation requires restarting the terminal or sourcing the profile.
How it compares
This skill provides a structured diagnostic process for `sivtr` specific issues, including checks for binary, hooks, and provider sessions, offering targeted troubleshooting compared to general system debugging.
Compared to similar skills
skills side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| skills (this skill) | 0 | 2mo | Review | Beginner |
| n8n-expression-syntax | 6 | 4mo | No flags | Beginner |
| python-repl | 6 | 4mo | Review | Beginner |
| n8n-validation-expert | 6 | 4mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
n8n-expression-syntax
czlonkowski
Validate n8n expression syntax and fix common errors. Use when writing n8n expressions, using {{}} syntax, accessing $json/$node variables, troubleshooting expression errors, or working with webhook data in workflows.
python-repl
gptme
Interactive Python REPL automation with common helpers and best practices
n8n-validation-expert
czlonkowski
Interpret validation errors and guide fixing them. Use when encountering validation errors, validation warnings, false positives, operator structure issues, or need help understanding validation results. Also use when asking about validation profiles, error types, or the validation loop process.
powershell-windows
davila7
PowerShell Windows patterns. Critical pitfalls, operator syntax, error handling.
bats
OleksandrKucherenko
Bash Automated Testing System (BATS) for TDD-style testing of shell scripts. Use when: (1) Writing unit or integration tests for Bash scripts, (2) Testing CLI tools or shell functions, (3) Setting up test infrastructure with setup/teardown hooks, (4) Mocking external commands (curl, git, docker), (5) Generating JUnit reports for CI/CD, (6) Debugging test failures or flaky tests, (7) Implementing test-driven development for shell scripts.
browser-daemon
noiv
Persistent browser automation via Playwright daemon. Keep a browser window open and send it commands (navigate, execute JS, inspect console). Perfect for interactive debugging, development, and testing web applications. Use when you need to interact with a browser repeatedly without opening/closing it.