skills/daily-log/SKILL.md
Reliable daily log management for development sessions. Use this skill when adding session entries to daily logs to ensure correct file paths and formatting.
npx skillsauth add nicksteffens/claude-config daily-logInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Daily logs are stored at: ~/.claude/daily-logs/YYYY/YYYY-MM.md
Example: December 2025 logs are at ~/.claude/daily-logs/2025/2025-12.md
ALWAYS use the AskUserQuestion wizard to gather session details - it's much easier than manual entry.
Use AskUserQuestion with these question sets:
First Question Set (Basic Info):
Second Question Set (Details):
Determine the file path:
YEAR=$(date +%Y)
MONTH=$(date +%m)
TODAY=$(date +%Y-%m-%d)
LOG_FILE="$HOME/.claude/daily-logs/$YEAR/$YEAR-$MONTH.md"
Check if date heading exists:
## YYYY-MM-DD in the file---)Use wizard responses to populate the session template
Multiple sessions same day:
--- horizontal ruleAfter writing the log entry, ALWAYS commit it to the ~/.claude git repo:
git -C ~/.claude checkout main
git -C ~/.claude add daily-logs/
git -C ~/.claude commit -m "docs: add daily log for YYYY-MM-DD"
IMPORTANT: ~/.claude IS a git repo (nicksteffens/claude-config).
Use git -C ~/.claude to operate on it from any working directory.
Daily logs should ALWAYS be committed to the main branch.
After committing, ask the user if they'd like to push (git -C ~/.claude push origin main).
## YYYY-MM-DD
### Session Overview
**Duration:** [time]
**Main Objective:** [objective]
**Success Rating:** [X]/10
### What We Accomplished
- [bullet points]
### Challenges Encountered
- [bullet points or "None"]
### Most Valuable Collaboration
[description]
### Key Insight
[main learning]
### Follow-Up Items
- [ ] [action items]
### Role Distribution
**Human:** [role]
**Claude:** [role]
### Success Factors
[what made it successful, if rating 6+]
---
// First question set - Basic info
AskUserQuestion({
questions: [
{
question: "How long did we work together today?",
header: "Duration",
multiSelect: false,
options: [
{label: "30-45 minutes", description: "Quick focused session"},
{label: "1 hour", description: "Standard session length"},
{label: "1.5-2 hours", description: "Extended working session"},
{label: "2+ hours", description: "Deep dive session"}
]
},
{
question: "How would you rate today's session overall?",
header: "Success",
multiSelect: false,
options: [
{label: "10/10 - Exceptional", description: "Everything went perfectly, exceeded expectations"},
{label: "8-9/10 - Excellent", description: "Highly productive, met all objectives"},
{label: "6-7/10 - Good", description: "Accomplished goals with some minor issues"},
{label: "4-5/10 - Fair", description: "Made progress but faced challenges"}
]
},
{
question: "What was your primary role during this session?",
header: "Your Role",
multiSelect: false,
options: [
{label: "Directing", description: "Provided high-level guidance and decisions"},
{label: "Collaborating", description: "Active pair programming and problem solving"},
{label: "Reviewing", description: "Primarily reviewing and approving Claude's work"},
{label: "Learning", description: "Observing and learning new techniques"}
]
},
{
question: "What was the most valuable aspect of our collaboration?",
header: "Value",
multiSelect: false,
options: [
// Customize based on session context
{label: "Option 1", description: "Description"},
{label: "Option 2", description: "Description"}
]
}
]
})
// Second question set - Details
AskUserQuestion({
questions: [
{
question: "What challenges did we encounter during this session?",
header: "Challenges",
multiSelect: true, // Allow multiple challenges
options: [
// Customize based on session context
{label: "Challenge 1", description: "Description"},
{label: "Challenge 2", description: "Description"},
{label: "No significant challenges", description: "Session went smoothly overall"}
]
},
{
question: "What's the key insight or learning from today?",
header: "Insight",
multiSelect: false,
options: [
// Customize based on session context
{label: "Insight 1", description: "Description"},
{label: "Insight 2", description: "Description"}
]
},
{
question: "Any follow-up items for future sessions?",
header: "Follow-up",
multiSelect: true, // Allow multiple follow-up items
options: [
// Customize based on session context
{label: "Task 1", description: "Description"},
{label: "Task 2", description: "Description"},
{label: "None - complete for now", description: "No immediate follow-up needed"}
]
}
]
})
#!/bin/bash
YEAR=$(date +%Y)
MONTH=$(date +%m)
TODAY=$(date +%Y-%m-%d)
LOG_DIR="$HOME/.claude/daily-logs/$YEAR"
LOG_FILE="$LOG_DIR/$YEAR-$MONTH.md"
mkdir -p "$LOG_DIR"
if [ ! -f "$LOG_FILE" ]; then
MONTH_NAME=$(date +%B)
echo "# Daily Logs - $MONTH_NAME $YEAR" > "$LOG_FILE"
echo "" >> "$LOG_FILE"
fi
echo "Log file: $LOG_FILE"
echo "Today's date heading: ## $TODAY"
development
Static reference for Shortcut team UUIDs, mention names, and workflow IDs across both workspaces. Use this when creating or assigning Shortcut stories instead of querying the API for team lists.
tools
Update Shortcut epics using the API directly (since MCP doesn't support epic updates). Handles linking to objectives, changing state, updating owners, etc.
content-media
Get Designer Team's current iteration and assign stories to it
data-ai
Create a new session log entry in the second-brain. Extracts context from the current session and asks for your assessment.