agentsclimarketplace

Fizzy write

Skill Rijul1204/rashedul-agentic-engineering/skills/fizzy-write

My agentic-engineering workbench — Claude Code skills, subagents, and CI workflows I reuse across projects.

Install
npx -y skills add Rijul1204/rashedul-agentic-engineering --skill fizzy-write

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Create cards, create boards, update cards, close/reopen cards, add comments, assign users, or move cards to a column in Fizzy. Use when user says "create card", "create board", "add task to fizzy", "close fizzy card", "comment on fizzy card", "assign fizzy card", "move card to column", or anything involving writing to the Fizzy task board.

SKILL.md

6.0 KB, as published. Nobody here has run it

Fizzy Write — Manage Cards & Boards

Create and manage cards, boards, comments, and assignments in the Fizzy task board.

Credentials

Bearer token:

eCaGiEZPirmuqVQwuNmCMNd6

Account ID: 6132669 Base URL: https://app.fizzy.do

Known Boards

Board IDNameDefault?
03fd4omd9qico7wmyyof5yfe4QA BoardYES

If the user names a specific board, resolve it by calling GET /6132669/boards and matching by name. Otherwise, always use the QA board.

Workflow

Step 1 — Parse the user's intent

Identify the operation:

IntentOperation
"create a card / task"Create card
"create a board"Create board
"update / edit card #N"Update card
"close / done card #N"Close card
"reopen card #N"Reopen card
"comment on card #N"Add comment
"assign card #N to [user]"Assign
"move card #N to [column]"Triage (move)
"tag card #N with [tag]"Apply tag

For create card: extract title, optional description, optional board name (defaults to QA board). For create board: extract board name and optional description.

IMPORTANT — Fizzy does NOT support Markdown. Do not use **bold**, # headers, - bullet syntax, or any Markdown in card titles, descriptions, or comments. Use plain text with spacing and line breaks for structure. Example:

Implementation notes:

  - Check user region against Dots coverage map
  - Block enrollment if region unsupported
  - Show clear error message to player

Use indentation and blank lines for readability — not Markdown syntax.

Step 2 — Execute the API call

Use curl with the Bearer token. All endpoints are under https://app.fizzy.do.

Create card (on QA board by default)

curl -s -X POST "https://app.fizzy.do/6132669/boards/03fd4omd9qico7wmyyof5yfe4/cards" \
  -H "Accept: application/json" \
  -H "Authorization: Bearer R2Rek4vNLSrr12F9QFkBy3BZ" \
  -H "Content-Type: application/json" \
  -d '{
    "card": {
      "title": "<TITLE>",
      "description": "<OPTIONAL_DESCRIPTION>"
    }
  }'

Create board

curl -s -X POST "https://app.fizzy.do/6132669/boards" \
  -H "Accept: application/json" \
  -H "Authorization: Bearer R2Rek4vNLSrr12F9QFkBy3BZ" \
  -H "Content-Type: application/json" \
  -d '{
    "board": {
      "name": "<BOARD_NAME>",
      "description": "<OPTIONAL_DESCRIPTION>"
    }
  }'

List boards (to resolve a board name → ID)

curl -s "https://app.fizzy.do/6132669/boards" \
  -H "Accept: application/json" \
  -H "Authorization: Bearer R2Rek4vNLSrr12F9QFkBy3BZ"

Update card

curl -s -X PUT "https://app.fizzy.do/6132669/cards/<CARD_NUMBER>" \
  -H "Accept: application/json" \
  -H "Authorization: Bearer R2Rek4vNLSrr12F9QFkBy3BZ" \
  -H "Content-Type: application/json" \
  -d '{
    "card": {
      "title": "<NEW_TITLE>"
    }
  }'

Close card

curl -s -X POST "https://app.fizzy.do/6132669/cards/<CARD_NUMBER>/closure" \
  -H "Accept: application/json" \
  -H "Authorization: Bearer R2Rek4vNLSrr12F9QFkBy3BZ" \
  -H "Content-Type: application/json"

Reopen card

curl -s -X DELETE "https://app.fizzy.do/6132669/cards/<CARD_NUMBER>/closure" \
  -H "Accept: application/json" \
  -H "Authorization: Bearer R2Rek4vNLSrr12F9QFkBy3BZ"

Add comment

curl -s -X POST "https://app.fizzy.do/6132669/cards/<CARD_NUMBER>/comments" \
  -H "Accept: application/json" \
  -H "Authorization: Bearer R2Rek4vNLSrr12F9QFkBy3BZ" \
  -H "Content-Type: application/json" \
  -d '{
    "comment": {
      "body": "<COMMENT_TEXT>"
    }
  }'

Assign user (toggle — assigns if unassigned, unassigns if already assigned)

curl -s -X POST "https://app.fizzy.do/6132669/cards/<CARD_NUMBER>/assignments" \
  -H "Accept: application/json" \
  -H "Authorization: Bearer R2Rek4vNLSrr12F9QFkBy3BZ" \
  -H "Content-Type: application/json" \
  -d '{
    "assignee_id": "<USER_ID>"
  }'

Move card to column (triage)

curl -s -X POST "https://app.fizzy.do/6132669/cards/<CARD_NUMBER>/triage" \
  -H "Accept: application/json" \
  -H "Authorization: Bearer R2Rek4vNLSrr12F9QFkBy3BZ" \
  -H "Content-Type: application/json" \
  -d '{
    "column_id": "<COLUMN_ID>"
  }'

To resolve a column name → ID, first call GET /6132669/boards/<BOARD_ID>/columns.

Apply or remove tag

curl -s -X POST "https://app.fizzy.do/6132669/cards/<CARD_NUMBER>/taggings" \
  -H "Accept: application/json" \
  -H "Authorization: Bearer R2Rek4vNLSrr12F9QFkBy3BZ" \
  -H "Content-Type: application/json" \
  -d '{
    "tag_title": "<TAG_TITLE>"
  }'

Step 3 — Confirm or report error

On success:

  • For card creation: confirm with card number and deep link: https://app.fizzy.do/6132669/cards/<CARD_NUMBER>
  • For board creation: confirm with board name and deep link: https://app.fizzy.do/6132669/boards/<BOARD_ID>
  • For other operations: confirm the action taken (e.g., "Card #42 closed.")

On error (non-2xx response or error field in JSON):

  • Show the error message and suggest a fix (e.g., wrong card number, token expired)

Pagination

List endpoints return paginated results with a Link header containing rel="next". Follow the next link if you need all results and the response is paginated.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.