← ClaudeAtlas

loupe-boardlisted

Use when working a project board in the Loupe app through the loupe MCP, calling board_columns, card_create, card_list, card_get or card_update, writing a card, moving a card between columns, linking a document to a card, or linking a pull request to a card.
ubermuda/loupe · ★ 2 · AI & Automation · score 65
Install: claude install-skill ubermuda/loupe
# Working a Loupe board Each project in Loupe has one board, and each board has its own columns. A card carries a title, a Markdown body, a type, a status and a reporter. The status is the slug of the column the card sits in. The tools act on the project your token is bound to. An instance can switch the board off, and every tool then answers "The board is switched off on this instance." ## Read the columns before you name one Call `board_columns` before you pass a `status` to any tool. Use the slugs it returns. `card_list` returns the same list in `columns`, so a session that has read the board already holds them. Each column carries these fields: | Field | Meaning | |---|---| | `slug` | The value you pass as `status`. | | `label` | The name a person sees on the board. | | `terminal` | `true` for a column that holds finished work. A board has at least one. | | `default` | `true` for the one column where a card created with no `status` lands. | A new board starts with `backlog` (default), `next`, `in-progress` and `done` (terminal). The project owner can add, rename, reorder, flag and delete columns, so never assume those four. A rename that changes the slug breaks every outside reference to the old slug. A slug you read in an earlier session can be gone. An unknown slug is refused, and the error lists the slugs the board has. No tool writes a column. Ask the owner when the board needs a column it does not have. This skill names a column by its role. Match each role