skills/huntly-knowledge-base/SKILL.md
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".
npx skillsauth add lcomplete/huntly huntly-knowledge-baseInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Access user's personal knowledge base stored in Huntly via SQLite database.
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.
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 |
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 FieldJSON 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[], updatedAtpage_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)development
Maintainer-only workflow for handling GitHub Secret Scanning alerts on OpenClaw. Use when Codex needs to triage, redact, clean up, and resolve secret leakage found in issue comments, issue bodies, PR comments, or other GitHub content.
development
Maintainer workflow for OpenClaw releases, prereleases, changelog release notes, and publish validation. Use when Codex needs to prepare or verify stable or beta release steps, align version naming, assemble release notes, check release auth requirements, or validate publish-time commands and artifacts.
development
Run, watch, debug, and extend OpenClaw QA testing with qa-lab and qa-channel. Use when Codex needs to execute the repo-backed QA suite, inspect live QA artifacts, debug failing scenarios, add new QA scenarios, or explain the OpenClaw QA workflow. Prefer the live OpenAI lane with regular openai/gpt-5.4 in fast mode; do not use gpt-5.4-pro or gpt-5.4-mini unless the user explicitly overrides that policy.
development
End-to-end Parallels smoke, upgrade, and rerun workflow for OpenClaw across macOS, Windows, and Linux guests. Use when Codex needs to run, rerun, debug, or interpret VM-based install, onboarding, gateway smoke tests, latest-release-to-main upgrade checks, fresh snapshot retests, or optional Discord roundtrip verification under Parallels.