codyswanngt/lisa-posthog-access
plugins/lisa-cursor/skills/lisa-posthog-access/SKILL.md
Vendor-neutral access layer for PostHog. PostHog skills and observability rules MUST delegate through this skill rather than calling PostHog MCP tools or REST directly. Resolves PostHog MCP first when available, then falls back to POSTHOG_PERSONAL_API_KEY bearer auth.
$ install --global
skillsauthnpx skillsauth add codyswanngt/lisa lisa-posthog-accessInstall 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: Jul 5, 2026, 3:22 AM104.9s1 file scanned
SKILL.md
- name:
- lisa-posthog-access
- description:
- Vendor-neutral access layer for PostHog. PostHog skills and observability rules MUST delegate through this skill rather than calling PostHog MCP tools or REST directly. Resolves PostHog MCP first when available, then falls back to POSTHOG_PERSONAL_API_KEY bearer auth.
- allowed-tools:
- ["Bash", "Read", "Skill"]
PostHog Access: $ARGUMENTS
Single chokepoint for PostHog operations. Caller skills and rules MUST NOT call
mcp__posthog__* tools or PostHog REST directly.
Invocation Contract
operation: query project_id:<ID> payload:{...}
operation: insights project_id:<ID>
operation: persons project_id:<ID> [query:<QUERY>]
operation: events project_id:<ID> [after:<ISO>] [before:<ISO>]
Return parsed JSON in a <result> block.
Substrate Selection
Probe in order:
- PostHog MCP, if available and authenticated.
POSTHOG_PERSONAL_API_KEYbearer token against the configured PostHog host.
PostHog documents personal API keys and bearer authentication. The headless REST tier uses:
POSTHOG_HOST=${POSTHOG_HOST:-https://app.posthog.com}
posthog_api() {
local path="$1"
local method="${2:-GET}"
local body="${3:-}"
[ -n "$POSTHOG_PERSONAL_API_KEY" ] || {
echo "Error: POSTHOG_PERSONAL_API_KEY is not set." >&2
return 1
}
local args=(-sS -X "$method" -H "Authorization: Bearer $POSTHOG_PERSONAL_API_KEY")
[ -n "$body" ] && args+=(-H "Content-Type: application/json" --data-binary "$body")
curl "${args[@]}" "${POSTHOG_HOST%/}/api${path}"
}
If neither tier works, fail with:
Error: no PostHog access substrate available. Authenticate the PostHog MCP or set POSTHOG_PERSONAL_API_KEY.
Invariants
- Fallback is gated on
POSTHOG_PERSONAL_API_KEY. POSTHOG_HOSTdefaults to PostHog Cloud but can point at a self-hosted deployment.- Consumer skills do not embed PostHog REST paths.
Related Skills
codyswanngt/lisa-setup-sonar
tools
VerifiedTrustedCommunity
Configure the official SonarQube plugin + MCP as Lisa's single Sonar substrate across every supported coding agent. Installs/updates the SonarQube CLI, authenticates (browser login on a dev machine, or SONARQUBE_CLI_TOKEN headless), selects the Test Manager target, runs `sonar integrate <agent>` for each supported agent (Claude, Codex, Cursor, Copilot, Antigravity) and wires the MCP for OpenCode, then writes only non-secret policy to .lisa.config.json. Separate from the CI SonarCloud scan gate, which is unchanged.
1SKILL.mdUpdated Jul 24, 2026
codyswanngt/lisa-setup-sonar
tools
VerifiedTrustedCommunity
Configure the official SonarQube plugin + MCP as Lisa's single Sonar substrate across every supported coding agent. Installs/updates the SonarQube CLI, authenticates (browser login on a dev machine, or SONARQUBE_CLI_TOKEN headless), selects the Test Manager target, runs `sonar integrate <agent>` for each supported agent (Claude, Codex, Cursor, Copilot, Antigravity) and wires the MCP for OpenCode, then writes only non-secret policy to .lisa.config.json. Separate from the CI SonarCloud scan gate, which is unchanged.
1SKILL.mdUpdated Jul 24, 2026
codyswanngt/lisa-setup-sonar
tools
VerifiedTrustedCommunity
Configure the official SonarQube plugin + MCP as Lisa's single Sonar substrate across every supported coding agent. Installs/updates the SonarQube CLI, authenticates (browser login on a dev machine, or SONARQUBE_CLI_TOKEN headless), selects the Test Manager target, runs `sonar integrate <agent>` for each supported agent (Claude, Codex, Cursor, Copilot, Antigravity) and wires the MCP for OpenCode, then writes only non-secret policy to .lisa.config.json. Separate from the CI SonarCloud scan gate, which is unchanged.
1SKILL.mdUpdated Jul 24, 2026
codyswanngt/lisa-setup-sonar
tools
VerifiedTrustedCommunity
Configure the official SonarQube plugin + MCP as Lisa's single Sonar substrate across every supported coding agent. Installs/updates the SonarQube CLI, authenticates (browser login on a dev machine, or SONARQUBE_CLI_TOKEN headless), selects the Test Manager target, runs `sonar integrate <agent>` for each supported agent (Claude, Codex, Cursor, Copilot, Antigravity) and wires the MCP for OpenCode, then writes only non-secret policy to .lisa.config.json. Separate from the CI SonarCloud scan gate, which is unchanged.
1SKILL.mdUpdated Jul 24, 2026