Skill snapshot

Skill fedec65/bettercallclaude/legal-briefing-workspace/iteration-1/skill-snapshot

Auto-activates structured briefing sessions for complex legal queries -- detects when multi-agent coordination benefits from pre-execution intake and plan buildingFrom its SKILL.md

Install

npx -y skills add fedec65/bettercallclaude --skill skill-snapshot

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

SKILL.md

3.4 KB, 708 tokens by cl100k_base, as published. Nobody here has run it

Legal Briefing Skill

You are aware of BetterCallClaude's briefing session capability. When you detect a complex legal query that would benefit from structured intake before execution, suggest or activate a briefing session.

Activation Criteria

Suggest a briefing session when any of the following conditions are met:

Complexity Indicators (score >= 5)

Three or more legal domains in a single query (e.g., corporate + tax + compliance).
Multi-jurisdictional question (federal + cantonal, or multiple cantons).
Document output expected alongside analysis (e.g., "analyze and draft").
Financial exposure mentioned above CHF 100,000.
Multiple parties with conflicting interests.

Ambiguity Indicators

Desired output is unclear (research? strategy? document? compliance check?).
Jurisdiction cannot be determined from the query.
Multiple valid routing paths exist with significantly different outcomes.
The query uses vague terms: "handle", "deal with", "figure out", "advise on".

Pipeline Indicators

Query maps to a workflow template (litigation-prep, due-diligence, contract-lifecycle).
Three or more agents would need to be coordinated.
Data dependencies exist between agents (output of one feeds into another).

When NOT to Activate

Skip briefing and route directly when:

Query is a simple, focused question (complexity 1-3).
User explicitly specifies a single agent with @agent_name.
User uses --skip-briefing or --direct flag.
Query is a citation lookup, translation, or format verification.
User is resuming a previously approved execution plan.

Activation Behavior

Implicit Suggestion (auto-detected complexity >= 5)

When the /legal gateway scores a query at complexity 5+ and no --skip-briefing flag is present:

💡 This query involves [N domains / multi-jurisdiction / pipeline coordination].
A briefing session would help build a precise execution plan before I start working.

**Options**:
- **Proceed with briefing** (recommended) — I'll ask a few targeted questions first
- **Skip briefing** — Route directly to agents (add `--skip-briefing` to bypass in future)

Explicit Activation

When the user invokes /bettercallclaude:briefing, always activate regardless of complexity.

Memory Key Patterns

The briefing system uses these memory keys for persistence:

Pattern	Purpose
`briefing_[id]`	Full state for a specific briefing session
`briefing_latest`	ID of the most recently active briefing
`briefing_index`	Registry of all briefing sessions with status

Integration Points

/legal gateway: Briefing phase is embedded between intent classification and routing.
Orchestrator agent: Consumes the approved execution plan YAML for step-by-step execution.
All specialist agents: Can be spawned as panel members during the consultation phase.
Summarizer agent: Can be appended to the execution plan's final stage.

Quality Standards

Briefing suggestions must be helpful, not obstructive — never block simple queries.
Auto-detection should have a low false-positive rate: only suggest for genuinely complex cases.
The user must always have a clear path to skip the briefing if they prefer direct routing.

What ships with it: 2 files

18.5 KB alongside SKILL.md

agents_briefing.md13.1 KB
commands_briefing.md5.4 KB

Gives 0 of the 12 instructions most legal skills give in 708 tokens

Counted across 234 of the 234 authors here whose files we hold, read 2026-08-07

Use text operators for text fieldsin 11 of 234, across 6 files
Consult qualified counsel before usein 11 of 234, across 3 files
Use PatentSearch API for patent searchesin 10 of 234, across 5 files
Confirm jurisdiction, employment type, and required clausesin 9 of 234, across 2 files
Choose a document template and tailor role-specific termsin 9 of 234, across 2 files
Validate compensation, benefits, and compliance requirementsin 9 of 234, across 2 files
Add signature, confidentiality, and IP assignment terms as neededin 9 of 234, across 2 files
Open the implementation playbook for detailed templatesin 9 of 234, across 2 files
Use TSDR for trademark data retrievalin 9 of 234, across 4 files
Ask for clarification if required inputs are missingin 8 of 234, across 2 files
Set the USPTO_API_KEY environment variablein 8 of 234, across 3 files
Use the uspto-opendata-python library for PEDSin 8 of 234, across 3 files

Said here and by no other author read

suggest briefing proactively for complex queries
give user clear path to skip briefing
check queries against all activation indicators
ask targeted questions during briefing
build execution plan yaml for orchestrator
persist briefing session state via memory keys

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.