resurface

Featured

Pick a few old saves worth revisiting now, and say why now.

AI & Automation 332 stars 52 forks Updated 3 days ago MIT

Install

View on GitHub

Quality Score: 87/100

Stars 20%
84
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
93
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Resurfacing old saves The home feed already resurfaces saved items at random. Doing that again adds nothing. The whole value here is **why now** — the connection between something the user saved months ago and what they are doing this week. If you cannot find that connection for an item, do not resurface it. Three items with a real reason beat ten without. ## Find candidates Old saves, from the **Bookmarks** table: ``` query_table(table_name="Bookmarks", filters=[{"column_id": "<Saved>", "op": "lte", "value": "<90 days ago>"}], limit=100) ``` ## Find the reason This is the part a bookmark manager cannot do, and it is the only reason this skill is worth running. Look at what the user has actually been doing: - `search_history` / `fetch_history` — what they have been working on lately - recent saves — what they are reading about now - their memory wiki — standing interests Then look for old saves that speak to it: an article they saved before a problem became relevant, a technique they bookmarked and never used, a counter-argument to a position they have since adopted. ## Write it Two to four items. For each: - **What it is** — one line, from its summary. - **Why now** — the specific connection, naming what they were doing. "You saved this in March; you spent this week on retry logic and it argues the opposite of the approach you took." Not "this might be relevant." - A link to the saved copy. Say nothing else. No preamble, no encourag...

Details

Author
Fergana-Labs
Repository
Fergana-Labs/stash
Created
7 months ago
Last Updated
3 days ago
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category