Nex Reports

Automated report generation and scheduling meta-skill that aggregates data from multiple Nex tools into unified, actionable business briefings for day-to-day...

Security Scan

The skill's code, required binaries, and environment variables match its stated purpose (aggregating Nex tool outputs and sending/saving reports); the main risks are expected features (IMAP access, Telegram delivery, and a 'custom' module that can run user-supplied shell commands) and a small packaging/installation omission to review before install.

Purpose & Capability

The name/description (aggregating Nex tools into scheduled reports) aligns with the code and declared requirements: python3, IMAP creds for the EMAIL module, and TELEGRAM_* for delivery. The modules call expected nex-* CLIs and use IMAP/ICS/JSON files where described. No unrelated credentials or unexpected external services are requested.

Instruction Scope

Runtime instructions and SKILL.md stay within the described reporting scope (creating/scheduling reports, reading IMAP, parsing ICS/task JSON, running nex-* commands, and delivering via Telegram or saving files). Important scope note: there is a CUSTOM module that runs arbitrary shell commands (module config key 'command') — this is an explicit feature of the skill but grants the ability to execute any command the config contains. The agent or user creating/editing configs could therefore cause arbitrary command execution if they supply a dangerous command. Otherwise, the instructions reference only the declared env vars and the user's home data dir (~/.nex-reports).

Install Mechanism

No formal install spec was provided in the registry (install is 'instruction-only'), but a setup.sh and CLI scripts are included in the package. That is not inherently malicious, but you should inspect setup.sh before running it because it may install the CLI into the user's environment or write files (the README describes doing so). The code itself uses only standard library modules and expects optional external nex-* binaries.

Credentials

The required environment variables (IMAP_HOST, IMAP_USER, IMAP_PASS, IMAP_PORT, TELEGRAM_TOKEN, TELEGRAM_CHAT_ID) are proportional to features (IMAP email checks and Telegram delivery). There are no unrelated secrets requested. IMAP_PASS and TELEGRAM_TOKEN are sensitive and will be used directly by the tool as expected.

Persistence & Privilege

The skill does not request always:true and does not modify other skills or global agent settings. It will create a data directory (~/.nex-reports/) and an SQLite DB for configs/history, which is expected for its function. The included setup.sh may also install a CLI; review it if you want to avoid adding binaries to your system.

Assessment

This package is coherent with its stated purpose, but review these before installing: - Inspect setup.sh before running it (it may install the CLI or write files to your home directory). - Be cautious with IMAP_PASS and TELEGRAM_TOKEN — they are sensitive credentials used for email checks and Telegram delivery; prefer app-specific passwords and a bot token limited to the needed chat. - The CUSTOM module executes arbitrary shell commands from the report configuration; do not add untrusted/opaque commands to configs or allow the agent to write configs that include commands you wouldn't run yourself. - If you plan to run scheduled jobs, run them in a controlled environment (non-root user, container, or VM) because modules may call external nex-* CLIs and the custom command feature could execute dangerous commands. - If you need higher assurance, run the tool in a sandbox, or ask the publisher for provenance/signing of releases and an explicit install script rather than running the bundled setup without review.

Scheduled Report Generator - Create, schedule, and deliver automated reports combining data from multiple Nex tools.

When to Use

Use this skill when the user asks about:

• Creating automated reports (daily, weekly, monthly)
• Morning briefings or weekly summaries
• Scheduling reports for specific times
• Combining multiple data sources into one report
• Getting health checks, CRM pipeline, expenses, deliverables in one place
• Email notifications or Telegram updates
• Report templates and presets
• Overdue items, expiring domains, vault alerts in one view
• Custom automated reporting
• Report history or viewing past reports

Trigger phrases: "create a report", "morning briefing", "weekly summary", "schedule a report", "automated report", "report briefing", "compile data", "overzicht", "samenvatting", "dagrapport", "wekelijk rapport"

Quick Start

bash setup.sh

This creates the data directory, initializes the database, and checks for nex-* command availability.

Commands

Create a Report

nex-reports create "Monday Morning" \
  --schedule "0 8 * * 1" \
  --modules health,crm,deliverables,domains \
  --output markdown \
  --output-target file

Schedule presets: DAILY_MORNING, DAILY_EVENING, WEEKLY_MONDAY, WEEKLY_FRIDAY, MONTHLY_FIRST

Run a Report

nex-reports run "Monday Morning"
nex-reports run --all

Manage Configs

nex-reports list
nex-reports show "Monday Morning"
nex-reports edit "Monday Morning" --modules health,crm,expenses
nex-reports delete "Monday Morning"

View History

nex-reports history "Monday Morning" --limit 20

Test Modules

nex-reports modules
nex-reports test health

Available Modules

• EMAIL - Check unread emails via IMAP
• CALENDAR - Parse ICS calendar file
• TASKS - Read JSON taskboard file
• HEALTH - Run nex-healthcheck check
• CRM - Run nex-crm pipeline
• EXPENSES - Run nex-expenses summary monthly
• DELIVERABLES - Run nex-deliverables overdue
• DOMAINS - Run nex-domains expiring
• VAULT - Run nex-vault alerts
• CUSTOM - Run arbitrary shell command

Output Formats

• markdown - Full markdown report for documents/email
• html - Simple HTML report
• telegram - Compact Telegram format with emojis
• json - JSON structured data

Output Targets

• file - Save to disk (~/.nex-reports/reports/)
• telegram - Send to Telegram (requires TELEGRAM_TOKEN and TELEGRAM_CHAT_ID)
• both - Save and send to Telegram

Configuration

Set via environment variables:

export IMAP_HOST=imap.gmail.com
export IMAP_USER=[e-mail]
export IMAP_PASS=your-app-password
export IMAP_PORT=993

export TELEGRAM_TOKEN=your-bot-token
export TELEGRAM_CHAT_ID=your-chat-id

Data Directory

Reports and database stored in: ~/.nex-reports/

• reports.db - SQLite database
• reports/ - Generated report files
• templates/ - (Reserved for future use)

Examples

Morning briefing combining health, CRM, and deliverables:

nex-reports create "Daily Standup" \
  --schedule "0 9 * * 1-5" \
  --modules health,crm,deliverables \
  --output telegram \
  --output-target telegram

Weekly summary to file (every Friday 5pm):

nex-reports create "Weekly Summary" \
  --schedule WEEKLY_FRIDAY \
  --modules health,crm,expenses,deliverables,domains,vault \
  --output markdown \
  --output-target file

Custom command in report:

nex-reports create "Git Status" \
  --schedule "0 10 * * *" \
  --modules custom \
  --output markdown

View the last run:

nex-reports show "Daily Standup"

Scheduling

Reports are created with cron expressions. Use an external scheduler (systemd timer, crontab, etc.) to execute:

nex-reports run "Daily Standup"

on a schedule.

---

Nex Reports by Nex AI | nex-ai.be