duriandurino/calendar-log
skills/calendar-log/SKILL.md
Log daily activities to Google Calendar as concise EOD summaries. Use when creating end-of-day summaries, logging milestones to calendar, tracking pentest progress, or when asked to "log to calendar" or "create EOD entry". Creates clean, scannable calendar events.
development
Updated Apr 15, 2026
$ install --global
skillsauthnpx skillsauth add duriandurino/openclawrino calendar-logInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 15, 2026, 5:23 PM12.3s2 files scanned
SKILL.md
- name:
- calendar-log
- description:
- Log daily activities to Google Calendar as concise EOD summaries. Use when creating end-of-day summaries, logging milestones to calendar, tracking pentest progress, or when asked to "log to calendar" or "create EOD entry". Creates clean, scannable calendar events.
Calendar Log
Create concise, well-formatted calendar entries for daily activity tracking.
Quick Start
gog calendar create "primary" \
--summary "EOD — [Topic] ([Date])" \
--from "YYYY-MM-DDTHH:MM:00+08:00" \
--to "YYYY-MM-DDTHH:MM:00+08:00" \
--account [email protected] \
--description "[formatted summary]" \
--all-day
Format Rules
Event Title Pattern
EOD — [Topic/Project] (YYYY-MM-DD)
Examples:
EOD — Vault Pentest (2026-03-18)EOD — GWorkspace Setup (2026-03-18)
Description Format (Concise)
Use this exact structure — MAX 15 lines:
🎯 [Main Achievement]
📦 Deliverables
• [Item 1]
• [Item 2]
🔍 Key Findings
• [Finding 1]
• [Finding 2]
📊 Status: [In Progress / Complete / Blocked]
Alternative: Milestone Log
For logging specific events (not EOD):
[Milestone Type] — [Brief Description]
• What: [One line]
• Status: ✅ Done / 🔄 In Progress / ❌ Blocked
Time Options
| Type | Flags |
|------|-------|
| All-day event | --all-day --from "YYYY-MM-DD" --to "YYYY-MM-DD" |
| Specific time | --from "YYYY-MM-DDTHH:MM:00+08:00" --to "..." |
| End of day | --from "...T18:00:00" --to "...T18:30:00" |
Workflow
1. COLLECT activities from session/memory
2. FORMAT using template above
3. CREATE calendar event with gog
4. CONFIRM event link returned
Example: Pentagon Test EOD
gog calendar create "primary" \
—summary "EOD — Vault Pentest (2026-03-18)" \
—all-day \
—from "2026-03-18" \
—to "2026-03-18" \
—account [email protected] \
—description "🎯 Vault decrypted (15 min)
📦 Full report, slides, 9 findings
🔍 V-012: Hardcoded key (CRITICAL)
📊 Status: Complete"
Full Day Capture
To capture the WHOLE day, review:
memory/YYYY-MM-DD.md— daily log entries- Git commits from today
- Tool calls and sub-agent spawns
- Key milestones and decisions
Include ALL major activities, not just the final task.
Guidelines
- Full day coverage — capture morning to evening activities
- Use emojis sparingly — 🎯📦🔍🛠️📊 for section headers only
- Chronological order — morning activities first
- One event per day — single comprehensive entry
- Bullet points over paragraphs — always
- Keep under 20 lines — still scannable but complete
Related Skills
duriandurino/vuln
testing
VerifiedTrustedCommunity
Vulnerability analysis and CVE matching for penetration testing. Use when: user asks to check for vulnerabilities, match CVEs against service versions, analyze scan results for weaknesses, research exploitability, assess risk of discovered services, or identify known vulnerabilities. This is the analysis phase — no exploitation yet. NOT for: active scanning (use enum skill), exploitation (use exploit skill), or post-exploitation (use post skill).
SKILL.mdUpdated Apr 15, 2026
duriandurino/vuln-phase-essentials
development
VerifiedTrustedCommunity
Methodology and decision framework for the penetration testing vulnerability phase. Use when: validating scanner output, distinguishing confirmed vulnerabilities from hypotheses, explaining CVE/CWE/CVSS, prioritizing findings with KEV/EPSS/business context, guiding vuln-analysis workflow, or reinforcing evidence-backed reporting during the vulnerability phase. NOT for: initial recon or active enumeration, hands-on exploitation, post-exploitation, or replacing the specialized vuln skill's concrete checks.
SKILL.mdUpdated Apr 15, 2026
duriandurino/slides-cog
development
VerifiedTrustedCommunity
Great slides need two things: content worth presenting and design worth looking at. #1 on DeepResearch Bench (Feb 2026) — CellCog researches and fills content mindfully from minimal prompts, no filler. State-of-the-art PDF generation for presentations, pitch decks, keynotes, and slideshows you can present as-is. Requires cellcog skill for SDK. If cellcog is unavailable, use gog slides as fallback (Google Workspace).
SKILL.mdUpdated Apr 15, 2026
duriandurino/report-phase-essentials
development
VerifiedTrustedCommunity
Methodology and quality framework for the penetration testing report phase. Use when: writing or QA-ing pentest reports, improving executive and technical readability, enforcing evidence completeness, adding remediation and retest guidance, including cleanup/restoration and residual risk, or securing report packaging and delivery. NOT for: running phase-specific testing tasks or replacing the specialized reporting implementation/publishing workflow.
SKILL.mdUpdated Apr 15, 2026