timeline-generator

Build dependency network and critical path from a matter plan. Produce an interactive Gantt, flag near-critical tasks, and run what-if cascade scenarios when delays occur — showing programme impact and drafting communications. Produces filtered workstream or jurisdiction views for local counsel. Trigger on: 'build a timeline', 'Gantt chart', 'critical path', 'what if X is delayed', 'what moves if', 'schedule impact', 'how does this affect the programme', 'when do we finish', 'can we still close on time', 'if we miss this deadline', 'run a what-if', 'visualise the plan', 'Germany timeline', 'what does the Employment workstream look like', 'timeline for local counsel', 'just show me the [workstream] tasks'.

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 domain-rich, highly actionable instruction skill with excellent workflow sequencing and validation gates. Its main weaknesses are verbosity from explaining concepts Claude already knows and a monolithic structure with no progressive disclosure into reference files.

Suggestions

Trim or remove general scheduling primers Claude already knows (e.g. the effort-vs-duration and float definitions) to recover token budget.

Split the long Domain Knowledge and Output Format sections into reference files (e.g. LEGAL_PATTERNS.md, OUTPUT_TEMPLATES.md) referenced one level deep from the main body.

Consolidate the duplicate cascade-impact-table definitions that appear in both the What-If Cascade Protocol and Output Format sections.

Dimension	Reasoning	Score
Conciseness	Mostly efficient domain guidance, but several sections explain general scheduling concepts Claude already knows ('Float is the amount of schedule flexibility a task has', 'Duration is the elapsed time... Effort is the person-hours') and the body runs ~360 lines with repeated rationale prose that could be tightened.	2 / 3
Actionability	Highly actionable for an instruction skill: concrete dependency formulas (ES = Predecessor EF + lag), worked lag example (Wednesday 7 May → Wednesday 14 May), exact table column specs, colour hex codes, and explicit output templates the LPM can fill directly.	3 / 3
Workflow Clarity	Multi-step processes are explicitly sequenced (Steps 1–8, What-If Protocol Steps 1–9) with validation checkpoints ('If critical inputs are missing, stop and ask'), versioning discipline, and feedback loops (rerun critical path after every confirmed change).	3 / 3
Progressive Disclosure	No bundle files exist and the skill is a single ~360-line monolith; sections are well-organized with headings, but content that could be split out (Domain Knowledge patterns, Output Format templates, What-If Protocol) all sits inline with no one-level-deep references.	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.

A strong, third-person description that names concrete capabilities, provides an explicit trigger clause with natural phrasings, and carves out a distinctive legal-LPM niche. It is somewhat long but earns its length with genuine trigger coverage rather than padding.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions: 'Build dependency network and critical path', 'Produce an interactive Gantt', 'flag near-critical tasks', 'run what-if cascade scenarios', 'drafting communications', 'filtered workstream or jurisdiction views'.	3 / 3
Completeness	Clearly answers what it does (build network, Gantt, cascade analysis) and when to use it via an explicit 'Trigger on:' clause with many example triggers.	3 / 3
Trigger Term Quality	Extensive natural trigger phrases a user would actually say: 'build a timeline', 'Gantt chart', 'critical path', 'what if X is delayed', 'when do we finish', 'can we still close on time'.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear niche (legal-matter critical-path / programme scheduling) with distinctive triggers like 'Germany timeline' and 'timeline for local counsel' unlikely to fire for unrelated 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.