document-approval-tracker

Approval cascade definition and tracking for multi-stakeholder document workflows. Internal review sequences, client approval workflows, regulatory review, overdue chasing with escalation logic, version control coordination, and cross-jurisdiction document dependencies. Use when defining who reviews a document and in what order, tracking where a document is stuck in the approval chain, chasing an overdue reviewer, preventing reviewers working on superseded drafts, or mapping dependencies between documents across jurisdictions. Trigger on: 'who needs to approve this', 'document approval', 'review sequence', 'stuck in review', 'overdue approval', 'who has the document', 'version control', 'wrong version', 'document dependency', 'NL SPA waiting on German opinion', 'approval cascade', 'review chain', 'document circulation', 'chasing the partner', 'client approval process', 'where is the document'.

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.

A strong, highly actionable instruction skill with clear sequenced workflows and validation gates, undermined mainly by verbosity and a complete absence of progressive disclosure — everything lives in one long file.

Suggestions

Trim motivational and restatement prose (e.g. the 'Why Document Approval Fails' section and repeated 'produce the output, do not ask' directives) to tighten conciseness toward a leaner body.

Split the long M365 Connected Mode / DMS integration and Domain Knowledge sections into reference files (e.g. references/connected-mode.md, references/domain-knowledge.md) and link to them one level deep, so progressive disclosure can score higher.

Consolidate the duplicated 'produce it / do not ask / use placeholders and flag gaps' output rules into a single Output Format section instead of restating them inside each mode.

Dimension	Reasoning	Score
Conciseness	Mostly actionable domain guidance, but padded with motivational prose ("Document approval is the invisible critical path..."), a "Why Document Approval Fails" section, and repeated "Produce the output — do not ask whether to produce it" directives that could be tightened.	2 / 3
Actionability	Provides copy-paste-ready skeletons, position-tracker tables, email templates per escalation day, SLA defaults, and a version-status table — concrete and executable rather than abstract.	3 / 3
Workflow Clarity	Four modes are clearly sequenced behind an input-classification step and a hard identifier-block gate, with explicit checkpoints (80% SLA flag, gaps checklist, version ground-truth table) and feedback loops (Mode 2/3 hybrid produces tracker then chaser).	3 / 3
Progressive Disclosure	Well-organized into labeled sections but monolithic — ~385 lines in a single SKILL.md with no bundle files and no offloaded references, so content that could be split (DMS integration, connected mode, domain knowledge) is inline.	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 highly specific, complete, and trigger-rich, with third-person voice and a well-defined legal-LPM niche. Its only weakness is verbosity — the trigger list is long and somewhat padded — but no description dimension directly penalizes length.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "Approval cascade definition and tracking", "overdue chasing with escalation logic", "version control coordination", and "cross-jurisdiction document dependencies" — rather than vague abstractions.	3 / 3
Completeness	Explicitly answers both what (cascade definition/tracking, chasing, version control, dependency mapping) and when via a clear "Use when..." clause plus explicit trigger terms.	3 / 3
Trigger Term Quality	The "Trigger on:" list supplies many natural phrases a user would say ("who needs to approve this", "stuck in review", "where is the document", "wrong version") with good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear legal project-management niche with distinctive triggers ("approval cascade", "NL SPA waiting on German opinion", "chasing the partner"); unlikely to fire for unrelated skills despite a few generic terms like "version control".	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.