modules/programs/agents/shared/skills/start-day/SKILL.md
Generate a daily kickoff note with GitHub context and recent vault activity
npx skillsauth add MichaelVessia/nixos-config start-dayInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Create today's daily note with GitHub work items and recent vault context.
Run these gh api queries (all repos):
# Assigned issues (with links)
gh api 'search/issues?q=assignee:@me+is:open+is:issue' --jq '.items[] | "[\(.repository_url | split("/") | .[-1])#\(.number)](\(.html_url)): \(.title)"'
# PRs requesting your review (with links)
gh api 'search/issues?q=review-requested:@me+is:open+is:pr' --jq '.items[] | "[\(.repository_url | split("/") | .[-1])#\(.number)](\(.html_url)): \(.title)"'
# Your open PRs (with links)
gh api 'search/issues?q=author:@me+is:open+is:pr' --jq '.items[] | "[\(.repository_url | split("/") | .[-1])#\(.number)](\(.html_url)): \(.title)"'
Use the Atlassian MCP to fetch Jira tickets assigned to the user:
atlassianUserInfo to get accountIdgetAccessibleAtlassianResources to get cloudIdsearchJiraIssuesUsingJql:
assignee = currentUser() AND status != Done ORDER BY priority DESC- [ ] [KEY-123](https://flocasts.atlassian.net/browse/KEY-123): titleFallback: If the Atlassian MCP fails, use the Jira REST API with curl:
curl -s -u "$(jira me):$JIRA_API_TOKEN" \
"https://flocasts.atlassian.net/rest/api/3/search/jql?jql=assignee%3DcurrentUser()%20AND%20status%21%3DDone%20ORDER%20BY%20priority%20DESC&fields=key,summary" \
| jq -r '.issues[] | "- [ ] [\(.key)](https://flocasts.atlassian.net/browse/\(.key)): \(.fields.summary)"'
Use the Google Calendar MCP to fetch today's meetings:
gcal_list_events with:
timeMin: today at 00:00 (RFC3339 without timezone, e.g., 2026-01-09T00:00:00)timeMax: today at 23:59 (RFC3339 without timezone, e.g., 2026-01-09T23:59:59)maxResults: 20- [ ] HH:MM - Event summaryFind recent notes in ~/obsidian/Notes/:
Daily notes (YYYY-MM-DD.md): last 3 days Other notes: last 3 days if Monday, otherwise yesterday only
Read the found notes and extract:
- [ ]) from TODOs sections- [x] containing GitHub links like
repo#123)Create or append to ~/obsidian/Notes/YYYY-MM-DD.md.
## Start Day
#start-day
### Meetings
- [ ] HH:MM - Meeting from Google Calendar
### TODOs
- [ ] task from previous notes
- [ ] another incomplete task
### Jira Tickets
- [ ] [KEY-123](https://flocasts.atlassian.net/browse/KEY-123): ticket title
(Exclude items checked off in previous notes. "None" if empty after
filtering.)
### PRs to Review
- [ ] [repo#456](https://github.com/org/repo/pull/456): pr title (Exclude items
checked off in previous notes. "None" if empty after filtering.)
### My Open PRs
- [repo#789](https://github.com/org/repo/pull/789): pr title (Exclude items
checked off in previous notes. "None" if empty after filtering.)
- [x]) in previous notes (match
by repo#number)# Journal YYYY-MM-DD header if it doesn't existdevelopment
Restate the last message in plain human language, with no jargon.
testing
Fan out a batch of work items into one PR each via isolated worktree agents, review every PR before it opens, then babysit all PRs through green CI and review feedback. Use when the user wants to fan out PRs, dispatch parallel PR agents over a list of items, or run a batch of independent changes as separate PRs.
development
Dispatch user-visible coding or research agents through Herdr with Codex-Desktop-like thread ergonomics. Use when the user asks to use Herdr to spawn, dispatch, fan out, inspect, follow up with, or monitor agent workspaces/threads.
development
Generate self-contained HTML visualizations with Plannotator theming. Use for implementation plans, PR explainers, architecture diagrams, data tables, slide decks, and any visual explanation of technical concepts. Plans and PR explainers follow Plannotator's prescriptive approach; all other visual content delegates to nicobailon/visual-explainer.