flomo 推文入库
Skill9 starsChanged 11 days agoMITView on GitHub
用户丢来推文/X 链接,要简介、要粘贴进 flomo、或说「写到 flomo」时使用。产出纯文本简介+裸链接,写入时必带 #Grokbot/Import。
In this repository6 other files it gives its agents.
- digital-garden-onboardingSkill
- getting-startedSkill
- obsidian-apprentice-rulesSkill
- Obsidian 批量剪藏Skill
- orphan-notesSkill
- related-notesSkill
The file
Files
flomo 推文入库
把用户给的推文 / X 链接整理成可粘贴、可入库的纯文本,并按需写入 flomo。
附加价值(先守这条)
不要只把推文原文再抄一遍。每条要有一句简介(这条在讲什么、对用户当下事有什么用),再附可点开的原链接。简介是新信息;链接是回源。
何时用
- 用户丢一批
x.com/.../status/...链接,要简介 - 用户说要粘贴到 flomo、纯文本、不要超链接形式
- 用户说「写到 flomo / 存进 flomo」
输出与写入格式(硬规则)
- 纯文本:不要 Markdown 超链接
[文字](url);标题式加粗也可省,方便整段复制 - 每条结构:
- 一行简介(可带一句用途)
- 下一行推文原链接(完整
https://x.com/.../status/...,去掉追踪参数?s=?a=等) - 若推文里还有重要外链(文档、教程站),再单独一行写「文档:url」之类,仍用裸链接
- 条与条之间空一行
- 写入 flomo 时:正文必须包含标签
#Grokbot/Import(与主题标签并存,例如#Grokbot/长沙分享);先get_format_guide,再用官方 flomo 连接器创建/更新 - flomo 只支持有限格式(加粗、高亮、下划线、列表);不要依赖标题、引用、代码块、Markdown 链接语法
步骤
- 从用户消息里抽出全部 status id / 链接
- 用 X 公共读取拉取正文(长文看
note_tweet/ Article 字段),确认作者与要点 - 按用户给出的顺序写简介;聊天里回复时若用户要粘贴 flomo,直接给纯文本块
- 用户明确要求写入 flomo 时:一条笔记收一批(除非用户要求一条一记);标签至少
#Grokbot/Import;写完把 flomo 原链(https://v.flomoapp.com/mine/?memo_id=...)用裸链接或聊天可点链接回给用户 - 不要擅自点赞、回复、转发;只读推文、只写用户自己的 flomo
边界
- 不编造推文内容;拉不到就标明哪条失败
- 不把情绪隐私类内容擅自扩写进公开向素材
- 非用户亲身经历,简介里不要写成「他做过」
迭代
改标签名、简介语气、一条一记还是一批一记:优先改本 skill,再让例程或口头习惯跟着变。
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

