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.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Generate beautiful interactive timeline HTML pages from JSON configuration data, with three layout modes:
vertical) — A classic top-to-bottom timeline with event cards alternating on either side of the axishorizontal) — A horizontally scrollable timeline, best for displaying fewer eventsdual-side) — Events are placed on the left or right based on the side field, great for side-by-side comparisonsAll layouts support:
python3 scripts/generate_timeline.py --config timeline_data.json --output timeline.html
cat timeline_data.json | python3 scripts/generate_timeline.py --stdin --output timeline.html
python3 scripts/generate_timeline.py --config data.json --layout horizontal --output timeline.html
{
"title": "Project Milestones",
"layout": "vertical",
"theme": {
"primaryColor": "#2563eb",
"secondaryColor": "#7c3aed",
"backgroundColor": "#ffffff",
"textColor": "#1f2937",
"lineColor": "#d1d5db",
"fontFamily": "system-ui, -apple-system, sans-serif"
},
"events": [
{
"date": "2024-01-15",
"title": "Project Kickoff",
"summary": "Approval completed, core team assembled",
"details": "Detailed description text, shown when the card is expanded...",
"icon": "🚀",
"category": "Milestone",
"color": "#10b981",
"side": "left"
}
]
}
| Argument | Description |
|---|---|
--config, -c | Path to the JSON config file (mutually exclusive with --stdin) |
--stdin | Read JSON from standard input |
--output, -o | Output HTML file path (defaults to stdout) |
--layout, -l | Override layout mode: vertical, horizontal, dual-side |
--title, -t | Override the timeline title |
| Field | Required | Description |
|---|---|---|
date | Yes | Date label — any format works (e.g. 2024-01, Q1 2024, Phase One) |
title | Yes | Event title |
summary | No | Short description, always visible on the card |
details | No | Detailed content, revealed on click |
icon | No | Emoji or single-character icon (defaults to ●) |
category | No | Category tag displayed on the card |
color | No | Event node color (overrides the theme color) |
side | No | Only for dual-side layout: left or right |
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Simulates academic peer review, evaluating papers across Originality, Methodology, Results, and Writing to provide Major/Minor Revision recommendations with actionable feedback. Triggers when a user asks to "review my paper," "simulate peer review," or "give my paper a peer review.
The English summary is being prepared. Showing the original description.
This skill should be used when the user asks to "attack Active Directory", "exploit AD", "Kerberoasting", "DCSync", "pass-the-hash", "BloodHound enumeration", "Golden Ticket", "Silver Ticket", "AS-REP roasting", "NTLM relay", or needs guidance on Windows domain penetration testing.
The English summary is being prepared. Showing the original description.
This skill should be used when the user asks to "test API security", "fuzz APIs", "find IDOR vulnerabilities", "test REST API", "test GraphQL", "API penetration testing", "bug bounty API testing", or needs guidance on API security assessment techniques.
The English summary is being prepared. Showing the original description.
Generate multiple radically different interface designs for a module using parallel sub-agents. Use when user wants to design an API, explore interface options, compare module shapes, or mentions "design it twice".
The English summary is being prepared. Showing the original description.
Interactive system flow tracing across CODE, API, AUTH, DATA, NETWORK layers with SQLite persistence and Mermaid export. Use for security audits, compliance documentation, flow tracing, feature ideation, brainstorming, debugging, architecture reviews, or incident post-mortems. Triggers on audit, trace flow, document flow, security review, debug flow, brainstorm, architecture review, post-mortem, incident review.
The English summary is being prepared. Showing the original description.
Authentication patterns: session vs JWT vs OAuth comparison, provider selection (NextAuth, Clerk, Supabase Auth), security checklist, and common mistakes. Use when implementing auth, reviewing auth flows, or choosing auth providers.
The English summary is being prepared. Showing the original description.