BC 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 decision making. Create custom composite reports combining curated data from nex-healthcheck (infrastructure uptime and service health), nex-crm (sales pipeline status and hot prospects), nex-expenses (spending patterns and budget tracking), nex-deliverables (project progress and overdue items), nex-domains (domain expiry alerts and SSL certificate warnings), and nex-vault (contract expirations and renewal deadlines). Schedule reports to run fully automatically on recurring schedules (daily, weekly, monthly) using standard cron expressions and pre-built convenient presets (DAILY_MORNING at 8am, WEEKLY_MONDAY, WEEKLY_FRIDAY, MONTHLY_FIRST). Generate morning briefings for team standups, weekly summaries for stakeholder reviews, or monthly business reviews for strategic planning in multiple output formats (markdown for email with professional formatting, simple HTML, compact Telegram format with emojis, structured JSON for API integration). Route report delivery via Telegram for instant mobile notifications and team alerts or save generated reports to files for email distribution, client sharing, and documentation archives. Perfect for Belgian agency operators, business owners, and management teams who need daily or weekly snapshots of overall business health without manual data compilation overhead.
As a process C 58/100 · Has gaps — weak spots: inputs and preconditions, failures and branches, running it twice
How to improve
- Shorten the description to 1024 characters.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 2
✓ No critical or high findings
Medium and low: 2
-
low Exfiltration
exfil-webhook-urllib/notifier.py:29Webhook / callback URL commonly used for exfiltration (verify the destination) (the skill's own vendor host; quoted — discussed, not commanded)url = f"https://api.telegram.org/bot{token}/sendMessage"vendor-hostquoted -
low Dangerous commands
cmd-cron-mentionREADME.md:187Mentions editing / listing crontab# Add to crontab -e
Files scanned: 12. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- error
description-longdescription is 1476 chars, limit 1024
Process rating: all ten parameters 58/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 7 mutating operations with no state check
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 100Steps. 30 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 991 tokens
- low 10 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 1476: 120–800 characters recommended
- +2Single-language instructions
- +4Structure: 16 headings
- +3Step-by-step instructions: 30 items
- +3Output format is stated explicitly
- +4Has examples (12 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 60.