Firebase MCP
Gives AI development tools Firebase-specific capabilities and expertise.
A passive recording project allows you to have complete control over your data. Automatically take screenshots of all your screens, index them, and save them locally.
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/skills/arkohut-pensieve)在同一工作中把 AI 连到服务的 MCP
Gives AI development tools Firebase-specific capabilities and expertise.
同类工作,排序与 Skill 列表相同
| 本项 pensieve | timesfm | Shadowbroker | google-maps-scraper | tradingview-mcp | |
|---|---|---|---|---|---|
| 作者 | arkohut | google-research | BigBodyCobain | gosom | atilaahmettaner |
| Skill 数 | 1 | 1 | 1 | 1 | 1 |
| GitHub 星标 | 1,405 | 35,629 | 11,602 | 8,209 | 5,307 |
| 最近代码更新 | 2026年7月19日 | 2026年11月13日 | 2026年11月17日 | 2026年11月15日 | 2026年11月15日 |
| 许可证 | Apache-2.0 | Apache-2.0 | AGPL-3.0 | MIT | MIT |
arkohut 提供的 1 个 Skill(指令集),AI 读取后照做 · 不是 MCP server
MCP = 手
把 AI 连到外部服务或数据,例如读取 Notion 或开发票。需要有程序或服务器在运行。
Skill = 手册
教 AI 怎么做某项工作的文本文件,不连接任何服务。
有些会重叠:少数 Skill 带有调用工具的脚本,少数 MCP 只提供知识。请从你想完成的工作出发。
Claude CodeCodexOpenCode
依据开发者 README 和 repo 中的文件夹
GitHub account arkohut (person), 8 years old
★ 1,405 stars · code last changed 2026年7月19日
No, plain text files the AI reads and follows
No scripts, so it does not go online by itself
No hooks or writes to machine settings found
Checked automatically from the repo files at commit 3e55c66 (read only, nothing was run). Not a safety guarantee: read it and decide for yourself
第一步:你用哪个 AI?
选择你用的应用,本页只显示该应用的安装方法
Uploading to claude.ai would fail: the description is over 200 characters (633). Use "Let the AI install it" instead
复制这句话,粘贴到 Claude Code 的对话中
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
重新打开 Claude Code,输入 /pensieve-search,或直接提出相关任务,Claude 会自动选用
Checked against official docs 2026年11月12日 · Source: code.claude.com
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹
git clone --depth 1 https://github.com/arkohut/pensieve.git /tmp/popnx-skill-arkohut-pensieve-3e55c66 && mkdir -p ~/.claude/skills && cp -R '/tmp/popnx-skill-arkohut-pensieve-3e55c66/skills/pensieve-search' ~/.claude/skills/pensieve-searchChatGPT 桌面应用内置 Codex,Codex 从 ~/.agents/skills 文件夹读取 Skill
在 ChatGPT 桌面应用中打开 Codex,把这句话粘贴到对话中
The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
把 pensieve-search 文件夹放到 ~/.agents/skills/pensieve-search
~ 是你的主文件夹($HOME)
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹
git clone --depth 1 https://github.com/arkohut/pensieve.git /tmp/popnx-skill-arkohut-pensieve-3e55c66 && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-arkohut-pensieve-3e55c66/skills/pensieve-search' ~/.agents/skills/pensieve-searchChecked against official docs 2026年11月15日 · Source: learn.chatgpt.com
不能使用你自己安装的 Skill,只能使用目录中插件自带的 Skill
想在 ChatGPT 中使用这个 Skill,请按上面的方法使用 ChatGPT 桌面应用
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
复制这句话,粘贴到 Codex 的对话中 · 适用于 ChatGPT 桌面应用中的 Codex、Codex CLI 和 IDE 扩展
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Codex 会自动发现新安装的 Skill;如果没有出现,请重启 Codex · 使用方法:在 ChatGPT 中输入 @ 并选择 Skill · 在 Codex CLI 或 IDE 扩展中运行 /skills,或输入 $ 加 Skill 名称
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹
git clone --depth 1 https://github.com/arkohut/pensieve.git /tmp/popnx-skill-arkohut-pensieve-3e55c66 && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-arkohut-pensieve-3e55c66/skills/pensieve-search' ~/.agents/skills/pensieve-search复制这句话,粘贴到 Cursor 的对话中
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
在 Cursor 的 Agent 聊天中输入 / 并选择 pensieve-search
Checked against official docs 2026年11月12日 · Source: cursor.com
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹
git clone --depth 1 https://github.com/arkohut/pensieve.git /tmp/popnx-skill-arkohut-pensieve-3e55c66 && mkdir -p ~/.cursor/skills && cp -R '/tmp/popnx-skill-arkohut-pensieve-3e55c66/skills/pensieve-search' ~/.cursor/skills/pensieve-search适用于其他能读取 Skill 的应用。这句话列出了 Claude Code、Codex 和 Cursor 的路径,AI 会按你的应用选择 · Copy this sentence into the app’s chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Checked against official docs 2026年11月12日 · Source: code.claude.com, learn.chatgpt.com, cursor.com
其他支持 Agent Skills 的应用(如 Gemini CLI、GitHub Copilot)使用不同文件夹,请查看该应用的指南,再把含 SKILL.md 的文件夹复制过去。
已于 2026年11月11日 对照 Claude Code、Codex 和 Cursor 官方指南核实 skill 文件夹
✓ 命令已检查 2026年11月17日
以下文字来自开发者的 repo,不是 PopNx MCP 的指令
显示前 8,000 个字符 · 在 GitHub 打开完整文件
---
name: pensieve-search
description: Search the user's local Pensieve screenshot archive by text, app, or time range. Use when the user asks to find a screenshot ("find that thing I looked at last week", "show me when I was working on the Mastra integration", "find screenshots of the YouTube video about X"), or to locate a specific moment in time across captured activity. Returns ranked entity_ids with filepaths, timestamps, OCR snippets, and VLM-extracted structured metadata (app, topic, workspace). Can open the image locally for the user. Skip when the user wants aggregated stats, time-series analytics, or cross-day project rollups — those need separate tools.
---
# Pensieve Search Skill
Pensieve (`memos`) continuously captures screenshots and indexes them. This skill teaches you to query that index over its HTTP API.
## Where the data lives
- **Server**: `http://127.0.0.1:8839` by default (config: `server_host` / `server_port`).
- Override with `MEMOS_SERVER_HOST` / `MEMOS_SERVER_PORT` env vars or `~/.memos/config.yaml` if the user has a non-default setup. Confirm with the user if the default doesn't respond.
- **Screenshots on disk**: `~/.memos/screenshots/YYYYMMDD/<entity>.webp`. The API returns `filepath` directly so you don't have to compute it.
- **Web UI** (same server, browser-friendly):
- **Search page** (mirrors API filters as URL params): `http://127.0.0.1:8839/?q=...&start=...&end=...&app_names=...&library_ids=...` — you should always offer this URL in your reply so the user can click and verify results visually.
- **Entity detail page**: `http://127.0.0.1:8839/entities/<id>` — opens one specific screenshot in context with its metadata. Offer this for any hit you cite.
- **Config page**: `http://127.0.0.1:8839/config` — surface this if the user asks about settings.
## Pre-flight check
Before the first query in a session, verify the server is up:
```bash
curl -s -o /dev/null -w "%{http_code}\n" "http://127.0.0.1:8839/api/search?q=test"
```
`200` means good. `000` or connection-refused means memos isn't running — tell the user to start it (`memos serve` or system-service).
**Always quote the URL** — the `?` and `&` are zsh glob characters and will fail with `no matches found` if unquoted. Every `curl` example below assumes a quoted URL.
## The endpoint
```
GET /api/search
```
Parameters:
| Param | Type | Notes |
|---|---|---|
| `q` | string | Full-text query (jieba-tokenized; works for Chinese + English mixed). Empty `q=""` returns recent screenshots without ranking. |
| `start`, `end` | int (UNIX seconds, UTC) | Time window on `file_created_at`. Both required together. |
| `app_names` | string | Comma-separated `active_app` values, e.g. `"Google Chrome,iTerm2"`. |
| `library_ids` | string | Comma-separated; usually leave unset to query all. |
| `limit` | int 1..200 | Default 48. Use 10–20 for casual queries, 200 only when scanning. |
| `facet` | bool | Include `facet_counts` (per-app counts), `date_range` (`earliest`/`latest`), and `date_buckets` (count per day or month, see Strategy 5). Set true on broad queries to help narrow. |
| `date` | string | Bucket filter, `YYYY-MM` or `YYYY-MM-DD`. Intersected with `start`/`end`. |
Returns `SearchResult { hits: [...] }`. Each hit:
```json
{
"document": {
"id": "12345",
"filepath": "/Users/.../screenshots/20260423/00001.webp",
"file_created_at": "2026-04-23T04:18:21+00:00",
"tags": [],
"metadata_entries": [
{"key": "active_app", "value": "iTerm2", "source": "..."},
{"key": "active_window", "value": "✳ Debug memos service background job issue", "source": "..."},
{"key": "ocr_result", "value": "...long JSON of OCR boxes...", "source": "ocr"},
{"key": "structured_vlm_v1_qwen3_6_35b", "value": {"primary": {"app": "Claude Code", "title_or_topic": "...", "what": "...", "workspace": "memos"}}, "source": "structured_vlm"},
...
]
}
}
```
The `metadata_entries` is the goldmine — the VLM-extracted structured fields (`primary.app`, `primary.title_or_topic`, `primary.what`, `primary.workspace`) live inside the `structured_vlm_v1_*` entry's `value`. **In `/api/search` hits the `value` is a parsed JSON object, not a string** — access fields directly with `.value.primary.what`, and do NOT pipe through `fromjson` (it errors with "only strings can be parsed"). Note the inconsistency: `/api/entities/{id}` and the `/context` endpoint (Strategy 6) return the same `value` as a **JSON string**, where you *do* need `fromjson`. The portable branch is `(.value | if type=="string" then fromjson else . end)`. The exact key suffix (e.g. `qwen3_6_35b`) varies per install — match with `select(.key | startswith("structured_vlm"))`.
**Important**: that JSON metadata is also fully tokenized into the FTS index. So `q="Claude Code Mastra workspace"` will match a screenshot whose VLM said `app=Claude Code, what="...Mastra...", workspace=...` — even if "Mastra" doesn't appear in the OCR text.
## How to query well
### Strategy 0 — look at raw results before narrowing
Resist the urge to pre-anchor on what you think the user means. A "find 最终幻想" question sounds like it's about the *game*, but the same brand lives across YouTube videos, Bilibili clips, wallpaper engines, wikis, store pages, and game launchers. The user's casual phrasing names the topic, not the surface — only the corpus knows where they actually consumed it.
So run one wide query first and let the results tell you what surfaces exist:
```bash
curl -s --get 'http://127.0.0.1:8839/api/search' \
--data-urlencode 'q=最终幻想' --data-urlencode 'facet=true' --data-urlencode 'limit=20' > /tmp/raw.json
jq -r '.hits[].document
| "\(.file_created_at) \([.metadata_entries[] | select(.key=="active_app") | .value][0] // "?") \([.metadata_entries[] | select(.key=="url") | .value // "-"][0]) \([.metadata_entries[] | select(.key=="active_window") | .value // "-"][0] | .[0:80])"' /tmp/raw.json
```
Sample output (verified on a real install):
```
2026-04-03T15:26Z Google Chrome about:blank (55) When Tifa played「Tifa's T…Rebirth🖤 Ru's Piano - YouTube
2026-04-02T15:47Z Google Chrome about:blank (55) Final Fantasy X「To Zanark… Medley | Ru's Piano - YouTube
2026-02-15T15:59Z Google Chrome https://www.bilibili.com/video/BV1K2HQzbEAy… “蒂法的审视 手机动态壁纸 wallpaper engine_哔哩哔哩_bilibili”🔊
2026-01-30T05:17Z Google Chrome https://www.bilibili.com/ 哔哩哔哩 (゜-゜)つロ 干杯~-bilibili
```
Now you know: the user doesn't play Final Fantasy — they watch **Ru's Piano** play FF themes on YouTube, and **蒂法的审视 wallpaper engine** clips on Bilibili. If you'd anchored on `q=最终幻想 game` or guessed `app_names=Final Fantasy` you'd have found nothing. The corpus revealed both the surfaces (YouTube + Bilibili) AND the user's actual relationship to the topic (music + wallpapers, not gameplay).
Now you can build **per-surface queries** anchored on each surface's stable identifier and merge the timelines.
**Anchor on stable identifiers, not free-text names**, because free-text is noisy — short or common substrings match the `library_ids=` parameter inside memos's own URL bar, and a CJK brand name often matches OCR'd filenames of unrelated downloaded videos. Stable identifiers come from the URL or the exact app name:
- Website: domain in the URL (`guancha.cn`, `youtube.com/watch?v=…`)
- Bilibili channel: UID in `space.bilibili.com/<uid>` (e.g. `10330740`)
- YouTube channel: handle in URL (`@mastra-ai`, `@RusPiano`)
- App / brand on macOS: exact `active_app` value (`iTerm2`, `Google Chrome`, `企业微信`)
Cross-check every match by filtering hits client-side on the URL or app fields — never trust the FTS hit list alone for "did the user actually visit / consume X" questions. The skill's job is to use multiple raw queries + client-side filtering to give the user a *true* answer, not to take the first FTS rank as gospel.
### Strategy 1 — conte提问、分享技巧或报告无法使用。按“有帮助”数量排序。