用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt;运行前请先检查来源。
npx skills add https://github.com/Fergana-Labs/stash --skill overview命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地?可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | overview |
| description | Chart what's in the library — topics, sources, saves over time — and say what the shape means. |
| when_to_use | When the user asks for an overview of their saves, what they've been reading about, a breakdown by topic, or charts of their library. |
| version | 1 |
A chart on its own is decoration. Every chart here answers a question the user would otherwise have to ask, and you say the answer in words next to it.
From the Bookmarks table via query_table. You need the whole table, not
a page — read total from the first call and page with offset until you
have it. Counting 100 of 4,000 saves and calling it a distribution is worse
than not charting at all.
Columns you'll use: Saved (ISO date), Topics (array), Site, Type,
Status.
Skip any chart the data can't support. Fewer than ~20 saves, or fewer than three distinct topics, means the honest output is a sentence, not a chart.
Under each chart, one or two sentences of what it shows — the actual reading, not a caption. "Two thirds of your saves are from three domains" is worth writing. "This chart shows saves by domain" is not.
Close with what stands out across all four: a topic that stopped, a source that dominates, a burst that maps to something they were building.