Meticulous Session Data Skill: What It Does and How to Install It
Makes your agent download recorded Meticulous user sessions for your changes, so it can read the flows and reuse network mocks.
- Installs
- 8.7K
- on skills.sh
- Stars
- 10
- on GitHub
- Updated
- Oct 2026
- last repo commit
meticulous-use-session-data makes your agent run meticulous local relevant-sessions with --format=multi-file. That downloads each relevant recorded session into .meticulous/sessions/ as a folder of user events, network requests, storage state and URL history.
The agent then reads the manifest and per-session files to understand what users do, copies response bodies into test mocks, and checks that sessions cover the changed code. It needs the meticulous command-line tool, a signed-in Meticulous project and a git repo. It begins by running meticulous-cli-update.
Good for
- Developers writing tests who want real API responses as mocks
- Developers checking which user flows a change affects
- Teams already recording sessions with Meticulous
Install meticulous-use-session-data
Claude Code
- 1
Copy this prompt.
Install the meticulous-use-session-data skill in Claude Code. Run this command: /plugin marketplace add alwaysmeticulous/skills /plugin install meticulous@meticulous Then check that it loaded and tell me how to use it.
- 2
Paste it into Claude Code. It shows the change and asks before running it.
meticulous-use-session-data starts by running meticulous-cli-update, and the README installs the whole set of skills (the repo has 11). Full setup: app.meticulous.ai/docs/agents/setup. Plugin skills are named /meticulous:<skill-name>. After the plugin install, type /mcp and choose Authenticate for the Meticulous server. Choose one route; the skills CLI command targets Claude Code, Codex and Cursor together.
From the project README. Source.
What's in the skill
When it loads
Download and use structured Meticulous session data (user flows + network mocks) for testing code changes locally. Use when you need to understand what user interactions and API calls a test covers, or when you want network mocks for writing tests.
Sections in SKILL.md
- Step 1 — Find relevant sessions and download their data
- Step 2 — Understand the output structure
- Step 3 — Navigate the data
- Step 4 — Use the data for testing
- Understanding user flows
- Creating network mocks
- Verifying coverage
- Alternative: Download specific sessions
- Final step — Report feedback to Meticulous
Key facts
- Installs on skills.sh
- 8,652 (Nov 2, 2026)
- GitHub stars (repo)
- 10 (Nov 2, 2026)
- Last commit (repo)
- Oct 29, 2026
- What installs
- 1 file: SKILL.md. The repo holds 11 skills in all; this one starts by running meticulous-cli-update
- Also needs these skills
- meticulous-cli-update
What it includes
Runs the CLI and skills update check unless it already ran in this conversation.
Installs or updates software; see the safety section.
Runs code ·
meticulous-cli-update (first)Finds sessions covering your branch changes and downloads each as a folder.
Run from the repo root. Writes to .meticulous/sessions/ by default; --outputDir changes that. --minimum-times-to-cover-each-line picks a diverse subset.
Runs code ·
meticulous local relevant-sessions --format=multi-fileReads manifest.json, then summary.json, user-events.json and network-requests per session.
Also url-history.json, context.json and storage files for cookies, localStorage, sessionStorage and IndexedDB.
Files ·
Read the session foldersReads user flows, builds network mocks from response bodies, and checks coverage.
Mock data comes from the response.content.text field of each network-requests file.
Read ·
Use the data for testsDownloads one session you already know the ID of.
The MCP equivalent is get_session_data, which returns the data inline instead of writing to disk.
Write ·
meticulous download session --sessionId=<id> --format=multi-fileSends Meticulous one short note on whether the data was enough.
Uses --outcome helped, neutral or hindered and --skill=meticulous-use-session-data.
Network ·
meticulous agent submit-feedback
From the official docs
Permissions
Medium risk
This skill writes recorded session data, including cookies and API responses, into your repo. Keep that folder out of version control.
What it can do
- Read your data
- Create and change things
- Delete things
- Read-only mode
Watch out for
Downloaded sessions include cookies and API responses
SKILL.md lists cookie, localStorage and sessionStorage files and full request and response bodies in each session folder. Our advice: keep .meticulous/ out of version control and check it before sharing the repo. github.com
It installs or updates software for you
Every Meticulous skill starts with meticulous-cli-update, which can run npm install --global @alwaysmeticulous/cli@latest, npx skills add alwaysmeticulous/skills with -y, and plugin updates. SKILL.md says to recommend the command instead if you decline a permission prompt. github.com
It sends a feedback note to Meticulous
The skill ends with meticulous agent submit-feedback (or the MCP submit_feedback) carrying a one or two sentence message, an outcome and the skill name. Tell your agent to skip it if you prefer. github.com
The plugin route connects a hosted MCP server
The plugin bundles an .mcp.json for https://app.meticulous.ai/api/mcp and no hooks or agents appear in the repo tree. You sign in from /mcp in Claude Code. github.com
Technical details
| Talks to | app.meticulous.ai |
|---|---|
| Sign-in and keys | Browser sign-in with meticulous auth login stores a token; METICULOUS_API_TOKEN or ~/.meticulous/config.json also work. |
| Scopes |
|
Questions
How do I install meticulous-use-session-data?
Use the install box at the top of this page. The README installs the whole set of Meticulous skills, because the skill starts with meticulous-cli-update and the README installs the full set. You also need the meticulous command-line tool and a sign-in, which the README gives as npm install --global @alwaysmeticulous/cli@latest then meticulous auth login.
Does meticulous-use-session-data work in the Claude app?
Not as a Claude app skill. It runs the meticulous command-line tool and works with your git repo, so use Claude Code, Codex or Cursor, which the README names. The plugin route also connects a hosted Meticulous MCP server.
Do I need a Meticulous account?
Yes. The skills use the Meticulous CLI or MCP server, and sign-in happens in your browser through meticulous auth login. An API token set in METICULOUS_API_TOKEN also works, according to the skills' update instructions. What Meticulous itself costs is not stated in the repo.
Is meticulous-use-session-data safe to use?
It runs commands and talks to Meticulous, so read what your agent proposes. It writes recorded cookies, storage and API responses into .meticulous/sessions/ in your repo. Every Meticulous skill also starts with an update check that can install packages, and it ends with a feedback note sent to Meticulous. See the safety section for details.
Is it official?
Yes. It is in Meticulous's own repo (alwaysmeticulous/skills), and the plugin manifest names Meticulous as the owner.
Where is the data stored?
In .meticulous/sessions/ inside your repo by default, with a manifest.json and one folder per session. Use --outputDir to put it elsewhere.
Information
updated Nov 2, 2026
- Repository
- alwaysmeticulous/skills
- Folder
skills/meticulous-use-session-data
Sources
Docs, issue trackers and discussions this page is built from.
Show all 6Hide
- alwaysmeticulous/skills README · github.com
- Meticulous agent setup docs · app.meticulous.ai
- meticulous-use-session-data SKILL.md · github.com
- meticulous-cli-update SKILL.md · github.com
- marketplace.json · github.com
- plugin.json · github.com