Discover Business skills, compare source repositories and read the instructions for each workflow.
Plan-then-execute workflow combining structured planning with autonomous Ralph Loop execution. Triggers on: '/ralph-plan ', 'plan and execute', 'plan then execute', 'smart ralph'. Creates plan via interview and...
Start a Ralph Loop - an autonomous iteration pattern for completing complex tasks. Triggers on: '/ralph-loop ', 'ralph loop', 'start ralph'. Creates state in .claude/ralph/, injects ultrawork mode, and iterates...
Structured planning with draft management. Use this skill when the user wants to plan a feature, task, or project before implementation. Triggers on: '/plan ', 'let's plan', 'plan for', 'help me plan'. Creates...
Git worktree automation for isolated feature development. Triggers on: '/worktree create', '/worktree list', '/worktree remove'. Creates isolated working directories with automatic setup.
MUST be used for ANY git workflow that involves committing code. This includes explicit commit requests AND implicit ones like 'ship it', 'wrap it up', or finishing implementation work. Handles staging, message...
Create new blog posts with proper frontmatter, structure, and ScottInk voice. Use when writing blog posts or starting technical articles.
Audit local analytics for bot traffic, referrer spam, and data quality. Use when investigating discrepancies between Fathom and local stats.
Validate blog posts for quality, consistency, en-GB spelling, and ScottInk style. Use when reviewing posts before publication.
Prepare newsletters for publication by validating format, structure, frontmatter, and content. Use when reviewing drafts before sending.
Write in Scott's authentic voice - British, conversational, self-deprecating, code-first. Use when writing blog posts, technical content, or documentation.
Lint content for spelling errors, en-GB compliance, and writing quality. Use when checking markdown files before publication.
Use when building, auditing, or reviewing SvelteKit remote functions for validation, batching, and optimistic UI patterns
Search, filter, and retrieve Claude/Codex history indexed by the memex CLI. Use when the user wants to index history, run lexical/semantic/hybrid search, fetch full transcripts, or produce LLM-friendly JSON out...
Search, filter, and retrieve Claude/Codex history indexed by the automem CLI. Use when the user wants to index history, run lexical/semantic/hybrid search, fetch full transcripts, or produce LLM-friendly JSON o...
Search memex for user feedback patterns (frustration, corrections, praise, successful outcomes) to identify recurring mistakes and wins, then generate CLAUDE.md or AGENTS.md improvements.
Stage meaningful diffs and create commits with WHY-focused messages. Use when agent needs to commit code changes.
Use this skill when the user asks to save, remember, recall, or organize memories. Triggers on: 'remember this', 'save this', 'note this', 'what did we discuss about...', 'check your notes', 'clean up memories'...
Claude Codeセッションの標準的なMarkdownフォーマット規約。セッションログ、対話履歴、ツール実行結果を一貫した構造で記録する必要がある場合に使用。不正確な情報への注釈方法とnb標準のハッシュタグ形式も定義
Use Nia MCP server for external documentation, GitHub repos, package source code, and research. Invoke when needing to index/search remote codebases, fetch library docs, explore packages, or do web research.
Use when implementation complete and tests pass - closes bd epic, presents integration options (merge/PR/keep/discard), executes choice
Use when facing 3+ independent failures that can be investigated without shared state or dependencies - dispatches multiple Claude agents to investigate and fix independent problems concurrently
Use to expand bd tasks with detailed implementation steps - adds exact file paths, complete code, verification commands assuming zero context
Use when creating new skills, editing existing skills, or verifying skills work - applies TDD to documentation by testing with subagents before writing
Use when writing or changing tests, adding mocks - prevents testing mock behavior, production pollution with test-only methods, and mocking without understanding dependencies
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.