---
name: trove-organize-library
description: Propose a useful collection structure for the Trove bookmarks you can inspect, then organize approved items without claiming you reviewed the entire library.
---

# Organize a Trove library

Use this with the Trove MCP connector enabled. This skill is a workflow, not a way to bypass Trove permissions. Ask the user before creating, moving, archiving, or retagging anything.

## Scope and limits

- Start with `list_tags` and `list_collections`. `list_bookmarks` can show at most 100 recent bookmarks and has no pagination. `search_bookmarks` requires a query and can page matching results, but broad searches cannot guarantee coverage of every save. Never claim a complete library audit from these tools alone.
- State the exact subset you inspected and compare it with `list_tags.totalBookmarks` when available. If the user wants a complete reorganization and the visible subset is incomplete, ask for a user-provided export or a narrower project/collection scope before making a whole-library plan.
- Use titles, previews, and collection descriptions to classify. Tags can help but may be too sparse to define themes on their own.
- Put each bookmark in the most specific relevant child collection. `search_in_collection` on a parent includes nested children, so avoid duplicating a bookmark in both parent and child solely for search.

## Workflow

1. Inspect the in-scope saves and existing collection tree. Keep a table of bookmark URL, proposed collection, optional project collection, and reason. Flag uncertain placements rather than guessing.
2. Propose no more than a handful of clear top-level themes. Show the tree with counts and examples. Ask the user to approve names, membership, and any proposed archiving or intent tags before writing.
3. For approved new collections, call `create_collection` or `create_nest_collection`. Existing collections should be reused. Moving an existing collection with `assign_nested_collection` can change its privacy; stop for any user confirmation the tool requires.
4. Add a bookmark with `assign_bookmark_collections {url, collection_name}`. Its default is additive; do not use `mode: "move"` unless the user explicitly requests removing its other memberships. Use `remove_bookmark_from_collection` only for an approved correction.
5. Add an `intent-try`, `intent-apply`, `intent-think`, `intent-learn`, or `intent-watch` tag with `update_bookmark` only if the user approved intent tagging. Archive only items the user approved for archiving.
6. Work in small, resumable batches. Record completed URLs and actions in a table or file if the client supports one. If a tool is temporarily unavailable, stop, report what succeeded, and leave a clear remainder; do not retry in a loop.
7. Verify the affected collections and a sample of updated bookmarks. Report how many saves were inspected, changed, skipped, and still outside the inspected subset.

## Useful follow-up

Once the tree is approved, use `trove-slot-new-saves` to file recent additions and `trove-make-use` to turn saved material into a reading queue or synthesis.