技能作者

其他 社区

技能解读

当前原文的自动摘译,尚未人工审校。

你在做什么

给定一个领域(由用户的目标暗示),您将: 阅读 /mnt/references/ 中的参考材料以进行领域基础 将这些材料综合为可重用的技能 生成完整的 SKILL.md 文件

关键原则:技能是框架,而不是实例

一项技能必须可以在其领域内的许多请求中重复使用。它捕获了该领域的_判断和专业知识_,而不是任何一项请求的细节。不好:食谱技能中包含了培根蛋面的具体说明。好:一种食谱技能,教授如何通过正确的时间安排、技术顺序和成分比例来构建任何食谱。

关键原则:命名域,而不是应用程序

技能名称必须描述知识领域,而不是要求您构建的第一件事。领域是主题专业知识;应用程序是您利用专业知识构建的。坏处:“竞争性摇摆记分卡生成”——太狭窄,仅适用于记分卡。好:“竞争性摇摆”——适用于记分卡,

专业知识从何而来

参考材料 (/mnt/references/):将技能建立在真实知识基础上的特定领域文档、数据、规则和标准。务必先检查并阅读参考资料。您的参数知识:培训中的常识。当参考材料存在时,它就是事实的主要来源。你的

您的流程

阅读/mnt/references/中的所有参考资料 确定可重用的原则、规则和判断框架 将领域专业知识(可重用)与实例细节分开(丢弃) 编写完整的 SKILL.md 使用 system_write_file 将其保存为 SKILL.md

流狐档案 运行与权限由流狐静态检查推断,不代表作者声明或实际测试结果。
领域
通用
作者声明的智能体
未找到明确声明;不据此推断已兼容或已测试
静态检查
88 / 100 · 启发式扫描,不代表运行安全
运行环境证据
未执行;当前没有隔离运行测试证据
作者 / 版本 / 许可证
@breadboard-ai · 未声明许可证
上下文用量评级
低消耗
接入复杂程度
即装即用
是否需要外部接口密钥
不需要
兼容的系统
未声明(默认跨平台)
运行环境要求
未检出明确要求
检测到的文件与系统行为
  • 只读
  • 允许写入 / 修改
网络行为
仅限本地
安装命令数
无(仅作为资料)

需要注意: 未声明工具权限范围;实际权限由运行环境决定。

作者说明文件(原文) SKILL.md

# Skill Author

You are now acquiring the meta-skill of **writing skills**. After reading this
document, you will know how to produce high-quality SKILL.md files that teach
other agents new capabilities.

## What You're Doing

Given a **domain** (implied by the user's objective), you will:

1. Read reference material from `/mnt/references/` for domain grounding
2. Synthesize that material into a reusable skill
3. Produce a complete `SKILL.md` file

## Critical Principle: Skills Are Frameworks, Not Instances

A skill must be **reusable across many requests** in its domain. It captures the
_judgment and expertise_ of the domain — not the specifics of any one request.

**BAD**: A recipe skill that includes carbonara-specific instructions. **GOOD**:
A recipe skill that teaches how to structure ANY recipe with proper timing,
technique sequencing, and ingredient proportions.

The test: if your skill only works for the first request that triggered it,
you've written an answer, not a skill. Rewrite it.

## Critical Principle: Name the Domain, Not the Application

The skill name must describe the **domain of knowledge**, not the first thing
you're asked to build. The domain is the subject-matter expertise; applications
are what you build WITH that expertise.

**BAD**: "Competitive Wobbling Scorecard Generation" — too narrow, only works
for scorecards. **GOOD**: "Competitive Wobbling" — works for scorecards,
training guides, match commentary, athlete profiles, etc.

**BAD**: "Italian Pasta Recipe Creation" — fuses a cuisine with a format.
**GOOD**: "Culinary Arts" — works for any recipe, any cuisine, any format.

## Where Expertise Comes From

- **Reference material** (`/mnt/references/`): domain-specific documents, data,
  rules, and standards that ground the skill in real knowledge. **Always check
  for and read reference material first.**
- **Your parametric knowledge**: general knowledge from training.

When reference material exists, it is the primary source of truth. Your
parametric knowledge fills in general framing and structure, but domain-
specific facts MUST come from the references.

## SKILL.md Format

```markdown
---
name: [Human-readable skill name]
description: [1-2 sentence description of what this skill enables]
---

# [Skill Name]

[Opening paragraph: "You are now acquiring the skill of..."]

## What You're Building

[Describe the RANGE of artifacts this skill enables — not just one type. The
skill should support multiple applications within the domain.]

## Memory Integration

Check `/mnt/memory.md` for user preferences before generating.

## Domain Expertise

[The reusable judgment framework synthesized from references. Rules, heuristics,
quality criteria, common mistakes, tradeoffs. This is the CORE of the skill —
the expertise that makes output substantive rather than shallow.]

## Output Format

[Exact file names, structure, and how to save them]
```

## Your Process

1. Read ALL reference material in `/mnt/references/`
2. Identify the reusable principles, rules, and judgment frameworks
3. Separate domain expertise (reusable) from instance specifics (discard)
4. Write the complete SKILL.md
5. Save it using `system_write_file` as `SKILL.md`

## Output

Save the skill as `SKILL.md` and call `system_objective_fulfilled` with a
summary of what the skill teaches.

讨论

基于 GitHub Discussions。登录 GitHub 即可参与讨论、点赞、订阅更新。