Sometimes an AI gives you a technically correct answer, but you still cannot follow the explanation. It may skip an important step, introduce too many new terms, or assume you already know a specialist concept.
I created Reexplain For Me, a reusable AI agent skill that addresses this problem. Instead of explaining everything from zero, it starts with what you already know and walks through the difficult part, one step at a time.
What does Reexplain For Me do?
The skill is intended for adults who already know the basics of a subject, but need help with a particular advanced concept. It is especially useful when reading technical documentation, understanding software behaviour, or comparing implementation choices.
Its instructions tell the AI agent to:
Give a short, useful answer before the detailed explanation.
Explain one new idea at a time and define unfamiliar technical terms.
Use one consistent example across several steps, rather than switching examples halfway.
Explain where an analogy stops being accurate.
Correct factual mistakes directly, without unnecessary praise.
Compare choices using their benefits, limitations, risks, and requirements.
Confidence labels help you judge the answer
Another feature is explicit confidence tagging. The skill asks the AI to distinguish what is supported by evidence from what is inferred or uncertain:
[Certain]: a claim supported by checked evidence or a demonstrated calculation.
[Likely]: a strong inference based on the available evidence.
[Guessing]: a claim with insufficient evidence, including an explanation of what information is missing.
These labels are not a guarantee that the model is correct. They are a way to make its assumptions and uncertainty easier to inspect.
How to use Reexplain For Me
With an AI agent that has the skill installed, invoke it by name and identify where the explanation became difficult:
Use $reexplain-for-me. I know what a database index does.
Walk me through why a query planner might scan the whole table anyway.
Use one example and carry it through each step.
If you still do not understand a particular step, you can ask the agent to return to that step and explain it with a smaller example. You can also include a passage, diagram description, or error message to give the agent more context.
Can I use it with other AI agents?
The repository provides the skill in SKILL.md format, with additional Codex metadata under agents/openai.yaml. It is written primarily as a Codex skill, but the instructions are plain text and can be reused in other AI agent environments.
For agents that support compatible skill files, install it using that agent’s supported skill location or import method. For agents that do not, you can adapt the contents of SKILL.md as custom instructions or a reusable prompt. The exact installation procedure and invocation command depend on the agent; not every platform recognizes $reexplain-for-me automatically.
Get the skill on GitHub
Reexplain For Me is available in my GitHub repository. Read the README for the usage example and the complete SKILL.md for its response rules.
The objective is simple: make AI explanations easier to follow without talking down to technically competent readers, hiding uncertainty, or agreeing with incorrect assumptions.
Running a local AI system such as Ollama, Open WebUI, or a Retrieval-Augmented Generation (RAG) application often means preparing a collection of PDF files, Microsoft Word documents, and LibreOffice files. These formats are useful for everyday work, but they are not always easy to parse or index correctly.
MarkForge converts these files into Markdown, a simple text format suitable for local AI knowledge bases. In this guide, we will install the Punctiq version of MarkForge using Docker on Ubuntu Linux and convert documents without sending them to an external service.
MarkForge is an open-source, self-hosted document converter. It supports batch processing, Markdown previews, extraction of figures, optional AI-assisted cleanup, and ZIP exports containing converted documents and associated files.
Document type
Supported extension
PDF
.pdf
Microsoft Word
.docx
Legacy Microsoft Word
.doc
OpenDocument Text
.odt
Important: Several unrelated projects also use the MarkForge name. This article covers github.com/Punctiq/markforge. Its supported Office document formats do not include Excel, PowerPoint, or OpenDocument spreadsheet/presentation files.
Why Markdown for Local AI?
Markdown is plain text with lightweight structure. It can preserve headings, paragraphs, lists, simple tables, and image references without the additional formatting data found in Word files and PDFs.
For a local RAG system, Markdown content can be split into smaller sections, embedded, and stored in a vector database. Keeping the headings can also make the retrieved passages easier to understand. However, conversion is not a guarantee of accurate extraction. Tables, equations, and multi-column pages still need to be checked.
Step 1: Install MarkForge with Docker
We will use Docker on Ubuntu. The project’s Docker image includes dependencies such as LibreOffice and Pandoc.
Clone the source repository:
git clone https://github.com/Punctiq/markforge.git
cd markforge
With the API key left empty, MarkForge can perform normal document conversion without invoking an external AI model. Keep AUTH_ENABLED=false only if the application remains restricted to your own machine or another trusted environment.
Build and start the application:
docker compose up -d --build
Open http://127.0.0.1:8010 in a browser on the Docker host. The provided Compose configuration binds port 8010 to the host’s loopback address, rather than exposing the service directly to the local network or internet.
Check whether the service is responding:
curl http://127.0.0.1:8010/api/v1/health
Step 2: Convert PDF, Word, and ODT Files
Open the MarkForge web interface.
Select a .pdf, .docx, .doc, or .odt document.
Disable AI Cleanup for conversion without LLM calls.
Start conversion and inspect the resulting Markdown preview.
Download the Markdown or the ZIP package containing the output and figures.
The ZIP package is helpful when a document has figures that need to remain together with the Markdown file.
Automate a conversion with curl
MarkForge also provides a conversion API. For example, to convert manual.pdf into a ZIP package:
This approach can be adapted to a local document-processing script. Check the API response and converted content before automatically indexing the output.
PDF limitation: This version uses PyMuPDF to extract existing text. Image-only scanned pages without selectable text are not automatically processed with OCR. Perform OCR separately before conversion if your PDF consists of scanned pages.
Step 3: Optional AI Cleanup with Ollama
MarkForge can optionally send extracted Markdown to an LLM for formatting cleanup. It supports OpenAI-compatible endpoints, including a locally hosted Ollama server.
For MarkForge installed directly on the same host as Ollama, a basic configuration is:
Use a model that you actually have installed. Docker users must change the endpoint: inside the MarkForge container, 127.0.0.1 refers to the container itself, not the machine running Ollama. Configure a reachable host or Docker network address before enabling cleanup.
Safe, Balanced, and Aggressive cleanup modes are available. For technical, academic, and compliance-related documents, begin with Safe mode and compare the output against the original document. An LLM may alter terminology, numbers, or meaning while attempting to improve formatting.
Step 4: Import Markdown into a Local AI Knowledge Base
After conversion, place the Markdown files and extracted figures inside a local folder:
You can then import the documents into an Open WebUI knowledge collection or process them in a custom RAG pipeline. For lengthy material, splitting content by section headings often makes chunks more useful than splitting at arbitrary positions.
Before indexing, check headings, reading order, tables, equations, citations, and references to images. Keep a copy of the source file for future verification.
Why Privacy Matters When Converting Documents
Many websites offer free PDF-to-Markdown and Word-to-Markdown conversion. While convenient, uploading files to a service you do not control may expose confidential information.
This is particularly important for documents containing student records, unpublished academic manuscripts, internal technical specifications, contracts, financial details, or other personal information.
When using a third-party service, you may not have full visibility into document retention, server logging, subcontractors, or how uploaded data is processed. Privacy claims should be checked against the provider’s actual terms and technical practices.
Self-hosting reduces unnecessary exposure by keeping processing on infrastructure under your control. It does not automatically guarantee privacy. If you enable a remote LLM provider for AI cleanup, extracted document content may still leave your network.
For sensitive documents, keep conversion local, disable cloud cleanup, restrict access to the MarkForge server, and secure temporary files and converted outputs. Never expose an unauthenticated document converter directly to the public internet.
Final Thoughts
MarkForge provides a straightforward way to convert PDF, Word, and OpenDocument Text files into Markdown for Ollama, Open WebUI, and other local AI workflows. Its self-hosted installation is useful when the documents should remain on your own computer or trusted server.
For a private RAG knowledge base, the recommended workflow is simple: convert locally, inspect the Markdown, and then index only the verified content.
I’ve put my latest project on GitHub: renogybt-emulator, a Python library and command-line tool that emulates the Bluetooth interface exposed by Renogy BT-1 and BT-2 modules connected to an MPPT solar charge controller.
The aim is to make it easier to develop and test solar-monitoring software without needing a physical controller, solar panels or batteries on the desk.
TLDR; This software make a Linux computer behave like a Renogy solar charge controller over Bluetooth, so you can test your apps without physical solar equipment.
Demo Screenshots From Official Renogy Mobile Application
How it works
The BT-1 and BT-2 modules provide Bluetooth Low Energy (BLE) access to Renogy equipment, using RS232 and RS485 respectively on the controller side. My emulator runs on a Linux computer with a BLE adapter and presents the Bluetooth services and simulated controller data that a compatible client expects.
Underneath, it implements the BLE GATT services and characteristics used for communication, together with a Modbus RTU responder. A client sends a request over Bluetooth, and the emulator replies with values from its simulated register bank. Those values include battery voltage, charging current, solar power, temperatures and load status.
This lets a monitoring application connect to an emulated device and exercise its normal communication path.
Updated 22 October 2026. Commands below target Ubuntu/Debian package installations.
PHP has released emergency fixes for CVE-2026-109618 and CVE-2026-109619, both rated critical at CVSS 9.2. They can allow unauthenticated remote code execution. One involves unsafe out-of-memory cleanup; the other involves stale internal state across requests. Apache mod_php has a demonstrated attack before application code runs. PHP-FPM also requires patching. See the official announcement.
1. Check and update PHP
Back up your database, application files and configuration. Identify every runtime:
Check vendor backports. Ubuntu fixes include 8.3.6-0ubuntu0.24.04.13 for 24.04 and 8.5.4-0ubuntu1.5 for 26.04. Compare complete revisions against Ubuntu’s security notice. Other repositories need their own advisories. An older-looking version can contain the fix.
Confirm the web runtime afterward and test login, uploads and database access. Updating WordPress or OJS alone does not update PHP.
2. Update containers separately
Host updates do not patch container PHP. Confirm a patched image exists, then replace app with your Compose service:
Typical Ubuntu paths are /etc/php/8.3/fpm/php.ini for FPM and /etc/php/8.3/apache2/php.ini for mod_php. Adjust the branch number. php --ini reports CLI configuration only.
Test these example values. Disable file uploads if unused. Apply upload-progress settings at startup, then restart workers; application code and FPM .user.ini are too late for the confirmed early path.
Test Nginx with sudo nginx -t before reloading, or Apache with sudo apache2ctl configtest. These limits reduce exposure; they do not fix either CVE.
4. Emergency mitigation while patching
Prefer removing public PHP access and serving a static maintenance page. A PHP maintenance plugin still invokes PHP.
The OOM advisory recommends this incomplete emergency measure in the relevant FPM pool, such as /etc/php/8.3/fpm/pool.d/www.conf:
php_admin_value[memory_limit] = -1
This removes one controllable OOM trigger but permits unlimited per-request PHP memory, increasing denial-of-service risk. Use frontend limits and suitable cgroup/container boundaries. Underlying allocation failures remain dangerous; do not substitute RLIMIT_AS or RLIMIT_DATA. Audit overrides and restart all workers. Restore suitable finite PHP limits after patching.
For PHP 8.5, also set fatal_error_backtraces=0 in startup configuration. Remove invalid or obsolete per-request INI settings. These address specific stale-state paths only. Hiding warnings provides no protection.
5. Retire public PHP 7.4 applications
PHP 7.4 reached upstream end of life on 28 November 2022. Retire unused applications or migrate them to supported PHP. Legacy source patches and vendor fixes exist, but require explicit verification and should support temporary migration arrangements.
Remove forgotten subdomains, restrict administration through VPN/access policies, and keep FPM off public port 9000. Review logs, unexpected files, accounts and scheduled tasks. Patching does not remove existing backdoors. If compromise is suspected, isolate the system and preserve evidence. Follow NCSC guidance.
Forgotten the password to an old PDF? You can try recovering it locally on Linux with pdfcrack.
This guide covers recovery of the password needed to open a PDF. Use it on your own files or files you have permission to recover.
IMPORTANT:pdfcrack runs on the CPU and has no built-in CUDA or NVIDIA GPU support. For NVIDIA acceleration, use Hashcat instead.
Start with a small password dictionary
A dictionary is a text file containing one password candidate per line. Start with a short list of passwords you remember using, then try common-password lists. This keeps the first attempt quick and helps check that the setup works before running a larger job.
SecLists password collection: browse other lists when the initial attempt fails. Choose password lists rather than web directory or URL lists.
CrackStation dictionaries: the download page offers a human-password list of about 64 million entries and a full dictionary requiring about 15 GiB when extracted. Try these later, after smaller lists.
This takes the first 1,000 lines. It does not guarantee that they are the best candidates. Extract compressed dictionaries before using them. A larger dictionary takes longer and still cannot recover a password that is absent from the list.
Recover a PDF password with pdfcrack
Install pdfcrack on Ubuntu:
sudo apt update
sudo apt install pdfcrack wget
Replace locked.pdf with your PDF filename:
pdfcrack -f locked.pdf -w small.txt
The -f option selects the PDF and -w selects the dictionary. User-password recovery is the default. If the first list fails, repeat with common-passwords.txt. See the pdfcrack manual for other options.
The project documents support for standard security-handler revisions 2, 3 and 4. Unsupported encryption requires another tool. Installing NVIDIA drivers will not add GPU support to pdfcrack.
You need a working NVIDIA driver and a compatible CUDA installation. The Hashcat requirements page lists the NVIDIA CUDA Toolkit requirement. Confirm that hashcat -I detects your NVIDIA GPU before continuing. A working nvidia-smi alone does not confirm that Hashcat can use it.
Hashcat needs an extracted password-verification record, rather than the PDF itself. The third-party pdf2hashcat script can prepare it locally:
Select the matching PDF mode using the identification output and Hashcat’s example hashes. The encryption settings determine the mode. The PDF filename or version alone is insufficient.
For example, only if mode 10500 matches your extracted record:
Here, -a 0 selects a dictionary attack, while --show displays recovered results. Check the startup output to confirm that the NVIDIA device is being used. Mode 10500 is not suitable for every PDF.
Exhausted means the selected candidates were tried without a match. It does not mean the PDF has no password. GPU acceleration can increase guessing speed, but recovery time depends on the encryption and password. A long random password may remain impractical to recover.
Some Linux tools bring back memories as soon as you open them. Midnight Commander is one of those tools. Its familiar blue panels, text menus, and function keys recall the days when managing files in a terminal was an ordinary part of using a computer.
Known simply as mc, GNU Midnight Commander is a terminal file manager with two directory panels. Open your source folder on one side and the destination on the other, then browse and copy files using the keyboard.
For anyone who remembers DOS-era file managers, this layout feels familiar. The available actions appear along the bottom of the screen, and the keyboard does most of the work. There is something satisfying about seeing both folders at once and moving through them without repeatedly typing ls and cd.
Midnight Commander also remains useful when working on a Linux server through SSH. It runs inside the terminal, so you can browse directories, inspect files, and organise folders without opening a graphical desktop. It includes a file viewer and an editor, too.
How to install Midnight Commander on Ubuntu
Install it using Ubuntu’s package manager:
sudo apt update
sudo apt install mc
Then launch it:
mc
Start with these shortcuts, documented in the official manual:
Key
Action
Tab
Switch between panels
F1
Open help
F3
View a file
F4
Edit a file
F5
Copy files
F6
Move or rename files
F7
Create a directory
F8
Delete files
F10
Quit
Modern desktops have changed how we manage files, but this old style still has its appeal. Two panels, clear actions, and a keyboard within reach are enough to make routine file management comfortable. If you have not used Midnight Commander for years, try typing mc again.