Agent skill · Security

survey-sdk-audit

Audit PostHog survey SDK features and version requirements

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill survey-sdk-audit --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 14 KB
Bundled scripts: none
Path: skills/analysis/survey-sdk-audit/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Surveys SDK Feature Audit Skill Use this skill when auditing survey feature support across PostHog SDKs for `surveyVersionRequirements.ts`. **Feature to audit:** $ARGUMENTS ## Setup Check (Run First) Before starting, verify the SDK paths are accessible. Run `ls` on each path: - `$POSTHOG_JS_PATH` - `$POSTHOG_IOS_PATH` - `$POSTHOG_ANDROID_PATH` - `$POSTHOG_FLUTTER_PATH` If any path is empty or doesn't exist, ask the user: "I need the path to [SDK repo] on your machine. Where is it located?" Once you have all paths, ask the user if they'd like to save them for future sessions by adding to `.claude/settings.local.json`: ```json { "env": { "POSTHOG_JS_PATH": "/path/to/posthog-js", "POSTHOG_IOS_PATH": "/path/to/posthog-ios", "POSTHOG_ANDROID_PATH": "/path/to/posthog-android", "POSTHOG_FLUTTER_PATH": "/path/to/posthog-flutter" }, "permissions": { "allow": [ "Read(/path/to/posthog-js/**)", "Read(/path/to/posthog-ios/**)", "Read(/path/to/posthog-android/**)", "Read(/path/to/posthog-flutter/**)", "Grep(/path/to/posthog-js/**)", "Grep(/path/to/posthog-ios/**)", "Grep(/path/to/posthog-android/**)", "Grep(/path/to/posthog-flutter/**)" ] } } ``` **Note:** The `Read` and `Grep` permissions gra

What's inside
Steps it walks through
  1. Setup Check (Run First)
  2. Using SDK Paths in Commands
  3. Tracking Issue
  4. SDK Paths and Changelogs
  5. Flutter Native Dependencies
  6. Audit Process
  7. Step 1: Understand the Feature
  8. Step 2: Search Changelogs First
  9. Step 3: Search Code If Not in Changelog
  10. Step 4: For Flutter, Find When Native Dependency Was Bumped
  11. Step 5: Verify Feature Actually Works (Not Just Types)
  12. Reference Implementation
  13. Web-Only vs Cross-Platform Features
  14. Output Format
Ships with 1 file
  • metadata.json
Commands it runs
echo $POSTHOG_JS_PATH
gh api repos/PostHog/posthog/issues/45658 --jq '.body' > /tmp/tracking_issue_body.md
gh api repos/PostHog/posthog/issues/45658 -X PATCH -f body="$(cat /tmp/tracking_issue_body.md)"
Search changelog for the feature keyword
grep -n -i "KEYWORD" /path/to/CHANGELOG.md
Find commits that added the keyword (use -S for exact string match)
cd /path/to/sdk && git log --oneline --all -S "KEYWORD" -- "*.swift" "*.kt" "*.ts" "*.tsx"
Then find the first version tag containing that commit
git tag --contains COMMIT_HASH | sort -V | head -3
Find when Flutter started requiring iOS version X.Y.Z
More from claude-skill-registry
All skills →
About this skill
What does the survey-sdk-audit skill do?

Audit PostHog survey SDK features and version requirements

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill survey-sdk-audit --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going