cold-start-interview

Configure a civil legal aid office's shared context via guided interview.

22|5|Updated May 20, 2026
One-click install
npx skills add https://github.com/lawdroidAI/legal-aid-plugin --skill cold-start-interview-lawdroidai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cold-start-interview
Source: https://github.com/lawdroidAI/legal-aid-plugin/tree/main/skills/cold-start-interview
Command: npx skills add https://github.com/lawdroidAI/legal-aid-plugin --skill cold-start-interview-lawdroidai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps managing attorneys configure a civil legal aid office’s shared working context so that every staff member’s downstream outputs use the office’s actual practice areas, funding restrictions, eligibility guidelines, supervision model, and required templates.

Core Features & Use Cases

  • Office setup and configuration seeding: collects practice areas, jurisdictions, funding sources, eligibility guidelines, conflict-check procedure, escalation posture, and supervision style for use by all later skills.
  • Ethical and confidentiality guardrails: records account/data-handling terms and client consent/confidentiality practices so staff know what is allowed before using AI-assisted workflows on real matters.
  • Integration discovery and shared CLAUDE.md creation: checks connected MCP connectors (reporting success only when testable), seeds “office procedures” and templates into the shared configuration file, and drives an initial onboarding/eligibility-screening run.

Quick Start

Run /legal-aid:cold-start-interview as the managing attorney, answer the guided questions, and confirm the generated office profile before staff begin using /legal-aid:onboard.

Frequently Asked Questions about cold-start-interview

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure shared office context for a civil legal aid practice?

Guided office setup uses a Part 0/Part 1/Part 2 interview flow to collect practice areas, jurisdictions, funding-source restrictions, eligibility guidelines, supervision models, and conflict-check procedures, then writes a completed shared configuration file.

What is the best way to set up confidentiality guardrails for AI-assisted legal workflows?

Setting up confidentiality guardrails involves recording account data-handling terms and client consent practices during the initial configuration interview, ensuring staff know what AI-assisted workflows are permitted on real matters before proceeding.

Can I check MCP integrations and report connection status during office setup?

Checking MCP integrations during office setup tests connected MCP connectors and accurately reports connection status, succeeding only when testable connections are confirmed and writing the verified results to the shared configuration file.

Does legal aid office setup support eligibility screening and template seeding?

Legal aid office setup supports eligibility screening and template seeding by seeding office procedures and required templates into the shared configuration file, then driving an initial onboarding and eligibility-screening run for staff.

When should I re-run the legal aid office configuration interview?

Re-running the office configuration interview applies to fresh installs, placeholder cleanup, or integration re-checks, ensuring the shared operating context accurately reflects current practice areas, funding restrictions, and supervision models.

What limitations exist when testing MCP connectors during a fresh configuration?

Testing MCP connectors during configuration reports success only when connections are testable, meaning untestable or unavailable connectors will not report as successful in the shared CLAUDE.md file.