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'.
90
88%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
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 an excellent skill description that clearly defines a specific niche (legal matter site configuration on collaboration platforms), lists concrete capabilities, and provides comprehensive trigger guidance. The explicit 'Use when' clause and extensive 'Trigger on' list with natural user phrases make it highly effective for skill selection. The scope boundary clarification regarding Power Automate is a nice touch that further reduces conflict risk.
| 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' (site architecture, workflow identification, dashboard design, data quality governance, user adoption for collaboration platforms) and 'when' with an explicit 'Use when...' clause and a detailed 'Trigger on:' list covering multiple scenarios. | 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 + collaboration platform configuration + specific triggers like 'matter site' and 'platform governance' 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 strong, highly actionable skill with excellent workflow clarity and concrete, template-driven outputs across all four modes. Its main weakness is length — at 400+ lines it pushes the boundaries of token efficiency, with some domain knowledge sections that could be condensed or externalized. The progressive disclosure could be improved by splitting mode details into separate reference files while keeping the SKILL.md as a concise overview with navigation.
Suggestions
Extract the detailed mode specifications (Modes 1-4) into separate reference files (e.g., MODE1-SITE-SETUP.md, MODE2-AUTOMATION.md) and keep SKILL.md as a concise overview with mode summaries and links.
Condense the 'Domain Knowledge — Why Law Firm Platforms Fail' section to a bullet list of anti-patterns (one line each) rather than full paragraph explanations — the mode instructions already encode these principles in their design constraints.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is quite long (~400+ lines) and includes substantial domain knowledge sections that, while valuable, could be more tightly written. The 'Why Law Firm Platforms Fail' section explains concepts that are arguably inferable from the mode instructions themselves. However, the structured tables and templates are efficient and earn their tokens. Some redundancy exists between mode output rules and the general output format section. | 2 / 3 |
Actionability | Highly actionable throughout — Mode 1 provides specific list schemas with field names, Mode 2 includes a complete automation brief template with concrete examples (weekly status chase, overdue task alert), Mode 3 provides a fully populated dashboard specification example, and Mode 4 includes a structured intervention plan template. The automation candidate table with triggers, actions, and value is immediately usable. | 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 four-test validation for automation candidates in Mode 2 is an excellent checkpoint. Mode 4 includes a diagnostic table before recommending fixes. The 'do not produce until identifier block is confirmed' is an explicit validation gate for all modes. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear mode separation and cross-skill handoffs, but it is monolithic — everything lives in a single file with no references to external documents for detailed content. The M365 Connected Mode section, domain knowledge section, and the extensive Mode 1-4 content could benefit from being split into separate reference files. For a skill of this length, inline delivery of all content reduces scannability. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
100%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
8f9093f
- Reviewed
Table of Contents
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.