gws-obsidian-prep

gws-obsidian-prep is a skill for Claude Code from michaeljauk/brain-starter. It costs 0 tokens per session (902 once invoked), scanned A, original, MIT.

A recipe that reads today's or tomorrow's events from Google Calendar using the gws command-line tool and creates meeting-preparation notes in an Obsidian vault. Obsidian is a note-taking application, and a command-line tool is operated by typing commands in a terminal.

In plain words
What is it for?
Use it to prepare notes for upcoming meetings, inspect a day's or week's schedule, and skip events such as out-of-office blocks, short auto-blocks, and solo calendar entries.
Why use it?
It gathers calendar details and turns relevant meetings into preparation notes, reducing manual copying and filtering. It requires the gws and Obsidian tools to be installed and authenticated.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

Good fit Use it to prepare notes for upcoming meetings, inspect a day's or week's schedule, and skip events such as out-of-office blocks, short auto-blocks, and solo calendar entries.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/michaeljauk/brain-starter/gws-obsidian-prep
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add michaeljauk/brain-starter --skill gws-obsidian-prep
Clone the repo
git clone --depth 1 https://github.com/michaeljauk/brain-starter

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for gws-obsidian-prep

README.md
[![agentmods](https://agentmods.dev/badge/skills/michaeljauk/brain-starter/gws-obsidian-prep/github.svg)](https://agentmods.dev/skills/michaeljauk/brain-starter/gws-obsidian-prep)
Your own site
<a href="https://agentmods.dev/skills/michaeljauk/brain-starter/gws-obsidian-prep"><img src="https://agentmods.dev/badge/skills/michaeljauk/brain-starter/gws-obsidian-prep/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for gws-obsidian-prep

Your own site · 80×15
<a href="https://agentmods.dev/skills/michaeljauk/brain-starter/gws-obsidian-prep"><img src="https://agentmods.dev/badge/skills/michaeljauk/brain-starter/gws-obsidian-prep.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 902 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00902
Opus 5 $0.00000 $0.00451
Sonnet 5 $0.00000 $0.00180
Haiku 4.5 $0.00000 $0.00090

Measured 10d ago against content hash b20ba0c60341, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

gws-obsidian-prep scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/gws-obsidian-prep/SKILL.md · 147 lines

How it starts

The opening of the file, as written. The whole thing — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.

gws-obsidian-prep

Cross-skill recipe: fetch today's (or tomorrow's) Google Calendar events via gws CLI and create meeting prep notes in the Obsidian vault.

Prerequisites

  • gws CLI installed and authenticated (gws auth login -s calendar)
  • Obsidian CLI available (which obsidian — requires Obsidian running)
  • Vault path: ~/brain/

Trigger phrases

  • "What meetings do I have today / tomorrow?"
  • "Create prep notes for today's meetings"
  • "Show me this week's schedule"
  • "Prep note for [meeting name]"

Step-by-step workflow

1. Fetch events

# Today
gws calendar +agenda --today --format json

# Tomorrow
gws calendar +agenda --tomorrow --format json

# This week
gws calendar +agenda --week --format json

Parse the JSON array. Each event has: summary, start.dateTime, end.dateTime, attendees[], description, htmlLink.

2. Filter relevant events

Skip events where:

  • summary matches /OOO|Out of Office|Blocked|Focus Time/i
  • Duration < 10 minutes (likely auto-blocks)
  • No attendees other than self (solo blocks)

3. Check for existing prep note

For each event, check if a prep note already exists:

obsidian search query="YYYY-MM-DD Event-Name prep"

If a note is found, skip creation and report it.

4. Create prep note

If no existing note found, create one:

obsidian create \
  name="meetings/YYYY-MM-DD_Event-Name-prep" \
  content="..." \
  silent

Filename convention: YYYY-MM-DD_Event-Name-prep.md

  • Date = event date (not today if prepping ahead)
  • Event name: lowercase, hyphens, truncate at 40 chars
  • Always suffix -prep
  • Placed in meetings/ folder

5. Note template

---
title: "Prep: {event summary}"
date: YYYY-MM-DD
type: meeting-prep
tags: [meeting-prep]
---

# Prep: {event summary}

**Date:** {date} {start time} – {end time}
**Calendar:** {calendarId or "primary"}

## Attendees

{- Name (email) for each attendee, self last}

## Agenda

{event description if present, else "- [ ] (add agenda items)"}

## My talking points

- [ ]

## Open questions

- [ ]

## Related

{wikilinks to matching project notes — see Project matching below}

Read the full file on GitHub · 147 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 10d ago First seen · 147 lines · 0 tokens per session scan A b20ba0c60341

Subscribe to this mod's changes

gws-obsidian-prep is a skill published in the GitHub repository michaeljauk/brain-starter (5 stars, last pushed 13d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 902 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

priority-dashboard

Use this to rebuild, inspect, or temporarily steer {{username}}'s current PersonalOS priority dashboard from canonical Actions, Attention Triggers, and owner context. Do NOT use it to create, complete, or independently manage tasks; use task-manager for Action and Trigger lifecycle changes.

vincentmumme/personalos-boilerplate · 60 tokens

task-manager

Use this when {{username}} or an agent wants to add, review, prioritize, complete, defer, park, or inspect todos, open loops, confirmed actions, waiting states, or attention triggers. Maintains atomic records under operations/actions/ and operations/attention-triggers/ as the only local action truth. Do NOT use for…

vincentmumme/personalos-boilerplate · 90 tokens

resume

A workflow for reopening a paused task by scanning its saved project notes, blockers, logs, and delegated work. It presents the parked tasks so the user can choose which one to continue.

dzhokhov/markdown-agent-vault-ru · 204 tokens

vault-onboarding-guide

An interactive guide for learning a file-based knowledge store with an agent. It teaches how to organize incoming material, projects, plans, tasks, logs, parked work, and resumed work.

dzhokhov/markdown-agent-vault-ru · 187 tokens

obsidian

Obsidian vault management — create notes, backlinks, tags, and Dataview queries via file operations.

furkangonel/cowrangler · 24 tokens

pkm-session-end

Use when wrapping up a work session — creates devlog entry, captures undocumented decisions/research/debugging, audits link health of session work, and updates project index. Primarily used via the pkm-capture agent.

AdrianV101/obsidian-pkm-plugin · 49 tokens