Skill Creator
steveclarke
19 published skills · 404 GitHub stars across the catalog. View on GitHub ↗
handbook-writing
Creates clear, welcoming handbooks and documentation that help team members understand roles, responsibilities, and workflows. Transforms technical documentation into engaging guides. Use when user wants to create a handbook, improve documentation, write team guides, create process documentation, or make existing handbooks more readable and approachable.
bash-script-writing
Write clean, modular, production-ready bash scripts with proper error handling and maintainable structure. Use when creating new shell scripts, refactoring existing bash code, or when user asks for bash/shell scripting help with terms like "write a script", "bash script", "shell script", or "automate with bash".
find-bugs
Find bugs, security vulnerabilities, and code quality issues in local branch changes. Use when asked to review changes, find bugs, security review, or audit code on the current branch.
commit
Create well-structured commit messages following Conventional Commits format. Use when committing code changes, writing commit messages, or formatting git history.
code-simplifier
Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Focuses on recently modified code unless instructed otherwise.
bruno-endpoint-creation
Comprehensive guide for creating REST API endpoints in Bruno. Use when working with Bruno collections, creating .bru files, configuring API endpoints, setting up authentication, writing pre/post-request scripts, organizing Bruno collections, or testing REST APIs with Bruno.
code-review
Comprehensive code review process for conducting thorough, educational, and actionable code reviews. Use when reviewing pull requests, code changes, feature branches, conducting code quality assessments, or providing feedback on implementations.
domain-name-brainstormer
Generates creative domain name ideas for your project and checks availability across multiple TLDs (.com, .io, .dev, .ai, etc.). Saves hours of brainstorming and manual checking.
file-organizer
Intelligently organizes your files and folders across your computer by understanding context, finding duplicates, suggesting better structures, and automating cleanup tasks. Reduces cognitive load and keeps your digital workspace tidy without manual effort.
implement-a-plan
This skill should be used when the user asks to "implement this plan", "let's implement this plan", "I'm ready to implement this plan", "let's start working on this plan", "let's use this plan", "execute step 3.1", "resume working on this plan at section 4", "review this plan", "let's continue with the plan", or needs guidance on executing, resuming, or reviewing implementation plans with numbered sections and checkboxes.
implementation-plan
Creates implementation plan documents by determining plan structure, sequencing development phases, and generating actionable tasks. Use when user wants to create an implementation plan, needs to sequence development work, determine when and in what order to build features, or create detailed task breakdowns with code examples. Follows established feature development process with clear phase sequencing, integrated development (code + validation + data), and selective detail strategy (full code for novel aspects, references for established patterns).
invoice-organizer
Automatically organizes invoices and receipts for tax preparation by reading messy files, extracting key information, renaming them consistently, and sorting them into logical folders. Turns hours of manual bookkeeping into minutes of automated organization.
monthly-invoice-summary
Creates professional monthly invoice summaries for clients by analyzing Git commits and time sheet notes. Combines technical development work with business activities into clear, value-focused bullet points suitable for client invoicing. Use when creating monthly billing summaries, preparing client invoices, summarizing development work for billing periods, translating technical Git commits into client-friendly descriptions, or combining Git activity with time sheet notes for complete project summaries.
requirements-document
Creates requirements documents through structured 3-phase discovery process. Guides through requirements discovery, practical scoping, and generates consolidated requirements document with clear, practical language. Use when user wants to create a requirements document, needs to define what the system must do and quality constraints, or is documenting business capabilities, user workflows, and system requirements. Follows established feature development process with single consolidated document covering user stories, business data, rules, quality attributes, and success criteria.
technical-specification
Creates concise technical specification documents through 3-4 phase process. Guides through architectural decisions, system contracts, and technical design without getting bogged down in implementation details. Use when user wants to create a technical specification, needs to define how the system will be implemented technically, or is documenting architecture, data contracts, API specifications, and system components. Follows established feature development process with concise (5-10 page) specs focused on WHAT and WHY, not HOW to code. Optionally creates design brief for features with UI/UX complexity.
terminal-ui-design
Create distinctive, production-grade terminal user interfaces with high design quality. Use this skill when the user asks to build CLI tools, TUI applications, or terminal-based interfaces. Generates creative, polished code that avoids generic terminal aesthetics.
todoist-daily-review
Reviews today's Todoist tasks for tools/articles to investigate. Researches each item via web search, generates structured markdown summaries, appends to Obsidian daily notes, and marks tasks complete. Use when user asks to review Todoist items, do daily review, or process investigation tasks.
vision-document
Creates vision documents through structured 5-phase discovery process. Guides through problem discovery, solution exploration, user needs analysis, future & scope planning, and document generation. Use when user wants to create a vision document for a feature, needs to define strategic context and high-level goals, or is starting feature development and needs to establish the "why" and "what" before technical details. Follows established feature development process with lean, focused documents (100-150 lines max) that flow from general problems to specific scope.
youtube-transcript
Download YouTube video transcripts when user provides a YouTube URL or asks to download/get/fetch a transcript from YouTube. Also use when user wants to transcribe or get captions/subtitles from a YouTube video.