OpenParable
Skip to content
← Back to skills

Huntly Knowledge Base

Apps & Automation
huntly-knowledge-base

Huntly Knowledge Base is an Agent Skill for apps & automation published in the lcomplete/huntly repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

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".

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/lcomplete/huntly/blob/HEAD/skills/huntly-knowledge-base/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/huntly-knowledge-base, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

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) 
TypeConditionOrder By
My Listlibrary_save_status = 1saved_at
Archivelibrary_save_status = 2archived_at
Starredis_starred = 1starred_at
Read Lateris_read_later = 1read_later_at

Main Table: page

FieldDescription
id, title, urlBasic identifiers
description, contentText content (content is HTML)
author, author_screen_nameAuthor info
domain, site_nameSource website info
thumb_urlThumbnail image URL
library_save_status0/NULL=unsaved, 1=My List, 2=Archive
is_starred, is_read_later, is_mark_readBoolean flags
connector_typeNULL=web, 1=RSS, 2=GitHub
connector_idFK → connector
content_type0=history, 1=tweet, 2=markdown, 3=quoted tweet, 4=snippet
collection_idFK → collection
created_at, saved_at, starred_at, archived_at, read_later_atTimestamps
highlight_countStatistics
page_json_propertiesJSON 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, userProfileImageUrl
  • fullText, createdAt
  • quoteCount, replyCount, retweetCount, favoriteCount, viewCount
  • medias[] (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, homepage
  • stargazersCount, forksCount, watchersCount
  • topics[], updatedAt

Related Tables

  • page_highlight: page_id, highlighted_text, created_at
  • connector: id, name, type (1=RSS, 2=GitHub), subscribe_url, folder_id
  • collection: id, name, parent_id
  • folder: id, name (RSS folder organization)