- name
SKILL.md
스킬 파일은 게시자의 저장소에 그대로 있습니다.
복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add retentioneering/retentioneering-tools --skill retentioneering-product-analytics -a cursor -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add retentioneering/retentioneering-tools --skill retentioneering-product-analytics -a claude-code -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add retentioneering/retentioneering-tools --skill retentioneering-product-analytics -a codex -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add retentioneering/retentioneering-tools --skill retentioneering-product-analytics -a grok -y복사한 메시지를 Grok Bot 채팅에 보냅니다. Bot이 GitHub에서 이 SKILL.md를 가져와 모든 Bot이 공유하는 스킬에 추가합니다.
Install this skill: https://github.com/retentioneering/retentioneering-tools/tree/HEAD/.agents/skills/retentioneering-product-analytics게시자 제공
Turn event-level behavioral data into a reproducible answer to a product question — why users convert, churn, loop, or abandon — using user trajectories, transitions, funnels, and behavioral segments.
Do not merely generate visualizations. Connect each output to the question, separate observation from interpretation, and never present path correlations as causal effects.
Minimum: a path identifier (user or session), an event name, a timestamp (or a reliable order column — see gotcha G2 for order-only data). Useful extras: session id, segment attributes (device, source, plan), event properties, conversion labels.
python -c "import retentioneering; print(retentioneering.__version__)".
Expect 5.x; this skill's API map is version-verified for 5.0 — on a different major
version, trust installed docstrings over the map.references/api-map.md must be verified
against the installed package before use.Run scripts/inspect_event_log.py <path> [--sep ...] (or replicate its checks inline for
in-memory frames). It profiles columns, infers the user/event/timestamp mapping, checks
timestamp parseability, duplicates, per-path ordering, path-length distribution, and
emits artifacts/data-profile.json plus a ready-to-paste Eventstream(...) schema.
Report to the user before proceeding: inferred mapping, row/user/event-type counts, covered period, and any red flags (nulls in key columns, timestamp ties, suspected bots or ultra-long paths, order-only timestamps). Confirm the mapping if inference is ambiguous.
Map the question to a recipe in references/analysis-recipes.md:
navigation structure/loops → transition graph (R1/R6) · before/after an anchor →
step matrix (R3) · ordered conversion flow → funnel (R1/R2) · what winners do
differently → diff on a funnel-stage segment (R2) · heterogeneous users → clustering
without target leakage (R5) · between two funnel levels → truncate micro-journey (R4) ·
intervention timing → time-to-outcome (R7) · cross-segment scan → segment overview (R8) ·
value of a fix → Markov what-if (R9, advanced).
Combine recipes only when each addition resolves a distinct uncertainty.
artifacts/ by default).sample_paths(frac=, random_state=) for stable subsamples; stochastic steps get
explicit seeds.processed.recipe() and the package version into
artifacts/run-metadata.json — any artifact must be regenerable from raw data via
Eventstream.from_recipe(raw_df, recipe).Work through references/gotchas-and-validation.md section B. Non-negotiables:
every percentage names its denominator; population filters are disclosed with counts;
survivorship and exposure confounds addressed; no outcome leakage into features;
small cells flagged with n; caption numbers come from headless *_data twins;
visuals agree with tables.
Structure the final answer as:
Deliverables: analysis script or executed notebook; artifacts/data-profile.json;
artifacts/metrics.csv (key tables); interactive HTML exports via
widget.export_html(..., title=, analysis=) — write analysis= captions AFTER
conclusions are final; artifacts/summary.md (mapping, filters, assumptions, versions,
findings, limitations, next steps); artifacts/run-metadata.json (versions, parameters,
seeds, recipe() lineage).
>
---name: retentioneering-product-analyticsdescription: >---# .agents/skills/retentioneering-product-analytics/SKILL.mdFAQ
게시자에게서 .agents/skills/retentioneering-product-analytics/SKILL.md를 다운로드하거나 경로를 복사해 저장소를 엽니다. PlugMCP는 스킬을 목록에 올릴 뿐 파일을 호스팅하지 않습니다.
게시자가 https://github.com/retentioneering/retentioneering-tools에서 관리합니다.
Claude, Cursor, Codex, Grok Build는 게시자의 저장소에서 추가한 SKILL.md를 읽을 수 있습니다. Grok Bot은 채팅에서 스킬의 GitHub 폴더 링크를 보내면 설치합니다.