skills

Get personalized, evidence-based recommendations for improving your Claude Code/Nimbalyst workflow

Write blog posts with strong voice and SEO structure. Use when writing blog posts, articles, or thought leadership content.

Create structured technical and product documentation. Use when writing docs, guides, API references, or knowledge base articles.

Product launch announcements and release notes. Use when writing launch emails, release notes, changelog entries, or product announcements.

Battlecards, demo scripts, and GTM materials. Use when creating sales collateral, competitive battlecards, or go-to-market content.

HTML slide decks with consistent design system. Use when creating presentations, pitch decks, or slide-based content.

Comprehensive read-only code review of branch changes. Use when reviewing a branch before merging or when wanting a thorough code audit.

Guided bug report creation through conversation. Use when reporting a bug or helping someone document an issue.

Modularize large CLAUDE.md files with path-scoped rules. Use when CLAUDE.md is too large and needs modularization.

Analyze code quality, identify potential issues, and suggest improvements. Use when reviewing code structure, finding bugs, or evaluating maintainability.

Impact-focused git commit messages. Use when the user wants to commit changes with a well-crafted message.

Update dependencies with changelog review. Use when updating npm packages or libraries.

Execute plan docs with progress tracking. Use when implementing a structured plan file.

Clean up debug logging and dead code before commit. Use when preparing changes for commit.

Summarize recent git commits in standup format. Use when preparing for standups or summarizing recent work.

Generate comprehensive test coverage for existing code. Use when writing or expanding tests.

Identify edge cases and error states during design. Use when reviewing designs, writing specs, or planning QA.

Explain features by inspecting the codebase. Use when you need to understand how a feature works or explain it to stakeholders.

Analyze customer feedback for patterns and insights. Use when processing surveys, interviews, reviews, or support tickets.

Summarize GitHub activity across repos and PRs. Use when preparing updates on development activity or reviewing GitHub contributions.

Create structured Product Requirements Documents (PRDs) with prioritized requirements. Use when writing product specs, feature requirements, or project briefs.

Triage, deduplicate, and prioritize feature requests. Use when organizing a backlog of feature requests or customer asks.

Create executive status updates with metrics. Use when preparing team updates, executive summaries, or project status reports.

Draft strategy memos with rationale and alternatives. Use when communicating strategic decisions or driving alignment on major product decisions.

Track bugs, tasks, ideas, and decisions in markdown. Use when logging work items, tracking progress, or managing a personal task list.

Competitive analysis with SWOT and feature comparisons. Use when analyzing competitors, comparing products, or evaluating market positioning.

Simulate customer interviews for practice. Use when preparing for user interviews or testing interview scripts.

Parallel multi-agent research with citations. Use when conducting deep research, competitive analysis, or investigating complex topics.

Structure user research findings and insights. Use when documenting user research, interview synthesis, or usability testing results.