About this skill

Problem

Daily development tasks and small utilities are often scattered across websites, one-off scripts, and local apps: mortgage calculations, API tests, timestamp conversion, JSON formatting, image compression, PDF splitting, CPU usage checks. Switching tools and remembering parameters adds friction. @user_1a470ba8/dgngjx-skill groups these utilities into one Python CLI, invoked by natural-language triggers or module.tool subcommands.

How It Works

The skill exposes a unified dgngjx entry point. Starting it without arguments opens an interactive wizard, while module.tool calls invoke registered tools directly. registry.json stores module metadata, parameter schemas, dependencies, examples, and safety levels; the CLI loads only the registry at startup and defers loading tool code. Core capabilities include:
- Data and text: mortgage, social insurance, date/unit/currency conversion, Base64, MD5/SHA, word frequency, text diff, JSON, HTTP testing, and token estimation.
- Files and media: img.compress, img.removebg, PDF merge/split/encrypt, FFmpeg-based video conversion, Markdown to HTML, and CSV inspection.
- Development and system tools: QR codes, UUIDs, timestamps, IP/subnet utilities, password strength checks, CPU/memory/disk monitoring, and batch file renaming.

File access is governed by safety rules: executable scripts and system-cache-like files are hard-blocked; Office documents require confirmation; common files such as images, PDFs, and text files can be read and written directly. The CLI supports --json output and --yes for non-dangerous confirmations, while destructive operations such as deletion or overwrite remain interactive.

Boundaries

Zero-dependency tools work immediately, but image, PDF, and video features require external dependencies such as Pillow, PyPDF2, and FFmpeg. The skill does not handle online PSD editing, online Excel editing, non-browser screen recording, batch video encoding, or executable-file processing. For large files, complex video projects, or reverse-engineering work, use dedicated tools.

Screenshots

Use Cases

Debug API work by testing URLs, formatting JSON, and estimating token usage while inspecting response shapes.
Batch-process images for compression, background removal, or ID-photo generation instead of switching browser tools.
Prepare PDF deliverables by merging files, splitting selected pages, or encrypting the final document.
Check host health by viewing CPU, memory, and disk usage, then spot resource anomalies during debugging.

Best For

Frontend engineers: test APIs, format JSON, convert timestamps and color values.
QA engineers: test HTTP endpoints, validate file hashes, and generate UUIDs.
Ops engineers: monitor CPU, memory, and disk usage, batch-rename files, and export HTML.
Product managers: calculate mortgages, social insurance, dates, and exchange rates while preparing docs.