skill CX Codex

diary-study-plan — Claude Code skill: plan a diary study

Q: How do I install diary-study-plan in Claude?

Run `npx skills add Owl-Listener/designer-skills --skill diary-study-plan -a claude-code`. The skill lands in `~/.claude/skills/diary-study-plan/SKILL.md`.

Walks you through designing a diary study: prompts, cadence, duration, participant criteria and an analysis frame.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓

npx skills add Owl-Listener/designer-skills --skill diary-study-plan -a claude-code

Open on GitHub

What diary-study-plan does

The skill guides you through planning a longitudinal study, for when behaviour unfolds over days or weeks. You start with research goals, then build the plan: duration, participants, entry prompts, capture methods, a check-in schedule and onboarding.

Inside is a four-step instruction set plus an analysis framework — how to code, theme and synthesise entries across participants. Attrition gets its own step, since drop-off in diary studies is expected. For a single-session study the author points you to usability-test-plan instead.

It runs in Claude, Codex, Cursor, GitHub Copilot, Gemini CLI and OpenCode. Install goes through npx skills add or gh skill install, depending on the platform.

What it helps with

design a multi-week diary study
pick entry prompts and cadence for participants
write screening criteria and a compensation plan
build a coding and theming frame across participants
keep participants engaged until the study ends

Example prompts for the agent

Plan a 3-week diary study of how people use our app
Help me write entry prompts and a check-in schedule for a diary study
Draft the analysis framework for diary study entries

How to install diary-study-plan

1Skills CLI (Vercel)

npx skills add Owl-Listener/designer-skills --skill diary-study-plan -a claude-code

2Manually: put the files in place

~/.claude/skills/diary-study-plan/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/diary-study-plan/

1Skills CLI (Vercel)

npx skills add Owl-Listener/designer-skills --skill diary-study-plan -a codex

2Manually: put the files in place

.agents/skills/diary-study-plan/SKILL.md

For all projects use ~/.agents/skills/

1Skills CLI (Vercel)

npx skills add Owl-Listener/designer-skills --skill diary-study-plan -a cursor

2Manually: put the files in place

.cursor/skills/diary-study-plan/SKILL.md

Cursor also reads .agents/skills/ and .claude/skills/

1GitHub CLI

gh skill install Owl-Listener/designer-skills diary-study-plan

2Manually: put the files in place

.github/skills/diary-study-plan/SKILL.md

1Skills CLI (Vercel)

npx skills add Owl-Listener/designer-skills --skill diary-study-plan -a gemini-cli

2Platform CLI

gemini skills install https://github.com/Owl-Listener/designer-skills --path design-research/skills/diary-study-plan

Manually: put the files in place

.devin/skills/diary-study-plan/SKILL.md

The legacy .windsurf/skills/ path still works

Skills CLI (Vercel)

npx skills add Owl-Listener/designer-skills --skill diary-study-plan -a opencode

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about diary-study-plan

How do I install diary-study-plan in Claude?

Run npx skills add Owl-Listener/designer-skills --skill diary-study-plan -a claude-code. The skill lands in ~/.claude/skills/diary-study-plan/SKILL.md.

What does diary-study-plan do?

It walks you through designing a longitudinal diary study: goals, duration, participants, prompts, capture methods and an analysis frame.

How is it different from usability-test-plan?

diary-study-plan targets behaviour that unfolds over days or weeks. For a single session the author recommends usability-test-plan.

Source text

SKILL.md · MIT

---
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.

Similar skills

Everything for Design →

study-plan official anthropics Builds and adapts a long-term bar or exam study schedule based on weak subjects, daily habits, and past progress. CX Codex +1 705installs tooluniverse-gwas-study-explorer mims-harvard Compares GWAS studies, aggregates locus effect sizes, and evaluates replication across cohorts. It runs Python code directly using GWAS Catalog and Open Targets data. CX Codex +1 357installs ux-research-discovery-testing hueyexe Gives your agent a working method for discovery interviews, usability tests and synthesis, so product calls rest on observed behavior instead of opinions. CX Codex +1 468installs repo-intake-and-plan lllllllama Scans a repository through its README and project files, then builds a small reproduction plan. Use it before running experiments. CX Codex +1 476,200installs product-research claude-code-skills Picks a research method that matches your goal, sizes the sample with a stated confidence, and turns coded observations into insights without over-claiming. 213installs customer-journey-map phuryn Builds an end-to-end customer journey map with stages, touchpoints, emotions, pain points, and opportunities. Useful for experience research and onboarding work. CX Codex +1 3,100installs

From the same set111

north-star-vision Articulates a long-horizon product vision across 1-year, 2-3 year, and 5+ year horizons. Useful when a team lacks a clear strategic direction. CX Codex +1 2,000installs test-scenario Writes usability test scenarios with realistic context, success criteria and facilitation notes. Useful once the study is planned and the tasks are still missing. CX Codex +1 2,000installs stakeholder-alignment Builds alignment artifacts: a stakeholder map, RACI matrix, decision rights and a communication plan. Useful when unclear ownership stalls decisions. CX Codex +1 2,000installs metrics-definition Defines UX metrics and KPIs that connect design decisions to measurable outcomes. Useful when deciding what to measure before tracking changes. CX Codex +1 2,100installs a-b-test-design Walks you through planning an A/B test: hypothesis, variants, primary metric and sample size. Useful when a change can be measured quantitatively. CX Codex +1 2,100installs form-design Designs forms end to end, covering field order, grouping, validation, and accessibility. Useful when building anything from single inputs to multi-step flows. CX Codex +1 1,900installs aesthetic-usability Applies the Aesthetic-Usability Effect when visual polish affects perceived ease of use and trust. Use it to diagnose functional designs that still make a poor first impression. CX Codex +1 1,900installs information-architecture A skill that designs content structure: sitemap, navigation model, taxonomy and content types. Useful when you need to organise what already exists. CX Codex +1 1,900installs