القائمة
Use when the user says 'set up a report', 'create a digest', 'I want a daily/weekly summary of', 'monitor X and report on Y', or any request for scheduled information synthesis. Produces a Conductor workflow + rules for scheduled reports and digests.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when the user says 'when X happens, do Y', 'set up a rule for', 'react to', or any request to define an event-driven trigger. Produces a Conductor reaction rule YAML and saves it to ~/pantheon/conductor/rules/.
Use when the user says 'set up a webhook', 'connect X service to Pantheon', 'receive notifications from Y', or any request to bring external events into the Pantheon. Produces a webhook integration config and rule, saved to ~/pantheon/conductor/webhooks/ and ~/pantheon/conductor/rules/.
Use when the user says 'set up a pipeline', 'create a workflow', 'I need a multi-god process', or any request to chain multiple gods into a repeatable sequence. Produces a Conductor workflow YAML and saves it to ~/pantheon/conductor/workflows/.
Conductor handoff and acknowledgement protocol for Pantheon gods
Use after a design spec is written, before any implementation begins. Runs a structured assessment of holes, risks, pros/cons, system conflicts, overhead, and a go/no-go verdict. Must be completed before build handoff.
Use when the user says 'build Amber a skill', 'she needs something for X at the conference', 'make her a skill that does Y', 'package this up for her', 'design a skill for Amber', or any request to design, build, and ship a custom skill for Amber. The output is a fully packaged skill (zip file) ready to attach to Telegram and send to her agent for install. Designed to be invoked repeatedly as new conference needs come up.
| name | conductor-design-report |
| description | Use when the user says 'set up a report', 'create a digest', 'I want a daily/weekly summary of', 'monitor X and report on Y', or any request for scheduled information synthesis. Produces a Conductor workflow + rules for scheduled reports and digests. |
| version | 1.0.0 |
| author | Thoth & Hermes (Pantheon) |
| license | MIT |
| metadata | {"hermes":{"tags":["conductor","report","digest","schedule","cron","monitoring"],"related_skills":["conductor-design-rule","conductor-design-workflow"]}} |
Load this skill when the user wants a recurring summary of information. Keywords: "report," "digest," "daily briefing," "weekly summary," "monitor X," "keep an eye on."
Ask:
Scheduled reports are just Conductor workflows triggered by a cron rule.
# workflows/daily-morning-briefing.yaml
workflow:
id: daily-morning-briefing
name: "Daily Morning Briefing"
version: "1.0.0"
description: "Compile and deliver a daily summary of Pantheon activity"
triggers:
- type: schedule
expression: "0 7 * * 1-5" # Weekdays at 7 AM
steps:
- id: gather
god: thoth
skill: dawn-patrol
action: compile_digest
timeout: 15m
- id: format
god: hermes
skill: summarize
input_from: gather
timeout: 5m
- id: deliver
type: notify
method: telegram
input_from: format
# rules/daily-briefing.yaml
rules:
- id: daily-morning-briefing
when:
event_type: schedule.cron
expression: "0 7 * * 1-5"
then:
handling_mode: notify_and_log
action: dispatch_workflow
workflow: daily-morning-briefing
Two files:
~/pantheon/conductor/workflows/{report-id}.yaml~/pantheon/conductor/rules/{report-id}-schedule.yaml