会议议程生成助手

This skill should be used when the user provides meeting-related information (title, venue, time, agenda items, participants, etc.) and wants to generate a f...

Security Scan

The skill appears to do what its name and description claim (generate Word/PDF meeting agendas), but there are inconsistencies in the instructions vs. the implementation and it auto-installs Python packages at runtime — review before running in a production environment.

Purpose & Capability

Name, description, and code align: the Python script builds a .docx and attempts PDF conversion using Word COM / LibreOffice / docx2pdf. No unrelated credentials, binaries, or network endpoints are requested. The functionality requested (creating agenda documents with Chinese fonts) matches the files provided.

Instruction Scope

SKILL.md stays within scope (collect meeting fields, produce JSON, run the script, deliver files). It instructs the agent to use the user's workspace or a temp folder and to attach the produced files. Nothing in the instructions asks the agent to read unrelated system files or secrets. Note: SKILL.md and the script disagree about PDF dependencies (SKILL.md mentions reportlab; the script uses docx2pdf and win32com/LibreOffice), which is a documentation/implementation mismatch to be aware of.

Install Mechanism

There is no registry install spec, but the script auto-installs Python packages at runtime using pip (subprocess.check_call with sys.executable -m pip install). This is expected for an instruction-only skill but has security implications: it will modify the Python environment where the agent runs. The packages actually checked/installed by the script are 'python-docx' and 'docx2pdf', while SKILL.md claims it will auto-install 'python-docx' and 'reportlab' — an inconsistency that suggests sloppy documentation or a change in implementation.

Credentials

The skill requests no environment variables, credentials, or config paths. The script does probe for local programs (soffice/libreoffice) and will attempt Word COM on Windows, which is proportional to PDF conversion. No network endpoints or secret exfiltration are present in the code.

Persistence & Privilege

The skill is not always-enabled and does not request elevated platform privileges. However, its runtime behavior (automatic pip installs) will persist packages into the agent's Python environment, which is effectively modifying the runtime. This is not automatically malicious but is a persistent change you should be comfortable with.

What to consider before installing

This skill appears to implement a legitimate meeting-agenda generator, but take the following precautions before installing or running it: - Review and run the script in a sandboxed environment (or a disposable virtualenv) first. The script runs pip install programmatically and may modify your Python environment. - Note the documentation/implementation mismatch: SKILL.md mentions installing 'reportlab' while the script installs/uses 'docx2pdf'. Confirm which packages you want installed and consider installing them yourself (pip install python-docx docx2pdf) in a controlled environment before letting the script auto-install. - Inspect the remainder of the script (the file was truncated in the listing). Ensure the main() entrypoint does nothing unexpected (network calls, reading unrelated files, executing arbitrary commands). - Because the script can invoke external converters (Win Word COM, LibreOffice via subprocess), running it may execute local binaries; only run where those binaries are trusted. - If you want minimal impact, run the script inside a temporary virtual environment or container so pip installs do not affect your global Python environment. If you want, I can: - show the remainder of the script's main() body if you provide it, and re-check for unexpected behavior; - suggest an easy sandbox command set to run the script safely; or - produce a fixed SKILL.md that matches the actual implementation.

Meeting Agenda Generator

Purpose

Generate professional Chinese meeting agenda documents in Word (.docx) and PDF formats. Apply the standard font and layout conventions described in references/template.md.

Trigger Conditions

Use this skill when the user:

• Provides meeting information (title, time, location, agenda, participants) and asks to generate an agenda
• Mentions keywords like "会议议程"、"议程安排"、"生成议程"、"帮我做个会议议程"
• Provides raw meeting details and asks for a formatted document output

Workflow

Step 1: Collect Meeting Information

Ask the user to provide (or extract from their message):

• 会议名称 (Meeting title)
• 环节列表 (Session list), for each session:
  • 环节名称 (Session name)
  • 时间 (Time, e.g. "2026年4月2日（星期四）09:00-10:00")
  • 地点 (Location)
  • 内容 (Content description, optional for simple sessions)
  • 主持人 (Host, optional)
  • 议程 (Agenda items list, optional)
  • 参会人员 (Participants by organization, optional)
    • 单位名称 (Organization name)
    • 成员列表: 姓名 + 职务 + 补充说明(optional)

If any critical fields are missing, ask the user before proceeding. Use references/template.md for exact field names, structure, and JSON format.

Step 2: Build the JSON Data File

Construct a JSON file following the schema in references/template.md. Save it as a temporary file, e.g. agenda_input.json, in a working directory (suggest using the user's workspace or a temp folder).

Example minimal JSON:

{
  "title": "XXX合作座谈会议议程",
  "filename": "XXX合作座谈会议议程",
  "sections": [
    {
      "name": "产品演示",
      "time": "2026年4月2日（星期四）09:00-10:00",
      "location": "XX楼会议室",
      "content": "演示核心功能"
    }
  ]
}

Step 3: Run the Generation Script

Execute scripts/generate_agenda.py with the JSON data file:

python <skill_base_dir>/scripts/generate_agenda.py \
  --data <path_to_agenda_input.json> \
  --output <output_directory>

• <skill_base_dir> is the absolute path to this skill directory (typically ~/.workbuddy/skills/meeting-agenda)
• <output_directory> is where the files will be saved (use the user's workspace directory or a subdirectory they specify)

The script will:

1. Auto-install python-docx and reportlab if not present
2. Generate <filename>.docx (Word document)
3. Generate <filename>.pdf (PDF document)

Step 4: Deliver Results

After generation:

1. Confirm both files exist
2. Report the file paths to the user
3. Use deliver_attachments tool to attach both .docx and .pdf files

Font & Style Reference

Refer to references/template.md for the complete font specification:

• Meeting title: FangSong GB2312 (仿宋_GB2312), 24pt (小一), bold, centered
• Section headings (including 人员): Heiti (黑体), 16pt, bold, left-aligned; numbered with Chinese numerals (一、二、三…)
• Field labels (时间/地点/内容/议程 etc.): Heiti (黑体), 16pt, bold
• Body text (field values, agenda items): FangSong GB2312 (仿宋_GB2312), 16pt
• Organization unit headers: Kaiti GB2312 (楷体_GB2312), 16pt, bold, preceded by two full-width spaces (　　)
• Member lines: FangSong GB2312, 16pt, NO leading dash; name and title separated by two full-width spaces (　　)

人员排列规则：

• 每个 section 如含 persons 字段，人员独立作为一个带序号的一级标题（如"三、人员"），序号接续前面环节编号

Error Handling

• If PDF generation fails (missing fonts or reportlab issues), still deliver the Word file and explain the PDF issue
• If the user's system lacks Chinese fonts, the Word file will still display correctly when opened in Word; the PDF may show fallback fonts
• If python-docx install fails, ask the user to run pip install python-docx reportlab manually