optimize-simplicite-logs
Parses Simplicité logs into structured JSON, significantly reducing token consumption.
Install
mkdir -p .claude/skills/optimize-simplicite-logs && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/16001" && unzip -o skill.zip -d .claude/skills/optimize-simplicite-logs && rm skill.zipInstalls to .claude/skills/optimize-simplicite-logs
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
capability to parse Simplicité logs from a raw `.txt` file, filter fields to reduce noise, and output the result as structured JSON.Key capabilities
- →Parse Simplicité logs from a raw .txt file.
- →Filter log fields to reduce noise and context size.
- →Output structured JSON from log data.
- →Capture stack traces and multiline errors within the 'body' field.
- →Print parsed JSON directly to stdout if no output path is specified.
- →Optimize AI context size by extracting relevant log fields.
How it works
The skill uses a Python or PowerShell script to parse a raw Simplicité .txt log file, filters specified fields, and converts the data into a structured JSON format.
Inputs & outputs
When to use optimize-simplicite-logs
- →Reducing context size for AI analysis
- →Parsing Simplicité error logs
- →Troubleshooting application logs
About this skill
Optimize Simplicite Logs
This skill provides the capability to parse Simplicité logs from a raw .txt file, filter fields to reduce noise, and output the result as structured JSON. This is critical for optimizing AI context size (saving ~56% of tokens) and providing structured, predictable data for troubleshooting.
When to Use This Skill
Use this skill when you need to:
- Analyze user-provided Simplicité log files in
.txtformat. - Avoid ingesting massive raw log files into your context window.
- Extract structured fields (like
timestamp,level,body) from verbose multi-line log output.
IMPORTANT: Instead of directly reading a raw .txt log file provided by the user using file read tools, you must use one of the log converter scripts (PowerShell or Python) to parse the file into a JSON format first, optionally extracting only the fields needed.
Prerequisites
- Access to either the PowerShell script (
/scripts/SimpliciteLog2Json.ps1) or the Python script (/scripts/simplicite-log2json.py).
Core Capabilities
1. Context Optimization
Reduces the tokens consumed by large Simplicité logs by extracting only relevant log fields (e.g. body, timestamp, level) and discarding non-relevant structural log data (like app, endpoint, contextPath).
2. Multi-line Support
Properly captures stack traces and multiline errors inside the body field of the JSON structure, which a simple text search might miss.
3. Stdout Support
If no output path is provided for the JSON file (e.g. omitting --output or -Output), the parsed JSON will be printed directly to stdout, allowing you to pipe the output to other tools.
Output Summary
After processing, the tool prints a summary to stderr (or console):
Processed: 123 entries, Skipped: 2 entries
Usage Examples
Example 1: Python Version (Recommended)
Convert a log file to JSON, keeping only the most important fields:
python /absolute/path/to/skills/optimize-simplicite-logs/scripts/simplicite-log2json.py <input.txt> --include timestamp,level,body --output <output.json>
Example 2: PowerShell Version
/python /absolute/path/to/skills/optimize-simplicite-logs/scripts/SimpliciteLog2Json.ps1 -InputPath "<input.txt>" -Output "<output.json>" -Include "body,timestamp,level"
After generating the <output.json>, you can safely read the resulting file to perform your analysis.
Guidelines
- Always Convert First: Never directly read
.txtlog files from Simplicité using standard text reading tools. Always convert them to JSON using the available scripts. - Filter Fields: Use
--include(Python) or-Include(PowerShell) to restrict fields to what is absolutely necessary to diagnose the issue (usuallytimestamp,level,body). - Available Fields: The fields you can filter include:
timestamp,app,level,endpoint,contextPath,event,user,class,function,rowId,body.
Common Patterns
Pattern: Fast Contextual Troubleshooting
# 1. Run the script to generate a minified JSON output in the current directory
python /absolute/path/to/skills/optimize-simplicite-logs/scripts/simplicite-log2json.py logs.txt --include timestamp,level,body --output logs_minified.json
# 2. Then read logs_minified.json to understand the context.
Limitations
- The parser depends on a fixed regex pattern that matches the standard Simplicité log output. If the log format has been heavily customized, parsing might fail or degrade.
When not to use it
- →When the log files are not from Simplicité.
- →When the log files are not in .txt format.
- →When the log format has been heavily customized and does not match the standard Simplicité output.
Prerequisites
Limitations
- →The parser depends on a fixed regex pattern that matches the standard Simplicité log output.
- →Parsing might fail or degrade if the log format has been heavily customized.
- →The skill is specifically for Simplicité log files.
How it compares
This workflow transforms verbose text logs into a structured, filtered JSON format, which is more efficient for AI context and troubleshooting than directly processing raw text files.
Compared to similar skills
optimize-simplicite-logs side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| optimize-simplicite-logs (this skill) | 0 | 3mo | Review | Intermediate |
| elasticsearch-analysis | 2 | 5mo | Review | Intermediate |
| observability | 1 | 6mo | No flags | Advanced |
| token-data-sources | 0 | 5mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by github
View all by github →You might also like
elasticsearch-analysis
incidentfox
Elasticsearch/OpenSearch log analysis using Lucene query syntax and Query DSL. Use when investigating issues via ELK stack, OpenSearch, or any Elasticsearch-based logging.
observability
incidentfox
Log, metric, and trace analysis methodology. Use when analyzing logs, investigating errors, querying metrics, or correlating signals across observability backends (Coralogix, Datadog, CloudWatch).
token-data-sources
justinchuby
When debugging why the analysis page shows missing or zero token data, or when adding new cost/usage visualizations.
lmt
SELISEdigitalplatforms
Use this skill for viewing service logs, filtering logs by date, streaming live logs, browsing distributed traces, or analyzing API performance and HTTP status distributions on SELISE Blocks.
langsmith-qa-postmortem
mikhailkogan17
Investigate EasyOref Q&A pipeline failures using LangSmith traces. Use when: Q&A answer wrong, Q&A timeout, bot didn't reply, intent misclassified, context empty, answer hallucinated, off_topic false positive. Requires LangSmith MCP tools.
arize-link
TruMedia-Creative
Generate deep links to the Arize UI. Use when the user wants a clickable URL to open a specific trace, span, session, dataset, labeling queue, evaluator, or annotation config.