lmorchard-agent-skills
lmorchard-agent-skills contient 8 skills collectées depuis lmorchard, avec une couverture métier par dépôt et des pages de détail sur le site.
Skills dans ce dépôt
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 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.
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.
Use when Les asks to be pinged, alerted, or notified on his phone — e.g. "ping me when the build passes", "alert me if the tests break", "let me know when this finishes", "text me when you need input", or any request for an intentional push notification at a chosen urgency. Distinct from the automatic Stop/Notification hooks.