lin

v1.0.0

Generate annual insurance welfare Word reports from `gh_hg_bscyearall_dues` in OpenClaw format. The packaged Python entry extracts the target year, inspects...

0· 88·0 current·0 all-time
by番茄番茄番茄范@lin-shiwu

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for lin-shiwu/annual-insurance-word-report.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "lin" (lin-shiwu/annual-insurance-word-report) from ClawHub.
Skill page: https://clawhub.ai/lin-shiwu/annual-insurance-word-report
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install annual-insurance-word-report

ClawHub CLI

Package manager switcher

npx clawhub@latest install annual-insurance-word-report
Security Scan
VirusTotalVirusTotal
Pending
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description, SKILL.md, skill.json, and src/main.py all describe querying a MySQL table, reading INFORMATION_SCHEMA column comments, mapping fields, and producing a .docx from a bundled base64 template. The declared inputs (db_host, db_user, db_password, database, table_name, year, etc.) are exactly what this task needs.
Instruction Scope
Runtime instructions are focused: install requirements, run src/main.py with db parameters or request_text. The entry code reads the bundled base64 template, queries MySQL (via PyMySQL or a mysql CLI fallback), reads INFORMATION_SCHEMA, and writes outputs/. It does not contact external network endpoints or attempt to read unrelated system files. Note: the code may invoke the mysql CLI via subprocess.run when PyMySQL isn't available — this is expected for the provided fallback but means the system must have mysql on PATH if used.
Install Mechanism
There is no remote download; requirements.txt only lists PyMySQL. The template is embedded in-repo as a base64 text file. No install script pulls arbitrary code from the network or writes binary blobs to unusual locations.
Credentials
The skill requests database connection parameters as inputs (db_host/db_user/db_password/database/table_name), which are proportionate to querying MySQL. No unrelated environment variables or external service credentials are requested.
Persistence & Privilege
always is false; the skill is user-invocable and does not request permanent/force-installed privileges or modify other skills or system-wide agent settings.
Scan Findings in Context
[base64-block] expected: A large base64-encoded Word template is embedded in assets/beijing_office_annual_template.docx.base64.txt. The base64 presence is expected for an included .docx template; the pre-scan flagged a base64 block but that is consistent with the described behavior.
Assessment
This skill appears to do what it says: generate a .docx report from a MySQL table using an embedded template. Before running it: (1) don't run it with high-privilege or production DB credentials — provide a least-privilege, read-only account scoped to the reporting schema; (2) inspect the bundled template (assets/...base64.txt) if you need to confirm its contents; (3) be aware the code may call the mysql CLI fallback (subprocess.run) if PyMySQL is unavailable — ensure mysql on PATH is the binary you expect; (4) run in an isolated environment if you are unsure (or review the full src/main.py for any additional behavior). Overall there are no red flags that contradict the declared purpose, but treat any DB access as sensitive and use appropriate credentials and environment isolation.

Like a lobster shell, security has layers — review code before you run it.

latestvk972032txnhvqkxym4gs7q70hs842dpm
88downloads
0stars
1versions
Updated 3w ago
v1.0.0
MIT-0

Annual Insurance Word Report

What this package does

  • Resolves the target year from year or from request_text
  • Queries gh_hg_bscyearall_dues
  • Reads INFORMATION_SCHEMA.COLUMNS comments before rendering
  • Fills the bundled yearly Word template without depending on Word COM
  • Writes the finished .docx file to outputs/ by default

Inputs

  • request_text: optional natural-language request, for example 帮我生成2023年业务报告
  • year: optional explicit year, for example 2023
  • template_path: optional custom .docx template path
  • output_path: optional custom output .docx path
  • db_host: optional, default 127.0.0.1
  • db_port: optional, default 3306
  • db_user: optional, default root
  • db_password: optional, default root
  • database: optional, default test_db
  • table_name: optional, default gh_hg_bscyearall_dues
  • charset: optional, default utf8mb4
  • mysql_cli: optional fallback path to mysql CLI if PyMySQL is unavailable

Run

Install dependencies:

pip install -r requirements.txt

Run with an explicit year:

python src/main.py --year 2023

Run with request text extraction:

python src/main.py --request-text "帮我生成2023年业务报告"

Custom database example:

python src/main.py --year 2023 --database test_db --db-user root --db-password root

Notes

  • The default output path is outputs/annual-insurance-report-<year>.docx.
  • The default template is stored as text in assets/beijing_office_annual_template.docx.base64.txt and is restored to a temporary .docx at runtime.
  • The package keeps the original business mapping: 团意、子女、女工、重疾、轻症、住院、津贴、补充、两癌、综合A、综合B、合计.
  • If PyMySQL is not installed, the entry falls back to the mysql CLI when mysql_cli is provided or mysql is on PATH.

Comments

Loading comments...