Definitive guide to building CLI applications with Cobra and Viper — command-first architecture, configuration management, environment variable binding, and in-memory CLI testing. Written by spf13, the original creator of both libraries.
Safe file operations in Go using spf13/fileflow (move, copy, rename across filesystems with conflict-safe naming) and spf13/pathologize (make filenames and path segments safe on every OS).
Review Go design documents before implementation begins — catches over-engineering, missing error paths, interface misuse, and Cobra/Viper convention violations while a plan is still cheap to change.
Idiomatic Go patterns and best practices — package design, error handling, interfaces, concurrency, testing, and project layout. Written by spf13 (former Go team lead, author of Cobra, Viper, Hugo, Afero).
Building native desktop applications in Go with Wails v2 (stable) and v3 (alpha). CRITICAL: v2 and v3 have incompatible APIs that LLMs constantly blend — this skill detects the version and follows only that version's patterns.
Analyze HitKeep AI visibility data. Use for AI crawler fetches, AI-referred visits, assistant names or families, citation yield, resource types, top paths, fetch failures, Search Console context, GPTBot, ClaudeBot, ChatGPT, Claude, Perplexity, AI search, or whether assistants are discovering and sending traffic to a…
Official parent skill for analyzing HitKeep data through HitKeep MCP and official docs. Use for broad traffic, event, ecommerce, Web Vitals, AI visibility, Search Console, opportunity, tracking-health, MCP setup, or analytics-surface questions; use a narrower HitKeep analytics skill when the task clearly matches one.
Analyze HitKeep ecommerce and conversion data. Use for revenue, orders, average order value, products, sources, ecommerce funnels, conversion changes, UTM performance, acquisition quality, or aggregate city, provider, and ASN context.
Verify HitKeep tracking setup and automatic event collection. Use when installation status, missing pageviews or events, WordPress or script installs, automatic outbound clicks, downloads, form submissions, hostname mismatches, blockers, consent, CSP, or the difference between tracker failure and analytics…
Diagnose HitKeep traffic drops, spikes, source shifts, and suspicious changes. Use when traffic, sessions, visitors, pageviews, events, or conversions changed; when a deploy may have affected measurement or behavior; or when search, referral, direct, campaign, and bot explanations need to be separated.
Read-only MCP server for aggregate HitKeep analytics and official documentation. Remote server at {hitkeep_host}.
★not rated 97▲
+4 todayA
tokens not measured
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: