collaboration-platform-advisor-scott-margetts
Collaboration platform configuration methodology for legal matter sites. Site architecture, workflow identification, dashboard design, data quality governance, and user adoption for SharePoint, Teams, and equivalent platforms. M365 is the reference implementation — outputs are platform-agnostic enough to brief IT or build simple automations without becoming a Power Automate manual. Use when setting up a matter site, identifying workflows to automate, designing reporting dashboards, managing platform data quality, or driving user adoption. Trigger on: 'set up the matter site', 'configure ShareP
npx skills add lawve-ai/awesome-legal-skills --skill collaboration-platform-advisor-scott-margetts --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
Designs and governs collaboration platforms for legal matters, focusing on site structure, workflows to automate, dashboards, data quality governance, and user adoption. Uses M365 as the reference implementation but outputs are platform-agnostic so IT can brief or implement without relying on Power Automate. Targets law firms setting up matter sites, identifying automations, dashboard design, data quality, or adoption initiatives.
How it works
Mode 1 — Matter site setup and architecture: Specifies a structured site architecture with document libraries organized as Matter root → Workstreams/Jurisdictions → Phase subfolders, including a naming convention and version control. Defines lists (RAID log, Matter plan, LC tracker, Scope change register) and a Teams channel structure and permission scheme. Outputs the architecture using placeholders when details are unknown and does not request missing identifiers until confirmed.
Mode 2 — Workflow identification and automation briefing: Analyzes current manual workflows to identify automatable items using a four-point test. For each eligible workflow, creates a formal Automation Brief with fields: Name, Trigger, Condition, Action, To, Subject, Body, Platform, Data source, Owner, IT effort. Produces one completed brief per automation that passes the test; marks non-qualifying workflows as not suitable due to required judgment.
Mode 3 — Dashboard and reporting design: Designs audience-specific dashboards with up to five views, ensuring data flows automatically from lists (RAID log, matter plan, LC tracker, scope register). Uses placeholders where matter-specific data is not provided and flags gaps requiring confirmation before build.
Mode 4 — Data quality and adoption: Provides a diagnosis framework for data quality symptoms and adoption issues, outlining likely causes and fixes aimed at embedding the platform, though the specific recommended fixes would be determined through subsequent interaction.
When to use it
Use when setting up a new matter site, identifying automatable workflows, designing dashboards, addressing data quality problems, or driving platform adoption.
What it can touch
The skill references and organizes work around SharePoint, Teams, and Power Automate as the primary M365 reference implementation, describing inputs, data sources (lists, libraries), and platforms for automation and dashboards. It requires LPM-maintained ownership of automation and dashboard data sources.
Caveats
Focuses on methodology rather than actual tool configuration; outputs are platform-agnostic and intended for briefing IT or enabling simple automations. Requires user-provided identifiers (client, matter, output version, date) to proceed with Mode 1 outputs; placeholders are permitted but must be completed to generate architecture content.
# Collaboration Platform Advisor You are a Legal Project Management skill that designs and governs legal matter collaboration platforms — their structure, workflows, dashboards, data quality, and adoption. You work with M365 (SharePoint, Teams, Power Automate) as the reference implementation and produce outputs in platform-agnostic terms so an LPM can brief IT or build simple automations directly. This skill encodes methodology, not tool configuration. Law firm platform failures are rarely technical — they are design and adoption failures. A platform that is too complex for a partner to navigate in 90 seconds will not be used. A dashboard that requires manual data entry from an associate is a dashboard that will have stale data. The design principles here exist to prevent those failures. ## When to use this skill - Setting up a collaboration site for a new matter or programme - Identifying which workflows to automate and how to describe them for IT - Designing dashboards that surface the right information without manual effort - Managing data quality when a platform's data has become unreliable - Driving adoption when a platform exists but nobody is using it --- ## Before Starting
- When to use this skill
- Before Starting Any Mode
- Operating Modes
- Mode 1 — Matter site setup and architecture
- Mode 2 — Workflow identification and automation briefing
- Mode 3 — Dashboard and reporting design
- Mode 4 — Data quality and adoption
- Domain Knowledge — Why Law Firm Platforms Fail
- Output Format
- LPM vs Attorney Boundary
- Cross-Skill Handoffs
- M365 Connected Mode (Optional)
- Time-Sensitive Assumptions
What does the collaboration-platform-advisor-scott-margetts skill do?
Collaboration platform configuration methodology for legal matter sites. Site architecture, workflow identification, dashboard design, data quality governance, and user adoption for SharePoint, Teams, and equivalent platforms. M365 is the reference implementation — outputs are platform-agnostic enough to brief IT or build simple automations without becoming a Power Automate manual. Use when setting up a matter site, identifying workflows to automate, designing reporting dashboards, managing platform data quality, or driving user adoption. Trigger on: 'set up the matter site', 'configure ShareP
How do I install it?
Run `npx skills add lawve-ai/awesome-legal-skills --skill collaboration-platform-advisor-scott-margetts --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From lawve-ai/awesome-legal-skills, a repository with 618 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.