Design a diary study — prompts, cadence, duration, participant criteria, and analysis frame. Use when behaviour unfolds over days or weeks. For a single-session study, use `usability-test-plan`.
Scanned 9/5/2026
Install to Claude Code
Skills Directorynpx -y skills add Owl-Listener/designer-skills --skill diary-study-plan --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Diary Study Plan?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/owl-listener-diary-study-plan)More formats (shields.io, HTML) on the badges page.
---
name: diary-study-plan
description: Design a diary study — prompts, cadence, duration, participant criteria, and analysis frame. Use when behaviour unfolds over days or weeks. For a single-session study, use `usability-test-plan`.
---
# Diary Study Plan
Design a longitudinal diary study to capture user behavior in context over time.
## Context
You are a UX researcher designing a diary study for $ARGUMENTS.
## Instructions
1. **Define research goals**: What longitudinal behaviors or experiences are you studying?
2. **Design the study**:
- **Duration**: Recommended length (typically 1-4 weeks)
- **Participants**: 8-15 participants, screening criteria, compensation plan
- **Entry prompts**: Daily or event-triggered prompts (mix of structured and open-ended)
- **Capture methods**: Photo, video, text, voice — what to ask participants to document
- **Check-in schedule**: Mid-study interviews or pulse surveys
- **Onboarding**: Participant briefing, practice entries, tool setup
3. **Create an analysis framework**: How to code, theme, and synthesize entries across participants.
4. **Plan for attrition**: Strategies to keep participants engaged throughout the study.
5. Present as a ready-to-execute research plan.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Recovers prior coding-agent session context by running `catchup <agent> --since-compact`, which extracts a clean summary of a previous Codex, Claude Code, Antigravity, OpenCode, or Pi Agent session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", or asks to recover/summarize a previous session before continuing. Do NOT use for the current conversation, git history, or any non-agent log.
