activity-log
Display the daily activity log showing all content analyzed today. Use when the user asks what they've watched, read, or analyzed today, mentions activity log, daily log, or wants to see their consumption history.
Best use case
activity-log is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Display the daily activity log showing all content analyzed today. Use when the user asks what they've watched, read, or analyzed today, mentions activity log, daily log, or wants to see their consumption history.
Teams using activity-log should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/activity-log/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How activity-log Compares
| Feature / Agent | activity-log | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Display the daily activity log showing all content analyzed today. Use when the user asks what they've watched, read, or analyzed today, mentions activity log, daily log, or wants to see their consumption history.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Activity Log Display Display the activity log for today or a specific date. ## When to Use Activate this skill when the user: - Asks "what did I watch/read/analyze today?" - Mentions "activity log", "daily log", "consumption log" - Wants to see their learning history - Asks about their progress or what they've consumed ## Instructions 1. **Determine the date**: - Default: today's date in YYYY-MM-DD format - If user specifies a date, use that date instead 2. **Check if log file exists** at `logs/YYYY-MM-DD.md` 3. If file doesn't exist: - Say: "No activity logged for [date] yet." - Optionally mention: "Use /yt, /read, /arxiv, or /analyze to process content." - Stop here 4. If file exists: - **Read the log file** - **Display the contents** to the user in a readable format ## Log File Format The log file typically looks like: ```markdown # Activity Log: YYYY-MM-DD ## Videos Watched - [Video Title](../reports/youtube/filename.md) - 14:32 - [Another Video](../reports/youtube/filename2.md) - 16:45 ## Articles Read - [Article Title](../reports/articles/filename.md) - 10:15 ## Papers Reviewed - [Paper Title](../reports/papers/filename.md) - 11:30 ``` ## Optional Arguments If the user provides a date (e.g., "show me yesterday's log" or "what did I read on December 20th"), show that day's log instead of today's. ## Error Handling - If specified date's log doesn't exist: "No activity logged for [date]." - If logs folder doesn't exist: "No activity logs found. Start analyzing content to create logs." ## Related - Slash command equivalent: `/log` - Log location: `logs/YYYY-MM-DD.md` - Created automatically when analyzing content
Related Skills
activity-logging
Follow these patterns when implementing activity emission and audit logging in OptAIC. Use for emitting ActivityEnvelopes on mutations (create, update, delete, execute), designing payloads, and ensuring audit compliance.
bgo
Automates the complete Blender build-go workflow, from building and packaging your extension/add-on to removing old versions, installing, enabling, and launching Blender for quick testing and iteration.
8bit-docs-patterns
Create documentation with gaming-specific examples, retro styling, and 8-bit terminology. Apply when documenting gaming blocks, RPG components, or retro-styled UI elements.
1k-new-skill
Creates a new Claude Code Skill following best practices. Use when the user wants to create a new skill, add a skill, or asks about writing skills for Claude Code. Fetches latest documentation before generating skill content. New skill. Create a skill.
zotero-literature-verification
Complete workflow for verifying academic literature citations using Zotero MCP with full PDF reading and token management
zerubbabel-devops
Provides expert DevOps analysis, CI/CD pipeline review, and infrastructure assessment. Use this skill when the user needs deployment pipeline evaluation, infrastructure review, or platform engineering guidance. Triggers include requests for DevOps audit, CI/CD review, deployment strategy assessment, or when asked to evaluate infrastructure patterns. Produces detailed consultant-style reports with findings and prioritized recommendations — does NOT write implementation code.
zeabur
Zeabur cloud platform assistant for deployment, management, and optimization. Use when: (1) Deploying applications to Zeabur (Git, Docker, local upload, templates), (2) Managing Zeabur services via CLI (npx zeabur) or GraphQL API, (3) Configuring domains, environment variables, networking, or volumes, (4) Troubleshooting deployment failures, connectivity issues, or build errors, (5) Optimizing Zeabur costs, performance, or high availability architecture, (6) Working with Zeabur templates (YAML spec creation and deployment), (7) Setting up CI/CD pipelines with Zeabur, (8) Managing databases and prebuilt services on Zeabur, (9) Any mention of zeabur, zeabur.yaml, zbpack, zeabur.app, or zeabur CLI commands. Triggers: zeabur, deploy to zeabur, zeabur cli, zeabur api, zeabur template, zbpack, zeabur.app, zeabur domain, zeabur variable, zeabur service.
yaml-validator
Comprehensive YAML syntax validation, error fixing, and schema validation for various formats (GitHub Actions, Docker Compose, Kubernetes, GitLab CI). Use when Claude needs to: (1) Validate YAML syntax, (2) Check YAML files for errors, (3) Fix common YAML formatting issues, (4) Validate against schemas like GitHub Actions workflows, Docker Compose files, Kubernetes manifests, or GitLab CI pipelines, (5) Debug YAML parsing errors. Triggers on phrases like "check yaml", "validate yaml", "fix yaml errors", "yaml syntax".
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
writing-rules
Use when creating rule files in .claude/rules/, adding project conventions, or scoping guidelines to specific paths. Use when user says "add rule", "create convention", "scope guideline". NOT for laws (use <law> in CLAUDE.md).
write-rfc
Write RFCs for the ToolHive ecosystem. Use when the user wants to create a new RFC, proposal, or design document for toolhive, toolhive-studio, toolhive-registry, toolhive-registry-server, toolhive-cloud-ui, or dockyard projects.
wp-migrate
WordPress site migration and deployment using wp-migrate.sh. Use when migrating WordPress sites, syncing databases, managing backups, testing migrations, debugging migration issues, or working with WordPress deployment workflows including Duplicator, Jetpack Backup, and Solid Backups archives. Also use for code modifications, testing, git workflows, PR creation, and release management for this project.