Estelle van Ravestyn
Back to overview
Section 01 · Podimo ·

Podimo

Research operations · tooling

AI skills, toolkits and repositories

Built a quant/qual insight repository (NotebookLM) and AI-assisted analysis toolkit (GitLab & Claude Code) with transcript analysers and reporting workflows, speeding up project turnaround by 20%.

Role
Established Research Operations for a lean 2-person User Research team
Reviewers
Two-person review
Timeline
Scope
Analysis · delivery · Research Ops
Confidentiality-safe illustration of connected documentation and repository systems for Podimo AI and Research Ops.
AI & Research Ops — a confidentiality-safe representation of the internal knowledge, review and release workflow.
01
Business goals & context

What I built. A shared, version-controlled "app store" for the team's Claude skills — so there's one source of truth, full history, and no more emailing docs around.

[add text] Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.

[add text — NotebookLM] Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur, excepteur sint occaecat cupidatat non proident.

[add text] How do we scale research practice without scaling the team?

Live today5 skills
Of which3 transcript analysers
ReviewersTwo, incl. a research colleague
InstallRepo added once as a plugin
02
The problem

TODO — add copy: the business + user problem, and what you got wrong.

03
My role

TODO — add copy: your scope, influence and what you initiated.

04
Direction

TODO — add copy: the decision you took, before the solution.

05
Impact
0
Skills live today
Including three transcript analysers.
0
Reviewers on every change
Nothing merges without a second pair of eyes.
0
[add text]
Time saved, studies supported, or people onboarded.
06
Approach & rationale

GitLab = where the skills live. Every change goes through a Merge Request that a teammate reviews before it's merged — so there's one source of truth, full history, and no more emailing docs around.

Claude Code = where you use them. The repo is installed once as a plugin, so skills appear automatically and auto-update from GitLab — no local copies to maintain.

Two folders. experimental/ holds drafts; skills/ holds what has been vetted and shipped.

GitLabClaude CodeMerge Request reviewVersioned releasesNotebookLM

One caveat: skills auto-load in Claude Code only — in Cowork, copy the skill text from GitLab and paste it in.

Figure 06
The loop
01
Edit or add a skill
Drafted in experimental/
→
02
Merge Request
Change proposed, not pushed
→
03
Teammate reviews & merges
Second pair of eyes before anything ships
→
04
Bump the version
Released deliberately, not silently
→
05
Everyone picks it up
Claude Code auto-updates from GitLab
Drafts live in experimental/; vetted skills move to skills/. Nothing reaches the team without review.
07
Final solution

[add text] Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua ut enim ad minim veniam.

01
The skills repository
Two folders — experimental drafts and vetted, shipped skills — with full version history and one source of truth.
02
Onboarding guide
Written so a colleague can install the plugin and start using the skills without being walked through it. [add link if the portfolio is public — the current one is internal.]
03
Review process
Two named reviewers on every Merge Request, so quality control is a step in the workflow rather than a habit people have to remember.

[add text] How the team was onboarded, and what adoption looks like now.

08
Outcomes

[add text] Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris.

One source of truth. Skills live in one versioned place with full history, instead of being emailed around as documents.
Auto-updating. The repo is installed once as a plugin, so there are no local copies to maintain and everyone stays in sync.
Review built into the workflow. Every change is proposed as a Merge Request and reviewed before it reaches anyone.
[add text] The measurable effect on analysis time, insight delivery or Research Ops capacity.
09
Reflection

TODO — add copy: what you would do differently.