メニュー
Reports your GitHub activity for a specific day using the gh CLI, showing commits, issues, and activity timeline. Use this when you need to review what you accomplished on GitHub for a particular date.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | gh-daily-timeline |
| description | Reports your GitHub activity for a specific day using the gh CLI, showing commits, issues, and activity timeline. Use this when you need to review what you accomplished on GitHub for a particular date. |
| license | MIT |
This skill reports your GitHub activity for a specific day using the gh CLI.
Run the script with an optional date argument (defaults to today):
# Get today's activity
bash gh-activity.sh
# Get activity for a specific date
bash gh-activity.sh 2025-12-15
The date format must be YYYY-MM-DD.
gh (GitHub CLI) - must be authenticated with your GitHub accountjq - for JSON processingCommits: Lists all commits you made with their actual commit messages, grouped by repository and branch.
Issues: Shows all issues you created, commented on, or interacted with, including issue titles and the type of interaction.
Activity Timeline: A chronological view of all your GitHub events for the day (pushes, PRs, issue comments, etc.).
gh api /users/{username}/eventsgh api /repos/{repo}/compare/{before}...{head}Guide for authoring Agent Skills with strong YAML `description` triggers, progressive disclosure, and bundled resources. Use when creating or updating a skill, running init_skill.py or package_skill.py, or improving a bland skill description so agents load the skill on the right user tasks.
Build an awesome marimo notebook that brings a research paper or dataset to life — for competitions, tutorials, demos, or blog companions. Use when asked to "make an awesome marimo notebook," "build a notebook for this paper," "create a competition submission," or pair-program an interactive research explainer on molab. Covers: what makes a notebook engaging (intuition game, real experiment, novel extension, design system), paper selection, narrative arc and proportions, custom anywidget patterns, wigglystuff CellTour, effective GPU usage, memory-efficient training (fused STE, gradient checkpointing), parallel review subagents, and a pre-publication polish checklist. CRITICAL: mo is auto-injected (import in ONE cell); every top-level name must be unique across ALL cells; custom anywidget needs model.save_changes(); use mo.output.replace() for live charts; guard all torch.cuda calls for CPU-only machines.
Create VS Code-style typewriter animation videos with mechanical keyboard sounds. Supports 4 typing speeds, ghost text autocomplete, strikethrough corrections, emoji picker, file tab switching, syntax highlighting (6 languages), Chinese IME (pinyin + direct mode), inline images, image stacks, animated checkboxes, Excalidraw hand-drawn diagrams, 8 visual themes, 4 sound packs, and A-roll narration sync. Built on Remotion (React-based video rendering). Use when the user wants to create code typing videos, explainer B-roll, or typewriter-style animations.
Create animated videos using Remotion from topics, product URLs, Google reviews, talking-head videos, CSV data, or channel/brand URLs. Supports 6 video types: educational explainers, product launch demos, testimonial/social proof, avatar video overlays, data visualization dashboards, and lower third overlays. Each follows a 2-step workflow: research/scrape/analyze then design and animate with spring animations, SVG diagrams, and count-up effects. Requires the Remotion best practices skill (install with `npx skills add remotion-dev/skills`). Use when the user asks to create a Remotion video, explainer video, educational video, product demo video, testimonial video, video with animated overlays, data visualization video, animated dashboard, lower third, transparent overlay, short-form vertical video for mobile, or multi-product video from a website.
Improve coherence in drafts through a four-pass sub-agent workflow: resolve argument conflicts, smooth section transitions, smooth paragraph transitions, and run a final coherence audit. Use when a user says things like 'make this coherent', 'tighten the flow', 'this feels choppy', 'can you smooth transitions', or asks to revise prose in Markdown, notes, essays, blog posts, emails, or docs so ideas connect cleanly without adding new points.
Break long-lived pull request branches into a mergeable stack of small PRs with clear dependency order and story flow. Use when a branch has grown too large, when the user asks to split a PR into stacked PRs, or when each PR must be reviewable in about 5 minutes while preserving logical narrative across the stack.