Token导航 LogoToken导航

Agent Skill · 研究检索

platform-and-infrastructure(平台和基础设施)

platform-and-infrastructure 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

platform-and-infrastructure 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为需要联网;许可证信息还不明确,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 68,490。

总安装 233周安装 10GitHub Stars 3下载 82核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:platform-and-infrastructure(平台和基础设施)
来源仓库:https://github.com/oldwinter/skills
仓库路径:skills/platform-and-infrastructure
安装命令:
npx skills add https://github.com/oldwinter/skills --skill platform-and-infrastructure
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/oldwinter/skills --skill platform-and-infrastructure

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中快速定位候选结果。适用于关键词搜索、任务场景匹配和来源线索筛选等研究检索场景。通过 npx skills add 命令从 GitHub 仓库安装,需结合原始 README 核验具体用法。

安装前建议确认权限范围、维护状态及是否触发联网或文件读写操作。可配合来源仓库进一步了解技能的实际功能和限制条件。

来源仓库内路径:skills/platform-and-infrastructure

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/oldwinter/skills --skill platform-and-infrastr…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

platform-and-infrastructure 怎么安装?

在终端执行 npx skills add https://github.com/oldwinter/skills --skill platform-and-infrastructure。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

platform-and-infrastructure 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

platform-and-infrastructure 需要什么权限?

权限级别是需要联网。该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

platform-and-infrastructure 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

platform-and-infrastructure 用的人多吗?

公开数据是累计安装 233 次,近一周安装 10 次,下载 82 次,GitHub 3 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

platform-and-infrastructure 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
platform-and-infrastructure

平台和基础设施 · 本页

2333需要联网未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Platform & Infrastructure

Category: Engineering

Source: https://refoundai.com/lenny-skills/s/platform-infrastructure


Platform & Infrastructure | Refound AI

Lenny Skills Database SKILLS PLAYBOOKS GUESTS ABOUT SKILLS PLAYBOOKS GUESTS ABOUT Engineering 5 guests | 6 insights

Platform & Infrastructure Platform and infrastructure work is the 'invisible' foundation that determines whether your product can scale. The best products often win on reliability, performance, and architecture rather than feature count. Infrastructure investments require anticipating 100X scale before you need it.

Download Claude Skill

Read Guide

The Guide 5 key steps synthesized from 5 experts.

1 Prioritize invisible qualities over visible features The success of major platforms often depends on reliability, speed, privacy, and safety rather than feature count. WhatsApp won with end-to-end encryption and performance, not a feature-rich interface. Focus on the infrastructure qualities that build trust and enable scale.

Featured guest perspectives

"It wasn't the hundreds of features, it was all in the infrastructure and the platform... performance, reliability, privacy, safety, all of those things."

— Asha Sharma 2 Abstract common capabilities into shared infrastructure Scaling feature velocity requires identifying repetitive components and building them into a core platform architecture. Standardize capabilities like data export, filtering, or permissions at the infrastructure level so developers only focus on unique product logic.

Featured guest perspectives

"We actually stopped for the first time and say, 'What is the column like?' And we also organized all the product architecture around it... we defined what is it, and then create an infrastructure for all these shared things, making the work of adding a new column just thinking about the specific product that you want to provide."

— Daniel Lereya 3 Set a 'doomsday clock' for scaling projects While avoiding premature optimization is good, you need to monitor infrastructure limits and trigger scaling projects before failure. Know your breaking points (like running out of database capacity) and plan far enough ahead to avoid catastrophic outages during growth spikes.

Featured guest perspectives

"During COVID, we just couldn't scale up our infrastructure. For the longest time... we're running off even the largest instance there is for Postgres. So there's a doomsday clock... we just need to go as fast as you can to become sharding problem."

— Ivan Zhao 4 Dedicate top talent to 100X problems Critical infrastructure projects require dedicated teams focused on long-term architectural shifts rather than incremental features. Isolate your most talented engineers to solve 100X scale problems that will provide competitive advantage, even if it means temporarily reducing feature output.

Featured guest perspectives

"We need few of our most talented people that are now not going to contribute features anymore. We are putting them on a separate place, and let's think and solve this problem while thinking about 100X."

— Daniel Lereya 5 Default to server-side tracking For analytics and data infrastructure, server-side tracking is superior to client-side SDKs. It avoids data loss from ad-blockers, ensures cross-platform consistency, and reduces developer maintenance burden. Use server-side logs with user IDs as the primary source for behavioral events.

Featured guest perspectives

"The biggest mistake is setting up analytics using client side SDKs... start tracking events from your servers instead of from your clients."

— Vijay

✗ Common Mistakes

Competing on feature count when reliability and performance matter moreWaiting until infrastructure is failing to start scaling projectsBuilding the same capabilities repeatedly instead of abstracting them into platformRelying on client-side tracking that loses data to ad-blockers ✓ Signs You're Doing It Well

New features ship faster because common capabilities are already solvedYou know your infrastructure breaking points and have projects to address them before they hitEnterprise customers trust you because of reliability and data residency, not just featuresYour top engineers are excited to work on foundational problems, not just shipping features

All Guest Perspectives

Deep dive into what all 5 guests shared about platform & infrastructure.

Asha Sharma 1 quote

Listen to episode →

"it wasn't the hundreds of features, it was all in the infrastructure and the platform... performance, reliability, privacy, safety, all of those things." Tactical: Prioritize reliability, speed, and end-to-end encryption in communication platformsFocus on data residency and availability to build trust with enterprise customers

View all skills from Asha Sharma →

Daniel Lereya 2 quotes

Listen to episode →

"We actually stopped for the first time and say, 'What is the column like?' And we also organized all the product architecture around it... we defined what is it, and then create an infrastructure for all these shared things, making the work of adding a new column just thinking about the specific product that you want to provide." Tactical: Identify repetitive feature components and build them into a core platform architectureStandardize capabilities like 'export to Excel' or 'filtering' at the infrastructure level "We need few of our most talented people that are now not going to contribute features anymore. We are putting them on a separate place, and let's think and solve this problem while thinking about 100X." Tactical: Isolate top talent to work on long-term architectural shifts that provide a competitive edgeAnticipate infrastructure breaking points by planning for 100X current capacity

View all skills from Daniel Lereya →

Eli Schwartz 1 quote

Listen to episode →

"If you create a categorized sitemap where you can say, 'These are all the questions on health and from the sitemap... then a search engine can navigate through the entire site, and all of the questions and answers are discoverable.'" Tactical: Build a categorized HTML sitemap that allows bots to navigate the entire site depthImplement 'related content' links on every page to create a crawlable web for search engines

View all skills from Eli Schwartz →

Ivan Zhao 1 quote

Listen to episode →

"During COVID, we just couldn't scale up our infrastructure. For the longest time, Simon's really good at don't do premature optimization, so for the longest time, we Notion runs on one instance of Postgres database... we're running off even the largest instance there is for Postgres. So there's a doomsday clock... we just need to go as fast as you can to become sharding problem." Tactical: Monitor database limits and set a 'doomsday clock' to trigger scaling projects (like sharding) before failure.Be prepared to halt feature development to focus entirely on critical infrastructure scaling.

View all skills from Ivan Zhao →

Vijay 1 quote

Listen to episode →

"The biggest mistake is setting up analytics using client side SDKs... start tracking events from your servers instead of from your clients." Tactical: Default to server-side event tracking to avoid data loss from ad-blockersUse server-side logs with user IDs as the primary source for behavioral events

View all skills from Vijay →

Install This Skill

Add this skill to Claude Code, Cursor, or any AI coding assistant that supports Agent Skills.

1 Download the skill

Download SKILL.md

2 Add to your project

Create a folder in your project root and add the skill file:

.claude/skills/platform-infrastructure/SKILL.md 3 Start using it

Claude will automatically detect and use the skill when relevant. You can also invoke it directly:

Help me with platform & infrastructure Related Skills Other Engineering skills you might find useful. 19 guests Engineering Culture A high-performance engineering culture can be built around extreme experimentation frequency and tig... View Skill → → 18 guests Managing Tech Debt When a technical solution lacks the operational flexibility required by the business, a full rebuild... View Skill → → 1 guests Technical Roadmaps A written strategy is essential for organizational alignment and provides a baseline that can be cri... View Skill → → 2 guests Design Engineering The guest discusses the creation of a specific 'Design Engineering' function at Snap and Captions th... View Skill → →

AI Transformation Partner

Start Your Journey

SERVICES AI Audit AI Automation AI Training COMPANY About Case Studies Book a Call

© 2026 Refound. All rights reserved.

平台分布

Codex

34.3%
按下载量换算28

Claude

31.2%
按下载量换算26

Cursor

20.04%
按下载量换算16

Gemini CLI

10.24%
按下载量换算8

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills