Agent showcaseStudy Bulletin
SHOWCASE · STATIC PAGE

Learning updates,
timely and sourced.

The Study Bulletin Coordinator helps a group see what matters first: deadlines, schedule changes, assignments, and new learning materials—in one concise, verifiable bulletin.

This is a static showcase. It is not connected to Hermes, Lark, or any API. A direct-message test received a reply; posting and pinning a bulletin in a group have not been verified.

Structure example
Study bulletin · Preview

Weekly learning bulletin

Layout example · not a live result

!
Priority: deadlines & changesDate and time · owner · required action
2
Learning updatesNew assignments · coursework · materials
3
Reference materialsNewest items appear last
↗ Source links appear beside each item
Profilestudy-bulletin
ReviewUser approval required
Lark direct-message testReply received
Group posting & scheduleNot verified

A direct message was routed to the Agent and received a reply. Posting or pinning a bulletin in a group has not been tested. The Sunday 8:00 p.m. schedule and `[URGENT]` trigger have not been verified as running automatically.

Capabilities

Turn scattered updates into an actionable bulletin.

The Agent keeps information that is still relevant, identifies changes, and cites sources so the group can verify them.

Gather from multiple sources

Announcements, messages, links, and learning files from sources the Agent is authorized to access.

Compare changes

Compare deadlines, owners, and document versions; keep older items while their deadlines remain active.

Summarize with sources

Put urgent actions first, write concise action-oriented updates, and keep source links beside each item.

How it works

Seven steps, with a clear approval checkpoint.

The workflow stops at a draft until the user approves it. The `[URGENT]` label starts processing immediately but does not bypass approval.

Collect

New announcements, links, and learning materials from approved sources.

Extract

Requirements, deadlines, assignments, criteria, and key points from audio/video.

Detect changes

Compare dates, owners, and document versions.

Prioritize

Urgent items first; routine updates by recency.

Verify

Check facts against sources and validate links; flag anything unclear.

Draft the bulletin

Use a title and concise bullets for important actions, materials, and links.

User approval

Post or pin only after approval.

Confirm completion

Check posting/pinning status and archive completed items.

Priority order

Urgent information stays visible.

Group 1 · First

Urgent & important

Deadline changes, exams/tests, cancelled or make-up classes, and messages marked urgent.

Group 2 · Next

Updates to follow

Assignment changes, new supplementary materials from instructors, and new weekly coursework.

Group 3 · End

Routine updates

Reference links and everyday discussion, ordered from newest to oldest.

Preview

See the bulletin format.

The content below is prewritten to demonstrate the structure. It was not generated by an Agent run.

Sample bulletin

All content is illustrative and does not represent a real class or announcement.

Expand / collapse sample

WEEKLY SUMMARY BULLETIN — SAMPLE

Illustrative data · not published · not a live result

Priority 1[Verified deadline] — [Owner]: [Action required]. [Source link]
Priority 2[Assignment change or new learning material]. [Source link]
Materials[Material title] — [short description]. [Material link]
Before publicationThe user checks the facts and approves the draft. If `[NEEDS VERIFICATION]` remains, the Agent stops and does not post.

Standards & limits

What the Agent can and cannot do.

Agent SHOULD / MUST
  • ✓Verify deadlines, owners, tasks, and document versions against their sources.
  • ✓When deadline sources conflict, prefer the instructor's official notice and tell the user about the discrepancy.
  • ✓Mark missing details or inaccessible links as `[NEEDS VERIFICATION]`.
  • ✓Wait for approval before posting or pinning a bulletin.
Agent MUST NOT
  • ×Invent information beyond the sources or choose between conflicting versions without verification.
  • ×Bypass access controls or edit source documents or assignments.
  • ×Mediate heated disputes; leave the decision to the user.
  • ×Post or pin without approval or while verification issues remain.