CtrlK
BlogDocsLog inGet started
Tessl Logo

downloading-batch-export-files

Export PostHog events, persons, or sessions on demand and download the resulting files. Use when the user asks to download/export raw PostHog data, create a one-off file export, fetch a Parquet or JSONLines export, or use the file_download_batch_exports API. Covers starting the export with MCP, polling completion, and downloading via the existing REST redirect endpoint.

75

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

93%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, highly actionable skill body that covers the full export-to-download workflow with concrete endpoints and a status feedback loop. The only meaningful gap is the lack of an explicit post-download verification step.

Suggestions

Add a brief post-download verification step (e.g., confirm the file is non-empty and, for Parquet, openable) to strengthen the feedback loop for this batch operation.

Optionally note the typical poll interval or backoff recommendation in step 3 to make the polling loop fully self-contained.

DimensionReasoningScore

Conciseness

Lean and operational with no conceptual padding (no explanations of what PostHog or Parquet is); every line earns its place, matching the 'lean and efficient' top anchor.

5 / 5

Actionability

Fully executable guidance: exact MCP tool names, a copy-paste-ready example JSON request, precise REST endpoint paths, and filename templates cover the common cases.

5 / 5

Workflow Clarity

A clear 6-step sequence with an explicit status-handling table and retry-on-transient-state feedback loop; the batch-operation validation cap does not bind because status validation is present. Held at 4 rather than 5 because there is no explicit verification of downloaded file integrity (e.g., non-empty / valid file).

4 / 5

Progressive Disclosure

A single, well-organized SKILL.md with clearly signaled sections (MCP tools, numbered workflow, Watch-outs), no nested or dead references, and no monolithic wall of text; no bundle files exist, so well-organized sections suffice for the top anchor.

5 / 5

Total

19

/

20

Passed

Description

92%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 that clearly states capabilities and trigger conditions with concrete PostHog-specific terms. The only minor gap is the absence of file-extension keywords.

Suggestions

Consider adding file extensions (e.g., '.parquet', '.jsonl') to the trigger phrases to maximize natural keyword coverage.

DimensionReasoningScore

Specificity

Names the domain (PostHog events/persons/sessions) and multiple concrete actions across the full lifecycle (start export, poll completion, download), matching the 'multiple specific concrete actions; comprehensive coverage' anchor.

5 / 5

Completeness

Explicitly answers both 'what' (export and download events/persons/sessions) and 'when' with concrete trigger phrases in a 'Use when the user asks to...' clause, matching the top anchor.

5 / 5

Trigger Term Quality

Strong natural trigger phrases ('download/export raw PostHog data', 'one-off file export', 'Parquet or JSONLines export') plus the technical API name, but lacks file extensions like .parquet/.jsonl that would push it to a 5.

4 / 5

Distinctiveness Conflict Risk

Tightly scoped to PostHog batch exports and the file_download_batch_exports API, a clear niche with distinct triggers and minimal risk of firing for unrelated skills.

5 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
PostHog/posthog
Reviewed

Table of Contents

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.