agents/skills/fizzy-cli/SKILL.md
Fizzy project management CLI for boards, cards, columns, steps, comments, and notifications. Use when the user wants to manage tasks, track work, create/update cards, organize boards, or interact with Fizzy (fizzy.do). Triggers: "create a card", "list my boards", "move card", "check notifications", "update task", "fizzy", "board", "card", or any project management action.
npx skillsauth add dpaluy/dotfiles fizzy-cliInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Ruby CLI for Fizzy project management. Installed as fizzy gem.
Credentials stored at ~/.config/fizzy-cli/tokens.yml. Check status before operations:
fizzy auth status
If not authenticated:
fizzy auth login --token YOUR_PAT_TOKEN
Generate a Personal Access Token from your Fizzy profile > API section > "Personal access tokens".
Multi-account:
fizzy auth accounts # List accounts (* = default)
fizzy auth switch /SLUG # Change default (e.g. /6160537)
All commands support:
--json — Machine-readable JSON output (use for parsing)--account /SLUG — Target a specific accountfizzy identity # Show all accounts and user info
fizzy identity --json # JSON format
fizzy boards list
fizzy boards get BOARD_ID
fizzy boards create "Board Name"
fizzy boards update BOARD_ID --name "New Name"
fizzy boards delete BOARD_ID
fizzy boards sync # Refresh boards cache
.fizzy.yml)fizzy init scaffolds a per-project config in the current directory:
account: 'ACCOUNT_SLUG'
boards:
BOARD_ID_1: Board Name 1
BOARD_ID_2: Board Name 2
When a project directory has a .fizzy.yml, prefer the boards it declares over picking from fizzy boards list. If the user is working inside a project and no .fizzy.yml exists, ask before assuming a board; offer to run fizzy init to record the mapping.
Cards are addressed by number (integer), not ID. The --board flag is only required for create.
fizzy cards list # All open cards
fizzy cards list --board BOARD_ID # Filter by board
fizzy cards list --status closed # open (default), closed, all
fizzy cards list --column COLUMN_ID # Filter by column
fizzy cards list --assignee USER_ID # Filter by assignee
fizzy cards get 42 # Show card details + steps
fizzy cards create "Title" --board BOARD_ID # Create (--body, --column optional)
fizzy cards update 42 --title "New title" # Update (--body optional)
fizzy cards delete 42
fizzy cards close 42 # Close (mark done)
fizzy cards reopen 42 # Reopen a closed card
fizzy cards not-now 42 # Defer card
fizzy cards triage 42 --column COLUMN_ID # Move to column
fizzy cards untriage 42 # Remove from triage
fizzy cards tag 42 "bug" # Add tag by title
fizzy cards assign 42 USER_ID # Toggle assignment
fizzy cards watch 42 # Subscribe to updates
fizzy cards unwatch 42 # Unsubscribe
fizzy cards golden 42 # Mark as golden
fizzy cards ungolden 42 # Remove golden
Columns are scoped to a board — --board is always required.
fizzy columns list --board BOARD_ID
fizzy columns get COLUMN_ID --board BOARD_ID
fizzy columns create "To Do" --board BOARD_ID
fizzy columns update COLUMN_ID --board BOARD_ID --name "Done"
fizzy columns delete COLUMN_ID --board BOARD_ID
Steps are scoped to a card — --card NUMBER is always required.
No list endpoint; steps are returned inline in fizzy cards get.
fizzy steps create "Write tests" --card 42
fizzy steps get STEP_ID --card 42
fizzy steps update STEP_ID --card 42 --completed # Mark done
fizzy steps update STEP_ID --card 42 --no-completed # Unmark
fizzy steps update STEP_ID --card 42 --description "Updated text"
fizzy steps delete STEP_ID --card 42
Scoped to a card — --card NUMBER is always required.
fizzy comments list --card 42
fizzy comments get COMMENT_ID --card 42
fizzy comments create "Looks good" --card 42
fizzy comments update COMMENT_ID --card 42 --body "Updated text"
fizzy comments delete COMMENT_ID --card 42
Works on cards and optionally on comments — --card NUMBER always required.
fizzy reactions list --card 42 # Card reactions
fizzy reactions list --card 42 --comment COMMENT_ID # Comment reactions
fizzy reactions create "thumbsup" --card 42
fizzy reactions create "heart" --card 42 --comment COMMENT_ID
fizzy reactions delete REACTION_ID --card 42
fizzy tags list # All tags for account
fizzy users list
fizzy users get USER_ID
fizzy users update USER_ID --name "New Name"
fizzy users deactivate USER_ID
fizzy notifications list
fizzy notifications read NOTIFICATION_ID
fizzy notifications unread NOTIFICATION_ID
fizzy notifications mark-all-read
fizzy pins pin 42 # Pin a card
fizzy pins unpin 42 # Unpin a card
Note: fizzy pins list requires session auth (not available with PAT).
fizzy boards list --json
BOARD_ID=$(fizzy boards list --json | jq -r '.[0].id')
fizzy cards list --board $BOARD_ID
fizzy columns list --board $BOARD_ID
fizzy cards create "Ship feature X" --board $BOARD_ID
fizzy cards triage 42 --column $COLUMN_ID
fizzy cards assign 42 $USER_ID
fizzy cards tag 42 "feature"
fizzy steps create "Write tests" --card 42
fizzy steps create "Update docs" --card 42
fizzy cards get 42 # Shows steps inline
fizzy cards create "Bug fix" --board $BOARD_ID # Created
fizzy cards triage 42 --column $IN_PROGRESS_ID # In progress
fizzy cards close 42 # Done
fizzy cards reopen 42 # Needs more work
fizzy cards not-now 42 # Deferred
MY_ID=$(fizzy identity --json | jq -r '.accounts[0].user.id')
fizzy cards list --assignee $MY_ID
--json when parsing output programmaticallyfizzy cards get returns steps inline — no separate steps list endpointhelp to any subcommand: fizzy cards help, fizzy columns help~/.config/fizzy-cli/tokens.yml--account /SLUGdevelopment
Analyze a project's past Codex sessions, memory files, and existing local skills to recommend the highest-value skills to create or update. Use when a user asks what skills a project needs, wants skill ideas grounded in real project history, wants an audit of current project-local skills, or wants recommendations for updating stale or incomplete skills instead of creating duplicates.
tools
Remote control tmux sessions for interactive CLIs by sending keystrokes and scraping pane output.
tools
Google Workspace CLI (gws) for Drive, Gmail, Calendar, Sheets, Docs, Chat, and Admin APIs. Use when the user wants to interact with Google Workspace: list/upload/download Drive files, send/read Gmail, manage Calendar events, read/write Sheets, create Docs, send Chat messages, or administer Google Workspace. Triggers: "google drive", "gmail", "google calendar", "google sheets", "google docs", "google chat", "gws", "workspace", or any Google Workspace action.
tools
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.