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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

77%

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

The body is highly actionable and well-sequenced with strong validation checkpoints, but it is monolithic — everything lives inline in SKILL.md with no reference files — and somewhat verbose in places. Splitting the long tangential sections out and tightening prose would lift the two middling dimensions.

Suggestions

Move 'M365 Connected Mode (Optional)', 'Cross-Skill Handoffs', and 'Domain Knowledge — Why Law Firm Platforms Fail' into separate reference files (e.g. references/m365-connected-mode.md, references/handoffs.md) referenced one level deep from the body, improving progressive disclosure.

Tighten verbose prose passages — e.g. collapse the opening two-sentence failure framing and deduplicate the per-mode 'output rule' phrasing — to lift conciseness without losing the methodology.

Consider extracting the four Mode templates (site architecture, automation brief, dashboard spec, adoption plan) into a references/templates.md file so the main body reads as methodology with copy-ready templates one click away.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and encodes genuine domain expertise Claude lacks (law-firm platform failure modes), but passages like the opening 'A platform that is too complex...a dashboard that requires manual data entry...' and repeated output-rule phrasing could be tightened.	2 / 3
Actionability	Copy-paste-ready templates (automation brief, dashboard specification, adoption intervention plan), explicit SharePoint List field schemas, and a symptom→cause→fix diagnosis table give fully executable guidance.	3 / 3
Workflow Clarity	Clear per-mode sequencing with an explicit hard-gate identifier checkpoint ('do not produce...until the identifier block below is confirmed'), pre-flight checklist, and end-of-output gap flagging.	3 / 3
Progressive Disclosure	No bundle/reference files exist and the body is a ~300-line monolith; well-organized into sections, but content like 'M365 Connected Mode', 'Cross-Skill Handoffs', and 'Domain Knowledge' could be split into reference files.	2 / 3
	Total	10 / 12 Passed

Description

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.

The description is comprehensive and well-structured: concrete capabilities, explicit use-when guidance, plentiful natural trigger phrases, and a clearly bounded legal-LPM niche. It is somewhat long but the description rubric does not penalize verbosity and every part earns its place.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Site architecture, workflow identification, dashboard design, data quality governance, and user adoption' — rather than vague language.	3 / 3
Completeness	Explicitly answers both 'what' (configuration methodology for legal matter sites) and 'when' via a dedicated 'Use when...' clause and 'Trigger on:' list.	3 / 3
Trigger Term Quality	Broad coverage of natural phrases a user would say, e.g. 'set up the matter site', 'build a dashboard', 'nobody is using the platform', 'data quality is poor'.	3 / 3
Distinctiveness Conflict Risk	Clear niche — legal matter collaboration platforms on SharePoint/Teams/M365 — with distinctive, domain-specific triggers unlikely to collide with other skills.	3 / 3
	Total	12 / 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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: legalopsconsulting/lpm-skills
Commit: 178ed52

Reviewed: 6 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.