collaboration-platform-advisor

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 SharePoint', 'build a dashboard', 'what should we automate', 'brief IT on this workflow', 'nobody is using the platform', 'data quality is poor', 'set up Teams channel', 'matter site structure', 'alerts and notifications', 'user training', 'platform governance', 'status dashboard', 'what workflows can we automate', 'matter site template'.

Quality

88%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Discovery

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a strong, well-crafted description that clearly defines a specific niche (legal matter site configuration on collaboration platforms), lists concrete capabilities, and provides extensive explicit trigger guidance. The inclusion of both a 'Use when' clause and a detailed 'Trigger on' list with natural user phrases makes it highly effective for skill selection. The scope boundary clarification regarding Power Automate is a nice touch for disambiguation.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: site architecture, workflow identification, dashboard design, data quality governance, user adoption, and specifies platforms (SharePoint, Teams, M365). Also clarifies scope boundaries ('without becoming a Power Automate manual').	3 / 3
Completeness	Clearly answers both 'what' (collaboration platform configuration for legal matter sites with specific capabilities listed) and 'when' (explicit 'Use when...' clause plus a detailed 'Trigger on:' list with concrete phrases).	3 / 3
Trigger Term Quality	Excellent coverage of natural trigger terms users would actually say, including 'set up the matter site', 'configure SharePoint', 'build a dashboard', 'nobody is using the platform', 'data quality is poor', 'what should we automate', and many more realistic variations.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive niche: legal matter sites on collaboration platforms. The combination of legal domain + platform configuration + specific triggers like 'matter site' and 'brief IT on this workflow' makes it very unlikely to conflict with generic SharePoint or general legal skills.	3 / 3
	Total	12 / 12 Passed

Implementation

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a well-structured, highly actionable skill with excellent output templates and clear workflow gates. Its main weakness is length — the single-file approach creates a large token footprint that could be reduced by splitting mode-specific details into referenced files and trimming the domain knowledge section. The hard gate, pre-flight checklist, and explicit output rules demonstrate strong workflow design.

Suggestions

Split the four operating modes into separate referenced files (e.g., MODE1-SITE-SETUP.md, MODE2-AUTOMATION.md) to reduce the main skill's token footprint and improve progressive disclosure.

Compress the 'Domain Knowledge — Why Law Firm Platforms Fail' section into a concise bullet list of anti-patterns (2-3 words each with one-line fixes) rather than full paragraphs — Claude can infer the reasoning from brief descriptions.

Dimension	Reasoning	Score
Conciseness	The skill is quite long (~400+ lines) and includes some domain knowledge sections that explain concepts Claude could infer (e.g., 'Why Law Firm Platforms Fail' section explains general principles at length). The adoption diagnosis table and design principles, while useful, could be more compressed. However, the structured tables and brief templates are efficient, and most content is methodology-specific rather than generic.	2 / 3
Actionability	The skill provides highly concrete, copy-paste-ready output templates (automation briefs, dashboard specifications, adoption intervention plans, site architecture components). The automation brief skeleton, dashboard specification example, and structured tables with specific fields, triggers, and actions give Claude exact formats to populate rather than vague instructions.	3 / 3
Workflow Clarity	Each mode has a clear sequence: hard gate (identifier block) → pre-flight checklist → mode-specific inputs → structured output with explicit output rules. The hard gate is a genuine validation checkpoint ('do not produce any site architecture... until the identifier block is confirmed'). Mode 4 includes a diagnostic sequence (symptom → cause → fix) before intervention. Output rules explicitly state what to produce and what not to do.	3 / 3
Progressive Disclosure	The content is entirely self-contained in a single file with no references to external documents for detailed guidance. For a skill of this length and complexity (4 distinct modes, cross-skill handoffs, domain knowledge, M365 connected mode), splitting detailed mode specifications or the domain knowledge section into separate referenced files would improve navigability. The cross-skill handoffs section does reference other skills well, but the monolithic structure makes this a long single read.	2 / 3
	Total	10 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: legalopsconsulting/lpm-skills
Commit: 1eb58a1

Reviewed: 11 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.