report-package
starsforks
How to install report-package?
rlaope/oh-my-hermes/report-package
$npx -y skills add rlaope/oh-my-hermes --skill report-package[omh] Hermes Report Package workflow: weekly/monthly reports, executive briefs, PPT-ready outlines, and upload packages.
SKILL.md
| 1 | # Report Package |
| 2 | |
| 3 | This is a Hermes-native `report-package` workflow skill. |
| 4 | |
| 5 | ## Why This Exists |
| 6 | |
| 7 | `report-package` exists to make reporting a first-class operations surface: Hermes can produce clean report and slide outlines while keeping approvals, delivery, and binary deck export as separate evidence. |
| 8 | |
| 9 | ## Do Not Use When |
| 10 | |
| 11 | - The user needs SLO, incident, or error-budget review; use `reliability-review`. |
| 12 | - The user asks for a live `.pptx` deck file rather than a PPT-ready outline. |
| 13 | - The request is meeting minutes, scrum history, or action-item tracking. |
| 14 | |
| 15 | ## Examples |
| 16 | |
| 17 | Good example: |
| 18 | |
| 19 | - Prompt: report-package 월간 리더십 보고서 PPT outline 만들어줘. |
| 20 | - Expected behavior: Prepare a report package with sections, assumptions, missing inputs, and Markdown/JSON outline scope. |
| 21 | - Why: The request is packaging known information for reporting, not reliability validation or code work. |
| 22 | |
| 23 | Bad example: |
| 24 | |
| 25 | - Prompt: report-package prove our SLO passed and close the incident. |
| 26 | - Expected behavior: Route to `reliability-review` and require metric or incident evidence. |
| 27 | - Why: Report packaging cannot satisfy reliability closure evidence. |
| 28 | |
| 29 | ## Completion Checklist |
| 30 | |
| 31 | - The reporting window, inputs, audience, narrative, and evidence gaps are named. |
| 32 | - Draft report, generated package, approval, and delivery are separate states. |
| 33 | - The next action says whether to gather evidence, generate, revise, approve, or deliver. |
| 34 | |
| 35 | ## Recovery Notes |
| 36 | |
| 37 | - If input evidence is incomplete, mark the section as pending rather than fabricating a report claim. |
| 38 | - If delivery or attachment is unavailable, keep the report package prepared_not_observed. |
| 39 | |
| 40 | ## OMH Context Rail |
| 41 | |
| 42 | - This skill is part of OMH's Hermes workflow layer, not a standalone executor. |
| 43 | - Product context: OMH is a Hermes-native workflow pack: choose skills, shape work, prepare artifacts, show status, and hand off with evidence boundaries. |
| 44 | - Current lane: **Materials and visual summaries** (`design-orchestration`, `design-quality-gate`, `frontend`, `accessibility-audit`, `visual-qa`, `content-operator`, `media-input-operator`, `materials-package`, `+3 more`) - web, accessibility, visual QA, files, and packages. |
| 45 | - If the user intent belongs to another OMH lane, hand back to `oh-my-hermes` or name the adjacent workflow instead of force-fitting this skill. |
| 46 | - Cross-skill context: every OMH skill: match lane; generic tool can render or execute. |
| 47 | - Generic-tool checkpoint: image->img-summary; frontend->frontend/a11y/visual-qa; paper->paper-learning; content->content-operator; media->media-input-operator; file->materials-package; search->web-research; live->live-info-operator; audit->workspace/production/security; failures->build-failure; verify->verification-gate; code->codegraph/onboarding/ultraprocess. |
| 48 | - Coverage: Every generated workflow skill carries this rail. |
| 49 | - Normal users talk to Hermes; OMH CLI is infra. |
| 50 | - Boundary: Prepared OMH routing, cards, handoffs, or artifacts are not observed execution, image generation, delivery, review, CI, merge-readiness, or merge evidence. |
| 51 | |
| 52 | ## Use When |
| 53 | |
| 54 | Use when Hermes should turn supplied inputs into a report, executive brief, PPT-ready outline, or upload package without claiming presentation delivery. |
| 55 | |
| 56 | Strong routing signals: `report-package`, `report package`, `weekly report`, `monthly report`, `executive report`, `exec brief`, `leadership deck`, `status package`, `ppt outline`, `presentation outline`, `slide outline`, `upload package`, `보고서 패키지`, `주간 보고서`, `월간 보고서`, `경영진 보고`, `리더십 보고`, `PPT`, `피피티`, `슬라이드`, `발표자료`, `업로드 패키지` |
| 57 | |
| 58 | ## Catalog Metadata |
| 59 | |
| 60 | Category: `reporting` |
| 61 | Phase: `package-outline` |
| 62 | Hermes role: `operator` |
| 63 | Quality tier: `report-gated` |
| 64 | |
| 65 | Quality bar: |
| 66 | |
| 67 | - Name audience, reporting period, sections, supplied facts, assumptions, and missing data. |
| 68 | - Keep report packaging independent from reliability review unless explicitly requested. |
| 69 | - Export only Markdown/JSON outlines unless a separate presentation tool produces a binary deck. |
| 70 | |
| 71 | Handoff policy: |
| 72 | |
| 73 | Keep report narrative, sectioning, and Markdown/JSON outline packaging in Hermes; do not require reliability evidence unless the user asks for a reliability review. |
| 74 | |
| 75 | Required inputs: |
| 76 | |
| 77 | - audience |
| 78 | - reporting period or scope |
| 79 | - supplied facts |
| 80 | - missing data or assumptions |
| 81 | |
| 82 | Expected outputs: |
| 83 | |
| 84 | - report package |
| 85 | - PPT-ready Markdown or JSON outline |
| 86 | - assumptions and missing-input list |
| 87 | - optional achievements badge section sourced from `omh achievements export --format md` when requested |
| 88 | |
| 89 | Artifact expectations: |
| 90 | |
| 91 | - operation_artifact/v1 report-package artifact when a wrapper or CLI records it |
| 92 | |
| 93 | Safety rules: |
| 94 | |
| 95 | - Do not claim source review completion from a prepared report package. |
| 96 | - Do not claim stakeholder approval |
People who liked this also viewed
6 picksType
- find-skillsHelps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skSkillsJul 2026
- grill-meA relentless interview to sharpen a plan or design.SkillsJul 2026
- vercel-react-best-practicesVercel's official collection of agent skillsSkillsJul 2026
- improve-codebase-architectureScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.SkillsJul 2026
- setup-matt-pocock-skillsConfigure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.SkillsJul 2026
- triageMove issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.SkillsJul 2026
