huntly-knowledge-base
Access saved content and reading history from the Huntly sqlite knowledge base.
Install
mkdir -p .claude/skills/huntly-knowledge-base && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/4635" && unzip -o skill.zip -d .claude/skills/huntly-knowledge-base && rm skill.zipInstalls to .claude/skills/huntly-knowledge-base
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
This skill should be used when the user asks about their saved content, bookmarks, starred articles, highlights, reading history, tweets, or knowledge base in Huntly sqlite database. Triggers include "我的收藏", "知识库", "我保存了什么", "my bookmarks", "my library", "what did I save".Key capabilities
- →Query Huntly SQLite database
- →Retrieve saved library content
- →Filter content by save status or star status
- →Access tweet and GitHub metadata
How it works
The skill queries a local SQLite database using specific filters for library status and content types to retrieve user-saved information.
Inputs & outputs
When to use huntly-knowledge-base
- →Search my bookmarks
- →Retrieve saved articles
- →Look up reading history
- →Find highlighted content
About this skill
Huntly Knowledge Base
Access user's personal knowledge base stored in Huntly via SQLite database.
REQUIRED: Get Database Path First
STOP immediately after this skill triggers. Ask the user for the database path before ANY action.
"I need to access your Huntly database. What is the path to your db.sqlite file?"
Examples:
- /Users/username/Library/Application Support/Huntly/db.sqlite
- ~/Library/Application Support/Huntly/db.sqlite
- /home/username/.config/Huntly/db.sqlite"
DO NOT proceed with any queries until you have the database path. DO NOT auto-search for the file.
Core Rule: Library Content First
By default, query Library content (user actively saved), not auto-collected content.
Library Filter:
WHERE library_save_status IN (1, 2)
| Type | Condition | Order By |
|---|---|---|
| My List | library_save_status = 1 | saved_at |
| Archive | library_save_status = 2 | archived_at |
| Starred | is_starred = 1 | starred_at |
| Read Later | is_read_later = 1 | read_later_at |
Main Table: page
| Field | Description |
|---|---|
id, title, url | Basic identifiers |
description, content | Text content (content is HTML) |
author, author_screen_name | Author info |
domain, site_name | Source website info |
thumb_url | Thumbnail image URL |
library_save_status | 0/NULL=unsaved, 1=My List, 2=Archive |
is_starred, is_read_later, is_mark_read | Boolean flags |
connector_type | NULL=web, 1=RSS, 2=GitHub |
connector_id | FK → connector |
content_type | 0=history, 1=tweet, 2=markdown, 3=quoted tweet, 4=snippet |
collection_id | FK → collection |
created_at, saved_at, starred_at, archived_at, read_later_at | Timestamps |
highlight_count | Statistics |
page_json_properties | JSON string with extra data (see below) |
page_json_properties Field
JSON string containing type-specific metadata:
For tweets (content_type=1): TweetProperties
tweetIdStr,userIdStr,userName,userScreeName,userProfileImageUrlfullText,createdAtquoteCount,replyCount,retweetCount,favoriteCount,viewCountmedias[](mediaUrl, type, videoInfo),hashtags[],urls[],userMentions[]quotedTweet,retweetedTweet(nested TweetProperties)card(title, description, imageUrl, url, domain)
For GitHub repos (connector_type=2): GithubRepoProperties
name,nodeId,defaultBranch,homepagestargazersCount,forksCount,watchersCounttopics[],updatedAt
Related Tables
page_highlight:page_id,highlighted_text,created_atconnector:id,name,type(1=RSS, 2=GitHub),subscribe_url,folder_idcollection:id,name,parent_idfolder:id,name(RSS folder organization)
When not to use it
- →When the database path is not provided by the user
- →When searching for auto-collected content instead of library content
Prerequisites
Limitations
- →Requires user to provide the database path
- →Does not auto-search for the database file
How it compares
It provides direct programmatic access to local Huntly data, bypassing the need for manual database browsing.
Compared to similar skills
huntly-knowledge-base side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| huntly-knowledge-base (this skill) | 1 | 5mo | No flags | Intermediate |
| recall | 1 | 6mo | Review | Beginner |
| braindump | 7 | 5mo | No flags | Beginner |
| super-search | 10 | 2mo | Review | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
recall
parcadei
Query the memory system for relevant learnings from past sessions
braindump
huytieu
Quick capture of raw thoughts with intelligent domain classification and competitive intelligence extraction
super-search
supermemoryai
Search your coding memory. Use when user asks about past work, previous sessions, how something was implemented, what they worked on before, or wants to recall information from earlier sessions.
sql-research
tidyverse
Guide for researching SQL syntax and behavior for database backends. Use when you need to research how a SQL function, command, or feature works in a specific database before implementing it in dbplyr.
mem-search
thedotmack
Search claude-mem's persistent cross-session memory database. Use when user asks "did we already solve this?", "how did we do X last time?", or needs work from previous sessions.
baoyu-danger-x-to-markdown
JimLiu
Converts X (Twitter) tweets and articles to markdown with YAML front matter. Uses reverse-engineered API requiring user consent. Use when user mentions "X to markdown", "tweet to markdown", "save tweet", or provides x.com/twitter.com URLs for conversion.