一键导入
json-formatter
JSON formatting rules for lore entity output. Enforces export-compatible JSON, plural collections, consistent IDs, and domain field names.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
JSON formatting rules for lore entity output. Enforces export-compatible JSON, plural collections, consistent IDs, and domain field names.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Extract achievement entities from narrative text. Use when analyzing trophies, badges, ranks, leaderboards, titles, and progression reward milestones.
Extract analytics and game balance entities from narrative text. Use when analyzing player metrics, difficulty curves, drop rates, loot tables, heatmaps, and balance tuning.
Extract audio entities from narrative text. Use when analyzing music themes, sound effects, ambient audio, motifs, dynamic scoring, and silence as narrative device.
Extract biology entities from narrative text. Use when analyzing ecosystems, food chains, migration, hibernation, reproduction, extinction events, and evolution.
Extract celestial entities from narrative text. Use when analyzing galaxies, nebulae, black holes, star systems, moons, eclipses, solstices, and astronomical phenomena.
Extract character entities from narrative text. Use when analyzing characters, relationships, psychology, development arcs, voice/mocap data, and character variants.
| name | json-formatter |
| description | JSON formatting rules for lore entity output. Enforces export-compatible JSON, plural collections, consistent IDs, and domain field names. |
| user-invocable | false |
Base skill for JSON output formatting. All extraction skills produce JSON that can be loaded by the Lore GUI (LoreData.from_dict).
src/presentation/gui/lore_data.py.worlds, characters, locations).type or entity_type unless that field exists in the domain model.created_at, updated_at, start_date, end_date).{
"worlds": [],
"characters": [],
"locations": [],
"quests": [],
"items": [],
"events": [],
"stories": [],
"storylines": [],
"tags": [],
"images": [],
"choices": [],
"flowcharts": [],
"handouts": [],
"inspirations": [],
"environments": [],
"banners": [],
"character_relationships": [],
"factions": [],
"shops": [],
"maps": [],
"notes": [],
"requirements": [],
"sessions": [],
"tokenboards": [],
"pity": [],
"pulls": [],
"player_profiles": [],
"currencies": [],
"rewards": [],
"purchases": [],
"event_chains": [],
"faction_memberships": [],
"lore_axioms": [],
"music_controls": [],
"music_states": [],
"music_themes": [],
"music_tracks": [],
"progression_events": [],
"character_states": [],
"textures": [],
"models": [],
"next_id": 1
}
Use these minimum fields so JSON loads without validation errors:
id, name, description, created_at, updated_at, versionid, world_id, name, backstory, status, abilities, created_at, updated_at, versionid, world_id, name, description, location_type, created_at, updated_at, versionid, world_id, name, description, objectives, status, participant_ids, reward_ids, created_at, updated_at, versionIf a field is unknown, set it to null or an empty list (for arrays), but keep the key.