# You need to be skillsmaxxing
**作者**: The Startup Ideas Podcast (SIP)
**日期**: 2026-08-19T20:41:03.000Z
**来源**: [https://x.com/startupideaspod/status/2090177246179045536](https://x.com/startupideaspod/status/2090177246179045536)
---

## How to turn his AI skills into a plugin his whole team installs
Remy (AI with Remy) came back on podcast to how he runs his company on agent skills.
Most people build a great skill, then trap it on their own machine. Remy built a way to store skills in one place, ship them to every teammate, and keep every version.
This breaks down his workflow: what a skill is, why sharing them breaks, and the repo plus plugin setup that fixes it.
## A skill is an SOP for AI, saved as a markdown file.

The old way:
- Open a new chat and ask for a proposal
- Get a first result you dislike
- Re-explain the colors, the logo, the price at the bottom instead of the top
- Land on something good
- Next week, start over
The skill way: you package your way of doing things into one markdown file. Claude reads it and runs the process.
Remy ran a live demo. He typed one line: create a proposal for Greg Eisenberg for The Startup Ideas to sponsor the newsletter. Claude pulled his proposal skill and produced the branded document in one shot.
The mental model:Picture the most capable employee you ever hired. His computer holds your tools and MCPs. His instructions file gets read before every task. Behind him sits a bookshelf of SOPs.
Each skill has a name and a description at the top. That is the spine of the book. When the task calls for it, he pulls the book off the shelf and reads the whole thing.
Skills Remy built in a single week:
- Notion formatting (white space, divider lines, blue highlights)
- Brand voice (email assets, landing page copy)
- Email formatting in Resend (white space, blue buttons, logo, signature)
One good skill saves about two hours a week. Stack them and the math gets loud.
## The real problem: AI is single player

Every teammate has their own Claude or Codex setup. Someone builds something brilliant. It stays on their laptop.
Remy calls this the Microsoft Word era of skills. You built a document, you mailed it, and ten copies floated around with zero source of truth. Google Docs fixed that for documents. Skills are still waiting.
What people try first:
Zip files over Slack or email. You edit yours, theirs stays frozen. They improve theirs, you never see it. Ten copies, zero source of truth.
Google Drive, Dropbox, or Obsidian folders. Claude reads from one location: its own .claude/skills folder. Getting it to see a Drive folder takes symlinks and hacky work. It survives a small technical team. It breaks the day a junior marketer joins.
## Put every skill in a GitHub repo and make it a plugin

GitHub is Google Drive for code. That is the whole concept you need.
Remy has a repo called Team Skills, split by department: brand, content, newsletter, marketing, finance, general. That is the central source of truth.

A plugin is a bundle of skills, MCPs, and hooks. You can bundle all three or just one. His is a bundle of skills.
Under the hood it is a couple of JSON files that Claude and Codex read. In Remy's words: he has zero idea how it works, and zero need to know. He got Claude to set it up for him.
He has zero development background.
## Install it across the team
The click path:
- Open Claude Code
- Type /plugin
- Go to marketplaces
- Choose add marketplace
- Paste your GitHub repo URL
The marketplace is the app store. The plugins are the apps. Split them by department, so your copywriter installs the content plugin and skips the finance one.
Turn on auto update. That is the line that makes the whole system live. One person improves a skill, everyone receives it on the next run.
It works in Codex too. Remy runs the same plugin in both tools. Other tools remain [UNCLEAR], since he has tested only these two.
On a Claude enterprise account you get organization plugins. Your CTO builds it once and bakes it into every account, so non-technical staff stay out of the terminal entirely.
What you get for free:
- Version control, so a ruined skill reverts to an older version
- Company ownership, since the repo lives in your GitHub organization
- Continuity, so the skills stay when the employee who wrote them leaves
Remy's view: skills add enterprise value the same way SOPs do. SOPs train employees. Skills train agents to do economically valuable work.
## Keep a second repo for yourself

Remy runs a separate repo called Remy Skills. Personal sandbox, downloaded skills, and things he has yet to roll out.
What lives there:
- Inbox triage, which teaches Claude how he wants email handled
- A morning brief tied to his own apps
Why keep it, given nobody else uses it:
- One source of truth
- Cloud access, so a Hermes agent on a VPS can reach his skills
- Version control
Note on backups: about two months ago, Claude deleted Remy's .claude folder. 150 skills. 500+ hours of work. Zero backups. A repo is a working system and a parachute at the same time.
## Design skills and chains

Remy's rule: any online process is automatable with a good skill or a chain of them. The exceptions are physical, like washing dishes.
So any repeatable daily task becomes a skill. He works inside Claude or Codex and rarely opens an app front end. When a task ends and he knows it will return, he says: turn this into a skill.
When to split one skill into a chain:Ask whether you will ever want a sub-process on its own. His YouTube publish workflow is one orchestrator skill that runs three in sequence:

Publish workflow → Titles → Thumbnails → Descriptions
Some days he wants only thumbnails. That is why it is a chain.
The rule he lives by: thin agents, thick skills. Keep the agent instruction file lean. Make the skill fat, detailed, and full of context. Then any tool can run it and produce the output you wanted. (Remy credits the phrase to another builder; the name is [UNCLEAR] in the transcript.)
## The self-improvement loop

Remy appends the same block to the bottom of every SKILL.md. At the end of each run, before it finishes, the skill reviews itself:
- Did any step fail or need a workaround?
- Did the user correct or reject anything meaningful?
- Did you discover something a future run needs?
It proposes a change only when the change is worth making. He says yes or no. The skill updates itself.
This compounds across a team. Harold, one of Remy's teammates, hit an image upload error while staging assets in Resend. He found the workaround, updated the skill, pushed it. Remy received the improvement automatically. The whole team runs the better version now.
## The layer on top

Remy built a web app over the repo. The Team Skills repo is the backend, the way Supabase sits behind an app. Every skill on screen pulls live from GitHub.
What it shows:
- A graph of which skills call which other skills
- A library view where you read and edit any skill
- An ask box that searches your private company skills library
Real queries he ran: what are the best skills for decision making, and, I finished the weekly newsletter research, what do I run next. It answers from your own library and names the next skill in the sequence.
He added a usage bar the same day. A hook in the plugin tallies every skill run, by skill and by team member.
Where that leads:
- A Spotify Wrapped for your company: you ran the proposal skill 56 times
- A cull list: show me every skill untouched for six months
- A gap list: show me the skills I should be using
## Action checklist
- Pick three repeatable tasks you did this week and turn each into a skill
- Create a Team Skills repo in your GitHub organization, split by department
- Add the JSON files and turn the repo into a plugin (ask Claude to do it)
- Add the marketplace in Claude Code, then install the plugin
- Turn auto update on for every person on the team
- Create a second repo for your personal and downloaded skills
- Paste the self-improvement loop at the bottom of every SKILL.md
## Final thoughts

Remy built this around one idea: a skill is an SOP, and an SOP belongs to the company.

Most people treat AI output as a lottery. They open a fresh chat, describe their preferences again, and take whatever comes back. That is where slop comes from.
The chain that fixes it:
Repeatable task → Skill → Repo → Plugin → Whole team → Improvements flow back
You are storing judgment. Every skill is a recording of what good looks like to you, written once, run forever.
> "I don't think people are building enough skills and enough good quality skills." - Remy
## Checkout the full episode:
Apple: [https://podcasts.apple.com/us/podcast/you-need-to-be-skillsmaxxing-10x-your-claude-codex/id1593424985?i=1000784410060](https://podcasts.apple.com/us/podcast/you-need-to-be-skillsmaxxing-10x-your-claude-codex/id1593424985?i=1000784410060)
Spotify: [https://open.spotify.com/episode/7iYIgYwjWfiXSNc387g5ht?si=bac15cacaab348d7](https://open.spotify.com/episode/7iYIgYwjWfiXSNc387g5ht?si=bac15cacaab348d7)
Youtube: [https://www.youtube.com/watch?v=xHsftiyT9pQ](https://www.youtube.com/watch?v=xHsftiyT9pQ)
## 相关链接
- [The Startup Ideas Podcast (SIP)](https://x.com/startupideaspod)
- [@startupideaspod](https://x.com/startupideaspod)
- [4.5K](https://x.com/startupideaspod/status/2090177246179045536/analytics)
- [https://podcasts.apple.com/us/podcast/you-need-to-be-skillsmaxxing-10x-your-claude-codex/id1593424985?i=1000784410060](https://podcasts.apple.com/us/podcast/you-need-to-be-skillsmaxxing-10x-your-claude-codex/id1593424985?i=1000784410060)
- [https://open.spotify.com/episode/7iYIgYwjWfiXSNc387g5ht?si=bac15cacaab348d7](https://open.spotify.com/episode/7iYIgYwjWfiXSNc387g5ht?si=bac15cacaab348d7)
- [https://www.youtube.com/watch?v=xHsftiyT9pQ](https://www.youtube.com/watch?v=xHsftiyT9pQ)
- [Upgrade to Premium](https://x.com/i/premium_sign_up)
- [4:41 AM · Aug 20, 2026](https://x.com/startupideaspod/status/2090177246179045536)
- [4,579 Views](https://x.com/startupideaspod/status/2090177246179045536/analytics)
---
*导出时间: 2026/8/20 09:30:39*
---
## 中文翻译
# 你需要进行技能最大化
**作者**: The Startup Ideas Podcast (SIP)
**日期**: 2026-08-19T20:41:03.000Z
**来源**: [https://x.com/startupideaspod/status/2090177246179045536](https://x.com/startupideaspod/status/2090177246179045536)
---

## 如何将他的AI技能转化为整个团队都能安装的插件
Remy(来自AI with Remy)再次做客播客,分享他如何运用代理技能运营公司。
大多数人构建了一个出色的技能,却将其困在自己的机器上。Remy构建了一种方法,可以将技能存储在一个地方,分发给每位队友,并保留每个版本。
以下是他工作流程的解析:什么是技能、为什么共享会出问题,以及解决这个问题的仓库加插件方案。
## 技能是AI的标准操作流程,以markdown文件形式保存。

旧方式:
- 打开新对话,要求生成提案
- 得到你不满意的第一版结果
- 重新解释颜色、标志、价格应该放在底部而不是顶部
- 最终得到不错的结果
- 下周,重新开始
技能方式:你将做事方式打包成一个markdown文件。Claude读取它并执行流程。
Remy进行了一次现场演示。他输入了一行文字:为Greg Eisenberg创建一份关于The Startup Ideas赞助新闻通讯的提案。Claude调取了他的提案技能,一次性生成了品牌化文档。
心智模型:想象你雇佣过的最能干的员工。他的电脑里存放着你的工具和MCP。他的指令文件在每次任务前都会被读取。他身后是一个装满标准操作流程的书架。
每个技能在顶部都有名称和描述。那是书的书脊。当任务需要时,他从书架上取下那本书,通读全文。
Remy在一周内构建的技能:
- Notion格式化(留白、分隔线、蓝色高亮)
- 品牌语调(邮件素材、落地页文案)
- Resend中的邮件格式化(留白、蓝色按钮、标志、签名)
一个好技能每周大约节省两小时。叠加起来,效果惊人。
## 真正的问题:AI是单机游戏

每位队友都有自己的Claude或Codex设置。有人构建了出色的东西。它停留在他们的笔记本电脑上。
Remy称之为技能领域的Microsoft Word时代。你创建了一个文档,通过邮件发送,然后十个副本四处飘散,完全没有唯一真实来源。Google Docs解决了文档的问题。技能仍在等待同样的解决方案。
人们首先尝试的方法:
通过Slack或电子邮件发送压缩文件。你编辑你的版本,他们的版本保持冻结。他们改进他们的版本,你永远看不到。十个副本,零个唯一真实来源。
Google Drive、Dropbox或Obsidian文件夹。Claude只从一个位置读取:它自己的.claude/skills文件夹。让它看到Drive文件夹需要符号链接和黑客手段。这在小型技术团队中勉强可行。但当一个初级营销人员加入的那天,它就崩溃了。
## 将所有技能放入GitHub仓库并制作成插件

GitHub之于代码,就像Google Drive之于文档。这就是你需要的全部概念。
Remy有一个名为Team Skills的仓库,按部门划分:品牌、内容、新闻通讯、营销、财务、通用。这是中央唯一真实来源。

插件是技能、MCP和钩子的集合。你可以捆绑全部三类或仅一类。他的插件是技能的集合。
底层是几个Claude和Codex读取的JSON文件。用Remy的话说:他完全不知道它是如何工作的,也完全不需要知道。他让Claude帮他设置好了。
他没有任何开发背景。
## 在团队中安装
点击路径:
- 打开Claude Code
- 输入/plugin
- 进入市场
- 选择添加市场
- 粘贴你的GitHub仓库URL
市场就是应用商店。插件就是应用。按部门拆分,这样你的文案撰写人安装内容插件而跳过财务插件。
开启自动更新。这是让整个系统活起来的关键。一个人改进了技能,每个人在下次运行时都会收到更新。
它在Codex中同样适用。Remy在两个工具中运行相同的插件。其他工具尚不明确,因为他只测试了这两个。
在Claude企业账户中,你可以获得组织级插件。你的CTO构建一次,然后烘焙到每个账户中,这样非技术人员完全不需要接触终端。
你免费获得的好处:
- 版本控制,损坏的技能可以回退到旧版本
- 公司所有权,因为仓库存在于你的GitHub组织中
- 连续性,编写技能的员工离职后技能仍然保留
Remy的观点:技能像标准操作流程一样增加企业价值。标准操作流程培训员工。技能训练代理执行有经济价值的工作。
## 为自己保留第二个仓库

Remy运行一个名为Remy Skills的独立仓库。个人沙盒、下载的技能,以及尚未推出的内容。
那里有什么:
- 收件箱分类,教Claude他希望如何处理邮件
- 与他自己的应用关联的晨间简报
既然没有其他人使用,为什么还要保留它:
- 唯一真实来源
- 云访问,这样VPS上的Hermes代理可以访问他的技能
- 版本控制
关于备份的说明:大约两个月前,Claude删除了Remy的.claude文件夹。150个技能。500多个小时的工作。零备份。一个仓库既是工作系统,也是降落伞。
## 设计技能和链

Remy的规则:任何在线流程都可以通过一个好技能或技能链实现自动化。例外的是物理性的,比如洗碗。
所以任何可重复的日常任务都变成技能。他在Claude或Codex中工作,很少打开应用前端。当一个任务结束且他知道它会再次出现时,他会说:把这个变成技能。
何时将一个技能拆分成链:问问自己是否会在某个时候单独使用某个子流程。他的YouTube发布工作流是一个编排技能,按顺序运行三个子技能:

发布工作流 → 标题 → 缩略图 → 描述
有些日子他只需要缩略图。这就是为什么它是一个链。
他遵循的规则:薄代理,厚技能。保持代理指令文件精简。让技能丰满、详细、充满上下文。这样任何工具都可以运行它并产生你想要的输出。(Remy将这个说法归功于另一位构建者;名字在转录中不明确。)
## 自我改进循环

Remy在每个SKILL.md底部附加相同的代码块。每次运行结束时,在完成之前,技能会自我审查:
- 是否有任何步骤失败或需要变通方案?
- 用户是否纠正或拒绝了任何重要内容?
- 你是否发现了未来运行需要的东西?
只有当改变值得做出时,它才会提出修改建议。他说是或否。技能自我更新。
这在团队中产生复利效应。Remy的队友之一Harold在Resend中暂存素材时遇到了图片上传错误。他找到了变通方案,更新了技能,推送了它。Remy自动收到了改进。现在整个团队都在运行更好的版本。
## 上层应用

Remy在仓库之上构建了一个Web应用。Team Skills仓库是后端,就像Supabase位于应用之后一样。屏幕上的每个技能都实时从GitHub拉取。
它展示的内容:
- 一个技能调用关系的图谱
- 一个库视图,你可以阅读和编辑任何技能
- 一个提问框,可以搜索你的私有公司技能库
他实际运行过的查询:哪些技能最适合决策制定,以及,我完成了每周新闻通讯研究,接下来运行什么。它从你自己的库中回答,并指出序列中的下一个技能。
他在同一天添加了一个使用量统计栏。插件中的一个钩子统计每次技能运行,按技能和团队成员分类。
这将导向:
- 你公司的Spotify年度总结:你运行了提案技能56次
- 清理清单:显示我所有六个月未使用的技能
- 缺口清单:显示我应该使用但尚未使用的技能
## 行动清单
- 挑选你本周做的三个可重复任务,将每个变成技能
- 在你的GitHub组织中创建一个Team Skills仓库,按部门拆分
- 添加JSON文件并将仓库变成插件(让Claude来做)
- 在Claude Code中添加市场,然后安装插件
- 为团队中的每个人开启自动更新
- 为你的个人技能和下载的技能创建第二个仓库
- 在每个SKILL.md底部粘贴自我改进循环
## 最后的思考

Remy围绕一个核心理念构建了这一切:技能就是标准操作流程,而标准操作流程属于公司。

大多数人把AI输出当作彩票。他们打开一个新对话,再次描述他们的偏好,然后接受任何返回的结果。这就是垃圾输出的来源。
解决这个问题的链条:
可重复任务 → 技能 → 仓库 → 插件 → 整个团队 → 改进回流
你正在存储判断力。每个技能都是对你眼中"好"的标准的一次记录,写一次,永远运行。
> "我认为人们构建的技能还不够多,高质量技能也不够多。" - Remy
## 查看完整剧集:
Apple: [https://podcasts.apple.com/us/podcast/you-need-to-be-skillsmaxxing-10x-your-claude-codex/id1593424985?i=1000784410060](https://podcasts.apple.com/us/podcast/you-need-to-be-skillsmaxxing-10x-your-claude-codex/id1593424985?i=1000784410060)
Spotify: [https://open.spotify.com/episode/7iYIgYwjWfiXSNc387g5ht?si=bac15cacaab348d7](https://open.spotify.com/episode/7iYIgYwjWfiXSNc387g5ht?si=bac15cacaab348d7)
Youtube: [https://www.youtube.com/watch?v=xHsftiyT9pQ](https://www.youtube.com/watch?v=xHsftiyT9pQ)
## 相关链接
- [The Startup Ideas Podcast (SIP)](https://x.com/startupideaspod)
- [@startupideaspod](https://x.com/startupideaspod)
- [4.5K](https://x.com/startupideaspod/status/2090177246179045536/analytics)
- [https://podcasts.apple.com/us/podcast/you-need-to-be-skillsmaxxing-10x-your-claude-codex/id1593424985?i=1000784410060](https://podcasts.apple.com/us/podcast/you-need-to-be-skillsmaxxing-10x-your-claude-codex/id1593424985?i=1000784410060)
- [https://open.spotify.com/episode/7iYIgYwjWfiXSNc387g5ht?si=bac15cacaab348d7](https://open.spotify.com/episode/7iYIgYwjWfiXSNc387g5ht?si=bac15cacaab348d7)
- [https://www.youtube.com/watch?v=xHsftiyT9pQ](https://www.youtube.com/watch?v=xHsftiyT9pQ)
- [升级到Premium](https://x.com/i/premium_sign_up)
- [2026年8月20日 上午4:41](https://x.com/startupideaspod/status/2090177246179045536)
- [4,579次浏览](https://x.com/startupideaspod/status/2090177246179045536/analytics)
---
*导出时间: 2026/8/20 09:30:39*