The AI second brain
for your bookmarks.

---
name: linkcrypt-second-brain
description: Search, save, tag, and summarize the user's Link Crypt library over the getlinkcrypt.com REST API. Use this whenever the user asks about saved links, research sources, bookmarks, URLs, second-brain context, PARA tags, or adding a link to their library.
---

# Link Crypt API Skill

Link Crypt is the user's private URL layer for their AI second brain. It stores links, titles, descriptions, domains, tags, favorites, and read state. Use it to retrieve sources, save new URLs, and keep research organized.

## Configuration

Base URL: https://getlinkcrypt.com/api/v1
Auth header: Authorization: Bearer YOUR_LINKCRYPT_API_KEY
Content type: application/json

The user can create an API key in Link Crypt > Preferences > API keys. Never expose or commit the real key. Prefer an environment variable such as LINKCRYPT_API_KEY when your runtime supports it.

## When to use this skill

Use Link Crypt when the user asks to:
- Find, search, or summarize saved links.
- Retrieve sources for a topic, project, article, or research question.
- Save a URL into their library.
- Add or clean up tags.
- Build PARA-style views such as project:launch, area:health, resource:ai, or archive:2025.
- Feed a writing, coding, or research task with links the user has already saved.

## Search patterns

Use GET /search for keyword and advanced search:

curl -s "https://getlinkcrypt.com/api/v1/search?q=tag:ai%20domain:arxiv.org&limit=10" \
  -H "Authorization: Bearer YOUR_LINKCRYPT_API_KEY"

Useful query syntax:
- tag:ai
- domain:github.com
- title:rust
- description:embeddings
- tag:project:launch domain:docs.example.com

Use GET /links for browsing or filtering:

curl -s "https://getlinkcrypt.com/api/v1/links?tags=ai,research&limit=20" \
  -H "Authorization: Bearer YOUR_LINKCRYPT_API_KEY"

Use GET /links/:id for a specific saved link.

## Usage limits and efficiency

API calls are not unlimited. Be a careful token and request budget user:

- Prefer one targeted search over several broad searches.
- Use specific filters such as tag:, domain:, title:, and limit=5-10 before asking for more.
- Do not repeatedly fetch the same link or tag list in one conversation; reuse results already available in context.
- When the user asks a broad question, search once, summarize the top results, then ask whether to continue.
- Request only the fields or result count needed for the task when the API supports it.
- Batch related work: collect several URLs/tags from the user, then save or tag them in a small number of calls.
- Avoid calling stats, digest, or maintenance endpoints unless the user asks for analysis or cleanup.
- If you hit a rate or monthly usage limit, explain that API usage is metered and suggest narrowing the task or trying again later.

## Save a link

When saving a URL, include tags if the user provides them or if obvious from context. Prefer the user's existing tag style.

curl -s -X POST "https://getlinkcrypt.com/api/v1/links" \
  -H "Authorization: Bearer YOUR_LINKCRYPT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "url": "https://example.com/article",
    "title": "Optional title",
    "description": "Optional short note",
    "tags": ["resource:ai", "research"]
  }'

## Tags

List tags:

curl -s "https://getlinkcrypt.com/api/v1/tags" \
  -H "Authorization: Bearer YOUR_LINKCRYPT_API_KEY"

Add a tag to a link:

curl -s -X POST "https://getlinkcrypt.com/api/v1/links/LINK_ID/tags" \
  -H "Authorization: Bearer YOUR_LINKCRYPT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"name":"project:launch"}'

## Analysis

Get library stats:

curl -s "https://getlinkcrypt.com/api/v1/analyze/stats" \
  -H "Authorization: Bearer YOUR_LINKCRYPT_API_KEY"

Create a digest:

curl -s -X POST "https://getlinkcrypt.com/api/v1/analyze/digest" \
  -H "Authorization: Bearer YOUR_LINKCRYPT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"period":"week"}'

## Behavior rules

- Cite saved links by title and URL when using them as sources.
- When search returns many results, summarize the top results and ask whether the user wants a narrower filter.
- Reuse the user's existing tags whenever possible.
- Do not delete links or tags unless the user explicitly asks for deletion.
- If an API request fails, report the status/error and suggest checking the API key or subscription state.
- Keep API keys out of transcripts, commits, screenshots, and shared documents.

## Example user prompts

- "Search my Link Crypt for links about vector databases and summarize the strongest sources."
- "Save this URL to Link Crypt with tags project:launch and resource:marketing."
- "Find everything I saved from arxiv.org about agents."
- "Show my most-used tags and suggest a PARA cleanup."
- "Use my saved links to draft a reading list for this project."