timeline-builder

Generate beautiful interactive timeline HTML pages from JSON data, with vertical, horizontal, or dual-side layouts, collapsible details, and custom colors. Ideal for project milestones, company histories, or resumes. Triggered when a user mentions 'timeline', 'history of events', 'project milestones', 'release log', or asks to visualize a chronological sequence of data.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

92%Weight 40%Scale 1-5

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

A lean, highly actionable skill body with concrete commands, complete config and field tables, and a clean single-file bundle reference. The only slack is light marketing phrasing and a redundant use-cases list that could be trimmed for token efficiency.

Suggestions

Trim decorative adjectives ('beautiful', 'classic', 'best for', 'great for') from the layout descriptions to recover tokens without losing clarity.

Drop or compress the Use Cases list since it largely duplicates the trigger scenarios already in the description.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with tables and runnable commands and no padding of concepts Claude already knows, but retains minor trimmable marketing language ('beautiful interactive', 'classic top-to-bottom') and a slightly redundant Use Cases list.	4 / 5
Actionability	Provides fully executable, copy-paste-ready commands, a complete JSON config example, and explicit CLI argument and event-field tables covering the common cases.	5 / 5
Workflow Clarity	A single-purpose one-command tool whose single action is unambiguous and shown in multiple concrete invocation forms; the simple-skill exception applies and no destructive/batch cap is triggered.	5 / 5
Progressive Disclosure	Well-sectioned body with a real, clearly-referenced one-level-deep bundle file (scripts/generate_timeline.py) and no nested reference chains; content is appropriately organized for navigation.	5 / 5
	Total	19 / 20 Passed

Description

87%Weight 40%Scale 1-5

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, well-structured description that clearly states capabilities and provides concrete natural-language triggers in third-person voice. It could be pushed higher on specificity and trigger-term breadth by enumerating more distinct actions and synonyms/file extensions.

Suggestions

Broaden trigger-term coverage with synonyms and extensions users might say (e.g. 'Gantt', '.html timeline', 'event sequence', 'chronology').

Tighten specificity by framing discrete actions (e.g. 'Generate, theme, and lay out timeline HTML from JSON') rather than one verb plus feature adjectives.

Dimension	Reasoning	Score
Specificity	Lists several concrete capabilities (three layout modes, collapsible details, custom colors, JSON input) rather than vague language, though it centers on one core generation action with feature variants rather than a comprehensive set of distinct actions.	4 / 5
Completeness	Explicitly answers both 'what' (generate interactive timeline HTML from JSON with layouts/collapsible/custom colors) and 'when' via a concrete 'Triggered when a user mentions...' clause with specific trigger phrases.	5 / 5
Trigger Term Quality	Includes several natural trigger phrases users would actually say ('timeline', 'history of events', 'project milestones', 'release log', 'visualize a chronological sequence'), but lacks synonym/extension breadth (e.g. .html, Gantt).	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (interactive timeline HTML visualization) with distinct, specific triggers and minimal realistic overlap with other skills.	5 / 5
	Total	18 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: zebbern/claude-code-guide
Path: skills/timeline-builder/SKILL.md
Commit: 9d252b3

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