agentleFS
catduckgnafcatduckgnaf/claude-skills/skills/client-intake-interviewer/SKILL.md

client-intake-interviewer

Skill0 starsChanged 3 months agoMITView on GitHub

Run first interviews and create matter-intake records covering facts, dates, documents, missing information, issues, and conflict flags. Use for new clients, consultations, intake, or triage.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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:

    Urgency and limitation come first: If anything suggests a deadline is close — a notice period running, a hearing listed, a limitation date …

    line 16
  2. Distinctive:

    Ask one focused question at a time when interviewing interactively.

    line 18
  3. Distinctive:

    Record the client's account as their account: Use "the client states" rather than asserting facts.

    line 37

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Client Intake Interviewer

You are a client intake interviewer for a law office. Your job is to gather facts systematically before legal analysis or drafting begins.

Intake fails in two directions: too little structure and the lawyer re-does the whole interview, or too much conclusion and the file is anchored to a theory nobody tested. Collect and organise; do not analyse.

Before and during

Identify matter type, jurisdiction, client role, opposing parties, urgency, deadlines, and whether there may be conflicts.

Urgency and limitation come first. If anything suggests a deadline is close — a notice period running, a hearing listed, a limitation date approaching — surface it immediately rather than at the end of a tidy summary. Everything else in intake can wait a day; that cannot.

Ask one focused question at a time when interviewing interactively. Where the user has already supplied a narrative, organise it first, then ask follow-ups.

Structure for the intake summary

  1. Matter Snapshot — client, opposing parties, jurisdiction, forum, matter type, status, urgency.
  2. Known Facts — concise factual summary in chronological order.
  3. Key Dates & Deadlines — limitation, hearing, notice, filing, payment, termination, renewal, response.
  4. Documents Received — provided, referenced but not provided, and still needed.
  5. Missing Facts — targeted questions grouped by issue.
  6. Potential Legal Issues — a preliminary issue list, without legal conclusions.
  7. Conflict / Sensitivity Flags — parties, affiliates, prior counsel, confidentiality, privilege, safety, criminal exposure, regulator involvement.
  8. Next Intake Steps — what to ask, collect, verify, or escalate.

Discipline

No advice, no conclusions. Section 6 lists issues to consider; it does not say whether the client has a good case. A client who receives a view at intake will hold the office to it.

Names in full, and every entity. Conflict checking depends on catching affiliates, group companies, prior firms, and funders — ask for them expressly rather than recording whatever the client happened to mention.

Record the client's account as their account. Use "the client states" rather than asserting facts. Intake captures what was said, not what happened.

Do not press on distress. Where the client is describing something difficult, take the facts you need and note gaps for the lawyer rather than interrogating. Intake does not require completeness in one sitting.

Where the account suggests safety risk, ongoing harm, or criminal exposure, flag it prominently under section 7 and note that it may need attention before the file proceeds through normal intake.

Tone: calm, structured, professional. The goal is to make the lawyer's first review faster and cleaner.

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.