bar-complaint

Generate formal Oregon State Bar complaints with rules-based counts via docx-js.

1|Updated Feb 23, 2026
One-click install
npx skills add https://github.com/ValorInvestigator/claude-plugin-toolkit --skill bar-complaint
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bar-complaint
Source: https://github.com/ValorInvestigator/claude-plugin-toolkit/tree/main/skills/bar-complaint
Command: npx skills add https://github.com/ValorInvestigator/claude-plugin-toolkit --skill bar-complaint

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Oregon State Bar complaint process is highly structured, demanding exact formatting, rules citations, and evidence organization that most practitioners cannot produce manually under time pressure; this Skill turns a narrative of misconduct into a BR 2.5-ready package with compliance-grade rigor for referral to Disciplinary Counsel.

Core Features & Use Cases

  • Structured Document Generation: Uses docx-js on a Windows Node.js environment to output a fully formatted complaint with title block, client and respondent data, summary, counts, harm, requested actions, exhibits, and certification.
  • Rules-Driven Argumentation: Guides the user to break misconduct into discrete counts, cite ORPC rules (and UTCR where relevant), and reference exhibits so the Oregon State Bar reviewer sees a disciplined legal argument rather than a grievance.
  • Evidence & Procedural Guidance: Embeds instructions on inline field formatting, exhibit lettering, referral rationales, and footer/page numbering specifics so that the final document is submission-ready, not just a draft.

Quick Start

Ask the skill to create a BR 2.5 complaint with counts, exhibits, and referral rationales for the misconduct you described.

Frequently Asked Questions about bar-complaint

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

FAQPage Schema
How do I format a formal Oregon State Bar complaint under BR 2.5?

A formal Oregon State Bar complaint under BR 2.5 requires a structured document featuring a title block, summary, detailed counts citing ORPC rules, harm, requested actions, exhibits, and certification sections to trigger Disciplinary Counsel referral.

What is the best way to structure attorney misconduct allegations for a disciplinary referral?

Structuring attorney misconduct allegations for a disciplinary referral involves breaking the narrative into discrete, rules-based counts, citing specific ORPC rules, and referencing exhibits to present a disciplined legal argument rather than a grievance.

Can I automatically generate a docx document for Oregon bar complaints?

Yes, you can generate a docx document for Oregon bar complaints using docx-js on a Windows Node.js environment, which outputs a fully formatted, submission-ready package with inline field formatting and footer page numbering.

Does the Oregon State Bar complaint process require citing specific rules for conflicts and candor failures?

Yes, the Oregon State Bar complaint process requires citing specific ORPC rules for conflicts, candor failures, improper fees, or discovery tactics to ensure the misconduct allegations meet compliance-grade rigor for Disciplinary Counsel review.

What sections are needed in a BR 2.5 submission for reporting attorney misconduct?

A BR 2.5 submission for reporting attorney misconduct needs specific sections including client and respondent data, a summary, detailed counts, harm, requested actions, exhibits, and a certification formatted for Oregon State Bar review.

What limitations exist when using docx-js to generate legal documents for bar complaints?

When using docx-js to generate legal documents for bar complaints, the environment requires Windows Node.js, and users must manually ensure narrative accuracy and evidence organization before submission to the Oregon State Bar.