igorganapolsky/skills/configure-analytics
skills/configure-analytics/SKILL.md
# Skill: Configure Analytics Repeatable skill for setting up Plausible, PostHog, and GA4 analytics keys in both local `.env` and Railway production environment variables. ## When to use - New session notices analytics env vars are missing - After rotating any analytics API key - After creating a new GA4 property ## Prerequisites - Chrome logged into: plausible.io, us.posthog.com, analytics.google.com - Railway MCP authenticated OR Chrome logged into railway.com ## Steps ### 1. Gather keys
$ install --global
skillsauthnpx skillsauth add igorganapolsky/rlhf-feedback-loop skills/configure-analyticsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 27, 2026, 2:16 AM8.4s1 file scanned
SKILL.md
Skill: Configure Analytics
Repeatable skill for setting up Plausible, PostHog, and GA4 analytics keys
in both local .env and Railway production environment variables.
When to use
- New session notices analytics env vars are missing
- After rotating any analytics API key
- After creating a new GA4 property
Prerequisites
- Chrome logged into: plausible.io, us.posthog.com, analytics.google.com
- Railway MCP authenticated OR Chrome logged into railway.com
Steps
1. Gather keys from dashboards
Plausible API key:
- Navigate to https://plausible.io/settings/api-keys
- If no key exists, create one named "thumbgate-railway-prod"
- Copy the key value
PostHog project API key:
- Navigate to https://us.posthog.com/settings/project#variables
- Copy the "Project API Key" (starts with
phc_)
GA4 Measurement ID:
- Navigate to https://analytics.google.com
- Select the ThumbGate property (or create one: Admin → Create Property)
- Go to Data Streams → Web stream → copy Measurement ID (format: G-XXXXXXXXXX)
- If no ThumbGate property exists, skip — Plausible is primary
2. Set local .env
Write/update repo/.env with:
PLAUSIBLE_API_KEY=<key>
PLAUSIBLE_SITE_ID=thumbgate-production.up.railway.app
POSTHOG_API_KEY=<phc_key>
THUMBGATE_GA_MEASUREMENT_ID=<G-ID or leave commented>
3. Set Railway production vars
Option A — Railway CLI or GitHub deploy variables (preferred):
gh secret list --repo IgorGanapolsky/ThumbGate
gh variable list --repo IgorGanapolsky/ThumbGate
If Railway CLI auth works, set variables with railway variables set.
If Railway CLI reports invalid_grant, use the GitHub PR/deploy path and the
Railway dashboard in Chrome. Do not direct-push to main; use a focused branch,
PR, required checks, and branch-protected merge.
Option B — Chrome (if MCP not authenticated):
- Navigate to railway.com dashboard
- Click into the ThumbGate project → production service
- Go to Variables tab
- Add/update each key-value pair
- Railway auto-redeploys on variable change
4. Verify
# Local: run Plausible poller
npm run social:poll:plausible
# Production: check instrumentation scripts and health
curl -fsS https://thumbgate.ai/health
curl -fsS https://thumbgate.ai/checkout/pro | grep -E 'plausible|posthog|G-[A-Z0-9]+'
Current values (last updated 2026-05-26)
- Plausible site:
thumbgate-production.up.railway.app - PostHog project: US Cloud, project ID 299775
- GA4: use
THUMBGATE_GA_MEASUREMENT_IDwhen present; do not assume the dashboard is export-ready without provider credentials.
Related Skills
igorganapolsky/thumbgate-rules
tools
VerifiedTrustedCommunity
List the active ThumbGate prevention rules, reliability rules, and the promoted lessons behind them, so the user can see which guardrails are currently protecting this project and WHY each one exists. Reads the live rule and lesson stores via the prevention_rules, get_reliability_rules, and search_lessons MCP tools (CLI fallback `npx thumbgate rules`). Use when the user says "what is ThumbGate protecting me from", "show my rules", "show my gates", "what has the agent learned", "list active guardrails", or "what's blocked here". Do NOT use to CREATE a new rule (use the thumbgate-guard skill), to see runtime enforcement counts of what actually fired (use the thumbgate-blocked skill), or to diagnose whether ThumbGate is wired up at all (use the thumbgate-doctor skill).
23SKILL.mdUpdated Jun 12, 2026
igorganapolsky/thumbgate-protect
tools
VerifiedTrustedCommunity
Inspect this repo's branch and release governance (protected branches, release rules, protected-file globs) and, only when the user explicitly approves, grant a scoped, time-limited exception so a protected-file edit or publish can proceed under audit. Reads posture via the get_branch_governance MCP tool and records a narrow, expiring approval via the approve_protected_action MCP tool. Use when the user says "is main protected", "show branch governance", "what am I blocked from editing", "approve this protected change", or "let me edit a protected file just this once". Do NOT use to disable protection wholesale, to grant broad or standing exceptions, or to diagnose hook wiring (use the thumbgate-doctor skill) — this skill is for narrow, temporary, audited approvals only.
23SKILL.mdUpdated Jun 12, 2026
igorganapolsky/thumbgate-guard
tools
VerifiedTrustedCommunity
Turn the agent's most recent mistake into an enforced ThumbGate prevention rule (a PreToolUse block gate) so the same bad tool call is intercepted before it runs again, in this and every future session across Claude Code, Cursor, Codex, Gemini, Amp, and Cline. Captures the failure with the capture_feedback MCP tool, then force-promotes it via `npx thumbgate force-gate` so it is enforced, not just logged. Use when the user says "guard against this", "block this from happening again", "never do that again", "make that a rule", "stop the agent from repeating that", or right after a bad action or thumbs-down that should become a hard rule. Do NOT use to merely log a thumbs-up/down without enforcement (use the thumbgate-feedback skill), to recall prior context before starting work (use the Agent Memory skill), or to list rules that already exist (use the thumbgate-rules skill).
23SKILL.mdUpdated Jun 12, 2026
igorganapolsky/thumbgate-doctor
tools
VerifiedTrustedCommunity
Health-check whether ThumbGate is actually wired into this agent — PreToolUse/SessionStart hooks installed, MCP server reachable, lesson store present, statusline, and overall agent-readiness — then report exactly what to fix. Runs the existing `npx thumbgate doctor` audit and the check_operational_integrity MCP tool. Use when the user says "is ThumbGate wired up", "thumbgate doctor", "check my guardrails are installed", "why aren't my gates firing", "is the MCP server connected", or "agent readiness". Do NOT use to view rules (use the thumbgate-rules skill), to view what was blocked (use the thumbgate-blocked skill), or to capture a new rule (use the thumbgate-guard skill) — this skill only diagnoses setup and wiring.
23SKILL.mdUpdated Jun 12, 2026