solo-skills: 26 AI Skills for a One-Person Operation
A practical look at solo-skills, its reusable SKILL.md workflows, scripts, failure notes, and safe adoption boundaries.
solo-skills is best understood as an operational library, not a magic autonomous company. Its author turned recurring work from a one-person community operation into reusable SKILL.md procedures that compatible agents can read and execute.
The repository exposes 26 of 49 automated tasks, covering content production, publishing, communication, community operations, bots, reminders, style analysis, and agent maintenance. The interesting engineering choice is the treatment of failure: broken Korean input, inaccurate style assumptions, and missing transcripts remain visible in the workflows.
Install the files, then inspect the contract
git clone https://github.com/bam-bam-2/solo-skills
cp -R solo-skills/skills/* ~/.claude/skills/Copying the directory is only the first step. Check which skill directory your agent reads, what each script requires, and whether external actions default to dry-run. Posting, messaging, deletion, and remote removal need an explicit approval boundary and a recoverable failure path.
Why the modular shape matters
There are separate workflows for demo videos, PDF books, UI annotation, Naver and Threads publishing, meeting minutes, KakaoTalk, mail, Discord bots, reminders, resale search, style work, and Notion operations. This is easier to test than a single broad agent prompt: each skill has a smaller input/output contract and a narrower blast radius.
Failure notes are the real documentation
The Threads workflow measured 492 historical replies instead of trusting a generic style table. The video workflow uses an iframe, real click events, and a deterministic clock so renders can be reproduced. The KakaoTalk workflow documents Unicode typing, SSH clipboard, and missing-rendered-chat limitations. These details turn automation from a demo into something an operator can debug.
Adopt one low-risk task first
Treat each SKILL.md as an auditable runbook. It should state prerequisites, steps, success checks, failure handling, and side effects. Start with one repetitive task, record rework and failure rates, and expand permissions only after the output is reliable. The official repository is https://github.com/bam-bam-2/solo-skills; dependencies and licenses should be checked from the current files.