New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Meticulous Use Session Data

by FlintSH in FlintSH/Flare

Download and use structured Meticulous session data (user flows + network mocks) for testing code changes locally.

MITAuto-check passedFrontend & Design

Install Meticulous Use Session Data

skills CLI
$ npx skills add FlintSH/Flare --skill meticulous-use-session-data -a claude-code

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

GitHub CLI
$ gh skill install FlintSH/Flare meticulous-use-session-data --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/FlintSH/Flare.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/meticulous-use-session-data .claude/skills/meticulous-use-session-data && 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
meticulous-use-session-data
GitHub stars
135
Token cost
~1.8k tokens
SKILL.md length
571 words
Files
1
Skills in repo
10
Repo updated
First seen
Licence
MIT

At a glance

Download and use structured Meticulous session data (user flows + network mocks) for testing code changes locally.

  • Works in 4 steps: Find relevant sessions and download… → Understand the output structure → Navigate the data → …
  • You need to understand what user interactions and API calls a test covers
  • SKILL.md covers Step 1 — Find relevant…, Step 2 — Understand the output…, Step 3 — Navigate the data and Step 4 — Use the data for…, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Meticulous Use Session Data is an agent skill from FlintSH/Flare. 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.

Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Frontend & Design, covering UX design. The repository describes itself as: A modern, lightning-fast file sharing platform built for self-hosting. Created with support for ShareX, KDE Spectacle, Flameshot, and easy to set up. The licence is MIT.

When your agent uses it

  • You need to understand what user interactions and API calls a test covers
  • You want network mocks for writing tests

Example prompts

  • “/meticulous-use-session-data”

Workflow steps

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

  1. Find relevant sessions and download their data
  2. Understand the output structure
  3. Navigate the data
  4. Use the data for testing

What it can do on your machine

Read from SKILL.md and the folder at commit c910523. 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

    No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).

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

  • Network

    No URLs in SKILL.md.

    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.

Context cost

Meticulous Use Session Data loads about 1.8k tokens when it runs. Until then it costs about 69 tokens; SKILL.md has 571 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~69
When it runs · the whole SKILL.md, loaded when a task matches
~1.8k

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 FlintSH/Flare at commit c910523, republished under its MIT licence (© FlintSH). 571 words, ~1,814 tokens.

Download SKILL.mdSave it as .claude/skills/meticulous-use-session-data/SKILL.md (or your agent's skills folder).
name
meticulous-use-session-data
description
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.
user-invocable
true

Use this workflow to get structured session data from Meticulous — the recorded user flows and network mocks that cover your code changes.

Before starting, run the meticulous-cli-update skill to ensure the Meticulous CLI and skills are up to date — unless it has already run earlier in this conversation, in which case skip it.

Step 1 — Find relevant sessions and download their data

Run the following command from the root of the git repository:

bash
meticulous local relevant-sessions --format=multi-file --minimum-times-to-cover-each-line=1

This will:

  1. Identify which recorded sessions exercise the code paths changed on your current branch.
  2. Download each session's data as a structured directory tree to .meticulous/sessions/.

Options:

OptionTypeDefaultDescription
--formatmulti-file—Set to multi-file to download each relevant session's data as a structured directory tree
--minimum-times-to-cover-each-linenumber—Select at least this many sessions to cover each edited line, choosing the most diverse subset when more candidates are available
--include-superfluous-sessionsbooleanfalseAlso include sessions that do test some changes but were superfluous given --minimum-times-to-cover-each-line
--outputDirstring.meticulous/sessionsOutput directory for multi-file format
--showMaybeRelevantbooleanfalseAlso show sessions that may be affected
--startingPointShastring—Only consider changes since this commit SHA

Step 2 — Understand the output structure

The downloaded data is organized as follows:

.meticulous/sessions/
  manifest.json                       # List of all sessions with summary metadata
  sessions/
    <sanitized-session-id>/           # Special characters in session IDs are replaced for filesystem safety
      summary.json                    # Session overview: URL, viewport, duration, event count
      user-events.json                # Sequence of user interactions (clicks, typing, navigation)
      network-requests/
        summary.json                  # All network requests: method, URL, status (no bodies)
        <order>.json                  # Individual request/response pairs (with bodies)
      storage/
        cookies.json                  # Initial cookie state
        local-storage.json            # Initial localStorage state
        session-storage.json          # Initial sessionStorage (if present)
        indexed-db.json               # Initial IndexedDB (if present)
      url-history.json                # Page navigation history with timestamps
      context.json                    # Feature flags, user ID, custom context (if present)
      websockets/                     # WebSocket data (if present)
        summary.json                  # WebSocket connections overview
        <connection-id>.json          # Events for each connection

Step 3 — Navigate the data

  1. Start with manifest.json to see all available sessions. Each entry includes the session ID, start URL, event count, duration, and network request count. Pick the session(s) relevant to your task.

  2. Read summary.json inside a session directory for a quick overview of that session — the starting URL, viewport size, total duration, and number of events.

  3. Read user-events.json to understand the user flow. Each event has:

    • type: the interaction type (e.g., click, input, scroll)
    • selector: the CSS selector of the target element
    • timestampMs: when the event occurred
    • coordinates: click position (if applicable)

  4. Browse network-requests/summary.json to see all API calls made during the session. Each entry shows the HTTP method, URL, status code, content type, and response time — without response bodies, so it's quick to scan.

  5. Read individual network-requests/<order>.json files for the full request/response data of specific API calls. Use these as mock data when writing tests. The order field in the summary corresponds to the filename.

  6. Check storage/ files if you need to understand the initial application state (cookies, localStorage, etc.).

Show full SKILL.md (190 more words)Show less

Step 4 — Use the data for testing

Common use cases:

Understanding user flows

Read user-events.json to see the exact sequence of user interactions. This tells you what the user clicked, typed, and navigated, which helps you understand what your code change needs to support.

Creating network mocks

Use the network request files to create mock responses for your tests:

  1. Read network-requests/summary.json to find the relevant API endpoints.
  2. Read the individual network-requests/<order>.json files for the full request/response pairs.
  3. Use the response.content.text field as mock response data in your tests.
Verifying coverage

Cross-reference the user events and network requests with your code changes to verify that the session covers the code paths you've modified.

Alternative: Download specific sessions

If you already know which session IDs you need, you can download them directly:

bash
# CLI
meticulous download session --sessionId=<id> --format=multi-file

# MCP (returns the same structured data inline instead of writing it to disk)
get_session_data(sessionId="<id>")

The CLI writes to .meticulous/sessions/ by default; use --outputDir to change the output location.

Final step — Report feedback to Meticulous

Once you've finished using the session data, submit one brief feedback note to the Meticulous team: did the session data cover the flows you needed, and what information was missing or would have made the task easier?

bash
# CLI
meticulous agent submit-feedback --message="<one or two sentences>" --outcome=<helped|neutral|hindered> --skill=meticulous-use-session-data

# MCP
submit_feedback(message="<one or two sentences>", outcome="<helped|neutral|hindered>", skill="meticulous-use-session-data")

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

Files

Just SKILL.md in .agents/skills/meticulous-use-session-data of FlintSH/Flare.

Open the folder on GitHubat commit c910523

Compare with similar skills

Meticulous Use Session Data 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.

Meticulous Use Session Data compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Meticulous Use Session Data this skillFlintSH/Flare135—~1.8kAutomated safety check: PassMIT
Impeccablebestofjs/bestofjs3.1k27 repos~2.6kAutomated safety check: PassMIT
Interface Design for Dashboards and Appsholaboss-ai/holaOS11k3 repos~6kAutomated safety check: PassMIT
Animategrowupanand/ConvoForm1026 repos~1.9kAutomated safety check: PassApache-2.0
Migrate Content Iadocker/docs4.7k—~5.1kAutomated safety check: PassApache-2.0
UX WalkthroughXiaoMi/hiui878—~1.3kAutomated safety check: PassMIT

Similar skills

  • Impeccable

    bestofjs/bestofjs

    A skill your agent uses when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a…

    3.1k GitHub starsUsed in 27 repos~2.6k tokens
    Frontend & DesignAuto-check passed

  • Interface Design for Dashboards and Apps

    holaboss-ai/holaOS

    Pushes an agent past generic defaults when designing dashboards, admin panels, SaaS apps and tools, with attention to structure, type, navigation and how data is shown.

    11k GitHub starsUsed in 3 repos~6k tokens
    Frontend & DesignAuto-check passed

  • Animate

    growupanand/ConvoForm

    Review a feature and enhance it with purposeful animations, micro-interactions, and motion effects that improve usability and delight.

    102 GitHub starsUsed in 6 repos~1.9k tokens
    Frontend & DesignAuto-check passed

  • Migrate Content Ia

    docker/docs

    Official

    Handle Hugo docs information-architecture moves: discover old vs new URLs, add front matter aliases (Phase 1), update in-repo links (Phase 2), interactive List 2 resolution and fragment validation…

    4.7k GitHub stars~5.1k tokensUpdated yesterday
    Frontend & DesignAuto-check passed

  • UX Walkthrough

    XiaoMi/hiui

    体验走查 skill。适用于代码库、URL、截图三种输入，输出结构化体验问题报告，并同步生成本地 docx 报告。触发词：体验走查、UX review、交互走查、界面审查、体验问题。

    878 GitHub stars~1.3k tokensUpdated 2 mo ago
    Frontend & DesignAuto-check passed

  • Color Audit

    rome-os/rome

    Audit a design system's color palette against measurable color-science disciplines — WCAG/APCA contrast of declared token pairs, perceptual (OKLCH) ramp uniformity, color-blindness safety of…

    737 GitHub stars~2.7k tokensUpdated today
    Frontend & DesignAuto-check passed

More from FlintSH/Flare

All 10 skills in this repo

  • Meticulous CLI

    FlintSH/Flare

    Overview of the Meticulous CLI tool and its global options. An agent skill from FlintSH/Flare.

    135 GitHub stars~1.4k tokensUpdated 3 days ago
    Auto-check passed

  • Meticulous Fix

    FlintSH/Flare

    Fix the visual diffs that have been reviewed and rejected on a Meticulous test run, following their review comments if given.

    135 GitHub stars~2.3k tokensUpdated 3 days ago
    Auto-check passed

  • Meticulous Increase Coverage

    FlintSH/Flare

    Increase coverage for a Meticulous project by tracing specific under-covered files back to a real UI action in the codebase, driving that action with a real recorded browser session, and validating…

    135 GitHub stars~7k tokensUpdated 3 days ago
    Auto-check passed

  • Meticulous Iterative Dev

    FlintSH/Flare

    Iterative frontend development loop using Meticulous for per-step visual validation.

    135 GitHub stars~1.3k tokensUpdated 3 days ago
    Auto-check passed

  • Meticulous Review

    FlintSH/Flare

    Analyze a completed Meticulous test run — compare the diffs against the PR description to see what's expected, then focus on finding and flagging potential regressions.

    135 GitHub stars~2.3k tokensUpdated 3 days ago
    Auto-check passed

  • Meticulous Simulate And Diff

    FlintSH/Flare

    Run a Meticulous session simulation against a live URL and analyze the visual output — either by inspecting screenshots directly (quick-check mode) or by comparing pixel and HTML diffs against a…

    135 GitHub stars~1.8k tokensUpdated 3 days ago
    Auto-check passed

Categories

Questions about Meticulous Use Session Data

What does Meticulous Use Session Data do?

Download and use structured Meticulous session data (user flows + network mocks) for testing code changes locally. Meticulous Use Session Data is an agent skill from FlintSH/Flare. Download and use structured Meticulous session data (user flows + network mocks) for testing code changes locally.

When should I use Meticulous Use Session Data?

Meticulous Use Session Data fits situations like: you need to understand what user interactions and API calls a test covers; you want network mocks for writing tests.

How do I install Meticulous Use Session Data in Claude Code?

Run `npx skills add FlintSH/Flare --skill meticulous-use-session-data -a claude-code`. Or copy the skill folder (.agents/skills/meticulous-use-session-data in FlintSH/Flare) into .claude/skills/meticulous-use-session-data in your project. Claude Code loads it when a task matches its description.

How do I install Meticulous Use Session Data in Codex?

Run `npx skills add FlintSH/Flare --skill meticulous-use-session-data -a codex`. Or copy the skill folder (.agents/skills/meticulous-use-session-data in FlintSH/Flare) into .agents/skills/meticulous-use-session-data in your project. Codex loads it when a task matches its description.

Can I use Meticulous Use Session Data 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 FlintSH/Flare --skill meticulous-use-session-data -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/meticulous-use-session-data, .gemini/skills/meticulous-use-session-data, .github/skills/meticulous-use-session-data and .opencode/skills/meticulous-use-session-data in your project.

What does Meticulous Use Session Data need to run?

SKILL.md names no scripts, command-line tools or credentials: Meticulous Use Session Data is instructions for the agent only.

Does Meticulous Use Session Data access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Meticulous Use Session Data 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 Meticulous Use Session Data use?

Meticulous Use Session Data is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Meticulous Use Session Data use?

About 1.8k tokens (SKILL.md is roughly 7.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Meticulous Use Session Data?

Skills that share tags, products or a category with Meticulous Use Session Data: Impeccable (bestofjs/bestofjs, 3.1k stars), Interface Design for Dashboards and Apps (holaboss-ai/holaOS, 11k stars), Animate (growupanand/ConvoForm, 102 stars) and Migrate Content Ia (docker/docs, 4.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Meticulous Use Session Data?

FlintSH (a GitHub user) maintains it in FlintSH/Flare, which has 135 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on October 6, 2026.

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