shield_lock
JinDaGe
← Back to skills
extension
Category: Data & AnalyticsNo API key required

dayflow-source

Extract and normalize local Dayflow activity data into a compact evidence package for Daily Notes, weekly reports, work reviews, focus audits, or activity summaries. Use when Codex needs Dayflow timeline cards for a date range while keeping private paths, screenshots, credentials, and account identifiers out of outputs.

personAuthor: user_82d22b66hubcommunity
downloadDownload package

Dayflow Source

Use this skill as the data collection layer for Dayflow. It reads local Dayflow timeline cards, produces a bounded evidence package, and leaves interpretation or note writing to the caller.

Do not write or update notes from this skill alone.

Use Cases

  • Gather evidence for a Daily Note, weekly review, or work retrospective.
  • Reconstruct a date-range activity summary from Dayflow timeline cards.
  • Provide timeline-card evidence to another reporting or review skill.
  • Check Dayflow coverage gaps before relying on an activity summary.

Workflow

  1. Follow any local repository or vault instructions if the caller provides them.
  2. Determine the date range:
    • Daily review: one day, YYYY-MM-DD.
    • Weekly review: Monday through the requested end date.
    • Use another range only when the user gives it.
  3. Query Dayflow with scripts/query_dayflow.py:
python3 scripts/query_dayflow.py --start YYYY-MM-DD --end YYYY-MM-DD --format markdown

If running from outside the skill directory, use the installed path, for example:

python3 ~/.codex/skills/dayflow-source/scripts/query_dayflow.py --start YYYY-MM-DD --end YYYY-MM-DD --format markdown
  1. If the database cannot be read because it is outside the sandbox, request approval instead of inventing activity.
  2. Summarize only what is supported by Dayflow timeline cards.
  3. Return the evidence package to the caller. If the user directly invoked this skill, show the package and stop.

Evidence Package Shape

Use this shape in prose or Markdown:

## Dayflow Evidence

- Date range: YYYY-MM-DD..YYYY-MM-DD
- Cards reviewed: N
- Coverage notes: complete | partial | unavailable

### Activity Clusters
- Project or theme: supported by HH:MM-HH:MM cards; confidence high/medium/low.

### Notable Cards
- YYYY-MM-DD HH:MM-HH:MM, title, short evidence summary.

### Gaps
- Missing Dayflow data, unclear project labels, or low-confidence inference.

Privacy Rules

  • Treat Dayflow as evidence, not truth by itself. Prefer "Dayflow suggests..." when the project mapping is inferred.
  • Keep raw screenshots, local file paths, private app titles, and sensitive details out of final notes unless the user explicitly asks.
  • Do not include credentials, tokens, cookies, account identifiers, or local database paths in user-facing output.
  • For public or shareable summaries, aggregate or redact activity titles that expose private clients, repositories, people, or accounts.
  • Do not use Dayflow to override explicit user-written note content. Surface conflicts to the caller.
  • Prefer compact clusters over copying the whole timeline into a note.

Data Reference

Read references/dayflow_schema.md only when you need schema details or need to adjust the query script.