More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    zinn

    1

    Manage Zinn project boards and task lifecycles directly within your development environment via the Zinn CLI.

    Free

    Security scanned
    zinn

    zinn

    Example session with this skill installed

    Find my current task in the DEMO project, move it to In Progress, and add a comment that I'm starting on the auth middleware.

    • Read your context and instructions
    • Compiled the zinn

    I found DEMO-1 in the DEMO project, moved it to In Progress, and added the starting comment.

    What I ran

    zinn info --json
    zinn task list DEMO --json
    zinn task view DEMO-1 --json
    zinn project column list DEMO --json
    zinn task move DEMO-1 'In Progress' --json
    zinn task comment create DEMO-1 --text 'Starting on the auth middleware.' --json
    zinn task view DEMO-1 --json
    

    Result

    FieldValue
    ProjectDEMO (Demo App)
    TaskDEMO-1
    TitleRefactor auth middleware for OAuth2
    ColumnIn Progress
    CommentDEMO-1#1, "Starting on the auth middleware."
    {
      "id": "01a1bca9-a33f-7446-a71e-18bfd0d1934c",
      "key": "DEMO-1",
      "project_id": "01a1bca9-a2e0-75e5-a535-5d58e707d147",
      "status": "Active",
      "column": "In Progress",
      "column_id": "01a1bca9-a2e0-75e5-a535-6b3eda7dfed5",
      "is_first": false,
      "is_last": false,
      "title": "Refactor auth middleware for OAuth2",
      "description": "Replace the legacy session check with an OAuth2 middleware and keep the existing tests green.",
      "priority": null,
      "due_at": null,
      "labels": [],
      "label_ids": [],
      "created_at": 1794166596415,
      "updated_at": 1794166596504,
      "relations": [],
      "comments": [
        {
          "id": "01a1bca9-a3c3-76a6-a32d-15bb86ff7b01",
          "key": "DEMO-1#1",
          "task_id": "01a1bca9-a33f-7446-a71e-18bfd0d1934c",
          "text": "Starting on the auth middleware.",
          "created_at": 1794166596547,
          "updated_at": 1794166596547
        }
      ]
    }
    

    The task is in In Progress. Move it to Review when the tests pass.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Context rot and abandoned tasks kill productivity. This skill integrates Zinn project management directly into your development workflow, ensuring every code change is backed by a task and every blocker is documented. It stops you from losing track of follow-up work by managing the lifecycle of tasks from discovery to review without leaving your terminal or IDE.

    What it does

    • Project Discovery identifies the correct project and database via zinn info to ensure work is recorded in the right place.
    • Task Lifecycle Management moves tasks through custom project columns to reflect real-time progress.
    • Context Preservation records decisions, verification results, and blockers as concise task comments for handoffs.
    • Relation Mapping links follow-up work to parent tasks using dependencies to maintain a clear work graph.
    • CLI Drift Check compares the installed CLI with the version this skill was reviewed against when a command or result contradicts the instructions.

    How it works

    1. Resolve project by inspecting zinn.local.json or querying the Zinn CLI for the active database.
    2. Sync task state by fetching the full task JSON, including comments and relations, before starting implementation.
    3. Update workflow by moving the task to the "In Progress" column and adding dated progress comments.
    4. Handoff by recording final verification results and moving the task to the project's specific review column.

    Frameworks & tools

    This skill requires the zinn CLI (@zinn-dev/cli) installed and configured. It was reviewed against @zinn-dev/cli 0.44.0. If zinn --version differs, check zinn --help and the skill source for drift.

    Why this beats prompting it yourself

    Generic prompts often hallucinate column names or fail to read full task comments before making edits. This skill enforces a strict "read-before-write" workflow and correctly handles CLI exit codes and JSON parsing for reliable state management.

    Use cases

    • Resuming complex features by pulling dated decision logs from task comments.
    • Creating linked follow-up tasks for technical debt discovered during a PR.
    • Transitioning tasks to review with automated verification summaries.
    • Coordinating multi-agent work by checking task ownership in the project board.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Agents & Orchestration.

    Requires the Zinn CLI installed and configured. Does not authorize or perform git commits. Does not create projects on its own; it asks when the project is ambiguous. Does not isolate shared working trees in parallel agent environments.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Free to use

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 8 days ago

    • Free with an Agensi account

    Software
    @zinn-dev/cli

    Permissions

    Terminal / Shell
    Read Files
    Write Files
    Network Access
    Listed8 days ago

    What's inside

    Frequently Asked Questions

    The zinn skill streamlines project management by allowing you to manage task lifecycles, log blockers, and track dependencies directly through your AI agent without switching between your IDE and a browser-based board.

    The skill requires the Zinn CLI (`@zinn-dev/cli`) installed and configured. It was reviewed against 0.44.0; if `zinn --version` differs, check `zinn --help` and the skill source for drift.

    Yes. The skill resolves the project with `zinn info --json` and `zinn project list --json`, reads the project's columns with `zinn project column list <project-key> --json`, and links tasks with dependency or related relations when follow-up work appears.

    The skill tells the agent to compare the installed CLI with the version the skill was reviewed against when a command is unavailable or its results contradict the instructions, then check the source for drift. It is a reactive check, not an automatic sync.

    No. The skill tracks project state and task context. It does not authorize or perform git commits, pull requests or other repository-level write actions, so you keep control of the codebase.

    The skill asks the agent to read the full task, including its comments and relations, and the project's columns before changing anything. That makes it less likely to guess a column name or miss context, compared with a prompt that starts writing immediately.

    New in Agents & Orchestration

    Free