agentleFS
Nomanriaz786Nomanriaz786/claude-consulting-team/skills/customer-insight-synthesiser/SKILL.md

customer-insight-synthesiser

Skill1 starsChanged 26 days agoMITView on GitHub

Turns qualitative customer evidence into supported insights when teams need patterns, tensions and implications.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use after interviews, observations or open-text research and before developing solutions or propositions.

    line 9

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Customer Insight Synthesiser

When to use it

Use after interviews, observations or open-text research and before developing solutions or propositions.

What Claude needs

  • Transcripts, notes or coded observations
  • Research goals from client-context.md
  • Participant attributes and sampling logic
  • Existing hypotheses or segment definitions

Method

  1. Tag evidence by customer job, trigger, behaviour, barrier, alternative and outcome.
  2. Build an affinity map without forcing data into prior hypotheses.
  3. Compare patterns across participants and relevant segments.
  4. Identify tensions between stated preferences and observed behaviour.
  5. Form insight statements linking evidence, underlying need and business implication.
  6. Record outliers, saturation limits and questions requiring validation.

Output format

Present key insights with evidence references, segment variations, a jobs-and-barriers table, implications and open questions.

Quality checks

  • Insights go beyond restating what participants said
  • Frequency is not confused with importance
  • Minority and contradictory evidence remains visible

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.