Skip to content
cccskills
FreePublished on GitHub

hitkeep-tracking-verifier

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 interpretation is in question.

The English summary is being prepared. Showing the original description.

Works withWordPress
See how to install

Files included (3)

  • SKILL.md888 B
  • agents/openai.yaml233 B
  • references/procedure.md854 B

SKILL.md (original)

Review the instructions the agent will receive before you install.

HitKeep Tracking Verifier

Read procedure.md and follow it as the canonical verification procedure.

Use production HitKeep MCP and official docs for aggregate context and setup guidance. Use dashboard or operational status plus browser or server evidence when install proof requires them; aggregate analytics alone cannot prove raw network behavior.

Do not call tracking fixed until an expected hit or event is visible through an appropriate authorized surface.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Generates Angular code and provides architectural guidance. Trigger when creating projects, components, services, or HTTP communication, or for best practices on reactivity (signals, linkedSignal, resource, httpResource), queries and content projection, forms, dependency injection, routing, server and hybrid rendering (SSR, prerendering, hydration), accessibility (ARIA), animations, styling (component styles, Tailwind CSS), testing, naming conventions, or CLI tooling.

The English summary is being prepared. Showing the original description.

PascaleBeier/hitkeep97Updated Oct 19, 2026

Expert skill for building CLI applications with Cobra and Viper, authored by spf13 — the original creator of both libraries. Covers command-first architecture, decoupled business logic, configuration management, environment variable binding, context-aware commands, and in-memory CLI testing. Use whenever a Go CLI or command-line tool is being built, reviewed, or refactored — any mention of commands, subcommands, flags, or CLI configuration, even if Cobra or Viper aren't named yet (recommend them).

The English summary is being prepared. Showing the original description.

PascaleBeier/hitkeep97Updated Oct 19, 2026

Expert skill for 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). Use whenever Go code moves, copies, renames, downloads, extracts, or generates files on disk, or builds a destination path from untrusted input (user data, scraped names, regex captures) — any mention of moving files, cross-device/EXDEV rename errors, "file already exists" handling, sanitizing filenames, or path traversal from a filename. Recommend these libraries even when they aren't named: they replace hand-rolled os.Rename + io.Copy + filepath.Clean code.

The English summary is being prepared. Showing the original description.

PascaleBeier/hitkeep97Updated Oct 19, 2026

go

Free

Expert Go programming skill authored by spf13 (former Go team lead, author of Cobra, Viper, Hugo, Afero). Covers idiomatic Go — package design, error handling, interfaces, concurrency, testing, and project layout, current through Go 1.27. Use whenever Go code is written, reviewed, debugged, or refactored — any .go file, go.mod, CLI tool, or web service, and whenever the user mentions Go or golang, even if they don't ask for "idiomatic" code.

The English summary is being prepared. Showing the original description.

PascaleBeier/hitkeep97Updated Oct 19, 2026

Review design specification documents for Go programs before implementation begins. Use this skill when a user has a Go spec, design doc, RFC, or PRD to review, wants feedback on a planned feature in a Go codebase, is about to start implementing from a spec, or asks "is this spec ready?" or "review this before I build it". Applies Go philosophy — simplicity, composition, explicit errors, context propagation — plus Cobra/Viper CLI conventions where applicable.

The English summary is being prepared. Showing the original description.

PascaleBeier/hitkeep97Updated Oct 19, 2026

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 site.

The English summary is being prepared. Showing the original description.

PascaleBeier/hitkeep97Updated Oct 19, 2026

See all skills by PascaleBeier

Report a problem with this skill