Data-Wise

This skill should be used when a command's --refine flag is set, or the user asks to "refine my prompt", "optimize this prompt", "make this request sharper" — rewrites a vague natural-language request into a specific, well-structured prompt using project context, shows before/after, and confirms before the caller proceeds. Replaces the deprecated /craft:refine command.

This skill should be used when the user asks to "release", "create a release", "ship it", "publish a new version", "bump version and release", "cut a release", or mentions releasing to GitHub/npm/PyPI. Orchestrates the full release pipeline from pre-flight checks through GitHub release creation.

ADHD-friendly session and task workflow for craft users — captures context at session end, restores it at session start, picks the next task, breaks through blockers, holds focus on one task, reviews a craft spec, or refines a vague craft prompt. Use when wrapping up or resuming a coding session, when deciding what to work on next (also "what's next", "pick a task for me", "give me something to do"), when stuck or in decision paralysis, when focusing on a single craft task, or when reviewing/refining a craft spec or prompt. The full intent-to-operation map is in the "When to Use" table below.

This skill should be used when the user asks to "init a repo", "set up git", "manage branches", "switch branch", "create a worktree", "list worktrees", "clean merged branches", "sync with remote", "git activity", "git recap", "protect main", "apply branch protection", "bypass protection", "undo a commit", "fix a git mistake", or mentions git lifecycle, worktrees, branch protection, GitHub-side baseline protection, safety rails, or learning git workflows. Covers craft's full git lifecycle — repo init, branch and worktree management, remote sync, status/recap, local and GitHub-side branch protection, and the learning/safety reference docs.

This skill should be used when the user asks "what's my friction", "session insights", "friction report", "what patterns am I hitting", "analyze my sessions", "generate insights report", "aggregate facets", or "show CLAUDE.md suggestions". Aggregates session facet history into a friction/goals report. Formerly bundled with the brainstorm skill (ideation); split out because the two operations share no input or output. Directory name kept as brainstorm-insights for path stability — tests and references/insights.md reference it.

This skill should be used when the user asks to "release multiple formulas", "batch Homebrew update", "coordinate formula releases", "formula dependencies", or needs to manage releases across multiple Homebrew formulas with dependency ordering.

This skill should be used when the user asks to "audit guard", "guard friction", "tune guard", "guard false positives", "fix guard blocking", or mentions branch guard configuration issues. Analyzes branch-guard.sh rules; proposes JSON branch-policy config changes for policy-level false positives, and flags detection-logic bugs (which the flat config schema cannot fix) as needing a code PR instead.

This skill should be used when the user asks to "generate an ORCHESTRATE file", "turn a spec into a plan", "scaffold a feature breakdown", "scaffold a sprint backlog", "plan a sprint" (when a committed backlog/artifact is wanted, not just strategy advice), "generate roadmap artifacts", "create an implementation plan from SPEC", or needs to produce concrete planning artifacts (ORCHESTRATE-*.md, feature breakdowns with task estimates, sprint backlogs, milestone roadmaps). Differs from `project-planner` (high-level strategy/advice) by producing committed, actionable artifacts tied to specs and worktrees.

This skill should be used when the user asks to "list attachments", "download attachment", "email attachment", "calendar invite", "meeting invite", "download the file", "what files were attached", "get the attachment", "save attachment", "open the attachment", or wants to work with files attached to emails. Lists, downloads, and extracts calendar events from ICS invites.

This skill should be used when the user asks to "compose email", "write email", "send email to", "new email", "send a message to", "email someone", "write to", "new message", "draft an email", "message someone", or wants to draft and send a new message. Composes emails with a two-phase safety gate that never auto-sends.

This skill should be used when the user asks for "email config", "email setup", "configure email", "himalaya setup", "setup email", "set up email", "change email account", "which email account", "add email account", "switch email account", or needs help installing and configuring himalaya. Interactive setup wizard that checks installation, configures accounts, and tests connectivity.

This skill should be used when the user asks for "email digest", "daily digest", "email summary", "email roundup", "summarize my inbox", "what did I miss", "summary of recent emails", or wants a quick summary of recent messages. Generates a markdown digest grouped by priority. For a full morning briefing with calendar events and action items, use /himalaya:morning instead.

This skill should be used when the user asks to "export email", "save email", "export to markdown", "copy to clipboard", "save this email", "export as markdown", "save for later", "clip this email", "archive this to notes", or wants to preserve an email as structured markdown with YAML frontmatter and optionally copy to clipboard. Chains export_to_markdown and copy_to_clipboard.

This skill should be used when the user asks to "forward email", "forward this", "share this email", "send this to someone else", "pass this along", "forward this to", "redirect this email", or wants to send a copy of an email to another person. Reads the original, drafts a forward with context, and sends with safety gate.

This skill should be used when the user asks for "email help", "himalaya help", "email commands", "what can you do with email", "email features", "how do I use email", "what email tools are available", "show email capabilities", or wants to discover available email capabilities. Help hub for browsing all tools, prompts, skills, and workflows.

This skill should be used when the user asks to "check email", "inbox", "read email", "my emails", "any new messages", "what's in my email", "show me my mail", "unread emails", "check messages", "what emails do I have", "show my inbox", or wants to see what's new in their inbox. Lists envelopes from the default inbox via himalaya CLI.

This skill should be used when the user asks to "create a demo", "build a code demonstration", "write a vignette", "generate tutorial code", "make live-coding examples", "demo this package", or wants runnable instructional code for teaching, presentations, vignettes, or documentation. Designs progressive code examples that build from simple to complex with explanations, expected outputs, and common variations.

This skill should be used when the user asks to "classify docs", "what documentation do I need", "analyze doc needs", "documentation audit", or needs to determine what documentation types are needed based on code changes. Analyzes git commits and feature scope to return structured classification data.

This skill should be used when the user asks to "validate Mermaid diagrams", "lint diagrams", "check diagram syntax", "mermaid health score", or needs to validate Mermaid diagrams in markdown files for syntax errors, configuration, and rendering quality. Uses mcp-mermaid for full validation and local regex for fast pre-checks.

This skill should be used when the user asks to "update nav", "sync mkdocs navigation", "add a doc page", "reorganize navigation", "fix orphan docs", or needs to keep mkdocs.yml in sync with the docs/ directory. Handles directory-driven nav updates, new-page scaffolding with auto-nav insertion, and ADHD-friendly nav reorganization (≤7 top-level sections, ≤3 nesting depth).

Generate and maintain OpenAPI 3.1 specifications from code, design-first specs, and validation patterns. Use when creating API documentation, generating SDKs, or ensuring API contract compliance.

This skill should be used when the user asks to "set up a docs site", "build the site", "preview docs locally", "deploy docs", "publish the site", "audit site content", "change site theme", "check site health", "show site status", or otherwise manages the lifecycle of a documentation site (MkDocs, Quarto, pkgdown). Covers init/create/theme through build/preview/audit through deploy/publish/update.

Design and document statistical algorithms with pseudocode and complexity analysis

Numerical algorithms and computational techniques for statistics

Design and implementation of comprehensive simulation studies

Structured methodology for constructing and verifying mathematical proofs in statistical research

Evidence-based framework for transforming technical statistical papers into pedagogically-sound lessons using cognitive learning principles (dual coding, worked examples, progressive complexity). Includes a Paper-Type Dial (Section 0) that calibrates section emphasis for theory/proof papers, applied/simulation papers, methods papers, and hybrid papers — automatically adding a proof-strategy walkthrough for theory-heavy work. Use when designing lectures, handouts, or course materials to introduce new statistical techniques, methods, or complex concepts at any level. Apply for STAT 579 materials, journal club discussions, research seminars, flipped classroom preparation, or when a [teach-paper] handoff block is provided.