---
name: trove-slot-new-saves
description: Review recent Trove saves, file clear matches into an existing collection tree, and ask before creating collections or changing ambiguous items.
---

# Slot recent Trove saves

Use this with the Trove MCP connector and an existing collection tree. If the library has no useful tree yet, start with `trove-organize-library`.

## Ground rules

- `list_bookmarks {limit: 100}` shows at most the 100 most recent bookmarks; it does not accept a date or offset. Compare each returned save's created date with the requested time window. If more than 100 may have been saved since the last run, say the review may be incomplete.
- `search_bookmarks` supports date filters but requires a nonempty search query, so it is not a reliable exhaustive date-only feed.
- Match against existing leaf collections using names, descriptions, and a few representative saves. A bookmark may also go into a relevant project collection. Keep assignments additive.
- Clear matches to an existing collection may be filed after the user has asked you to file new saves. Ask before ambiguous placements, creating or re-parenting collections, removing memberships, or archiving.

## Workflow

1. Fetch the latest visible saves and the collection tree with `list_collections` (page top-level collections using `skip`). Exclude saves already correctly filed.
2. Classify each remaining save as a clear match, ambiguous, or unsorted. Show the uncertain cases with a proposed destination and short reason. Ask the user to resolve those cases together.
3. File approved clear matches using `assign_bookmark_collections {url, collection_name}` with its additive default. Use exact collection names from Trove. Do not use `mode: "move"` unless explicitly requested.
4. If the user wants intent tags, use `update_bookmark {url, tags_add: ["intent-try"]}` or the relevant intent. Do not add duplicate intent tags.
5. Propose a new child collection only when a meaningful cluster has formed; create it only after approval. Use `remove_bookmark_from_collection` to correct a mistaken assignment.
6. Report filed, confirmed, unsorted, and skipped counts, the latest date reviewed, and any coverage limit. On a temporary tool failure, stop and report the remaining URLs instead of looping retries.

## Next step

If several saves are tagged `intent-try`, ask whether the user wants a short weekly queue using `trove-make-use`.