client-intake-profile-check

Files (2)

• SKILL.md
• client-profile-template-fr.md · templates/

SKILL.md (first lines)

# Client Intake Profile Check

Use this skill when the user gives raw client information and wants a first structured output before research, solution design, or commercial proposal work.

The input can be:
- messy notes
- WhatsApp exports
- meeting notes
- questionnaire answers
- voice transcript summaries
- copied website text
- mixed facts collected over time

## Goal

Transform raw input into:
1. a **harmonized client profile**
2. a **completeness diagnosis**
3. a clear decision on whether we can continue toward research / solution design / proposal drafting

This skill exists to avoid starting from vague information and producing low-quality proposals.

## Core principle

Do **not** jump to solution design too early.
First create a reliable client profile.
Then check whether the mandatory information is present.
Only after that should the agent continue toward research, automation ideas, website ideas, AI agents, bots, or proposal drafting.

## What this skill must produce

The deliverable must always contain:
- a normalized client profile
- mandatory information already known
- mandatory information missing
- useful but non-blocking missing information
- optional information
- explicit assumptions if any
- a verdict:
  - **READY**
  - **READY WITH ASSUMPTIONS**
  - **BLOCKED**
- a recommended next action
- if information is missing: a **minimal question set** to ask the client
- a clear note that the **human decides** whether to:
  - continue immediately
  - ask the missing questions first

## Universal mandatory information

These are the minimum information blocks required across almost any domain.
If one of these blocks is too weak or absent, the skill should mark it clearly.

### 1. Activity identity
Mandatory:
- company / project name if known
- main activity
- main offer / what they actually sell
- target market or geographic context if known

### 2. Target customer
Mandatory:
- who they sell to
- B2B / B2C / mixed if known
- main customer segment

### 3. Main business objective
Mandatory:
- what they want to improve now
- top priority if identifiable

Examples:
- get more leads
- increase bookings
- reduce admin time
- improve follow-up
- improve customer support
- structure operations

### 4. Current way of operating
Mandatory:
- how requests arrive today
- how work is processed today
- which people/roles are involved if known
- tools/channels already used if known

### 5. Current frictions
Mandatory:
- key problems
- major bottlenecks
- major manual pain points
- lost opportunities / slow response / errors if identified

### 6. Expected scope or improvement area
Mandatory:
- what the client asked for or seems to want
- which area is in scope now
- whether this is a new setup or an improvement of existing tools if known

### 7. Constraints
Mandatory when known, otherwise strongly flag as missing if they are likely critical:
- budget level or ambition level
- timing / urgency
- channel constraints
- language constraints
- human constraints (small team, low technical maturity, need human validation, etc.)

## Useful information (good to know, but not always blocking)

- existing website / social presence
- current CRM / spreadsheet / booking tools
- service list details
- pricing model
- volume estimates
- team size
- brand positioning
- competitor references
- internal approval process
- preferred communication channels

From bmoby/team-hermes-skills, MIT.

More from bmoby/team-hermes-skills