agentleFS
eugenezhangco-speceugenezhangco-spec/athena/.claude/skills/bookmark/SKILL.md

bookmark

Skill0 starsChanged 7 months agoMITView on GitHub

Save links, articles, videos, and resources to the user's Notion Bookmarks database with auto-detected source and an optional note. Use when the user shares a URL with context like "bookmark this", "save this link", "save for later", "add to bookmarks", "remember this link", or forwards content they want to revisit.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 7 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If that file does not exist or does not contain those keys, pause and ask the user for the database ID (or suggest running the onboard …

    line 25
  2. Distinctive:

    If the user's database uses different property names, adapt to what they have — do not fail the save over naming differences.

    line 38
  3. Distinctive:

    Write a descriptive Name. If the user provided context, use that.

    line 50
  4. Distinctive:

    If the user said why they are saving it, capture that in Note.

    line 51
  5. Very specific:

    Create the entry via mcp__notion__notion-create-pages (or equivalent) using the database ID from personal/notion-databases.md.

    line 53
  6. Distinctive:

    Always auto-detect the Source from the URL.

    line 59
  7. Distinctive:

    If the user provides no context, save with an empty Note.

    line 60
  8. Distinctive:

    If the user says "remind me about this", set Reminder Set to true.

    line 61

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Skill: Bookmark

When to Use

  • User shares a link they want to save for later
  • User says "bookmark this", "save this link", "save for later", "add to bookmarks", "remember this link"
  • User shares a URL with a note about why it matters
  • User forwards content from social media they want to revisit

Prerequisites

This skill writes to a Notion database. The user must have configured their bookmarks database in personal/notion-databases.md with an entry like:

bookmarks_database_id: <user's Notion database ID>
bookmarks_data_source: collection://<data source id>
bookmarks_parent_page: <parent page id>

If that file does not exist or does not contain those keys, pause and ask the user for the database ID (or suggest running the onboard skill to wire Notion up).

Expected Notion Schema

PropertyTypeOptions
NametitleDescriptive title of the content
URLurlThe link
SourceselectYouTube, Instagram, Twitter, LinkedIn, TikTok, Web
NotetextWhy it was saved, key context
Date SaveddateAuto-set to today
Reminder SetcheckboxDefault false

If the user's database uses different property names, adapt to what they have — do not fail the save over naming differences.

Steps

  1. Extract the URL from the user's message.
  2. Auto-detect the Source from the URL domain:
    • youtube.com / youtu.be → YouTube
    • instagram.com → Instagram
    • twitter.com / x.com → Twitter
    • linkedin.com → LinkedIn
    • tiktok.com → TikTok
    • everything else → Web
  3. Write a descriptive Name. If the user provided context, use that. Otherwise derive from the URL. Never fabricate.
  4. If the user said why they are saving it, capture that in Note.
  5. Set Date Saved to today. Reminder Set defaults to false.
  6. Create the entry via mcp__notion__notion-create-pages (or equivalent) using the database ID from personal/notion-databases.md.
  7. Confirm back with the saved title and source.

Rules

  • Green tier action. Save first, confirm after. No approval dance.
  • Always auto-detect the Source from the URL. Only ask if ambiguous (e.g. shortened link).
  • If the user provides no context, save with an empty Note. Do not invent one.
  • If the user says "remind me about this", set Reminder Set to true.
  • Multiple links in one message get separate entries.

Output Format

Bookmarked:
- [Name] ([Source]) — [URL]

One line per entry. Include note summary in parentheses if one was provided.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.