Building 9 Claude Skills for Solo Studio: Stacking Instructions for Real Work

A developer on r/ClaudeAI spent a day building nine Claude skills for their solo studio, covering three SaaS products and client projects. The skills are folders with a SKILL.md file containing instructions for handling specific tasks. They auto-trigger when you describe the task naturally—you don’t need to call them by name.

The Nine Skills Built

• Video production – FFmpeg scripts, voiceover prompts, social clip extraction
• AI visual content – branded graphics, mockups, marketing assets
• API documentation – OAuth debugging, integration tracking
• Social media automation – cross-platform posting, voice consistency
• SEO content strategy – keyword research, content calendars
• Support ticketing – email templates in the developer’s voice
• Product analytics dashboards – real metrics, real queries
• Database performance optimization – query rewriting, indexing
• Financial modeling – MRR forecasting, scenario planning

Key Patterns That Worked

Skills stack automatically. For example, asking “create a demo video for my HR SaaS and show me the analytics impact” triggered both the video and analytics skills. Output: an FFmpeg recording script, editing manifest, voiceover draft, and a dashboard mockup with metrics to prove the video drove signups.

The most important lesson: write skills as instructions to an experienced colleague, not as documentation. Include specifics:

• Audio device names
• Brand colors as hex codes
• Customer names and what you charge them
• Words you refuse to use
• How you close emails

Three skills that immediately pulled weight:

• Support template skill caught itself using a banned word, flagged it inline, and offered the corrected version
• Financial model knew actual MRR, runway, and product roadmap — forecasts were usable, not generic
• Video skill defaulted to recommending recording without audio so ElevenLabs voiceover could be layered in post (the developer’s actual workflow)