How do I install the Eod Log skill?

Run npx skillmds@latest add apizanti-uxr/eod-log in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Eod Log safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Eod Log?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Eod Log free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Eod Log?

apizanti-uxr (@apizanti-uxr) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Eod Log by apizanti-uxr — Agent Skill

Name: Eod Log
Author: apizanti-uxr

Eod Log

End-of-day log. Requires all five MCPs healthy first (mcp-healthcheck). Gathers today's calendar, Drive transcripts, Jira, and Slack, scores items, writes to the local wiki created by daily-rituals, and asks once about Jira actions. Use when called by daily-rituals /eod.

apizanti-uxr Updated Sep 22, 2026

File contents

EOD Log

Runs after the MCP gate. Pause only at Step 5 (Jira actions).

Read ~/.cursor/skills/daily-rituals/sources.md first. If the wiki root does not exist, read and execute ~/.cursor/skills/daily-rituals/SKILL.md (first-run wiki create) before listing Drive files.

Step 0 — Verify all MCPs (hard gate)

Read and execute ~/.cursor/skills/mcp-healthcheck/SKILL.md before listing Drive files or scraping.

Any still down → report and stop. Do not write the wiki. All five healthy → continue.

Step 0.5 — List today's Drive files

search_drive_files(
  query: (createdTime >= startOfToday OR modifiedTime >= startOfToday) AND trashed = false,
  order_by: modifiedTime desc,
  page_size: 20
)

Present the list and ask which to ingest (none / all / skip / numbers). For each selected file: ~/.cursor/skills/daily-rituals/SKILL.md → /ingest [url].

Step 1 — Gather in parallel

Calendar — get_events(today, detailed: true): include accepted + organizer; exclude declined.

Drive — same search as 0.5; get_doc_as_markdown for each. Read only.

Jira — assignee = currentUser() AND updated >= startOfDay()

Slack — from:YOUR_SLACK_USERNAME after:<today> (username from sources.md). Group by thread; flag commitments.

Step 2 — Score (1–5)

Start at 1. Cap at 5.

Signal	Boost
External stakeholder / customer	+2
Senior teammate in the meeting or thread	+1
Deliverable shipped (Jira Done/Review, doc shared)	+2
Decision with rationale	+1
Sprint ticket touched (`YOUR_JIRA_PROJECT` from sources)	+1
Session ended blocked or open	+1
Carry-forward again	+1 per day
Pure admin / scheduling	−1

4–5 → [IMPORTANT].

Step 2.5 — Carry-forward

Read <wiki-root>/log/daily.md — yesterday's EOD.
Items in progress / blocked / unclear.
Resolved today → resolved. Else increment DAY N; DAY 3+ → score 5 and #stale.
Unmentioned 2+ days and not #blocked → auto-closed.

Step 3 — Write the log

Append at the top of <wiki-root>/log/daily.md:

## YYYY-MM-DD

### EOD

**Signal:** N important items

**Summary:** [1 sentence]

**Meetings:**
- [title] — [outcome] [score: N/5]

**Jira:**
- [KEY-XXX] — [what changed]

**Drive:**
- [title] — [what happened] [link]

**Slack:**
- [who] → [commitment]

**Decisions:**
- [decision] | [why] | [alternatives]

**Carry Forward:**
- [DAY N] [item]

**Tomorrow's focus:** [1 thing]

Step 4 — Ref pages

For each log item, create or update under <wiki-root>/ref/ per daily-rituals cross-linking. Update index.md.

Step 5 — Jira actions (only pause)

EOD logged. Wiki updated.

JIRA — anything to do before tomorrow?
[suggested ticket actions]

Say yes, no, or describe what to update. (or skip)

Use Atlassian MCP to edit, comment, or transition. For a new ticket, create it via the Atlassian MCP (do not assume a company-specific ticket skill).

Step 6 — Report

Wiki files written, important items, carry-forwards, sources skipped.

Fallback

Do not write an EOD if any of the five MCPs are down.

If a query fails after a passed gate, note it in SOURCES SKIPPED and continue.

---name: eod-logdescription: End-of-day log. Requires all five MCPs healthy first (mcp-healthcheck). Gathers today's calendar, Drive transcripts, Jira, and Slack, scores items, writes to the local wiki created by daily-rituals, and asks once about Jira actions. Use when called by daily-rituals /eod.---# EOD LogRuns after the MCP gate. Pause only at Step 5 (Jira actions).Read `~/.cursor/skills/daily-rituals/sources.md` first.If the wiki root does not exist, read and execute`~/.cursor/skills/daily-rituals/SKILL.md` (first-run wiki create) beforelisting Drive files.---## Step 0 — Verify all MCPs (hard gate)Read and execute `~/.cursor/skills/mcp-healthcheck/SKILL.md` before listingDrive files or scraping.**Any still down** → report and **stop**. Do not write the wiki.**All five healthy** → continue.---## Step 0.5 — List today's Drive files```search_drive_files( query: (createdTime >= startOfToday OR modifiedTime >= startOfToday) AND trashed = false, order_by: modifiedTime desc, page_size: 20)```Present the list and ask which to ingest (`none` / `all` / `skip` / numbers).For each selected file: `~/.cursor/skills/daily-rituals/SKILL.md` → `/ingest [url]`.---## Step 1 — Gather in parallel**Calendar** — `get_events(today, detailed: true)`:include `accepted` + organizer; exclude `declined`.**Drive** — same search as 0.5; `get_doc_as_markdown` for each. Read only.**Jira** — `assignee = currentUser() AND updated >= startOfDay()`**Slack** — `from:YOUR_SLACK_USERNAME after:<today>` (username from `sources.md`).Group by thread; flag commitments.---## Step 2 — Score (1–5)Start at 1. Cap at 5.| Signal | Boost ||--------|-------|| External stakeholder / customer | +2 || Senior teammate in the meeting or thread | +1 || Deliverable shipped (Jira Done/Review, doc shared) | +2 || Decision with rationale | +1 || Sprint ticket touched (`YOUR_JIRA_PROJECT` from sources) | +1 || Session ended blocked or open | +1 || Carry-forward again | +1 per day || Pure admin / scheduling | −1 |4–5 → **[IMPORTANT]**.---## Step 2.5 — Carry-forward1. Read `<wiki-root>/log/daily.md` — yesterday's EOD.2. Items `in progress` / `blocked` / `unclear`.3. Resolved today → `resolved`. Else increment DAY N; DAY 3+ → score 5 and `#stale`.4. Unmentioned 2+ days and not `#blocked` → `auto-closed`.---## Step 3 — Write the logAppend at the **top** of `<wiki-root>/log/daily.md`:```markdown## YYYY-MM-DD### EOD**Signal:** N important items**Summary:** [1 sentence]**Meetings:**- [title] — [outcome] [score: N/5]**Jira:**- [KEY-XXX] — [what changed]**Drive:**- [title] — [what happened] [link]**Slack:**- [who] → [commitment]**Decisions:**- [decision] | [why] | [alternatives]**Carry Forward:**- [DAY N] [item]**Tomorrow's focus:** [1 thing]```---## Step 4 — Ref pagesFor each log item, create or update under `<wiki-root>/ref/` per daily-ritualscross-linking. Update `index.md`.---## Step 5 — Jira actions (only pause)```EOD logged. Wiki updated.JIRA — anything to do before tomorrow?[suggested ticket actions]Say yes, no, or describe what to update. (or skip)```Use Atlassian MCP to edit, comment, or transition. For a new ticket, createit via the Atlassian MCP (do not assume a company-specific ticket skill).---## Step 6 — ReportWiki files written, important items, carry-forwards, sources skipped.---## FallbackDo not write an EOD if any of the five MCPs are down.If a query fails after a passed gate, note it in SOURCES SKIPPED and continue.

Frequently asked questions