Daily Report

Generate daily, weekly, and alert reports tracking leads, outreach, cost, priorities, and issues, saving structured summaries for progress monitoring.

Security Scan

The skill's instructions reference sending Telegram alerts, using a local model (ollama), and saving memory files, but the skill declares no required binaries, env vars, or config — those omissions are inconsistent and warrant caution.

Purpose & Capability

The SKILL.md describes daily/morning/eod/weekly reports, memory files, and immediate alerts via Telegram, and recommends using a local model (ollama). However the skill declares no description, no required binaries (e.g., ollama), and no required environment variables (e.g., TELEGRAM_TOKEN) even though the instructions imply external integrations and a local model are needed. Notion and budget/API references are mentioned but no integration credentials or APIs are declared.

Instruction Scope

Runtime instructions instruct saving reports to memory/YYYY-MM-DD.md and to "Trigger immediate Telegram alert" for several events. Those are actionable items that involve writing to disk and sending data externally, but the instructions do not specify how to authenticate or which endpoints to use. This is scope creep relative to a simple templating/reporting skill because it implies network communication and persistent storage without declaring required access.

Install Mechanism

No install spec and no code files are present, so nothing will be downloaded or installed by the skill itself. That lowers install-time risk, but it also means required runtime components (like ollama) must already exist on the host — the skill does not declare those dependencies.

Credentials

The skill requests no environment variables or credentials, yet its instructions clearly require access to external services (Telegram alerts, possibly Notion or other APIs) and to the filesystem for memory storage. This mismatch (no declared TELEGRAM_TOKEN, NOITON creds, or ollama binary) is disproportionate and ambiguous: if you supply credentials later, the skill could use them for exfiltration without a clear, declared purpose.

Persistence & Privilege

always:false and no install steps mean the skill does not request elevated or permanent presence. It will run only when invoked. Note: default platform behavior allows autonomous invocation; here that default is not combined with other high-risk privileges.

What to consider before installing

This skill is instruction-only and doesn't install code, but its runtime instructions expect things that aren't declared: a local model (ollama), the ability to write memory/*.md files, and the ability to send Telegram alerts (which requires a bot token). Before installing or enabling this skill: 1) Do not provide any external API tokens (Telegram, Notion, etc.) unless you trust the skill and can control where alerts go. 2) If you intend to use Telegram alerts, require the skill author to declare required env vars (e.g., TELEGRAM_BOT_TOKEN, TELEGRAM_CHAT_ID) and explain exactly what messages are sent. 3) Ensure ollama (or the intended model runtime) is intentionally installed and available if you want local model use; otherwise the skill's "local (ollama)" recommendation is meaningless. 4) Consider running the skill in an isolated/limited environment if it will be allowed to write files or send network requests. 5) If you cannot edit the SKILL.md or confirm required dependencies and credentials, treat this skill with caution or avoid installing it. These mismatches are likely sloppy configuration, but they could also result in unintended data transmission if you later supply credentials.

SKILL.md - Daily Report

Purpose

Track progress, report metrics, manage memory.

Model to Use

local (ollama) - simple aggregation, FREE

Morning Report (Send at 9:30 AM Spain)

🤖 SKYNET MORNING BRIEFING - {{date}}

📊 PIPELINE
├─ Total leads: X
├─ Ready for outreach: X
├─ In sequence: X
├─ Awaiting reply: X

📬 OVERNIGHT
├─ Leads found: X
├─ Emails drafted: X
├─ Cost: $X.XX

🎯 TODAY'S PRIORITIES
1. [Based on pipeline status]
2. [Based on day of week]
3. [Based on targets]

💰 BUDGET
├─ Spent today: $X.XX
├─ Daily remaining: $X.XX
├─ Monthly remaining: $X.XX

End of Day Report (Send at 9 PM Spain)

🤖 SKYNET EOD - {{date}}

📈 TODAY'S NUMBERS
├─ Leads sourced: X / 40 target
├─ DMs drafted: X / 25 target
├─ Emails drafted: X / 30 target
├─ Notion updated: ✓

💰 COST REPORT
├─ Today: $X.XX
├─ This week: $X.XX
├─ Budget remaining: $X.XX

🔥 HOT LEADS
[List any Priority A leads found]

⚠️ ISSUES
[List any blockers or errors]

📋 TOMORROW
[Next day priorities]

💾 Saved to memory/{{date}}.md

Weekly Report (Sunday 8 PM)

🤖 SKYNET WEEKLY - Week of {{date}}

📊 TOTALS
├─ Leads sourced: X
├─ Outreach sent: X (DMs + Emails)
├─ Replies: X
├─ Qualified: X
├─ Closes: X

💰 COSTS
├─ This week: $X.XX
├─ Avg per lead: $X.XX
├─ Avg per qualified: $X.XX

📈 CONVERSION
├─ Source → Qualified: X%
├─ Outreach → Reply: X%
├─ Reply → Meeting: X%

🎯 VS TARGETS
├─ Revenue: $X / $5,000 goal
├─ Days remaining: X
├─ Needed per day: $X

Memory File Format

Save to memory/YYYY-MM-DD.md:

# {{date}} - Daily Log

## Metrics
- Leads sourced: X
- DMs drafted: X
- Emails drafted: X
- Cost: $X.XX

## Leads Found (Summary)
- Priority A: X
- Priority B: X
- Skipped: X

## Issues
[Any problems encountered]

## Notes
[Context for future sessions]

## Tomorrow
- [ ] Task 1
- [ ] Task 2

Alerts (Send Immediately)

Trigger immediate Telegram alert for:

• Any reply detected
• Budget 75% depleted
• API error / rate limit
• Overnight run complete
• Task blocked / needs input