Produces short daily standups, evening reflections and weekly retrospectives for one person or a small team, kept in the session unless you name a place to save.
Install the "daily-standup-journal" agent skill from https://github.com/iflytek/skillhub/tree/main/builtin-skills/skills/daily-standup-journal into .claude/skills/daily-standup-journal/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "daily-standup-journal", then confirm the skill loads.
Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
skills CLI
$ npx skills add iflytek/skillhub --skill daily-standup-journal -a codex
Project install goes to .agents/skills/; add -g for ~/.codex/skills/.
Install the "daily-standup-journal" agent skill from https://github.com/iflytek/skillhub/tree/main/builtin-skills/skills/daily-standup-journal into .agents/skills/daily-standup-journal/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "daily-standup-journal", then confirm the skill loads.
Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add iflytek/skillhub --skill daily-standup-journal -a cursor
Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.
Install the "daily-standup-journal" agent skill from https://github.com/iflytek/skillhub/tree/main/builtin-skills/skills/daily-standup-journal into .cursor/skills/daily-standup-journal/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "daily-standup-journal", then confirm the skill loads.
Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
skills CLI
$ npx skills add iflytek/skillhub --skill daily-standup-journal -a gemini-cli
Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.
Install the "daily-standup-journal" agent skill from https://github.com/iflytek/skillhub/tree/main/builtin-skills/skills/daily-standup-journal into .gemini/skills/daily-standup-journal/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "daily-standup-journal", then confirm the skill loads.
Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
skills CLI
$ npx skills add iflytek/skillhub --skill daily-standup-journal -a github-copilot
Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.
Install the "daily-standup-journal" agent skill from https://github.com/iflytek/skillhub/tree/main/builtin-skills/skills/daily-standup-journal into .github/skills/daily-standup-journal/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "daily-standup-journal", then confirm the skill loads.
GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add iflytek/skillhub --skill daily-standup-journal -a opencode
OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
Install the "daily-standup-journal" agent skill from https://github.com/iflytek/skillhub/tree/main/builtin-skills/skills/daily-standup-journal into .opencode/skills/daily-standup-journal/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "daily-standup-journal", then confirm the skill loads.
OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
Skill name
daily-standup-journal
GitHub stars
5.2k
Token cost
~1.9k tokens
SKILL.md length
904 words
Files
3
Skills in repo
29
Repo updated
First seen
Licence
MIT
At a glance
Produces short daily standups, evening reflections and weekly retrospectives for one person or a small team, kept in the session unless you name a place to save.
Works in 10 steps: Daily Solo Standup (5-Minute Check-In) → Daily Team Standup (Async) → Evening Reflection (Gratitude + Growth) → …
Planning a workday with a short solo check-in
SKILL.md covers What It Does, Session Types, Trigger Phrases and Step-by-Step Instructions, plus 2 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Four session types are offered: a solo workday check-in with prompts about commitments, distractions, things to defer, energy and a success metric; an asynchronous team standup covering yesterday, today and blockers; an evening reflection on what went well, what was hard and what was learned; and a weekly retrospective with wins and losses and an optional energy map.
Depth follows what you ask for. Everything stays in the conversation by default: the skill does not save, fetch or share journal text unless you request it and name the destination, and it never claims to recall earlier entries that are not in the current context. Energy ratings use your own scale and are recorded, not diagnosed.
When your agent uses it
Planning a workday with a short solo check-in
Writing an async team standup that surfaces blockers
Reflecting on the day in the evening
Running a weekly retrospective for yourself or a small team
Example prompts
“Give me a five-minute standup for today. I'm a freelancer with two client deadlines.”
“Draft my async team standup: shipped the login fix, working on billing, blocked on API keys.”
“Walk me through a weekly retrospective for this week.”
Workflow steps
10 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 72429e6. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Daily Standup and Journal loads about 1.9k tokens when it runs. Until then it costs about 65 tokens; SKILL.md has 904 words of instructions outside code blocks.
Always· name and description, kept in context so the agent knows when to use it
~65
When it runs· the whole SKILL.md, loaded when a task matches
~1.9k
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
Download SKILL.mdSave it as .claude/skills/daily-standup-journal/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
daily-standup-journal
description
Generate concise daily standups, reflection prompts, and weekly retrospectives for individuals or teams. Use for planning a day, surfacing blockers, reviewing user-provided entries, or drafting a check-in without assuming prior history.
version
1.0.0
license
MIT
Daily Standup & Journal
What It Does
Generate a structured check-in for a solo workday, team sync, reflection, or retrospective. Keep the
result proportional to the user's requested depth.
Default to an in-session response only. Do not save, retrieve, or share journal content unless the user explicitly requests it and identifies the destination. Never claim to remember earlier entries that are not present in the current authorized context.
Session Types
1. Daily Solo Standup (5-Minute Check-In)
Best for: Freelancers, solopreneurs, remote workers
Prompt
Why It Matters
What am I committed to finishing today?
Clarifies intention
What will distract me, and how do I prevent it?
Anticipates friction
What is one thing I can defer or delete?
Reduces scope creep
What energy level am I at? (1-10)
Captures the user's self-reported capacity without diagnosing it
What is the one metric that tells me today was a win?
Creates a finish line
Format: Invite brief answers unless the user asks for a deeper reflection.
2. Daily Team Standup (Async)
Best for: Small remote teams, freelance collaborators
Question
Focus
What did I accomplish yesterday?
Progress visibility
What will I work on today?
Intentionality
What blockers do I need help with?
Surface roadblocks
What one thing would make today productive?
Proactive planning
Pro tip: Keep responses under 3 sentences each. Use a shared doc or channel. Read everyone's before starting your day.
3. Evening Reflection (Gratitude + Growth)
Best for: Personal development, habit tracking
Prompt
Purpose
What went well today?
Reinforce positive patterns
What challenged me?
Identify growth edges
What did I learn?
Consolidate insights
What would I do differently?
Meta-learning
What am I grateful for?
Emotional resilience
4. Weekly Retrospective
Best for: Solopreneurs, small teams, end-of-week review
Section A: Wins & Losses
| Win | Why It Mattered |
|-----|----------------|
| [event] | [impact] |
| Loss / Miss | Lesson Learned |
|-------------|----------------|
| [event] | [takeaway] |
Section B: Energy Map
If the user wants an energy map, ask them to rate each day using their own scale:
Infer solo/team, planning/reflection, and time horizon from the request. Ask one short question only
when the missing choice would materially change the output; otherwise use the standard daily
check-in and state the assumption.
Step 2: Generate the Prompts
Based on type, serve the relevant prompt set. Allow customization:
"Skip the gratitude part today"
"Add a question about client outreach"
"Make it shorter — I'm in a hurry"
Show full SKILL.md (357 more words)Show less
Step 3: Process the Responses
Summarize what the user actually supplied and distinguish observations from hypotheses:
Patterns: If the user supplied several entries, note repeated language and cite the relevant days.
Blockers: "You've had the same blocker for 2 days. Want to brainstorm a fix?"
Trends: Describe a possible trend only when the supplied entries support it; ask the user whether the interpretation fits.
Do not infer mood, health, sleep quality, burnout, or causes from an energy score or sparse journal entry.
Step 4: Offer Optional Export
By default, return the entry in the conversation and do not persist it. If the user asks for a rolling log, confirm the file or service, show the exact content to be written, and obtain confirmation before writing or sharing it. Do not overwrite an existing log without explicit approval.
Step 5: Surface Action Items
When the user's response supports action and they want planning help, suggest one or two concrete
actions:
"Reserve a focus block during the user's stated high-energy period"
"Consider moving the Friday call if the user says that time repeatedly causes problems"
Present these as suggestions. Do not change a calendar, cancel a meeting, send a message, or share a journal without explicit authorization.
Sample Sessions
Solo Freelancer Standup
Morning Input: "Run my standup"
Output:
DAILY STANDUP
1. What are you committed to finishing today?
2. What might distract or block you?
3. What can you defer or remove?
4. What is your current energy level (optional, 1-10)?
5. What observable outcome would make today a win?
Weekly Retro
Input: "Weekly retro"
Output:
WEEKLY RETROSPECTIVE
WINS
• [Add outcomes from this week's supplied entries]
MISSES OR LESSONS
• [Add only what the user reported]
POSSIBLE PATTERNS
• [Evidence-backed pattern, or "Not enough information"]
NEXT WEEK
Start: [User choice]
Stop: [User choice]
Continue: [User choice]
Quality checks
Use only entries supplied in the current authorized context.
Keep observations separate from interpretations.
Do not infer health, mood, motivation, or performance from sparse entries.
Offer a share-ready draft only when useful; never send or expose journal content without explicit
authorization.
Do not create a recurring review or reminder unless the user asks.
Daily Standup and Journal next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
Daily Standup and Journal compared with similar skills
Skill
Stars
Used in
Tokens
Auto-check
Licence
Repo updated
Daily Standup and Journal this skilliflytek/skillhub
Run a 复盘 (fupan), the structured project review widely used in Chinese companies: review the goal, assess the result, analyse why, and draw rules for next time, with a blame-free tone and owned…
Generates daily reports, reflections, weekly reports, self-reviews and trend insights, in Japanese, from Claude Code, Codex and opencode session logs using the nippo CLI.
Audits and rewrites formulaic, AI-sounding prose while keeping facts, voice and format, using a local Python scorer and inspect-only, rewrite or embedded-gate modes.
Access 2,000+ AI models and API tools through one MCP interface for inference, media generation, search, scraping, embeddings, social data, and structured retrieval.
Drafts a copy-paste-ready LinkedIn post from your facts and ideas, choosing the smallest structure that fits and keeping an accessible plain-text fallback for any styled text.
Produces short daily standups, evening reflections and weekly retrospectives for one person or a small team, kept in the session unless you name a place to save. Four session types are offered: a solo workday check-in with prompts about commitments, distractions, things to defer, energy and a success metric; an asynchronous team standup covering yesterday, today and blockers; an evening reflection on what went well, what was hard and what was learned; and a weekly retrospective with wins and losses and an optional energy map.
When should I use Daily Standup and Journal?
Daily Standup and Journal fits situations like: planning a workday with a short solo check-in; writing an async team standup that surfaces blockers; reflecting on the day in the evening; running a weekly retrospective for yourself or a small team.
How do I install Daily Standup and Journal in Claude Code?
Run `npx skills add iflytek/skillhub --skill daily-standup-journal -a claude-code`. Or copy the skill folder (builtin-skills/skills/daily-standup-journal in iflytek/skillhub) into .claude/skills/daily-standup-journal in your project. Claude Code loads it when a task matches its description.
How do I install Daily Standup and Journal in Codex?
Run `npx skills add iflytek/skillhub --skill daily-standup-journal -a codex`. Or copy the skill folder (builtin-skills/skills/daily-standup-journal in iflytek/skillhub) into .agents/skills/daily-standup-journal in your project. Codex loads it when a task matches its description.
Can I use Daily Standup and Journal in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add iflytek/skillhub --skill daily-standup-journal -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/daily-standup-journal, .gemini/skills/daily-standup-journal, .github/skills/daily-standup-journal and .opencode/skills/daily-standup-journal in your project.
What does Daily Standup and Journal need to run?
SKILL.md names no scripts, command-line tools or credentials: Daily Standup and Journal is instructions for the agent only.
Does Daily Standup and Journal access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Daily Standup and Journal safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Daily Standup and Journal use?
Daily Standup and Journal is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Daily Standup and Journal use?
About 1.9k tokens (SKILL.md is roughly 7.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Daily Standup and Journal?
Skills that share tags, products or a category with Daily Standup and Journal: Cn Fupan (mohitagw15856/pm-claude-skills, 1.4k stars), Daily Journal (ravila4/claude-adhd-skills, 158 stars), Gitea Workflow (jwynia/agent-skills, 170 stars) and Nippo Daily Report Generator (nwiizo/nippo, 180 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Daily Standup and Journal?
iflytek (a GitHub organization) maintains it in iflytek/skillhub, which has 5,165 GitHub stars. The repository holds 29 skills in this directory. The repository was last updated on October 10, 2026.
Source: iflytek/skillhub on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.