KS
Killer-Skills

json-formatter — how to use json-formatter how to use json-formatter, json-formatter setup guide, json-formatter alternative, json-formatter vs other formatters, what is json-formatter, json-formatter install, json-formatter for AI agents, json output formatting, valid JSON generation, Lore GUI data loading

v1.0.0
GitHub

About this Skill

Perfect for Worldbuilding Agents needing standardized JSON output formatting for Lore GUI compatibility. json-formatter is a base skill for formatting JSON output, following rules for valid JSON, export schema, and plural collections.

Features

Generates valid JSON with no trailing commas or comments
Uses the GUI export format defined in src/presentation/gui/lore_data.py
Supports plural collections with top-level keys and array values
Loads JSON data into the Lore GUI using LoreData.from_dict
Follows a defined export schema for consistent data formatting
Produces parseable JSON for seamless integration with other tools

# Core Topics

bivex bivex
[0]
[0]
Updated: 3/7/2026

Quality Score

Top 5%
54
Excellent
Based on code quality & docs
Installation
SYS Universal Install (Auto-Detect)
Cursor IDE Windsurf IDE VS Code IDE
> npx killer-skills add bivex/loreSystem/json-formatter

Agent Capability Analysis

The json-formatter MCP Server by bivex is an open-source Categories.community integration for Claude and other AI agents, enabling seamless task automation and capability expansion. Optimized for how to use json-formatter, json-formatter setup guide, json-formatter alternative.

Ideal Agent Persona

Perfect for Worldbuilding Agents needing standardized JSON output formatting for Lore GUI compatibility.

Core Value

Empowers agents to produce parseable JSON with a defined export schema, utilizing the GUI export format and supporting plural collections, to seamlessly load data into the Lore GUI via LoreData.from_dict, leveraging JSON validation and export schema definition from src/presentation/gui/lore_data.py.

Capabilities Granted for json-formatter MCP Server

Formatting JSON output for worldbuilding data
Generating valid JSON for Lore GUI data loading
Standardizing entity collections with plural names and array values

! Prerequisites & Limits

  • Requires adherence to valid JSON rules, no trailing commas or comments
  • Must use defined export schema from src/presentation/gui/lore_data.py
Project
SKILL.md
2.4 KB
.cursorrules
1.2 KB
package.json
240 B
Ready
UTF-8

# Tags

[No tags]
SKILL.md
Readonly

json-formatter

Base skill for JSON output formatting. All extraction skills produce JSON that can be loaded by the Lore GUI (LoreData.from_dict).

Rules

  1. Valid JSON: Output must be parseable JSON — no trailing commas, no comments.
  2. Export schema: Use the GUI export format defined in src/presentation/gui/lore_data.py.
  3. Plural collections: Each entity collection is a top-level key with a plural name and an array value (e.g., worlds, characters, locations).
  4. IDs are consistent: Use integer IDs for GUI export collections. For entity types that use UUIDs in the domain model, use UUID strings consistently across references.
  5. Field names: Use exact domain field names (snake_case). Do not invent type or entity_type unless that field exists in the domain model.
  6. Dates: Use ISO 8601 strings for timestamps (created_at, updated_at, start_date, end_date).

Output Structure (Export-Compatible)

json
1{ 2 "worlds": [], 3 "characters": [], 4 "locations": [], 5 "quests": [], 6 "items": [], 7 "events": [], 8 "stories": [], 9 "storylines": [], 10 "tags": [], 11 "images": [], 12 "choices": [], 13 "flowcharts": [], 14 "handouts": [], 15 "inspirations": [], 16 "environments": [], 17 "banners": [], 18 "character_relationships": [], 19 "factions": [], 20 "shops": [], 21 "maps": [], 22 "notes": [], 23 "requirements": [], 24 "sessions": [], 25 "tokenboards": [], 26 "pity": [], 27 "pulls": [], 28 "player_profiles": [], 29 "currencies": [], 30 "rewards": [], 31 "purchases": [], 32 "event_chains": [], 33 "faction_memberships": [], 34 "lore_axioms": [], 35 "music_controls": [], 36 "music_states": [], 37 "music_themes": [], 38 "music_tracks": [], 39 "progression_events": [], 40 "character_states": [], 41 "textures": [], 42 "models": [], 43 "next_id": 1 44}

Required Fields (Core Entities)

Use these minimum fields so JSON loads without validation errors:

  • worlds: id, name, description, created_at, updated_at, version
  • characters: id, world_id, name, backstory, status, abilities, created_at, updated_at, version
  • locations: id, world_id, name, description, location_type, created_at, updated_at, version
  • quests: id, world_id, name, description, objectives, status, participant_ids, reward_ids, created_at, updated_at, version

If a field is unknown, set it to null or an empty list (for arrays), but keep the key.

Related Skills

Looking for an alternative to json-formatter or building a Categories.community AI Agent? Explore these related open-source MCP Servers.

View All

widget-generator

Logo of f
f

widget-generator is an open-source AI agent skill for creating widget plugins that are injected into prompt feeds on prompts.chat. It supports two rendering modes: standard prompt widgets using default PromptCard styling and custom render widgets built as full React components.

149.6k
0
Design

chat-sdk

Logo of lobehub
lobehub

chat-sdk is a unified TypeScript SDK for building chat bots across multiple platforms, providing a single interface for deploying bot logic.

73.0k
0
Communication

zustand

Logo of lobehub
lobehub

The ultimate space for work and life — to find, build, and collaborate with agent teammates that grow with you. We are taking agent harness to the next level — enabling multi-agent collaboration, effortless agent team design, and introducing agents as the unit of work interaction.

72.8k
0
Communication

data-fetching

Logo of lobehub
lobehub

The ultimate space for work and life — to find, build, and collaborate with agent teammates that grow with you. We are taking agent harness to the next level — enabling multi-agent collaboration, effortless agent team design, and introducing agents as the unit of work interaction.

72.8k
0
Communication