AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Morning Update

skill-pbeens-obsidian-agents-md-morning-update · by pbeens

>

No reviews yet
0 installs
3 views
0.0% view→install

Install

$ agentstack add skill-pbeens-obsidian-agents-md-morning-update

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-pbeens-obsidian-agents-md-morning-update)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
3mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Morning Update? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Morning Update

Use this skill to build a daily YYYY-MM-DD Morning Update note in Daily Notes/.

Purpose

Create one concise note that surfaces:

  • critical Gmail from the last 24 hours
  • all calendar events for the target day
  • #today items from notes dated in the last three calendar days

Workflow

  1. Determine the target date in the user's local timezone.
  2. Create or update Daily Notes/YYYY-MM-DD Morning Update.md.
  3. Gather Gmail items from the last 24 hours.
  4. Gather calendar events for the target date.
  5. Scan Obsidian notes from the target date and previous two days for #today.
  6. Write the note with clear sections and preserve source wording where relevant.

Gmail

  • Treat "critical" conservatively.
  • Prioritize unread, starred, important, or directly actionable mail from the last 24 hours.
  • Include sender, subject, received time, and a brief why-it-matters note.
  • Format each Gmail item as a checklist item.
  • include the Gmail message or thread URL for each critical item when available
  • if a direct URL is unavailable, include the message/thread ID and subject as a fallback
  • If an item is ambiguous, include it under a review-oriented sublist instead of guessing.
  • Do not invent urgency.

Calendar

  • List every event for the target day as a checklist item.
  • Include start/end time, title, location, attendees, and meeting link when available.
  • Keep all-day events visible.
  • If the calendar is empty, say so explicitly.

Obsidian Scan

  • Search markdown notes in the vault for #today items in notes dated within the target day and the previous two calendar days.
  • Use the note's date-only filename when present, otherwise use created frontmatter if available.
  • Copy #today task text exactly as written.
  • Preserve inline hashtags verbatim.
  • Include the source note path next to each copied item.

Note Format

Use this structure:

  1. YAML frontmatter with created: YYYY-MM-DD, source: "[[skills/morning-update/SKILL.md]]", and tags: [Morning-Update]
  2. Overview
  3. Critical Gmail
  4. Calendar Today
  5. #today Items
  6. Follow-Ups
  7. Do not include an H1 title if the filename already serves as the note title.

In ## Critical Gmail, format each email as - [ ] rather than a bullet. In ## Calendar Today, format each event as - [ ] rather than a bullet.

Safety Rules

  • Keep the note concise and source-faithful.
  • Do not paraphrase task text.
  • Do not rewrite source notes.
  • If a source cannot be dated confidently, skip it rather than guessing.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.