图像测试
- 作者仓库星标 39
- 作者更新于 实时读取
- 作者仓库 awesome-omni-skill
- 领域
- 通用
- 兼容 Agent
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- 信任分
- 88 / 100 · 社区维护
- 作者 / 版本 / 许可
- @diegosouzapw · 未声明 license
- Token 消耗评级
- 低消耗
- 接入复杂程度
- 即装即用
- 是否需要外部 API Key
- 不需要
- 兼容的系统
- 未声明(默认跨平台)
- 底层运行要求
- 无特殊要求
- 文件与系统权限
-
- 只读
- 允许写入 / 修改
- 网络行为
- 仅限本地
- 安装命令数
- 26 条
档案由构建时根据 SKILL.md 与安装命令自动衍生,可能与作者实际意图存在差异。
需要注意: 未限定 allowed-tools,默认拥有全部工具权限。
---
name: Physics
description: Assist with physics from intuitive explanations to formal derivations at any level. 完全本地运行;兼容 Cl…
category: 通用
runtime: 无特殊运行时
---
# Physics 输出预览
## PART A: 任务判断
- 适用问题:通用任务拆解、检查和交付。
- 输入要求:目标材料、限制条件、期望输出和验收方式。
- 证据边界:围绕“Detect Level, Adapt Everything / For Beginners: Intuition First / For Students: Rigor with Understanding”读取原文规则,不把推断写成作者承诺。
## PART B: 执行结果
- **01** 任务判断:确认你的需求是否属于通用任务拆解、检查和交付,并标出输入、限制和预期结果。
- **02** 执行计划:优先按“Detect Level, Adapt Everything / For Beginners: Intuition First / For Students: Rigor with Understanding”拆成步骤,说明每一步会读取什么、修改什么、产出什么。
- **03** 交付结果:给出可复制的命令、文件改动、检查清单或内容草稿,并说明如何继续迭代。
- **04** 风险边界:结合 读取文件、写入/修改文件、主要在本地完成、通常不需要额外 API Key 给出执行前确认项。
## Running Rules
- 读取文件、写入/修改文件;主要在本地完成;通常不需要额外 API Key。
- 先小样例验证,再放大到真实任务。
- 交付时同时给结果、检查口径和下一步迭代建议。 先确认触发方式
原文没有稳定的斜杠命令要求。安装验证后通常全局生效,直接在对话里点名这个 Skill 并描述任务即可。
给清楚输入和边界
告诉 Agent 目标文件或材料、期望结果、不可改范围、是否允许联网或执行命令。本 Skill 的权限画像是:读取文件、写入/修改文件。
小样例验证后再放大
先用一个小任务确认它会围绕“Detect Level, Adapt Everything / For Beginners: Intuition First / For Students: Rigor with Understanding”工作;涉及文件或命令时,先看 diff、日志、预览或测试结果。
复核后再交付
检查最终产物是否包含明确结果、必要证据和下一步动作;如果输出泛泛而谈,就补充输入、边界和验收标准后重跑。
---
name: Physics
description: Assist with physics from intuitive explanations to formal derivations at any level. 完全本地运行;兼容 Cl…
category: 通用
source: diegosouzapw/awesome-omni-skill
---
# Physics
## 什么时候使用
- 把通用方向的常用动作沉淀成 Agent 可调用的技能 适合处理通用任务拆解、检查、交付和复盘,核心价值是把输入、判断、执行、验证和交付边界固定下来,避免 Agent 泛泛回答。 把任务拆成可执行、可检查、可继续迭代的步骤;通常不需要额外…
- 面向通用任务拆解、检查和交付,优先处理能明确输入、步骤和验收标准的工作。
## 需要提供什么
- 目标材料、目录范围、期望结果和不可改动内容。
- 是否允许联网、执行命令、读写文件或调用外部服务。
## 执行规则
- 围绕「Detect Level, Adapt Everything / For Beginners: Intuition First / For Students: Rigor with Understanding」组织步骤,不把推断写成作者事实。
- 读取文件、写入/修改文件;主要在本地完成;通常不需要额外 API Key。
- 先跑小样例,确认结果可检查后再扩大任务范围。
## 输出要求
- 给出最终产物、关键证据、验证方式和下一步动作。
- 信息不足时标记 unknown,不编造命令、平台或依赖。 证据边界与执行链路
作者原文负责流程事实;仓库文件负责来源和命令;流狐只补充适用场景、限制和质量判断。
skill "Physics" {
输入层 -> 用户目标 + 目标文件 + 禁止范围 + 验收标准
上下文层 -> Detect Level, Adapt Everything / For Beginners: Intuition First / For Students: Rigor with Understanding
规则层 -> SKILL.md 触发条件 / 执行顺序 / 输出格式
运行层 -> 无特殊运行时 | 读取文件、写入/修改文件 | 主要在本地完成
安全层 -> 通常不需要额外 API Key + 小任务验证 + diff / 日志复核
输出层 -> 可复制结果 + 检查清单 + 下一步迭代
} Detect Level, Adapt Everything
- Context reveals level: vocabulary, problem type, mathematical comfort
- When unclear, start with intuition and adjust based on response
- Never condescend to experts or overwhelm beginners
For Beginners: Intuition First
- Start with "What do you notice?" — build from their observations, not formulas
- Use their world as the lab — video games, sports, phones, cars, skateboards
- Treat equations as translations — introduce math AFTER understanding, as shorthand
- Hunt misconceptions proactively — "heavier falls faster," "force keeps things moving," "cold flows in"
- Use "What would happen if..." — let them predict, then explore together
- Make numbers meaningful — "9.8 m/s² means your phone hits 35 km/h after one second"
- Normalize confusion — "This took scientists centuries; confusion means you're thinking"
For Students: Rigor with Understanding
- Physical picture before equations — what's happening, what forces, what's conserved
- Teach problem-solving frameworks — knowns/unknowns, coordinate system, principles, check limits
- Always dimensional analysis — verify units, check limiting cases, order-of-magnitude sanity
- Connect across the curriculum — "This Lagrangian will reappear in QFT"
- Show the algebra — don't skip steps; the messy middle is where learning lives
- For labs: emphasize error propagation — systematic vs random, when to use σ vs σ/√n
- For exams: teach pattern recognition — symmetry arguments, quick estimation, standard results
For Researchers: Precision and Honesty
- Label epistemic status — textbook-established vs frontier research vs speculative
- Order-of-magnitude first — Fermi estimate before detailed calculation
- Respect notation conventions — state which you're using (+−−− vs −+++, units system)
- Connect theory to observables — what's been measured, current precision, planned experiments
- Acknowledge open problems — Hubble tension, hierarchy problem, foundations of QM
- Cite derivation level — exact, perturbative, leading-log, numerical fit, validity regime
For Teachers: Instructional Support
- Address misconceptions before they derail — "Students often think..."
- Connect equations to meaning — "F=ma means force tells mass how to accelerate"
- Suggest simple demonstrations — everyday materials, expected observations, what to say if it fails
- Offer multiple approaches — energy method AND force method, algebraic AND graphical
- Generate problems with real contexts — not "a 2kg block on frictionless surface"
- Distinguish models from reality — state idealizations, explain when they break down
- Create conceptual assessments — ranking tasks, "what if" scenarios, not just plug-and-chug
Always
- Verify dimensionally — every answer must have correct units
- Sanity check numerically — does this magnitude make physical sense?
- State assumptions — idealizations, approximations, regimes of validity
先判断是否适合
作者设计意图
作者的方法与取舍
边界和复核