技能模板生成器
- 作者仓库星标 6,311
- 作者仓库 OpenSpace
- 领域
- 数据
- 作者声明的智能体
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 88 / 100 · 启发式扫描,不代表运行安全
- 运行环境证据
- 未执行;当前没有隔离运行测试证据
- 作者 / 版本 / 许可证
- @HKUDS · 未声明许可证
- 上下文用量评级
- 低消耗
- 接入复杂程度
- 需简单配置
- 是否需要外部接口密钥
- 需要 · Vendor-specific
- 兼容的系统
- 未声明(默认跨平台)
- 运行环境要求
- 未检出明确要求
- 检测到的文件与系统行为
-
- 只读
- 允许写入 / 修改
- 命令执行
- 网络行为
- 允许外网请求
- 安装命令数
- 无(仅作为资料)
需要注意: 未声明工具权限范围;实际权限由运行环境决定。
Pattern: Circuit Breaker Data Service
Source: worldmonitor/src/services/*.ts
Category: service
Structure: Module-level CircuitBreaker instance, async fetch functions, typed interfaces
Key code: createCircuitBreaker({ name, cacheTtlMs }), breaker.execute(fn, default)
第 1 步:确定技能类别
将模式与三个 OpenSpace 类别之一进行匹配:类别 · 使用时间 · 示例 `tool_guide` · 该技能教授如何使用特定工具或技术 · “如何分析代码库”、“如何使用 Finnhub API” `workflow` · 该技能通过有序步骤规定端到端过程 · “创建面板组件”、“设置 API 代理端点” `reference` · 该技能提供为决策提供信息的知识 · 《WorldMonitor架构索引》、《新闻API对比》
第 2 步:编写描述
`description` 字段是最关键的一行 — 它决定 OpenSpace 是否为给定任务选择此技能。良好的描述(具体、可搜索):“使用 vanilla TypeScript DOM API 创建仪表板面板组件,遵循 worldmonitor 面板架构。” “与 Finnhub Stock API 集成,获取实时和历史股票市场数据。” “用于具有深色主题的响应式面板仪表板的 CSS 网格布局系统。”
第 3 步:编写可操作的说明
身体必须足够具体,以便人工智能代理可以跟随它而无需猜测。
第 4 步:添加依赖项提示
如果该技能依赖于其他技能的模式,请明确提及:这有助于 OpenSpace 在派生新技能时了解技能构成。
第 5 步:验证技能
保存之前,请验证: Frontmatter 是有效的 YAML — 无制表符、正确缩进、特殊字符周围的引号 名称与目录匹配 — `name: foo-bar` 位于 `foo-bar/SKILL.md` 代码块完整 — 每个片段都可以复制粘贴并运行 无损坏的引用 — 所有文件路径和 URL 均有效
# Skill Template Generator
Given a structured pattern description (from `codebase-pattern-analyzer` or manual analysis), generate a valid SKILL.md file that OpenSpace can register, select for tasks, and evolve over time.
## When to Use
- After extracting a pattern from a reference codebase, you need to package it as a reusable skill
- You want to create a new skill that teaches an agent how to perform a specific kind of task
- You are converting informal documentation or code examples into the SKILL.md format
## SKILL.md Format
Every skill is a directory containing at minimum a `SKILL.md` file:
```
my-skill-name/
├── SKILL.md # Required — the skill definition
├── scripts/ # Optional — helper scripts
├── references/ # Optional — reference data files
└── assets/ # Optional — images, templates
```
### Frontmatter (Required)
The file MUST start with YAML frontmatter containing exactly two fields:
```yaml
---
name: my-skill-name
description: One-sentence description of what this skill teaches. Must be specific enough for LLM skill selection to match it to relevant tasks.
---
```
**Rules:**
- `name` must match the directory name (kebab-case, lowercase)
- `description` should be 15-40 words, include key terms an LLM would search for
- No other frontmatter fields — everything else goes in the markdown body
### Body Structure
The markdown body follows this template:
```markdown
# [Skill Title]
[1-2 sentence summary of what this skill enables]
## When to Use
- [Trigger condition 1]
- [Trigger condition 2]
- [Trigger condition 3]
## [Core Content Sections]
[Step-by-step instructions, code templates, API references, etc.]
## Key Patterns
1. [Convention or best practice 1]
2. [Convention or best practice 2]
...
```
## Step 1: Determine Skill Category
Match the pattern to one of three OpenSpace categories:
| Category | Use When | Example |
|----------|----------|---------|
| `tool_guide` | The skill teaches how to use a specific tool or technique | "How to analyze a codebase", "How to use Finnhub API" |
| `workflow` | The skill prescribes an end-to-end procedure with ordered steps | "Create a panel component", "Set up API proxy endpoint" |
| `reference` | The skill provides knowledge that informs decisions | "WorldMonitor architecture index", "News API comparison" |
The category affects how OpenSpace judges the skill during execution analysis:
- **workflow**: Was the agent able to follow the prescribed steps?
- **tool_guide**: Did the agent use the described tool/approach?
- **reference**: Did the knowledge influence agent decisions?
## Step 2: Write the Description
The `description` field is the **most critical line** — it determines whether OpenSpace selects this skill for a given task.
**Good descriptions** (specific, searchable):
- "Create a dashboard panel component using vanilla TypeScript DOM API, following the worldmonitor Panel architecture."
- "Integrate with Finnhub Stock API for real-time and historical stock market data."
- "CSS grid layout system for a responsive panel dashboard with dark theme."
**Bad descriptions** (vague, generic):
- "A useful skill for building things."
- "TypeScript patterns."
- "How to make a panel."
**Formula**: `[Action verb] + [specific subject] + [key technology/approach] + [context/project reference]`
## Step 3: Write Actionable Instructions
The body must be concrete enough that an AI agent can follow it without guessing.
### For Workflow Skills
Include:
1. **File paths** — exact paths where files should be created (`src/components/MyPanel.ts`)
2. **Code templates** — complete, runnable code blocks (not pseudocode)
3. **Import statements** — every import the code needs
4. **Interface definitions** — typed data shapes
5. **Integration points** — how this connects to other parts of the project
Use `{baseDir}` for paths relative to the skill directory:
```
Read the reference file at {baseDir}/references/example.json
```
### For Tool Guide Skills
Include:
1. **API endpoints** — full URLs with parameter documentation
2. **Auth mechanism** — how to authenticate (query param, header, etc.)
3. **Response shapes** — JSON examples with field descriptions
4. **Rate limits** — free tier limitations
5. **Error handling** — common errors and how to handle them
### For Reference Skills
Include:
1. **Structured index** — tables, lists, or maps of the reference material
2. **Key file paths** — where to find specific things in the reference codebase
3. **Architecture decisions** — WHY certain patterns were chosen
4. **Comparison tables** — alternatives and tradeoffs
## Step 4: Add Dependency Hints
If the skill depends on patterns from other skills, mention them explicitly:
```markdown
## Prerequisites
This skill builds on:
- `panel-component` — for the Panel base class
- `data-service` — for the circuit breaker pattern
- `api-proxy-endpoint` — for server-side API key isolation
```
This helps OpenSpace understand skill composition when DERIVING new skills.
## Step 5: Validate the Skill
Before saving, verify:
1. **Frontmatter is valid YAML** — no tabs, proper indentation, quotes around special chars
2. **Name matches directory** — `name: foo-bar` lives in `foo-bar/SKILL.md`
3. **Code blocks are complete** — every snippet can be copy-pasted and run
4. **No broken references** — all file paths and URLs are valid
5. **Description is specific** — would an LLM pick this skill for the right task?
## Example: Converting a Pattern to a Skill
**Input** (from codebase-pattern-analyzer):
```
Pattern: Circuit Breaker Data Service
Source: worldmonitor/src/services/*.ts
Category: service
Structure: Module-level CircuitBreaker instance, async fetch functions, typed interfaces
Key code: createCircuitBreaker({ name, cacheTtlMs }), breaker.execute(fn, default)
```
**Output** (`data-service/SKILL.md`):
```markdown
---
name: data-service
description: Create data fetching services with circuit breaker pattern for API resilience. Services handle fetch, cache, retry, and expose typed data to panel components.
---
# Data Service Pattern
Each panel's data comes from a dedicated service module in `src/services/`. ...
## Circuit Breaker
[Full implementation code]
## Service Module Pattern
[Template with typed interfaces, breaker usage, export functions]
## Key Patterns
1. One circuit breaker per API endpoint
2. Export typed interfaces for data shapes
3. Wrap fetch calls in breaker.execute(fn, defaultValue)
...
```
## Evolution Hooks
Skills generated by this workflow are designed to evolve:
- **FIX**: When an API changes or code pattern breaks, OpenSpace updates the skill in-place
- **DERIVED**: When a new panel needs a similar service, OpenSpace derives a specialized version
- **CAPTURED**: When an agent discovers a novel pattern during execution, OpenSpace captures it as a new skill
The better the initial skill quality, the better the evolved descendants.
章节与文件索引
按说明文件中的顺序排列。
何时使用
技能.md 格式
前言(必填)
车身结构
第 1 步:确定技能类别
文件/命令 -> codebase-pattern-analyzer · name · description · tool_guide · workflow · reference · [Action verb] + [specific subject] + [key technology/approach] + [context/project reference] · src/components/MyPanel.ts
内容校验值 -> f7762c8a8234
当前原文的自动摘译,尚未人工审校。
何时使用
从参考代码库中提取模式后,您需要将其打包为可重用技能您想要创建一项新技能来教代理如何执行特定类型的任务您正在将非正式文档或代码示例转换为 SKILL.md 格式
技能.md 格式
每个技能都是一个至少包含一个
SKILL.md文件的目录:前言(必填)
该文件必须以包含两个字段的 YAML frontmatter 开头: 规则:
name必须与目录名称匹配(短横线大小写,小写)description应为 15-40 个单词,包括 LLM 将搜索的关键术语 没有其他 frontmatter 字段 - 其他所有内容都在 markdown 正文中车身结构
Markdown 正文遵循以下模板: