The System Skill Pattern
shruggingface.com
The System Skill Pattern
1–3 of 3 posts
Re: The System Skill Pattern
#2Author here-- hah, I'm surprised someone posted this already-- I just came to share it as a Show HN post and get the conversation started:
I’ve been playing with Claude Skills and stumbled on a simple pattern for tiny, durable personal data systems:
* CLI: a small, self-contained executable
* SKILL.md: the operator's manual (what to run, how to parse output, how to think about the system)
* SQLite: a local DB for persistent state
It’s nothing mind-blowing, but the ergonomics of this combo feel great.
If you define a process/flow, Claude can "turn the crank" by running the CLI, accumulating context, and animating the system to life over time.
They’re also easy to share: you can distribute System Skills via Claude Code’s `/plugin marketplace add `.
More details in the blog post and the toy Pomodoro System Skill reference implementation here:
Blog: https://www.shruggingface.com/blog/the-system-skill-pattern Repo: https://github.com/jakedahn/pomodoro
--
Curious whether any of this resonates. Also excited to hear any interesting System Skill ideas worth exploring!
Re: The System Skill Pattern
#3Author here-- hah, I'm surprised someone posted this already-- I just came to share it as a Show HN post and get the conversation started: I’ve been playing with Claude Skills and stumbled on a simple pattern for tiny, durable personal data systems: * CLI: a small, self-contained executable * SKILL.md: the operator's manual (what to run, how to parse output, how to think about the system) * SQLite: a local DB for per…
I think Steve Yegge's BD might be another "stateful" skill like this - have you compared the bead approach with yours