About this skill

Problem

Python office automation scripts often stop at “it runs”: there is no consistent entry point, no GUI, and logs are missing. After delivery, users may still need to configure the environment, and reuse requires code changes. This skill fixes common delivery requirements and reduces the communication gap between requirements and working tools.

How It Works

The skill follows a development pipeline with these core steps:
- Requirements: confirm input data, processing logic, output format, and compatibility constraints.
- Template start: build from a tkinter GUI template with window, buttons, progress bar, and log area.
- Coding rules: enforce file-header docstring, window-title attribution, logging, and try-except handling.
- Dual delivery: produce both a single-file exe tool and a Skill component, writing source code, tools, docs, and skill_center files under D:/PY.

Boundaries

It is best for internal office scripts, batch file processing, exe packaging, and reusable componentization. If the work involves backend services, multi-client collaboration, complex permissions, or cross-platform runtime, a separate design is needed; D:/PY paths and author attribution are team conventions and can be adjusted for external projects.

Screenshots

Use Cases

Build a logged tkinter tool to clean and merge a batch of Excel files, then package it as an exe.
Turn a repeated file-renaming script into a double-click exe with usage notes.
Extract recurring data-processing logic into a Skill component that returns run(**kwargs) status.
Store source, exe, docs, and the skill component under the team D:/PY layout.

Best For

Data delivery engineers who need to turn table cleaning, aggregation, and export into double-click tools.
Python engineers responsible for internal office scripts with GUI, logs, and exe packaging.
Application developers who want to turn repeated data processing logic into reusable Skill components.
Team members who must deliver tools under the Telecom Digital Intelligence integration service naming and layout rules.