Skip to content

Repository files navigation

Claude Skills

Custom skills for Claude Code CLI.

Skills

tmux-cli

Run interactive CLI commands (Python/Node REPLs, debuggers, long-running processes) in isolated tmux sessions.

Features:

  • Session isolation - all operations run in dedicated tmux-cli session
  • Support for REPLs, debuggers (pdb, gdb), test watchers, servers
  • Automatic cleanup of interactive sessions after task completion

Requirements:

  • tmux - terminal multiplexer
  • tmux-cli - CLI tool for tmux control

Installation:

# Install tmux (macOS)
brew install tmux

# Install tmux (Ubuntu/Debian)
sudo apt install tmux

# Install tmux-cli via uv
uv tool install claude-code-tools

Documentation: tmux-cli instructions & FAQ

codex-cli-interactive

Run interactive Codex CLI sessions for code review, security audits, refactoring, and multi-turn conversations with OpenAI Codex.

Features:

  • Interactive Codex sessions via tmux-cli isolation
  • Configurable model settings (gpt-5-codex, gpt-5)
  • Adjustable reasoning effort and sandbox modes
  • Task-specific presets for common workflows
  • Multi-turn conversation support

Requirements:

  • tmux (v3+) - terminal multiplexer
  • tmux-cli - CLI tool for tmux control
  • Codex CLI - OpenAI's coding assistant CLI
  • OpenAI API credentials configured

Installation:

# Install tmux (macOS)
brew install tmux

# Install tmux-cli via uv
uv tool install claude-code-tools

# Install Codex CLI
npm install -g @openai/codex

# Configure OpenAI credentials
export OPENAI_API_KEY="your-api-key"

ticktick

Manage TickTick tasks and projects from the command line with OAuth2 authentication and secure credential storage.

Features:

  • List, create, update, complete, and abandon tasks
  • Manage projects (lists)
  • Batch operations for multiple tasks
  • JSON output for scripting
  • Secure credential storage via pass (GPG-encrypted)

Requirements:

  • Bun - JavaScript runtime
  • pass - password manager for secure credential storage
  • TickTick OAuth app credentials (create here)

Installation:

# Install bun (macOS/Linux)
curl -fsSL https://bun.sh/install | bash

# Install pass (macOS)
brew install pass

# Install dependencies
cd ~/.claude/skills/ticktick && bun install

# Store credentials in pass
pass insert ticktick-cli/client-id
pass insert ticktick-cli/client-secret

# Authenticate
bun run scripts/ticktick.ts auth

browser-testing

Inspect and test any website through a headed Chrome instance driven over CDP (Chrome DevTools Protocol). Returns structured DOM data instead of screenshots — far less context than screenshot-based testing.

Features:

  • Structured page inspection: headings, links, forms, images (incl. broken ones), meta tags, console errors
  • Failed network requests — 4xx/5xx responses and network-level failures, so "page renders but the API 500s" is visible
  • Responsive checks at 4 breakpoints, axe-core accessibility audits, SEO audits, staging-vs-production comparison
  • Optional Lighthouse audit run against the same logged-in browser (--disable-storage-reset, so it can't wipe your session)
  • --out FILE — write the full report to disk and print only the lines that signal a real problem
  • Natural-language element finding, computed styles, arbitrary JS evaluation
  • Multi-step flows (click/fill/navigate/inspect) via the connect.py Python API
  • Persistent Chrome profile — logins survive restarts; tabs do not (no session-restore pile-up)
  • JPEG screenshots at CSS scale (no HiDPI 2x blowup), auto-downscaled to ≤2000px as a backstop
  • Drives your real Chrome install over CDP — no bundled browser download

Requirements:

  • Python 3.10+ (python3)
  • Google Chrome, Chromium, or Edge (auto-detected; override with CHROME_BIN)
  • Node.js (optional — only for --lighthouse)

Installation:

# No manual install — the venv (playwright + pillow + axe-core) bootstraps on first run
~/.claude/skills/browser-testing/scripts/bt https://example.com

Configuration (all optional): CDP_PORT (default 9333), BT_CHROME_PROFILE, CHROME_BIN, BT_SCREENSHOT_DIR.

Setup

Skills must be symlinked to ~/.claude/skills/ directory.

# Create skills directory if it doesn't exist
mkdir -p ~/.claude/skills

# Symlink a skill
ln -s /path/to/claude_skills/tmux-cli ~/.claude/skills/tmux-cli

Adding New Skills

  1. Create a directory with your skill name
  2. Add SKILL.md with frontmatter (name, description, allowed-tools) and instructions
  3. Symlink to ~/.claude/skills/

Example SKILL.md structure:

---
name: skill-name
description: Brief description of when to use this skill
allowed-tools: Bash, Read, Edit
---

# Skill Title

Instructions for Claude on how to use this skill...

About

Custom cool skills for Claude Code

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages