Listen Labs agent skills for Claude Code, Cursor and RevampKey

3 ready-made playbooks that teach an AI agent how to do real Listen Labs work: which tools to call, what to check first, and when to stop and ask you.

Download RevampKey, free I have it: connect Listen Labs

Connect Listen Labs once and all 3 skills install themselves and stay up to date. Mac, Windows and Linux.

All 3 Listen Labs skills

Each skill is one job. You ask in plain words and the agent loads the skill that matches, then follows its steps.

Start hereRead-only5 Listen Labs tools

Use Listen Labs safely with AI

Sets the scope before reading or changing studies: confirms the workspace, picks the narrowest read, pages through transcripts, and asks before any change.

Use it when

You have just connected Listen Labs and want to know what the assistant will and will not change.
You are about to summarise or edit studies and want to avoid working in the wrong workspace.
A study read or edit failed with a permission error and you want to understand why.

Tools it uses

list_studies
get_study_analysis
get_study_responses
get_response
search_across_studies

Example

Before you look at anything, confirm which Listen Labs workspace we are in, then tell me which studies have analysis ready.

You are in the Consumer Insights workspace. 12 studies are visible to you, and 5 of them have analysis ready. Nothing has been changed. Do you want me to summarise one of the 5 ready studies?

Use in RevampKeyRead the full skill →

Read-only5 Listen Labs tools

Find a theme across your Listen Labs studies

Searches your Listen Labs studies for a theme or hypothesis, checks the matching transcripts rather than trusting keyword hits, and reports where the evidence agrees, conflicts or is thin. It only reads, and asks before changing anything.

Use it when

You want to know if a pain point has come up in more than one study
You need every past study that touched on a topic before planning new research
You are testing whether a hypothesis holds across several rounds of interviews

Tools it uses

search_across_studies
list_studies
get_study_analysis
get_response
get_study_responses

Example

Across our studies from the last year, do people mention running out of time during onboarding? Show me the strongest evidence and where studies disagree.

Three studies mention onboarding time pressure. In the spring pricing study, 6 of 22 participants raised it unprompted, including one who said they gave up after the second setup screen. The autumn activation study agrees, with 4 unprompted mentions. The winter study mentions it only when the moderator asked, so I've counted it separately. The analysis for the spring study supports the finding; the autumn analysis is still generating.

Use in RevampKeyRead the full skill →

Read-only4 Listen Labs tools

Turn a Listen Labs study into a sourced readout

Reads one study's analysis and interview transcripts, checks each claim against what respondents actually said, and returns findings with verbatim quotes. It separates complete from in-progress interviews and flags anything the analysis overstated.

Use it when

You want the key takeaways from a study you have just finished
The analysis report reads well and you need to confirm it against the interviews
Leadership asks what respondents said about pricing and you need quotes to back it up

Tools it uses

list_studies
get_study_analysis
get_study_responses
get_response

Example

Give me a sourced readout of the Q3 onboarding study. Tell me which findings hold up in the transcripts.

Q3 onboarding study: analysis is ready, and I read 14 complete transcripts out of 18 total (4 still in progress, noted separately). Nine of the 14 said setup took longer than expected, with a quote from each. The analysis claimed most users wanted a template library, but only 3 of the 14 raised it, so I've marked that as unsupported. Two respondents disagreed about the pricing page, which I've listed as contested.

Use in RevampKeyRead the full skill →

Get all 3 without copying a file

RevampKey adds the skills when you connect Listen Labs, updates them for you and removes them when you disconnect.

Download RevampKey

How Listen Labs skills work

Connect Listen Labs
The Listen Labs MCP server gives the agent its tools.
Ask in plain words
“Across our studies from the last year, do people mention running out of time during onboarding? Show me the strongest evidence and where studies disagree.” Each SKILL.md says when it applies, so only the one that fits is loaded.
Approve any change
The agent calls the tools in order, checks its work, and shows you any change before it makes it.

How to install Listen Labs skills

In RevampKey the skills install themselves when you connect Listen Labs. In other tools each skill is one folder with a SKILL.md file, and you also need the Listen Labs MCP server connected there.

About 1 minute · nothing to copy

Download RevampKey for Mac, Windows or Linux and sign in.
Open Connectors and connect Listen Labs. All 3 skills come with it and stay up to date; they go away when you remove the connector.
Ask in plain language, for example “Across our studies from the last year, do people mention running out of time during onboarding? Show me the strongest evidence and where studies disagree.”
Download RevampKeyConnect Listen Labs · 1 click
Get RevampKey to connect Listen Labs
RevampKey is a free desktop app for Mac, Windows and Linux. Install it, sign in, and Listen Labs is one click away with its skills already attached.
Download RevampKey
Not now? Use the skills in your current tool
for s in essentials cross-study-theme-search study-readout-synthesis; do curl -fsSL --create-dirs -o .claude/skills/listen-labs-$s/SKILL.md https://revampkey.com/marketplace/listen-labs/skills/$s/SKILL.md done
Other tools

Into this project’s .claude/skills folder

Connect the Listen Labs MCP server in Claude Code.

Run this in your project folder to add all 3 skills:

for s in essentials cross-study-theme-search study-readout-synthesis; do
  curl -fsSL --create-dirs -o .claude/skills/listen-labs-$s/SKILL.md https://revampkey.com/marketplace/listen-labs/skills/$s/SKILL.md
done

Ask in plain language, for example “Across our studies from the last year, do people mention running out of time during onboarding? Show me the strongest evidence and where studies disagree.”

Into the shared .agents/skills folder

Connect the Listen Labs MCP server in Cursor.

Run this in your project folder to add all 3 skills:

for s in essentials cross-study-theme-search study-readout-synthesis; do
  curl -fsSL --create-dirs -o .agents/skills/listen-labs-$s/SKILL.md https://revampkey.com/marketplace/listen-labs/skills/$s/SKILL.md
done

Ask in plain language, for example “Across our studies from the last year, do people mention running out of time during onboarding? Show me the strongest evidence and where studies disagree.”

Into the shared .agents/skills folder

Connect the Listen Labs MCP server in Codex.

Run this in your project folder to add all 3 skills:

for s in essentials cross-study-theme-search study-readout-synthesis; do
  curl -fsSL --create-dirs -o .agents/skills/listen-labs-$s/SKILL.md https://revampkey.com/marketplace/listen-labs/skills/$s/SKILL.md
done

Ask in plain language, for example “Across our studies from the last year, do people mention running out of time during onboarding? Show me the strongest evidence and where studies disagree.”

Into the shared .agents/skills folder

Connect the Listen Labs MCP server in VS Code.

Run this in your project folder to add all 3 skills:

for s in essentials cross-study-theme-search study-readout-synthesis; do
  curl -fsSL --create-dirs -o .agents/skills/listen-labs-$s/SKILL.md https://revampkey.com/marketplace/listen-labs/skills/$s/SKILL.md
done

Ask in plain language, for example “Across our studies from the last year, do people mention running out of time during onboarding? Show me the strongest evidence and where studies disagree.”

RevampKey or copy the files?

In RevampKey

One click when you connect Listen Labs
Updated for you when a skill improves
Removed when you disconnect
The MCP server is set up for you
800+ other connectors, same way

Download free

Copy into your project

One command per project
Run it again to get updates
You connect the Listen Labs MCP server yourself
Works in Claude Code, Cursor, Codex and VS Code

See the command

Listen Labs skills FAQ

What is a Listen Labs agent skill?

A SKILL.md file: a short playbook an AI agent loads when your request matches it. Each Listen Labs skill describes one job, which Listen Labs tools to use in which order, what to check first and when to stop and ask you.

Do the Listen Labs skills change anything on their own?

3 of the 3 only read. The others tell the agent to show you the change and wait for a yes before it creates, edits or deletes anything in Listen Labs.

Which tools can use these skills?

Any agent that reads the open Agent Skills format: Claude Code, Cursor, Codex, VS Code with Copilot and RevampKey. In RevampKey they are attached when you connect Listen Labs; elsewhere you copy the folders into your project or skills directory.

Do I need the Listen Labs MCP server too?

Yes. The skills tell the agent how to do the work; the Listen Labs MCP server gives it the tools to do it. The Listen Labs MCP setup guide covers every client.

Listen Labs MCP server setup · This page as Markdown

Put Listen Labs’s best workflows in your agent

Download RevampKey, connect Listen Labs and ask your first question in about a minute.

Download RevampKey Connect Listen Labs · 1 click

All 3 Listen Labs skills

Use Listen Labs safely with AI

Use it when

Tools it uses

Find a theme across your Listen Labs studies

Use it when

Tools it uses

Turn a Listen Labs study into a sourced readout

Use it when

Tools it uses

Get all 3 without copying a file

How Listen Labs skills work

How to install Listen Labs skills

RevampKey or copy the files?

In RevampKey

Copy into your project

Listen Labs skills FAQ

Put Listen Labs’s best workflows in your agent

Skills for related tools