CtrlK
BlogDocsLog inGet started
Tessl Logo

analytics-product

Analytics de produto — PostHog, Mixpanel, eventos, funnels, cohorts, retencao, north star metric, OKRs e dashboards de produto.

60

Quality

71%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/analytics-product/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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.

The body is a strong, code-heavy reference with highly actionable examples and a clear optimization workflow, suffering only from generic boilerplate sections that add little. Trimming the templated When-to-use/Best-practices/Limitations blocks would tighten it further.

Suggestions

Remove or condense the generic boilerplate sections (When to Use, Do Not Use, Best Practices, Common Pitfalls, Limitations) that repeat templated, non-domain-specific text to improve conciseness.

Add an explicit validate-then-proceed checkpoint to the PostHog implementation workflow (e.g. verify the event appears in PostHog before scaling) to match the funnel workflow's rigor.

Replace the duplicated/boilerplate title section and the empty 'How It Works' framing with a single concise overview to avoid redundant structure.

DimensionReasoningScore

Conciseness

Body is mostly efficient concrete code (PostHog, cohort, A/B significance) with minimal explanation of concepts Claude knows, though generic boilerplate sections (When to Use, Best Practices, Common Pitfalls, Limitations) add mild padding that could be trimmed.

4 / 5

Actionability

Provides fully executable, copy-paste-ready Python (PostHog capture/identify, cohort retention, A/B significance with scipy, feature flags) plus concrete slash commands covering the common cases.

5 / 5

Workflow Clarity

The funnel-optimization workflow is a clear numbered sequence with an explicit statistical checkpoint ('p-value < 0.05', '2 semanas minimo') and event-naming rules; minor validation gaps exist in the implementation/setup workflows.

4 / 5

Progressive Disclosure

No bundle files exist; the single-file skill is organized into clearly labeled sections (Eventos, PostHog, Funil, Cohort, North Star, Comandos) with no nested references, giving good structure with minor gaps (some inline reference-like blocks could live separately).

4 / 5

Total

17

/

20

Passed

Description

61%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.

The description names a specific product-analytics niche with good trigger keywords but relies on domain nouns rather than concrete actions and entirely omits an explicit 'when to use' clause. Adding a 'Use when...' trigger sentence and a few action verbs would lift specificity and completeness.

Suggestions

Add an explicit 'Use when...' clause naming concrete triggers (e.g. 'Use when setting up event tracking, building conversion funnels, or defining a North Star metric').

Convert domain nouns into concrete actions (e.g. 'configurar tracking de eventos, criar funis de conversao, calcular retencao por cohort') to raise specificity from naming to action-listing.

Include natural synonyms/extensions users say (eventos, A/B testing, feature flags, .csv export) to push trigger term coverage toward comprehensive.

DimensionReasoningScore

Specificity

Lists concrete tools and domain nouns ('PostHog, Mixpanel, eventos, funnels, cohorts, retencao, north star metric, OKRs e dashboards') but no verbs describing concrete actions taken, so coverage is domain-naming rather than action-listing.

3 / 5

Completeness

The 'what' is clear (lists the analytics domain), but there is no 'Use when...' trigger clause at all, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

Contains many natural terms users say (funnels, cohorts, retencao, dashboards) plus tool names (PostHog, Mixpanel), giving good keyword coverage with only minor synonyms missing.

4 / 5

Distinctiveness Conflict Risk

The product-analytics niche anchored by named tools (PostHog, Mixpanel) is mostly distinct, with only minor overlap risk against related growth/monetization skills.

4 / 5

Total

14

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
sickn33/antigravity-awesome-skills
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.