setup
Purpose
Install or update the dasel v3 binary from GitHub Releases into user-space (~/.local/bin on Linux/WSL2/macOS, %LOCALAPPDATA%\Programs\dasel on Windows). The install script handles platform detection, SHA256 verification, and PATH setup.
Install Script
The install script is a PEP 723 Python script at ${CLAUDE_PLUGIN_ROOT}/scripts/install_dasel.py.
Commands
Install or update to latest version:
${CLAUDE_PLUGIN_ROOT}/scripts/install_dasel.py
Force reinstall (even if already at latest version):
${CLAUDE_PLUGIN_ROOT}/scripts/install_dasel.py --force
Preview what would happen without making changes:
${CLAUDE_PLUGIN_ROOT}/scripts/install_dasel.py --dry-run
Install to a custom directory instead of the default:
${CLAUDE_PLUGIN_ROOT}/scripts/install_dasel.py --bin-dir /custom/path
Verify Installation
After install, confirm dasel is available:
dasel --version
Expected output format: dasel version v3.x.x
Supported Platforms
- Linux x86_64 (amd64)
- Linux ARM64 (aarch64)
- Windows x64 (native + WSL2)
WSL2 uses the Linux binary (dasel_linux_amd64), not the Windows .exe. The WSL2 environment is a full Linux subsystem.
Troubleshooting
"command not found" after install
~/.local/bin is not in PATH. Add it:
export PATH="$HOME/.local/bin:$PATH"
Make persistent by adding to ~/.bashrc or ~/.zshrc:
echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.bashrc
source ~/.bashrc
Download failures
- Check internet connectivity:
curl -I https://api.github.com - GitHub API rate limits: unauthenticated requests are limited to 60/hour. Set
GITHUB_TOKENenvironment variable for higher limits. - Retry with
--forceafter transient failures.
SHA256 mismatch
The install script verifies the downloaded binary against the SHA256 digest from the GitHub API response. A mismatch indicates a corrupted download or tampered binary.
Fix: re-download with --force:
${CLAUDE_PLUGIN_ROOT}/scripts/install_dasel.py --force
Permission denied
Ensure the install directory exists and is writable:
mkdir -p ~/.local/bin
ls -ld ~/.local/bin
The directory should be owned by the current user with write permission.
More from jamie-bitflight/claude_skills
perl-lint
This skill should be used when the user asks to lint Perl code, run perlcritic, check Perl style, format Perl code, run perltidy, or mentions Perl Critic policies, code formatting, or style checking.
24brainstorming-skill
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or when users request help with ideation, marketing, and strategic planning. Explores user intent, requirements, and design before implementation using 30+ research-validated prompt patterns.
11design-anti-patterns
Enforce anti-AI UI design rules based on the Uncodixfy methodology. Use when generating HTML, CSS, React, Vue, Svelte, or any frontend UI code. Prevents "Codex UI" — the generic AI aesthetic of soft gradients, floating panels, oversized rounded corners, glassmorphism, hero sections in dashboards, and decorative copy. Applies constraints from Linear/Raycast/Stripe/GitHub design philosophy: functional, honest, human-designed interfaces. Triggers on: UI generation, dashboard building, frontend component creation, CSS styling, landing page design, or any task producing visual interface code.
7python3-review
Comprehensive Python code review checking patterns, types, security, and performance. Use when reviewing Python code for quality issues, when auditing code before merge, or when assessing technical debt in a Python codebase.
7hooks-guide
Cross-platform hooks reference for AI coding assistants — Claude Code, GitHub Copilot, Cursor, Windsurf, Amp. Covers hook authoring in Node.js CJS and Python, per-platform event schemas, inline-agent hooks and MCP in agent frontmatter, common JSON I/O, exit codes, best practices, and a fetch script to refresh docs from official sources. Use when writing, reviewing, or debugging hooks for any AI assistant.
7agent-creator
Create high-quality Claude Code agents from scratch or by adapting existing agents as templates. Use when the user wants to create a new agent, modify agent configurations, build specialized subagents, or design agent architectures. Guides through requirements gathering, template selection, and agent file generation following Anthropic best practices (v2.1.63+).
6