Install any skill in seconds. Free to start, no credit card required.
Get Started Free →ontology-of-everything/sce-creator
按两轮流程从原文萃取可调用知识元:先扫骨架(id+define+sources)并等人确认,再回查原文填 IPO/分解/组装与关系。 概念是中枢;场景只编排;实体是实例。
Passed 11 of 22 test cases with the skill, and 8 of 22 without it.
and 2 more in the full report
4 fixed7 passed either way10 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
In the 'Logback Logging Framework Integration Guide', Concept A ('Structured Logging') mentions Concept B ('JSON Layout Format') as an optional format, but Concept A can function without Concept B. Should the relation from A to B be categorized as '依赖' (dependency)?
| Checked | Without skill | With skill |
|---|---|---|
| Categorizes the relation from Concept A to Concept B as '参考' (reference) rather than '依赖' (dependency). | Missed | Passed |
The instructions your model reads when the skill loads.
把线性原文变成可调用的知识元。概念是中枢:先给出可执行定义,再驱动实体挂接与场景组装。价值在调用。三层划分灵感来自「人月聊 IT」《三层架构:场景、概念与实体》。
工作目录:用户指定;三个 yaml 文件名固定:
| 层 | 文件 |
|---|---|
| 场景 | sce-scenes.yaml |
| 概念 | sce-concepts.yaml |
| 实体 | sce-entities.yaml |
进度:_sce-round1-progress.md。
边要能支撑后续组装。每概念 2–6 条。离开对方仍能独立工作 = 参考,不是依赖。
| 类型 | 方向 | 何时用 |
|---|---|---|
| 包含 | 概念→概念 / 实体→实体 | 整体与部分 |
| 依赖 | 概念→概念 | 离开则无法执行 |
| 参考 | 概念→概念 | 仅提及,可独立工作 |
| 调用 | 场景/概念→概念或实体 | 组装或执行时使用 |
| 分解 | 概念→子概念 | 流程性概念的阶段 |
| 父子 | 实体→实体 | 层级,≤3 层;子项须独立来源、独立定义、可被单独引用 |
| 组装 | 场景阶段→概念/实体 | 阶段规则 |
| 别名 | 知识元→名称 | 命名变体,不另立条目 |
按序每批 5–10 篇(或等价篇幅),进度写入 _sce-round1-progress.md。
test cases passed, vs 8 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.