0
0
Source

Manages Fizzy boards, cards, steps, comments, and reactions. Use when user asks about boards, cards, tasks, backlog or anything Fizzy.

Install

mkdir -p .claude/skills/fizzy && curl -L -o skill.zip "https://mcp.directory/api/skills/download/8486" && unzip -o skill.zip -d .claude/skills/fizzy && rm skill.zip

Installs to .claude/skills/fizzy

About this skill

Fizzy CLI Skill

Requirements (Install & Auth)

Install via Homebrew (macOS)

brew install robzolkos/fizzy-cli/fizzy-cli

Configure Credentials

The CLI needs your API token and account. You can set these via environment variables or config files.

Environment variables (recommended for Clawdbot):

# Set these before running fizzy commands
export FIZZY_TOKEN="your_token_here"
export FIZZY_ACCOUNT="your_account_slug"  # e.g., "0000001"
export FIZZY_API_URL="https://fizzy.domain.net/"  # self-hosted
export FIZZY_BOARD="your_default_board_id"  # optional

Or use a config file (~/.config/fizzy/config.yaml):

token: your_token_here
account: your_account_slug
api_url: https://fizzy.domain.net/
board: your_default_board_id

Get Your Token

  1. Go to your Fizzy profile → Personal Access Tokens
  2. Generate a new token with Read + Write permissions

ID Formats

IMPORTANT: Cards use TWO identifiers:

FieldFormatUse For
id03fe4rug9kt1mpgyy51lq8i5iInternal ID (in JSON responses)
number579CLI commands (card show, card update, etc.)

All card CLI commands use the card NUMBER, not the ID.

Other resources (boards, columns, comments, steps, reactions, users) use their id field.


Response Structure

All responses follow this structure:

{
  "success": true,
  "data": { ... },           // Single object or array
  "meta": {
    "timestamp": "2026-01-12T21:21:48Z"
  }
}

List responses with pagination:

{
  "success": true,
  "data": [ ... ],
  "pagination": {
    "has_next": true,
    "next_url": "https://..."
  },
  "meta": { ... }
}

Error responses:

{
  "success": false,
  "error": {
    "code": "NOT_FOUND",
    "message": "Not Found",
    "status": 404
  },
  "meta": { ... }
}

Create/update responses include location:

{
  "success": true,
  "data": { ... },
  "location": "/6102600/cards/579.json",
  "meta": { ... }
}

Resource Schemas

Complete field reference for all resources. Use these exact field paths in jq queries.

Card Schema

IMPORTANT: card list and card show return different fields. steps only in card show.

FieldTypeDescription
numberintegerUse this for CLI commands
idstringInternal ID (in responses only)
titlestringCard title
descriptionstringPlain text content (NOT an object)
description_htmlstringHTML version with attachments
statusstringUsually "published" for active cards
closedbooleantrue = card is closed
goldenbooleantrue = starred/important
image_urlstring/nullHeader/background image URL
has_more_assigneesbooleanMore assignees than shown
created_attimestampISO 8601
last_active_attimestampISO 8601
urlstringWeb URL
comments_urlstringComments endpoint URL
boardobjectNested Board (see below)
creatorobjectNested User (see below)
assigneesarrayArray of User objects
tagsarrayArray of Tag objects
stepsarrayOnly in card show, not in list

Board Schema

FieldTypeDescription
idstringBoard ID (use for CLI commands)
namestringBoard name
all_accessbooleanAll users have access
created_attimestampISO 8601
urlstringWeb URL
creatorobjectNested User

User Schema

FieldTypeDescription
idstringUser ID (use for CLI commands)
namestringDisplay name
email_addressstringEmail
rolestring"owner", "admin", or "member"
activebooleanAccount is active
created_attimestampISO 8601
urlstringWeb URL

Comment Schema

FieldTypeDescription
idstringComment ID (use for CLI commands)
bodyobjectNested object with html and plain_text
body.htmlstringHTML content
body.plain_textstringPlain text content
created_attimestampISO 8601
updated_attimestampISO 8601
urlstringWeb URL
reactions_urlstringReactions endpoint URL
creatorobjectNested User
cardobjectNested {id, url}

Step Schema

FieldTypeDescription
idstringStep ID (use for CLI commands)
contentstringStep text
completedbooleanCompletion status

Column Schema

FieldTypeDescription
idstringColumn ID or pseudo ID ("not-now", "maybe", "done")
namestringDisplay name
kindstring"not_now", "triage", "closed", or custom
pseudobooleantrue = built-in column

Tag Schema

FieldTypeDescription
idstringTag ID
titlestringTag name
created_attimestampISO 8601
urlstringWeb URL

Reaction Schema

FieldTypeDescription
idstringReaction ID (use for CLI commands)
contentstringEmoji
urlstringWeb URL
reacterobjectNested User

Identity Schema (from identity show)

FieldTypeDescription
accountsarrayArray of Account objects
accounts[].idstringAccount ID
accounts[].namestringAccount name
accounts[].slugstringAccount slug (use with --account)
accounts[].userobjectYour User in this account

Key Schema Differences

ResourceText FieldHTML Field
Card.description (string).description_html (string)
Comment.body.plain_text (nested).body.html (nested)

Global Flags

All commands support:

FlagDescription
--account SLUGAccount slug (for multi-account users)
--prettyPretty-print JSON output
--verboseShow request/response details

Pagination

List commands use --page for pagination. There is NO --limit flag.

# Get first page (default)
fizzy card list --page 1

# Get specific number of results using jq
fizzy card list --page 1 | jq '.data[:5]'

# Fetch ALL pages at once
fizzy card list --all

Commands supporting --all and --page:

  • board list
  • card list
  • comment list
  • tag list
  • user list
  • notification list

Common jq Patterns

Reducing Output

# Card summary (most useful)
fizzy card list | jq '[.data[] | {number, title, status, board: .board.name}]'

# First N items
fizzy card list | jq '.data[:5]'

# Just IDs
fizzy board list | jq '[.data[].id]'

# Specific fields from single item
fizzy card show 579 | jq '.data | {number, title, status, golden}'

# Card with description length (description is a string, not object)
fizzy card show 579 | jq '.data | {number, title, desc_length: (.description | length)}'

Filtering

# Cards with a specific status
fizzy card list --all | jq '[.data[] | select(.status == "published")]'

# Golden cards only
fizzy card list --

---

*Content truncated.*

You might also like

flutter-development

aj-geddes

Build beautiful cross-platform mobile apps with Flutter and Dart. Covers widgets, state management with Provider/BLoC, navigation, API integration, and material design.

1,1421,171

drawio-diagrams-enhanced

jgtolentino

Create professional draw.io (diagrams.net) diagrams in XML format (.drawio files) with integrated PMP/PMBOK methodologies, extensive visual asset libraries, and industry-standard professional templates. Use this skill when users ask to create flowcharts, swimlane diagrams, cross-functional flowcharts, org charts, network diagrams, UML diagrams, BPMN, project management diagrams (WBS, Gantt, PERT, RACI), risk matrices, stakeholder maps, or any other visual diagram in draw.io format. This skill includes access to custom shape libraries for icons, clipart, and professional symbols.

969933

ui-ux-pro-max

nextlevelbuilder

"UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient."

683829

godot

bfollington

This skill should be used when working on Godot Engine projects. It provides specialized knowledge of Godot's file formats (.gd, .tscn, .tres), architecture patterns (component-based, signal-driven, resource-based), common pitfalls, validation tools, code templates, and CLI workflows. The `godot` command is available for running the game, validating scripts, importing resources, and exporting builds. Use this skill for tasks involving Godot game development, debugging scene/resource files, implementing game systems, or creating new Godot components.

691549

nano-banana-pro

garg-aayush

Generate and edit images using Google's Nano Banana Pro (Gemini 3 Pro Image) API. Use when the user asks to generate, create, edit, modify, change, alter, or update images. Also use when user references an existing image file and asks to modify it in any way (e.g., "modify this image", "change the background", "replace X with Y"). Supports both text-to-image generation and image-to-image editing with configurable resolution (1K default, 2K, or 4K for high resolution). DO NOT read the image file first - use this skill directly with the --input-image parameter.

797540

pdf-to-markdown

aliceisjustplaying

Convert entire PDF documents to clean, structured Markdown for full context loading. Use this skill when the user wants to extract ALL text from a PDF into context (not grep/search), when discussing or analyzing PDF content in full, when the user mentions "load the whole PDF", "bring the PDF into context", "read the entire PDF", or when partial extraction/grepping would miss important context. This is the preferred method for PDF text extraction over page-by-page or grep approaches.

697374

Stay ahead of the MCP ecosystem

Get weekly updates on new skills and servers.