json-repair
Use the `json_repair` Python library to fix invalid/malformed JSON, especially output from LLMs. Trigger this skill whenever you encounter broken JSON strings, need to parse unreliable JSON from model outputs, want a drop-in replacement for json.loads() that auto-repairs, or are building pipelines that consume LLM-generated JSON. Also use when the user mentions "json repair", "fix json", "malformed json", "invalid json from LLM", or needs to robustly parse JSON that may have missing quotes, trailing commas, unescaped characters, or other common LLM output defects.
What this skill does
# json_repair
A zero-dependency Python module that repairs invalid JSON strings — designed
specifically for the messy output LLMs produce (missing quotes, trailing commas,
unescaped characters, incomplete structures).
Install: `pip install json-repair`
## Quick Reference
### Core API
**`repair_json(json_str, return_objects=False, skip_json_loads=False, ensure_ascii=True, strict=False, schema=None, stream_stable=False, **kwargs)`\*\*
Repairs a JSON string. Returns a valid JSON string by default, or a Python object
when `return_objects=True`. Passes through all `json.dumps()` kwargs (indent, etc).
**`json_repair.loads(json_str, **kwargs)`** — drop-in replacement for `json.loads()`.
Returns a Python object. Accepts same kwargs as `repair_json`.
**`json_repair.load(fd, **kwargs)`** — drop-in replacement for `json.load()`.
Reads from a file descriptor.
**`json_repair.from_file(path, **kwargs)`\*\* — reads and repairs JSON from a file path.
### Usage Patterns
**Simple repair (string → string):**
```python
from json_repair import repair_json
fixed = repair_json('{"name": "test", "value": 42,}')
```
**Direct to object (fastest path — skips serialization):**
```python
import json_repair
obj = json_repair.loads(bad_json_string)
# or equivalently:
obj = json_repair.repair_json(bad_json_string, return_objects=True)
```
**From file:**
```python
import json_repair
obj = json_repair.from_file("output.json")
# or with file descriptor:
with open("output.json", "rb") as f:
obj = json_repair.load(f)
```
### Key Parameters
`return_objects=True` — return Python object instead of JSON string. Always faster
because it skips re-serialization.
`skip_json_loads=True` — skip the initial `json.loads()` validation check. Faster
only when you already know the input is invalid.
`ensure_ascii=False` — preserve non-Latin characters (CJK, Cyrillic, etc) in output
instead of escaping to `/uXXXX`.
`strict=True` — raise `ValueError` on structural issues (duplicate keys, missing
separators, empty keys) instead of repairing them. Useful for validation with
friendly error messages.
`stream_stable=True` — enable streaming-compatible repairs for incremental JSON input.
`schema=<dict|PydanticModel>` — guide repairs with a JSON Schema or Pydantic v2 model.
Requires `pip install 'json-repair[schema]'`. Fills missing values, coerces types,
drops disallowed properties. Mutually exclusive with `strict=True`.
### What It Fixes
LLM output commonly has these defects that json_repair handles:
- Missing or mismatched quotes around keys/values
- Trailing commas in objects and arrays
- Unescaped special characters in strings
- Incomplete key-value pairs (fills with `null` or `""`)
- Missing closing brackets/braces
- Single quotes instead of double quotes
- Comments or extra non-JSON characters mixed in
- Broken arrays/objects with missing elements
- Improperly formatted boolean/null literals
### Anti-Pattern — Don't Do This
```python
# WRONG: wasteful double-parse
try:
obj = json.loads(s)
except json.JSONDecodeError:
obj = json_repair.loads(s)
# RIGHT: json_repair already checks validity first
obj = json_repair.loads(s)
# RIGHT: if you insist on try/except, at least skip the redundant check
try:
obj = json.loads(s)
except json.JSONDecodeError:
obj = json_repair.loads(s, skip_json_loads=True)
```
### Schema-Guided Repairs (Beta)
Requires: `pip install 'json-repair[schema]'`
```python
from json_repair import repair_json
schema = {
"type": "object",
"properties": {"value": {"type": "integer"}},
"required": ["value"],
}
# Coerces "1" → 1, fills missing required fields
result = repair_json('{"value": "1"}', schema=schema, return_objects=True)
```
With Pydantic v2:
```python
from pydantic import BaseModel, Field
from json_repair import repair_json
class Payload(BaseModel):
value: int
tags: list[str] = Field(default_factory=list)
result = repair_json(
'{"value": "1", "tags": }',
schema=Payload,
skip_json_loads=True,
return_objects=True,
)
# → {"value": 1, "tags": []}
```
### CLI Usage
```
pip install json-repair # or: pipx install json-repair
json_repair input.json # repair and print to stdout
json_repair -i input.json # repair in-place
json_repair -o fixed.json input.json # repair to output file
cat broken.json | json_repair # pipe from stdin
json_repair --indent 4 input.json # custom indentation
json_repair --strict input.json # validate instead of repair
json_repair --schema schema.json input.json # schema-guided repair
```
### Performance Tips
In order of impact: `return_objects=True` is always faster (skips serialization),
`skip_json_loads=True` helps when input is known-invalid, and pass raw strings
(`r"..."`) when dealing with complex escaping. The library has zero external
dependencies by design.
### Version Pinning
Pin major only: `json_repair==0.*` — the library uses strict semver with frequent
minor/patch releases and no breaking changes within a major version.
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.