Data-Wise

@data-wise source repo

57 skills
0 followers
11 hours ago last updated

▌
Project Detector · data-wise bundle
This skill should be used when the user asks to "detect project type", "what kind of project is this", "generate CI workflow", "set up CI", or needs to identify build tools, test frameworks, and CI requirements. Smart detection of project types, build tools, and CI requirements for automated workflow generation.

0
installs
▌
Sync Features · data-wise
This skill should be used when the user asks to "sync features", "check for new Claude features", "update craft for latest Claude", "what's new in Claude Code", or wants to ensure craft is up-to-date with Claude Code/Desktop capabilities. Chains command-audit and unified release-watch into a prioritized action plan.

0
installs
▌
Hooks · data-wise
Common PostToolUse/PreToolUse hook templates for quality gates. Provides ready-to-install JSON blocks for MkDocs strict mode, linting, and other automated checks, with setup instructions for each.

0
installs
▌
Mode Controller · data-wise
This skill should be used when the user asks to "switch mode", "use debug mode", "optimize mode", "release mode", or mentions execution modes for craft commands. Manages craft plugin execution modes (default, debug, optimize, release) for different use cases.

0
installs
▌
Git Workflow · data-wise bundle
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.

0
installs
▌
Release · data-wise bundle
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.

0
installs
▌
Project Planner · data-wise
This skill should be used when the user asks to "plan a project", "estimate effort", or needs help with task breakdown and project management strategy — NOT for producing a committed planning artifact (feature breakdown, sprint backlog, roadmap file); see `plan-orchestrator` for that. Provides expert guidance on feature planning, estimation, and delivery management.

0
installs
▌
Guard Audit · data-wise
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.

0
installs
▌
System Architect · data-wise
This skill should be used when the user asks to "design a system", "architect a solution", "review architecture", "plan a refactoring", "evaluate technical trade-offs", or discusses software architecture patterns. Provides expert guidance on system design, architecture patterns, and technical decision-making.

0
installs
▌
Claude Md Lifecycle · data-wise bundle
This skill should be used when the user asks to "create CLAUDE.md", "scaffold CLAUDE.md", "sync CLAUDE.md", "update CLAUDE.md", "audit CLAUDE.md", "fix CLAUDE.md", "optimize CLAUDE.md", "edit CLAUDE.md sections", or otherwise wants to manage the CLAUDE.md lifecycle (init, sync, edit). Covers project-local and global (`~/.claude/CLAUDE.md`) files. For applying suggestions from the /insights report specifically, use the `insights-apply` skill instead.

0
installs
▌
Insights Apply · data-wise
This skill should be used when the user asks to "apply insights", "insights to rules", "update rules from insights", "apply suggestions", or mentions updating CLAUDE.md from insights data. Extracts suggestions from the /insights report and applies them to the global CLAUDE.md via the sync pipeline.

0
installs
▌
Grill · data-wise
This skill should be used when the user asks to "grill", "interrogate", "stress-test a spec/plan", "adversarially review a proposal", or invokes /craft:grill. Convergent counterpart to brainstorm — interrogates a spec/plan/topic one question at a time to surface gaps, contradictions, and unresolved dependencies before implementation, then captures a durable GRILL-*.md decision ledger that feeds /craft:plan → /do. For GENERATING options (divergent ideation), use the brainstorm skill instead.

0
installs
▌
Preflight Check · data-wise bundle
This skill should be used when the user asks to "pre-flight check", "validate before commit", "validate before PR", "validate before deploy", "is this ready to ship", "check readiness", "run pre-flight", "validate project state", or wants context-aware validation across commit/PR/release/deploy boundaries. Orchestrates universal validators (lint, tests, types, version sync, stale refs, docs, hook conflicts) and supports generating new custom validators.

0
installs
▌
Audit Router · data-wise bundle
This skill should be used when the user asks to "audit commands", "check command frontmatter", "audit skills", "check skill standards", "validate command/skill health", or invokes `/craft:code:command-audit` or `/craft:code:skill-standards`. Shared vocabulary + reference bodies for craft's two schema-audit commands — both validate craft's own frontmatter (commands/skills/agents vs `_schema.json`, or `skills/**/SKILL.md` vs Anthropic's authoring standards) and share the same `--format`/`--fix` semantics. Not for dependency or docs-site checks — see `/craft:code:deps-audit`, `/craft:code:deps-check`, `/craft:code:docs-check` instead, which are unrelated generic cross-project tools despite living in the same `commands/code/` directory.

0
installs
▌
Plugin Audit · data-wise
This skill should be used when the user asks to "audit my plugins", "check for plugin duplicates", "plugin collision check", "find duplicate skills across plugins", "which plugins overlap", or wants to know if an installed Claude Code plugin duplicates or shadows another plugin's commands/skills. Diffs enabled plugins' actual command/skill surface against each other and flags cross-namespace name collisions — e.g. a bare `workflow:brainstorm` skill in one plugin vs. `craft:brainstorm` in another. Read-only — reports findings, never disables or uninstalls a plugin itself. Do not confuse with guard-audit (branch-guard.sh rule tuning) or command-skill-token-efficiency (command-vs-skill placement within a single plugin) — this skill compares surfaces ACROSS installed plugins.

0
installs
▌
Brainstorm · data-wise
This skill should be used when the user asks to "brainstorm", "explore ideas", "design a feature", "draft a spec", "capture a spec", or mentions ideation, requirements gathering, spec capture, or brainstorming depth/focus modes. Generates BRAINSTORM/SPEC documents from project + conversation context. Replaces the deprecated /craft:brainstorm command. For session-facet friction or pattern analysis across past sessions, use the brainstorm-insights skill instead.

0
installs
▌
Devops Helper · data-wise
This skill should be used when the user asks to "set up deployment", "configure CI/CD", "create a Dockerfile", "choose a hosting platform", or discusses deployment and infrastructure decisions. Provides pragmatic DevOps guidance for indie developers.

0
installs
▌
Test Generator · data-wise
This skill should be used when the user asks to "generate tests", "create CLI tests", "add dogfooding tests", "create plugin validation tests", or needs automated and interactive test suites for a project. Generates dogfooding test suites (automated + interactive) for any project type.

0
installs
▌
Adhd Workflow · data-wise bundle
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.

0
installs
▌
Backend Designer · data-wise
This skill should be used when the user asks to "design an API", "plan database schema", "set up authentication", "design backend architecture", or discusses backend patterns and infrastructure. Provides pragmatic backend design guidance following "solid indie" principles.

0
installs
▌
Orchestrator Resilience · data-wise
Reference templates for orchestrator-v2 agent error handling, retry/backoff, circuit breaker, escalation, and execution timeline display. Load when the orchestrator hits an agent failure, needs to show a retry/timeout/escalation report, or the user asks for a `timeline` view. NOT needed for normal happy-path orchestration — only for error recovery and timeline display.

0
installs
▌
Test Strategist · data-wise
This skill should be used when the user asks to "plan test strategy", "improve test coverage", "fix flaky tests", "optimize test performance", or needs guidance on testing infrastructure and quality assurance. Provides expert guidance on test strategy design, coverage analysis, and test quality improvement.

0
installs
▌
Prompt Refiner · 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.

0
installs
▌
Frontend Designer · data-wise
This skill should be used when the user asks to "design a UI", "plan component architecture", "improve accessibility", "optimize frontend performance", or discusses UI/UX patterns. Provides pragmatic frontend design guidance with ADHD-friendly patterns.

0
installs
▌
Dist Extras · data-wise bundle
This skill should be used when the user asks to "publish to PyPI", "generate an install script", "curl install", "publish to Claude Code marketplace", "create marketplace.json", "PyPI trusted publishing", "private plugin", "plugin drift", "pin refresh", or needs help with non-Homebrew distribution channels (PyPI, curl-based installers, Claude Code marketplace). Covers Python package publishing, GitHub-release curl installers, Claude Code plugin marketplace listings (public and private), post-release pin-refresh, and drift detection.

0
installs
▌
Background Task Manager · data-wise
This skill should be used when the user asks to "check task status", "view task output", "cancel task", "kill background task", "list running tasks", "wait for task", "show task results", "stop background job", or mentions background task IDs from `/craft:orch`'s `orchestrate-dispatch` mode or other backgrounded commands. Manages the lifecycle of already-launched background tasks — status inspection, output retrieval, and cancellation.

0
installs
▌
Changelog Automation · data-wise bundle
Automate changelog generation from commits, PRs, and releases following Keep a Changelog format. Use when setting up release workflows, generating release notes, or standardizing commit conventions.

0
installs
▌
Repo Triage · data-wise
This skill should be used when the user asks to "triage the repo", "clean up open issues and stale branches", "what needs attention in this repo", or wants a batch pass over open GitHub issues plus stale worktrees/branches, grounded against current repo state, with confirmed (never automatic) deletion/closure and the remainder sorted into grill-ready/plan-ready/defer buckets.

0
installs
▌
Drive Engine · data-wise
This skill should be used when driving an approved SPEC to completion — "drive this spec to done", "run the orchestrate drive loop", "implement the spec autonomously until tests pass". Owns the reusable body behind /craft:orch:drive — parse-or-derive ORCHESTRATE phases, dispatch file-scoped subagents, and run the authoritative real verify gate.

0
installs
▌
Session State · data-wise
This skill should be used when the user asks to "save session", "resume session", "continue where I left off", "session history", or needs orchestrator session state persistence including save, load, resume, and history management.

0
installs
▌
Task Analyzer · data-wise
This skill should be used when the user asks to "analyze a task", "route a command", "what craft command should I use", or describes a development task that needs routing to the appropriate craft workflow. Analyzes natural language task descriptions and maps them to optimal craft command sequences.

0
installs
▌
Brainstorm Insights · data-wise bundle
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.

0
installs
▌
Workflow Engine · data-wise
This skill should be used when executing a coded, fixed-control-flow workflow — "run the workflow engine", "execute this WORKFLOW yaml", "run the coded orchestration", decompose→cover→verify→synthesize shapes. Owns the reusable body behind /craft:orch:workflow — compile a WORKFLOW definition to a deterministic wave plan, dispatch file-scoped agents wave by wave under a run-wide semaphore, structurally gate every output, and run a first-class verify gate.

0
installs
▌
Plan Orchestrator · data-wise
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.

0
installs
▌
Homebrew Setup Wizard · data-wise
This skill should be used when the user asks to "set up Homebrew automation", "homebrew setup", "automate formula updates", "configure Homebrew workflow", or needs end-to-end Homebrew formula automation from detection through workflow generation.

0
installs
▌
Architecture Decision Records · data-wise
Write and maintain Architecture Decision Records (ADRs) following best practices for technical decision documentation. Use when documenting significant technical decisions, reviewing past architectural choices, or establishing decision processes.

0
installs
▌
Command Skill Token Efficiency · data-wise
This skill should be used when the user is writing, editing, resizing, or reviewing a craft command (commands/**/*.md), skill (skills/**/SKILL.md), or agent (agents/*.md) file — including "add a new command for X", "this command is getting long", "should this be a skill instead", "make /craft:do leaner", "reduce token usage in this command", "audit command body size", or "is this skill too big". Also use it before finalizing any deprecated-true/replaced-by thin-shim split (the ADR-002 pattern). Checks whether content belongs in a command (invocation-specific — flags, frontmatter) versus a skill (procedure — the actual logic, which loads conditionally instead of every invocation), and runs a quantitative line-ratio check via scripts/audit-deprecated-commands.py --pair. Do not confuse with skill-standards' format/frontmatter compliance check (a different concern — that audits style rules, this audits token-cost structure) or guard-audit (tunes branch-guard rules, doesn't touch command/skill content).

0
installs
▌
Homebrew Multi Formula · data-wise
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.

0
installs
▌
Distribution Strategist · data-wise
This skill should be used when the user asks to "plan distribution", "how should I distribute this", "choose a package manager", "distribution strategy", or needs to select and prioritize distribution channels for a software project. Recommends optimal distribution channels based on project type and target audience.

0
installs
▌
Homebrew Formula Expert · data-wise
This skill should be used when the user asks to "create a Homebrew formula", "fix brew audit errors", "write a formula", "Homebrew best practices", or needs help with Homebrew formula syntax, dependencies, and troubleshooting. Expert knowledge of Homebrew formula creation and maintenance.

0
installs
▌
Homebrew Workflow Expert · data-wise
This skill should be used when the user asks to "create Homebrew release workflow", "automate formula updates with GitHub Actions", "configure tap CI", or needs GitHub Actions workflows for automated Homebrew formula updates and releases.

0
installs
▌
Help · data-wise
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.

1
install
▌
Inbox · data-wise
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.

1
install
▌
Reply · data-wise
This skill should be used when the user asks to "reply to email", "respond to email", "draft reply", "email reply", "answer that email", "get back to them", "write back", "respond to that", "reply to that message", or wants to respond to a specific message. Drafts replies with safety confirmation that never auto-sends.

1
install
▌
Stats · data-wise
This skill should be used when the user asks for "email stats", "inbox stats", "email analytics", "how many unread", "how many emails", "inbox count", "unread count", "email volume", "inbox overview", or wants to see inbox metrics. Shows unread count, top senders, oldest unread, and volume trends.

1
install
▌
Config · data-wise
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.

1
install
▌
Digest · data-wise
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.

1
install
▌
Export · data-wise
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.

1
install
▌
Manage · data-wise
This skill should be used when the user asks to "manage email", "bulk email", "move emails", "flag emails", "archive emails", "unflag emails", "move these emails", "flag this", "archive that", "mark as read", "star this email", "clean up my inbox", or wants to perform batch operations. Handles flag, unflag, move, and archive for multiple emails at once.

1
install
▌
Search · data-wise
This skill should be used when the user asks to "search email", "find email", "look for email", "email from", "email about", "did I get an email about", "find message from", "look for that email from", "any emails about", "search my inbox for", or wants to locate specific messages. Searches by keyword, sender, flags, or date using himalaya filter syntax.

1
install
▌
Triage · data-wise
This skill should be used when the user asks to "triage email", "classify email", "sort email", "go through my inbox", "what needs attention", "prioritize my email", "sort my messages", "which emails are important", "what should I respond to", or wants to prioritize their inbox. Classifies emails as actionable, informational, or skip using MCP prompts.

1
install
▌
Compose · data-wise
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.

1
install
▌
Forward · data-wise
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.

1
install
▌
Morning · data-wise
This skill should be used when the user asks for "morning briefing", "morning email", "start my day", "what happened overnight", "catch me up on email", "daily briefing", "email briefing", "morning roundup", or wants a comprehensive morning email review with urgency classification and action items.

1
install
▌
Respond · data-wise
This skill should be used when the user asks to "respond to all my emails", "batch reply", "draft replies for everything", "answer all emails", "mass respond", "generate draft replies", "reply to all unread", "process my inbox replies", "bulk respond", "catch up on replies", or wants to batch-generate draft replies for multiple emails at once. For single-reply use /himalaya:reply instead.

1
install
▌
Threads · data-wise
This skill should be used when the user asks to "show threads", "email conversations", "conversation view", "thread view", "show me the whole conversation", "threaded view", "group by subject", "show all replies", "read the whole thread", or wants to see emails grouped into conversations by subject line. Lists threads via list_threads and reads full thread context via read_thread.

1
install
▌
Attachments · data-wise
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.

1
install

57 published skills