Run any Skill in Manus with one click

Get Started

edge-ic-daily-report

Stars7

Forks14

UpdatedMay 13, 2026 at 15:19

Generate daily standup report from TODO file in Slack-ready format

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

openshift-eng

openshift-eng/edge-tooling

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Secretaries and Administrative Assistants, Except Legal, Medical, and ExecutiveOffice and Administrative Support Occupations·SOC 43-6014

SKILL.md

readonly

name	edge-ic:daily-report
description	Generate daily standup report from TODO file in Slack-ready format
allowed-tools	["Read","Write","Bash"]
user-invocable	true

IC: Daily Report

Generate a daily standup report from today's TODO file in Slack-ready format.

Task

Read today's TODO file ($HOME/.daily/YYYY/MM/YYYY-MM-DD.md) and generate a daily report following the format specified in plugins/edge-ic/references/DAILY_REPORT_FORMAT.md.

Instructions

Read the format specification from plugins/edge-ic/references/DAILY_REPORT_FORMAT.md
Read today's TODO file from $HOME/.daily/YYYY/MM/ using today's date
Parse all sections systematically (read every item from TODO file):
- Completed section: Parse EVERY completed item
- In Sprint (Blocked/Waiting): Parse ALL blocked items
- In Sprint (Available to Work): Parse ALL in-progress items
Consolidate into report bullets (group related items together):
- Group related completed items together where appropriate
- Combine multiple Jira tickets for the same work into one bullet (e.g., TICKET-123, TICKET-456: Description)
- Keep bullets high-level and avoid excessive detail
Generate the report with:
- Header line at the top for /copy command alignment
- :done-circle-check: for completed items
- :in-progress: for in-progress items
- :jira-blocker: for blocked items
- Concise descriptions
- Jira tickets: TICKET-ID: Description (https://redhat.atlassian.net/browse/TICKET-ID)
- Multiple tickets: TICKET-123, TICKET-456: Description (https://redhat.atlassian.net/browse/TICKET-123, https://redhat.atlassian.net/browse/TICKET-456)
Render as plain text ready for Slack
Validate format:
- Write report to temporary file (e.g., /tmp/daily-report-YYYY-MM-DD.txt)
- Run validation: plugins/edge-ic/bin/validate-daily-report.sh /tmp/daily-report-YYYY-MM-DD.txt
- Fix any errors reported by the validator
- Address warnings as best effort
Check with user before finalizing:
- Ask if there are any additional updates or items to include
- Ask if any bullets need revision or consolidation
- Confirm report is ready to post
After report is accepted, prompt user:
- "Would you like me to update any Jira tickets based on today's progress?"
- Offer to update status, add comments, or transition tickets as needed

Important

CRITICAL Guardrails:

Completeness: Include ALL completed items, in-progress items, and blocked items from the TODO file
Consolidation: Group similar items into single high-level bullets - avoid excessive detail
Validation: Run plugins/edge-ic/bin/validate-daily-report.sh and fix any errors, address warnings as best effort
User Confirmation: Always check with the user for additional updates before finalizing the report

This is a systematic translation task with intelligent consolidation, not a summarization task that omits items.

Example Output Format

Daily Report:

:done-circle-check: Updated weekly team report with risks across components
:done-circle-check: PROJECT-100: Both PRs merged - issue resolved (https://redhat.atlassian.net/browse/PROJECT-100)
:in-progress: PROJECT-102: IPv4 testing pending for network fix

More from this repository

same repository

edge-ic-morning

openshift-eng/edge-tooling

Surface your daily task list — QA-ready tickets, sprint backlog, carry-over items, open PRs, RHEL verification queue, and quarterly reminders. Use at the start of your day to see what needs attention.

2026-07-097

edge-ic-task-info

openshift-eng/edge-tooling

Show detailed info about a specific TODO task — its tracked links, notes, and live Jira/PR status. Use when the user asks about a task, wants context to resume work on it, or asks what's needed to finish a ticket. Not for listing all tasks (read the TODO file directly or use edge-ic:sprint-status for sprint-wide views)

2026-07-097

edge-ic-weekly-wrapup

openshift-eng/edge-tooling

End-of-week automation - review active work and prepare next week's TODO

2026-07-097

microshift-release-automated-testing

openshift-eng/edge-tooling

Run the full Prow CI release testing workflow — create PR, trigger jobs, check status, merge PR, download and upload artifacts

2026-07-097

microshift-ci-job-pcp-dashboard

openshift-eng/edge-tooling

Generate interactive PCP performance dashboard from a Prow job URL

2026-07-027

lvms-ci-prow-job

openshift-eng/edge-tooling

Download Prow job artifacts, identify root cause of failure, and produce a structured error report

2026-06-307

IC: Daily Report

Generate a daily standup report from today's TODO file in Slack-ready format.

Task

Read today's TODO file ($HOME/.daily/YYYY/MM/YYYY-MM-DD.md) and generate a daily report following the format specified in plugins/edge-ic/references/DAILY_REPORT_FORMAT.md.

Instructions

Read the format specification from plugins/edge-ic/references/DAILY_REPORT_FORMAT.md

Read today's TODO file from $HOME/.daily/YYYY/MM/ using today's date

Parse all sections systematically (read every item from TODO file):

Completed section: Parse EVERY completed item
In Sprint (Blocked/Waiting): Parse ALL blocked items
In Sprint (Available to Work): Parse ALL in-progress items

Consolidate into report bullets (group related items together):

Group related completed items together where appropriate
Combine multiple Jira tickets for the same work into one bullet (e.g., TICKET-123, TICKET-456: Description)
Keep bullets high-level and avoid excessive detail

Generate the report with:

Header line at the top for /copy command alignment
:done-circle-check: for completed items
:in-progress: for in-progress items
:jira-blocker: for blocked items
Concise descriptions
Jira tickets: TICKET-ID: Description (https://redhat.atlassian.net/browse/TICKET-ID)
Multiple tickets: TICKET-123, TICKET-456: Description (https://redhat.atlassian.net/browse/TICKET-123, https://redhat.atlassian.net/browse/TICKET-456)

Render as plain text ready for Slack

Validate format:

Write report to temporary file (e.g., /tmp/daily-report-YYYY-MM-DD.txt)
Run validation: plugins/edge-ic/bin/validate-daily-report.sh /tmp/daily-report-YYYY-MM-DD.txt
Fix any errors reported by the validator
Address warnings as best effort

Check with user before finalizing:

Ask if there are any additional updates or items to include
Ask if any bullets need revision or consolidation
Confirm report is ready to post

After report is accepted, prompt user:

"Would you like me to update any Jira tickets based on today's progress?"
Offer to update status, add comments, or transition tickets as needed

Important

CRITICAL Guardrails:

Completeness: Include ALL completed items, in-progress items, and blocked items from the TODO file

Consolidation: Group similar items into single high-level bullets - avoid excessive detail

Validation: Run plugins/edge-ic/bin/validate-daily-report.sh and fix any errors, address warnings as best effort

User Confirmation: Always check with the user for additional updates before finalizing the report

This is a systematic translation task with intelligent consolidation, not a summarization task that omits items.

Example Output Format

Daily Report: :done-circle-check: Updated weekly team report with risks across components :done-circle-check: PROJECT-100: Both PRs merged - issue resolved (https://redhat.atlassian.net/browse/PROJECT-100) :in-progress: PROJECT-102: IPv4 testing pending for network fix