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.
MCP server for interacting with the Supabase platform
같은 종류의 작업, Skill 목록과 같은 순서
| 이 항목 pensieve | timesfm | Shadowbroker | google-maps-scraper | tradingview-mcp | |
|---|---|---|---|---|---|
| 제작자 | arkohut | google-research | BigBodyCobain | gosom | atilaahmettaner |
| Skill 수 | 1 | 1 | 1 | 1 | 1 |
| GitHub 별 | 1,403 | 35,620 | 11,590 | 8,176 | 5,304 |
| 마지막 코드 변경 | 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의 Skill(지시 묶음) 1개, AI가 읽고 그대로 일해요 · MCP server가 아니에요
MCP = 손
AI를 외부 서비스나 데이터에 연결합니다(예: Notion 읽기, 청구서 만들기). 프로그램이나 서버가 실행 중이어야 합니다.
Skill = 안내서
작업 방법을 AI에게 가르치는 텍스트 파일. 어떤 서비스에도 연결되지 않습니다.
겹치는 경우도 있습니다. 도구를 부르는 스크립트가 있는 Skill도, 지식만 보내는 MCP도 있습니다. 하려는 작업을 기준으로 고르세요.
Claude CodeCodexOpenCode
제작자 README와 repo 폴더 기준
GitHub account arkohut (person), 8 years old
★ 1,403 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가 따르는 지시예요. 설치 전에 파일을 읽고, 믿을 수 있는 제작자 것만 설치하세요.
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가 따르는 지시예요. 설치 전에 파일을 읽고, 믿을 수 있는 제작자 것만 설치하세요.
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만 쓸 수 있습니다
이 Skill을 ChatGPT에서 쓰려면 위 방법대로 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가 따르는 지시예요. 설치 전에 파일을 읽고, 믿을 수 있는 제작자 것만 설치하세요.
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가 따르는 지시예요. 설치 전에 파일을 읽고, 믿을 수 있는 제작자 것만 설치하세요.
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-searchSkill을 읽을 수 있는 다른 앱용입니다. 이 문장에는 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
Gemini CLI, GitHub Copilot 같은 다른 Agent Skills 지원 앱은 폴더가 달라요. 그 앱 안내를 보고 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질문하고, 팁을 나누고, 안 되는 점을 알려 주세요. "도움이 됨"이 많은 순서예요.