Name: diagnosing-stacktrace-symbolication
Rating: 73.6 (1 reviews)
Author: PostHog

diagnosing-stacktrace-symbolication

Help users debug PostHog Error Tracking stack-trace symbolication for any supported platform — JavaScript/TypeScript web, React Native (Hermes), Android (Proguard / R8), or iOS / macOS (dSYM). The PostHog symbol-set lookup flow is universal across platforms; build-tool and artifact details live in per-platform references (JavaScript is fleshed out, others come as we encounter them). Use when stack frames stay minified or obfuscated after symbols are uploaded, PostHog symbol sets show last_used but frames are not readable, chunk IDs or dSYM UUIDs do not match, "Token not found" appears, uploaded source maps / dSYMs / Proguard mappings look empty, or bundler / symbol-upload configuration needs troubleshooting.

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

—

The risk profile of this skill

Quality

Content

88%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, actionable diagnostic workflow with concrete commands, MCP tool calls, and a failure-matrix checklist. The main weakness is progressive disclosure: the body repeatedly points to `./references/javascript.md`, but no `references/` directory or file exists in the bundle, so the key detailed reference is absent.

Suggestions

Add the missing `./references/javascript.md` file (or create the `references/` directory) so the in-body links resolve — currently every per-platform reference link is broken.

Tighten the opening definitional paragraph and the Step 1-2 prose; the cross-platform framing could be condensed since the platform table already conveys it.

For the 'coming soon' platforms, consider a one-line stub per reference file so the reference structure exists even before content is filled in, making the navigation complete.

Dimension	Reasoning	Score
Conciseness	Mostly lean and efficient with concrete commands and tool calls; the opening definitional paragraph ('Symbolication is the cross-platform name for...') and some prose around Steps 1-2 could be trimmed without losing actionable value.	4 / 5
Actionability	Provides copy-paste-ready executable guidance — the Vite config snippet, the `posthog-cli symbol-sets extract` command with npx/bunx alternatives, and specific MCP tool invocations with exact parameters covering the common cases.	5 / 5
Workflow Clarity	Clear 5-step pipeline (build config -> artifacts -> symbol sets -> compare -> fix) with explicit decision branches in Step 4, an interpretation checklist for symbol-set rows, and a cross-platform failure matrix that serves as a diagnostic checklist with 'Next check' feedback directions.	5 / 5
Progressive Disclosure	Good overview structure with well-signaled one-level-deep per-platform references and honest 'coming soon' markers, but the primary referenced file `./references/javascript.md` is not present in the bundle, leaving the main detailed reference target missing.	4 / 5
	Total	18 / 20 Passed

Description

95%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description with explicit 'what' and 'when' guidance, natural trigger terms including platform-specific synonyms, and a clear niche that minimizes conflict risk. The only minor weakness is that the action language ('debug'/'troubleshoot') is generic rather than enumerating several distinct concrete actions.

Dimension	Reasoning	Score
Specificity	Names the concrete domain (PostHog Error Tracking stack-trace symbolication) and lists specific platform targets and many concrete failure conditions, but the action verbs themselves ('debug', 'troubleshoot') are somewhat generic rather than a list of multiple distinct concrete actions.	4 / 5
Completeness	Explicitly answers both 'what' ('Help users debug PostHog Error Tracking stack-trace symbolication') and 'when' with a concrete 'Use when...' clause enumerating specific trigger phrases.	5 / 5
Trigger Term Quality	Comprehensive natural trigger terms a user would actually say — 'stack frames stay minified or obfuscated', 'Token not found', 'source maps / dSYMs / Proguard mappings look empty', plus platform-specific synonyms like chunk IDs, dSYM UUIDs, Hermes, and Proguard / R8.	5 / 5
Distinctiveness Conflict Risk	Clear narrow niche (PostHog Error Tracking symbolication across specific platforms) with distinct triggers; minimal risk of firing for unrelated skills.	5 / 5
	Total	19 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: PostHog/posthog
Path: products/error_tracking/skills/diagnosing-stacktrace-symbolication/SKILL.md
Commit: 130f3a1

Reviewed: 9 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.