菜单
Use when Les asks to log, capture, or journal what was worked on this session, jot a quick note or TIL down for later, or flag something as a blog candidate — anything destined for his daily Obsidian journal.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Compose daily blog posts in a multi-post single-file format from multiple data sources including Mastodon and Linkding. Use this skill when the user requests to create, update, or revise daily blog posts throughout the day.
Build Go-based command-line tools following established patterns with Cobra CLI framework, Viper configuration, SQLite database, and automated GitHub Actions workflows for releases. Use when creating new Go CLI projects or adding features to existing ones that follow the Cobra/Viper/SQLite stack.
Use when Les asks what he was up to yesterday, wants a standup report, or needs to reconstruct recent work from his Claude Code sessions — surveys transcripts in ~/.claude/projects and reports what actually shipped.
Compose weeknotes blog posts in Jekyll-style Markdown from six sources of personal signal (Mastodon, Linkding, GitHub, Spotify, YouTube, Pocket Casts) via the me-to-markdown orchestrator. Use this skill when the user requests to create, draft, or generate weeknotes content for a blog post.
Use when working through a multi-phase feature, bugfix, or GitHub issue that warrants tracked spec/plan/notes artifacts. Triggers: /dev-session command, /dev-session phase names (start/brainstorm/plan/execute/pr/retro/express), starting a new feature branch, picking up a GitHub issue.
Use when a brainstorming or design question would be clearer shown than told — mockups, wireframes, layout comparisons, architecture diagrams, side-by-side visual options — and Les has Television running. A display-only alternative to the superpowers brainstorming browser server: renders visuals as Television artifacts instead of spinning up a separate web server and tab.
| name | journal-note |
| description | Use when Les asks to log, capture, or journal what was worked on this session, jot a quick note or TIL down for later, or flag something as a blog candidate — anything destined for his daily Obsidian journal. |
Appends a note to Les's daily Obsidian journal in his house style — either a full
## entry under # notes (session writeups, blog seeds) or a one-line bullet under
# TIL (quick learnings). Captured notes are raw material the daily-blog-post-composer
and weeknotes-blog-post-composer skills compose from later, so favor reusable detail
over polish.
~/Documents/Obsidian/main/journals/<YYYY>/<YYYY-MM-DD>.md
Derive the path from the date: date "+%Y/%Y-%m-%d". The file usually already exists
(Obsidian daily template) with headings: # daily / today / tonight / tomorrow / this week / [[someday]] / followup / TIL / notes. Always Read it first, then insert
into the correct existing section — never reorder or rewrite other content (standup,
therapy, tasks stay untouched). If the file is missing, create it with at least # TIL
and # notes headings.
1. Session note → ## subsection appended to the end of # notes. For "log what we
did", writeups, anything blog-worthy.
## <lowercase topic>
- problem / context in one line
- what was built + the stack, terse
- the interesting bit — the gotcha, war story, or "aha" (this is the blog hook)
- blog angles: a few bullets to pull from later
2. Quick learning → single bullet under # TIL. No subsection, one line.
- tailscale node IP forwarded :8065 but refused :2586 → the service was on the wrong host
When unsure which: a paragraph's worth of story → # notes; a single fact or lesson →
# TIL. A future to-do that came up → bullet under # followup.
## headings; terse bullets; first-person lowercase prose ("i ran…")[[wikilinks]] for projects, tools, people, entities*(blog candidate)* italic tag under the heading when relevant## under # notes; a single learning is a bullet under # TIL. Don't drop a paragraph into TIL.