원클릭으로 Manus에서 모든 스킬 실행

hitkeep-tracking-verifier

스타72

포크5

업데이트2026년 7월 14일 15:38

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.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

PascaleBeier

PascaleBeier/hitkeep

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

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.

이 저장소의 다른 Skills

같은 저장소

hitkeep-development

PascaleBeier/hitkeep

Implement and route HitKeep contributions through the repository-owned hk developer platform. Use for any HitKeep code, UI, API, database, analytics-feature, seed, screenshot, documentation, integration, or release-preparation change, as well as setup, local development, builds, smoke tests, and contributor workflow discovery.

2026-07-1872

hitkeep-workspace

PascaleBeier/hitkeep

Operate HitKeep safely in isolated Git worktrees. Use when inspecting workspace state, resolving ports or URLs, starting or stopping development services, coordinating concurrent agents or QA runs, reusing active runs, reading bounded logs, or preparing a secret-free handoff.

2026-07-1872

hitkeep-qa

PascaleBeier/hitkeep

Plan, execute, investigate, and report HitKeep quality gates through hk. Use while iterating, before calling contributor work complete, when choosing change-aware versus PR-parity versus exhaustive validation, when CI parity matters, or when investigating a failed or asynchronous gate.

2026-07-1772

hitkeep-i18n

PascaleBeier/hitkeep

Maintain HitKeep dashboard localization. Use whenever a contributor adds or changes user-visible dashboard text, Transloco keys, locale JSON files, PrimeNG locale behavior, language switching, translated labels, localized layout, date/number/duration formatting, or supported dashboard languages.

2026-07-1472

hitkeep-ai-visibility-analyst

PascaleBeier/hitkeep

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.

2026-07-1472

hitkeep-analytics

PascaleBeier/hitkeep

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.

2026-07-1472

원클릭으로 모든 스킬 실행

name	hitkeep-tracking-verifier
description	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.