Agent skill

Retentioneering Contributing

by retentioneering in retentioneering/retentioneering-tools

Help the user turn their Retentioneering ideas, friction reports, bug findings, or feature needs into high-quality upstream contributions: from capturing and validating the idea, through minimal…

Apache-2.0Auto-check passedData & Analytics

Install Retentioneering Contributing

skills CLI
$ npx skills add retentioneering/retentioneering-tools --skill retentioneering-contributing -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install retentioneering/retentioneering-tools retentioneering-contributing --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/retentioneering/retentioneering-tools.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/retentioneering-contributing .claude/skills/retentioneering-contributing && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
retentioneering-contributing
GitHub stars
925
Token cost
~1.8k tokens
SKILL.md length
742 words
Files
3 (incl. references)
Skills in repo
2
Repo updated
First seen
Licence
Apache-2.0

At a glance

Help the user turn their Retentioneering ideas, friction reports, bug findings, or feature needs into high-quality upstream contributions: from capturing and validating the idea, through minimal…

  • Works in 7 steps: Capture the observation properly (do… → Validate against the CURRENT version → Minimal reproduction (the heart of a bug… → …
  • The user says they found a bug
  • SKILL.md covers Objective, Bundled references, The full route: idea → merged PR and Portfolio mode: many…
  • Calls uv, git and gh

What it does

Retentioneering Contributing is an agent skill from retentioneering/retentioneering-tools. Help the user turn their Retentioneering ideas, friction reports, bug findings, or feature needs into high-quality upstream contributions: from capturing and validating the idea, through minimal reproductions and issue drafts, to preparing, testing, and submitting a pull request that follows this repository's conventions. Use when the user says they found a bug, wants a feature, wrote a workaround worth upstreaming, or asks how to contribute, open an issue, or make a PR to retentioneering-tools.

Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/proposal-templates.md` and `references/repo-conventions.md`). Compatibility notes: Requires a git checkout of retentioneering-tools, Python = 3.10 with uv, and Node.js only when JS/widget code is touched. The gh CLI is optional but…

It sits in Data & Analytics, covering Customer journey mapping, Pull requests and UX design. It works with Python and Model Context Protocol. The repository describes itself as: Python toolkit, MCP server, and agent skills for reproducible, auditable clickstream and event log analytics. Helps AI agents, data scientists and analysts build, validate, and…. The licence is Apache-2.0.

When your agent uses it

  • The user says they found a bug
  • Wants a feature
  • Wrote a workaround worth upstreaming
  • Asks how to contribute

Example prompts

  • “/retentioneering-contributing”

Requirements

  • Python 3
  • Node.js
  • Compatibility (from SKILL.md): Requires a git checkout of retentioneering-tools, Python >= 3.10 with uv, and Node.js only when JS/widget code is touched. The gh CLI is optional but recommended for PR submission.

Workflow steps

7 steps, taken from the step headings in SKILL.md.

  1. Capture the observation properly (do this even for "small" ideas)
  2. Validate against the CURRENT version
  3. Minimal reproduction (the heart of a bug report)
  4. Choose the contribution shape
  5. Implement (when making a PR, not just an issue)
  6. Pre-flight and submit
  7. Follow through

What it can do on your machine

Read from SKILL.md and the folder at commit fda32f2. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • uv
    • git
    • gh
    • make
    • npm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use uv, git, gh and npm, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Requires a git checkout of retentioneering-tools, Python >= 3.10 with uv, and Node.js only when JS/widget code is touched. The gh CLI is optional but recommended for PR submission.

    From compatibility in the SKILL.md frontmatter.

Context cost

Retentioneering Contributing loads about 1.8k tokens when it runs, and up to ~4k if it reads all its reference files. Until then it costs about 132 tokens; SKILL.md has 742 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~132
When it runs · the whole SKILL.md, loaded when a task matches
~1.8k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from retentioneering/retentioneering-tools at commit fda32f2, republished under its Apache-2.0 licence (© retentioneering). 742 words, ~1,841 tokens.

Download SKILL.mdSave it as .claude/skills/retentioneering-contributing/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
retentioneering-contributing
description
Help the user turn their Retentioneering ideas, friction reports, bug findings, or feature needs into high-quality upstream contributions: from capturing and validating the idea, through minimal reproductions and issue drafts, to preparing, testing, and submitting a pull request that follows this repository's conventions. Use when the user says they found a bug, wants a feature, wrote a workaround worth upstreaming, or asks how to contribute, open an issue, or make a PR to retentioneering-tools.
compatibility
Requires a git checkout of retentioneering-tools, Python >= 3.10 with uv, and Node.js only when JS/widget code is touched. The gh CLI is optional but recommended for PR submission.
license
Apache-2.0
metadata.author
retentioneering
metadata.version
1.0.0
metadata.package
retentioneering
metadata.category
developer-tools
metadata.keywords
open source contribution, pull request, bug report, issue template, minimal reproduction, code review, oss workflow, github, retentioneering
metadata.homepage
https://retentioneering.com
metadata.documentation
https://retentioneering.com/docs
metadata.repository
https://github.com/retentioneering/retentioneering-tools

Contributing to retentioneering-tools

Objective

Convert a user's observation — a bug, a paper cut, a missing capability, a workaround they keep re-writing — into the smallest upstream change that would have prevented it, packaged so maintainers can accept it quickly.

Bundled references

FileRead it when
references/repo-conventions.mdbefore touching code — build/test/docs commands, architecture rules, naming, sync obligations
references/proposal-templates.mdwhen drafting — issue/feature/PR templates with worked examples

The full route: idea → merged PR

Stage 1 — Capture the observation properly (do this even for "small" ideas)

Record four things while they are fresh:

  1. Expectation — what the user believed would happen (quote the docstring/docs page that created the expectation, if any).
  2. Reality — what actually happened (exact error text or wrong output).
  3. Cost — time lost, wrong conclusion nearly shipped, workaround written.
  4. Environment — retentioneering.__version__, Python, OS, install source (pip wheel vs source checkout).

Field lesson: reports formatted as expectation/reality/cost/repro get acted on; "X is broken" reports stall.

Stage 2 — Validate against the CURRENT version

Many pain points are already fixed on v5-migration — verify before drafting:

  1. git log --oneline -30 and CHANGELOG.md — search keywords from the observation.
  2. Search existing issues/PRs: gh issue list --search "<keywords>", gh pr list ....
  3. Reproduce on the current checkout (see Stage 3). If it no longer reproduces, the contribution may become a docs clarification or a regression test instead — both welcome.
Stage 3 — Minimal reproduction (the heart of a bug report)

Build the smallest toy that shows the gap, e.g.:

python
import pandas as pd
from retentioneering import Eventstream
df = pd.DataFrame({"user_id": ["u1","u1","u2"], "event": ["a","b","a"],
                   "timestamp": pd.date_range("2026-01-01", periods=3, freq="1min")})
# EXPECTED: ...       ACTUAL: ...

Rules: synthetic data only (never the user's real log); deterministic (fixed frames, no randomness without seed); one behavior per repro; assert the expectation so the repro doubles as a failing test.

Stage 4 — Choose the contribution shape
SituationShape
Clear defect with reproIssue with repro; PR with fix + regression test if user wants to go further
Surprising-but-documented behaviorDocs PR (docstring is the source of truth — site pages regenerate from it)
Missing capabilityFeature issue: use-case first, proposed signature second, evidence third (see templates)
Repeated workaround in user's codeExtract as proposed API: show the workaround, its cost, the proposed call replacing it
Wrong-conclusion trap (library was silent)Frame as "missing signal": what the library knew and did not surface; propose the warning/field

For API proposals, the accepted framing (from templates): problem → evidence of frequency → proposed signature → semantics incl. edge cases → acceptance criteria → migration notes.

Show full SKILL.md (354 more words)Show less
Stage 5 — Implement (when making a PR, not just an issue)

Read references/repo-conventions.md first. Non-negotiables:

  1. Fork or branch from master-tracking v5-migration; one logical change per PR.
  2. make install-dev — installs deps (uv sync + npm install) and wires the git hook (a one-time-per-clone step) so commits are auto-checked; skip it and commits bypass the hooks locally and CI's lint job flags the formatting on your PR. Add make build only when touching widgets/JS.
  3. Follow naming conventions (ADR-0008): path_col/event_col/timestamp_col/session_col, start_anchor/end_anchor, verb-first processors, noun widgets, <widget>_data twins.
  4. All DuckDB execution goes through the unified query engine (L1) — no ad-hoc duckdb.sql with replacement-scan idioms (superseded ADR-0002).
  5. Add/extend tests next to the code area (tests/...); a bug fix MUST include the failing-before test from Stage 3.
  6. Keep the loud-and-helpful error pattern: errors that list valid values/keys are the house style; silent degradation (dropped rows, empty results without a signal) is an auto-reject.
  7. Sync obligations when renaming/changing API: MCP tool layer mirrors Eventstream method names; JS metric editor consumes the Python metric schema; docstrings feed the docs site — update all in the same PR (uv run python docs/scripts/render_pages.py).
Stage 6 — Pre-flight and submit
bash
uv run pre-commit run --all-files      # ruff lint+format, gitleaks, hygiene
uv run pytest tests/ -v                # full suite (CI runs 3.10–3.13)
uv run python docs/scripts/render_pages.py   # if docstrings changed

Commit style: imperative, scoped, explaining WHY when non-obvious (see git log for the house voice). Update CHANGELOG.md under the unreleased/current section for user-visible changes.

Submit:

bash
git push -u origin <branch>
gh pr create --title "<imperative summary>" --body-file pr_body.md

PR body (template in references/proposal-templates.md): what & why → linked issue → repro/before-after → tests added → sync checklist (docs/MCP/JS if applicable) → breaking-change note. CI must pass: lint + test (3.11/3.12/3.13). master is PR-only; merging does not release (releases are tag-driven by maintainers).

Stage 7 — Follow through

Respond to review within the PR (avoid force-push after review starts; append commits). If maintainers ask for direction changes, update the issue first, then the code — the issue is the contract.

Portfolio mode: many observations at once

When the user accumulated a batch (e.g., a journal of friction from a project): deduplicate → verify each against current version (Stage 2) → rank by (frequency × silent-failure risk) → file the top 3–5 as separate issues with repros → offer one PR for the cheapest verified fix to build credibility, referencing the issues for the rest. Do not open one mega-issue.

© retentioneering, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (references) in .agents/skills/retentioneering-contributing of retentioneering/retentioneering-tools.

  • SKILL.md
  • references/proposal-templates.md
  • references/repo-conventions.md

Open the folder on GitHubat commit fda32f2

Compare with similar skills

Retentioneering Contributing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Retentioneering Contributing compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Retentioneering Contributing this skillretentioneering/retentioneering-tools925—~1.8kAutomated safety check: PassApache-2.0
Instrument PRamplitude/builder-skills160—~2.9kAutomated safety check: PassNone
Funnel Analysisliangdabiao/claude-data-analysis-ultra-main2901 repos~781Automated safety check: NotesNone
Open PRArcadeAI/arcade-mcp1k—~2.9kAutomated safety check: PassMIT
Fast Dashdkedar7/fast_dash129—~1.9kAutomated safety check: PassMIT
Fix IssuePrefectHQ/fastmcp28k—~842Automated safety check: PassApache-2.0

Similar skills

  • Instrument PR

    amplitude/builder-skills

    Instruments a pull request with Amplitude analytics that conform to the project's existing taxonomy.

    160 GitHub stars~2.9k tokensUpdated 2 mo ago
    Data & AnalyticsAuto-check passed
  • Funnel Analysis

    liangdabiao/claude-data-analysis-ultra-main

    Analyze user conversion funnels, calculate step-by-step conversion rates, create interactive visualizations, and identify optimization opportunities.

    290 GitHub starsUsed in 1 repo~781 tokens
    Data & AnalyticsAuto-check: notes
  • Open PR

    ArcadeAI/arcade-mcp

    Prepare arcade-mcp changes for review by verifying intended behavior, filling the repository PR template, and creating or updating the PR.

    1k GitHub stars~2.9k tokensUpdated yesterday
    Agent WorkflowsAuto-check passed
  • Fast Dash

    dkedar7/fast_dash

    Build a Fast Dash web app from a Python function. An agent skill from dkedar7/fast_dash.

    129 GitHub stars~1.9k tokensUpdated 5 days ago
    Data & AnalyticsAuto-check passed
  • Fix Issue

    PrefectHQ/fastmcp

    Carry a selected FastMCP bug from reproduction through a scoped fix, compatibility review, validation, and a monitored pull request.

    28k GitHub stars~842 tokensUpdated today
    DevelopmentAuto-check passed
  • Code Review

    oaslananka/kicad-mcp-pro

    A skill your agent uses for GitHub Copilot pull request and code reviews in oaslananka/kicad-mcp-pro.

    120 GitHub stars~3.9k tokensUpdated today
    DevelopmentAuto-check passed

More from retentioneering/retentioneering-tools

  • Retentioneering Product Analytics

    retentioneering/retentioneering-tools

    Analyze event logs, clickstreams, user paths, product funnels, retention, behavioral segments, transition graphs, step matrices, sequence patterns, and customer journeys using Retentioneering.

    925 GitHub stars~1.6k tokensUpdated 2 days ago
    Auto-check passed

Questions about Retentioneering Contributing

What does Retentioneering Contributing do?

Help the user turn their Retentioneering ideas, friction reports, bug findings, or feature needs into high-quality upstream contributions: from capturing and validating the idea, through minimal…. Retentioneering Contributing is an agent skill from retentioneering/retentioneering-tools. Help the user turn their Retentioneering ideas, friction reports, bug findings, or feature needs into high-quality upstream contributions: from capturing and validating the idea, through minimal reproductions and issue drafts, to preparing, testing, and submitting a pull request that follows this repository's conventions.

When should I use Retentioneering Contributing?

Retentioneering Contributing fits situations like: the user says they found a bug; wants a feature; wrote a workaround worth upstreaming; asks how to contribute.

How do I install Retentioneering Contributing in Claude Code?

Run `npx skills add retentioneering/retentioneering-tools --skill retentioneering-contributing -a claude-code`. Or copy the skill folder (.agents/skills/retentioneering-contributing in retentioneering/retentioneering-tools) into .claude/skills/retentioneering-contributing in your project. Claude Code loads it when a task matches its description.

How do I install Retentioneering Contributing in Codex?

Run `npx skills add retentioneering/retentioneering-tools --skill retentioneering-contributing -a codex`. Or copy the skill folder (.agents/skills/retentioneering-contributing in retentioneering/retentioneering-tools) into .agents/skills/retentioneering-contributing in your project. Codex loads it when a task matches its description.

Can I use Retentioneering Contributing in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add retentioneering/retentioneering-tools --skill retentioneering-contributing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/retentioneering-contributing, .gemini/skills/retentioneering-contributing, .github/skills/retentioneering-contributing and .opencode/skills/retentioneering-contributing in your project.

What does Retentioneering Contributing need to run?

Going by SKILL.md and its folder, Retentioneering Contributing needs the command-line tools its instructions call (uv, git, gh, make and npm). Our summary lists: Python 3; Node.js. Compatibility (from SKILL.md): Requires a git checkout of retentioneering-tools, Python >= 3.10 with uv, and Node.js only when JS/widget code is touched. The gh CLI is optional but recommended for PR submission. .

Does Retentioneering Contributing access the network?

SKILL.md contains no URLs. Its commands use uv, git, gh and npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Retentioneering Contributing safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Retentioneering Contributing use?

Retentioneering Contributing is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Retentioneering Contributing use?

About 1.8k tokens (SKILL.md is roughly 7.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.2k tokens, read only when the agent opens those files.

What are the alternatives to Retentioneering Contributing?

Skills that share tags, products or a category with Retentioneering Contributing: Instrument PR (amplitude/builder-skills, 160 stars), Funnel Analysis (liangdabiao/claude-data-analysis-ultra-main, 290 stars), Open PR (ArcadeAI/arcade-mcp, 1k stars) and Fast Dash (dkedar7/fast_dash, 129 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Retentioneering Contributing?

retentioneering (a GitHub organization) maintains it in retentioneering/retentioneering-tools, which has 925 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 7, 2026.

Source: retentioneering/retentioneering-tools on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.