legal response

Data Community

Skill notes

Invocation

Common inquiry types: dsr or data-subject-request -- Data subject access/deletion/correction requests hold or discovery-hold -- Litigation hold notices vendor or vendor-question -- Vendor legal questions nda or nda-request -- NDA requests from business teams

Step 1: Identify Inquiry Type

Accept the inquiry type from the user. If the type is ambiguous, show available categories and ask for clarification.

Step 2: Load Template

Look for templates in local settings (e.g., legal.local.md or a templates directory). If templates are configured: Load the appropriate template for the inquiry type Identify required variables (recipient name, dates, specific details) If no templates are configured:

Step 3: Check Escalation Triggers

Before generating any response, evaluate whether this situation has characteristics that should NOT use a templated response. Universal Escalation Triggers (Apply to All Categories) The matter involves potential litigation or regulatory investigation The inquiry is from a regulator, government agency, or law enforcement The response could create a binding legal commitment or waiver

Step 4: Gather Specific Details

Prompt the user for the details needed to customize the response: Data Subject Request: Requester name and contact information Type of request (access, deletion, correction, portability, opt-out) What data is involved

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Data
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@anthropics · no license declared
Token usage
Heavy
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 1: Identify Inquiry Type

Accept the inquiry type from the user. If the type is ambiguous, show available categories and ask for clarification.

02
Step 2: Load Template

Look for templates in local settings (e.g., `legal.local.md` or a templates directory). If templates are configured: Load the appropriate template for the inquiry type Identify required variables (recipient name, dates, specific details) If no templates are configured:

03
Step 3: Check Escalation Triggers

Before generating any response, evaluate whether this situation has characteristics that should NOT use a templated response. Universal Escalation Triggers (Apply to All Categories) The matter involves potential litigation or regulatory investigation The inquiry is from a regulator, government agency, or law enforcement The response could create a binding legal commitment or waiver

04
Step 4: Gather Specific Details

Prompt the user for the details needed to customize the response: Data Subject Request: Requester name and contact information Type of request (access, deletion, correction, portability, opt-out) What data is involved

05
Step 5: Generate Response

Populate the template with the gathered details. Ensure the response: Uses appropriate tone (professional, clear, not overly legalistic for business audiences) Includes all required legal elements for the response type References specific dates, deadlines, and obligations Provides clear next steps for the recipient

06
Step 6: Template Creation (If No Template Exists)

If the user wants to create a new template, walk through the Template Creation Guide (see below) and present the finished template for review. Suggest the user save the approved template to their local settings for future use.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.