Agent Skills
› yifanfeng97/Hyper-Extract
› record-designer
record-designer
GitHub用于设计数据提取模板，支持model、list、set三种记录类型。根据需求定义字段结构、标识符及提取指南，生成标准化YAML配置。
Trigger Scenarios
design model template
create item list extraction
extract items
deduplicate entities
Install
npx skills add yifanfeng97/Hyper-Extract --skill record-designer -g -y
SKILL.md
Frontmatter
{
"name": "record-designer",
"description": "Design YAML extraction templates for record types (model, list, set).\nUse when user says: \"design model template\", \"create item list extraction\", \"extract items\", \"deduplicate entities\".\nTrigger: User wants to extract structured records, lists, or deduplicated entities.\nSkip: User mentions graph, relations, or knowledge graph (use graph-designer instead)."
}
Record Designer: model/list/set
Input from Brainstorm
Receive design specs from brainstorm:
- What fields to extract
- Field types and requirements
- Deduplication needs (for set)
Workflow
- Confirm type (model/list/set)
- Design fields (output.fields)
- Configure identifiers (identifiers.item_id for set)
- Set display (display.label)
- Write guideline (guideline)
- Review and output YAML
Critical: Output vs Guideline
Key Principle: Schema defines "WHAT", Guideline defines "HOW TO DO WELL". DO NOT repeat schema definitions in guideline.
| Guideline Should Have | Guideline Should NOT Have |
|---|---|
| Extraction strategy ("extract key information for...") | Field definitions ("field_a is for...") |
| Quality requirements ("maintain format consistency") | Type descriptions ("type field should be...") |
| Deduplication rules (for set type) | Required/optional clarifications |
| Common mistakes to avoid | Default value explanations |
Type Confirmation
| Type | Identifiers | Use Case |
|---|---|---|
| model | Not needed | Single object |
| list | Not needed | List of items |
| set | item_id required |
Deduplicated entities |
Output Template
language: en
name: [TemplateName]
type: [model/list/set]
tags: [...]
description: '...'
output:
description: '...'
fields:
- name: field_name
type: str/int/float/list
description: '...'
required: true/false
default: '...'
guideline:
target: 'You are a [domain] expert...'
rules: [...]
identifiers: {} # Or item_id for set
display:
label: '{field_name}'
Type-Specific Output
model
type: model
identifiers: {} # Not needed
list
type: list
identifiers: {} # Not needed
set
type: set
identifiers:
item_id: [deduplication field]
Cases by Type
Important: Load only the case matching user's selected type.
| Type | Case File |
|---|---|
| model | cases/earnings-summary.yaml |
| list | cases/product-features.yaml |
| set | cases/entity-registry.yaml |
Reference Files
Important: Check these files only when needed for the specific design task.
| Topic | When to Check |
|---|---|
| references/field.md | When designing output.fields |
| references/identifier.md | For set type only |
Design Checklist
- All fields have clear semantic meaning?
- Field types are appropriate (str/int/float/list)?
- Required vs optional is reasonable?
- Default values are safe/meaningful?
- For set: item_id can uniquely identify records?
- Display label references correct fields?
Guideline (Must Check)
- No field definitions repeated from schema?
- Extraction strategy defined?
- Quality requirements specified?
- Common mistakes warned?
- For set: deduplication rules clear?
Multi-language
-
zhdescriptions use pure Chinese -
endescriptions use pure English
Version History
- e698804 Current 2026-07-25 05:13
