← Back to Skills Marketplace
kevdogg102396-afk

Morning Coffee Briefing

by kevdogg102396-afk · GitHub ↗ · v1.0.0
cross-platform ⚠ suspicious
423
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install morning-coffee-briefing
Description
Daily morning briefing skill. Reads your TASKS.md and memory files, synthesizes a prioritized day plan, and sends it to you via Telegram so you start the day...
Usage Guidance
This skill does what it says — read your tasks and send a Telegram briefing — but there are a few red flags you should address before installing: 1) Confirm and add the required environment variables to the registry metadata (TELEGRAM_BOT_TOKEN, TELEGRAM_CHAT_ID, TASKS_FILE_PATH) so reviewers and your agent know what secrets are required. 2) Clarify {MEMORY_DIR} and limit exactly which memory files the skill is allowed to read (avoid open-ended 'any memory files' or globs that could expose sensitive data). 3) Remove or explicitly define the 'pipeline status' checks (what services, what credentials, and what endpoints) — otherwise the agent might attempt network calls or require other tokens. 4) Consider removing Bash/Glob/Grep from allowed tools or restrict file read operations to an explicit whitelist to prevent accidental file enumeration or arbitrary shell execution. 5) Test with a throwaway Telegram bot and a sandboxed TASKS.md/memory directory containing non-sensitive data to confirm behavior. If you cannot get explicit metadata for the memory paths and pipeline checks, treat this skill as higher risk and do not grant it access to real personal or production data.
Capability Analysis
Type: OpenClaw Skill Name: morning-coffee-briefing Version: 1.0.0 The skill is classified as suspicious due to the broad permissions granted by `allowed-tools: Bash` in `SKILL.md`. While the current use of Bash for a `curl` command to send a Telegram message aligns with the stated purpose, the ability to execute arbitrary shell commands creates a significant prompt injection vulnerability. An attacker could potentially exploit this to trick the agent into executing unintended commands or exfiltrating sensitive data by including it in the Telegram message, even though the skill itself does not explicitly instruct such malicious behavior.
Capability Assessment
Purpose & Capability
The name/description match the runtime instructions (read TASKS.md and memory files, send a Telegram message). However the registry metadata provided with the skill says there are no required env vars or config paths, while the SKILL.md explicitly requires TELEGRAM_BOT_TOKEN, TELEGRAM_CHAT_ID, and TASKS_FILE_PATH — a clear metadata/instruction mismatch. The skill also references {MEMORY_DIR} (not declared) and asks to check 'pipeline status' (no credentials or endpoints declared), which is beyond the minimal needs described.
Instruction Scope
SKILL.md instructs the agent to read TASKS.md plus 'any memory files' (MEMORY.md, projects.md, recent notes) and to 'check pipelines' — these are vague and could cause the agent to read many personal files or attempt network calls requiring other credentials. Allowed tools include Read, Bash, Glob, Grep, and WebSearch; Bash + Glob + Grep increase the risk that the agent could read or enumerate more files than intended or run shell commands. The Telegram send step is explicit and expected; the rest (memory access and pipeline checks) needs tighter scoping.
Install Mechanism
No install spec and no code files — the skill is instruction-only. That minimizes disk-written code and installer risk.
Credentials
The SKILL.md requires TELEGRAM_BOT_TOKEN, TELEGRAM_CHAT_ID, and TASKS_FILE_PATH — these are proportionate for sending messages and locating the tasks file. However the skill also references {MEMORY_DIR} (undeclared) and asks to check pipeline status without declaring any supporting credentials or endpoints. Registry metadata did not list the declared env vars, which is an inconsistency that could hide required secrets from reviewers.
Persistence & Privilege
always is false and the skill is user-invocable; it does recommend scheduling with cron but does not request system-wide persistence or modify other skills' configs. Autonomous invocation is allowed (platform default) but not combined here with other severe red flags.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install morning-coffee-briefing
  3. After installation, invoke the skill by name or use /morning-coffee-briefing
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
- Initial release of Morning Coffee Briefing skill. - Reads your TASKS.md and memory files to synthesize a prioritized daily plan. - Highlights top 3 priorities, a quick win, blockers, and pipeline status. - Sends your customized morning briefing via Telegram for a focused start to the day. - Environment variables required: TELEGRAM_BOT_TOKEN, TELEGRAM_CHAT_ID, TASKS_FILE_PATH.
Metadata
Slug morning-coffee-briefing
Version 1.0.0
License
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is Morning Coffee Briefing?

Daily morning briefing skill. Reads your TASKS.md and memory files, synthesizes a prioritized day plan, and sends it to you via Telegram so you start the day... It is an AI Agent Skill for Claude Code / OpenClaw, with 423 downloads so far.

How do I install Morning Coffee Briefing?

Run "/install morning-coffee-briefing" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Morning Coffee Briefing free?

Yes, Morning Coffee Briefing is completely free (open-source). You can download, install and use it at no cost.

Which platforms does Morning Coffee Briefing support?

Morning Coffee Briefing is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Morning Coffee Briefing?

It is built and maintained by kevdogg102396-afk (@kevdogg102396-afk); the current version is v1.0.0.

💬 Comments