fizzy

What This Skill Does

The Fizzy skill provides a comprehensive interface for the OpenClaw AI agent to interact with the Fizzy project management ecosystem. It enables seamless management of boards, cards, tasks, comments, and project workflows directly through command-line operations. By integrating this skill, users can delegate administrative project tasks—such as creating backlog items, updating card statuses, or retrieving project updates—to the agent. It is designed to handle the complexity of Fizzy's unique identifier system, ensuring that cards are managed via their human-readable sequence numbers while maintaining synchronization with internal database IDs.

Installation

To enable this skill, run the following command in your Clawhub-enabled environment: clawhub install openclaw/skills/skills/portavion/fizzy. Ensure the underlying fizzy-cli is installed on your host system via brew install robzolkos/fizzy-cli/fizzy-cli. After installation, you must configure your environment with your API credentials, including your FIZZY_TOKEN, FIZZY_ACCOUNT, and the FIZZY_API_URL if you are utilizing a self-hosted instance. These can be set as exported environment variables or stored securely in your ~/.config/fizzy/config.yaml file.

Use Cases

The Fizzy skill is ideal for technical teams and project managers who want to automate their agile workflow. Use it to quickly query the status of development sprints, generate daily stand-up reports by fetching card lists, or update task progress during deep work sessions without leaving your current workspace. It acts as a bridge between high-level project management and granular task execution.

Example Prompts

1. "What are the top priority cards currently sitting in the engineering backlog on my default board?"
2. "Update card 579 to move it to the 'In Review' column and add a comment saying 'Refactored the authentication module for better performance'."
3. "Summarize the recent activity on my current Fizzy board and list any new tasks assigned to me."

Tips & Limitations

Always remember that card commands require the 'number' (e.g., 579) rather than the 'id' (e.g., 03fe4rug...). If you are unsure of a card number, use card list first to retrieve the current mapping. Be aware that card list and card show return different datasets; detailed information, such as nested steps, is exclusively available via the card show command. Keep your API tokens secure, and if you are managing multiple projects, explicitly define the FIZZY_BOARD environment variable to prevent errors in cross-board operations.