← Back to Skills Marketplace
sopaco

Upward Reporting

by Sopaco · GitHub ↗ · v1.0.1 · MIT-0
cross-platform ✓ Security Clean
136
Downloads
0
Stars
0
Active Installs
2
Versions
Install in OpenClaw
/install upward-reporting
Description
职场汇报文档写作的总入口与路由。当用户说"写汇报"、"写文档"、"帮我写材料"但未明确场景时触发，帮助识别场景并路由到对应子skill。也提供所有汇报场景通用的风格规范和汇报对象适配指南。子skill：report-planning（规划汇报）、report-postmortem（故障复盘）、report-rev...
README (SKILL.md)

\r \r

upward-reporting — 汇报写作总入口\r

\r 本 skill 是所有职场汇报写作场景的路由入口，同时承载所有子场景共用的风格规范和范式选择指引。\r \r

场景路由\r

\r 当用户描述写作需求时，先判断场景，再加载对应子 skill（子 skill 文件位于本目录下）：\r \r | 用户说了什么 | 路由到 | 子 skill 路径 |\r |------------|-------|-------------|\r | 写规划、写方向、技术规划、团队规划、年度规划、部门汇报 | report-planning | report-planning/SKILL.md |\r | 故障复盘、事故总结、障碍分析、写改革计划、P0/P1复盘 | report-postmortem | report-postmortem/SKILL.md |\r | 年终述职、写述职、个人总结、晋升材料、绩效总结 | report-review | report-review/SKILL.md |\r | 晋升谈话、晋升面谈、1v1述职准备、向老板介绍自己、年终1on1 | report-review + 口头策略 | report-review/SKILL.md + 口头汇报策略 |\r | 横向协作、KO文档、拉通、项目启动会、跨团队对齐 | report-kickoff | report-kickoff/SKILL.md |\r | 写OKR、制定OKR、OKR进展、双周进展汇报、月度OKR、OKR复盘、KR拆解、写季度OKR | report-okr | report-okr/SKILL.md |\r \r

路由冲突解决\r

\r 当多个子场景的触发词重叠时，按以下优先级判断：\r \r

  1. 故障/事故关键词：提到"P0/P1/故障/事故/线上异常" → report-postmortem（优先级最高，故障复盘有紧迫性）\r
  2. OKR专用 vs 通用：提到"OKR/KR/O"且语境为制定/进展/复盘 → report-okr（即使语境模糊也优先OKR子skill）\r
  3. 晋升谈话 vs 常规述职：提到"晋升谈话/1v1/面谈准备/年终1on1" → report-review + oral-presentation-guide 组合（第一步加载 report-review 整理内容，第二步加载口头汇报策略准备表达）\r
  4. 个人 vs 团队：提到"我/个人/晋升/绩效/述职" → report-review；提到"团队/部门/方向/规划" → report-planning\r
  5. 横向协作关键词：提到"跨团队/拉通/对齐/KO/协作启动" → report-kickoff\r
  6. 无法判断：回到入口问题\r \r 如果场景不明确，先问以下问题再路由：\r \r
  7. 这份材料是给谁看的？（高层/大老板 / 直属上级 / 平级协作方 / 风控/财务等专业角色）\r
  8. 是什么场合？（例行规划 / 战略评审 / 事后复盘 / 述职评审 / 项目启动）\r
  9. 读者进来时的情绪预设是什么？（需要被说服 / 需要被安抚 / 在做评估 / 需要被拉动 / 需要核对数据）\r \r

核心原则：受众决定范式\r

\r 不同受众的信息需求和信任机制完全不同，这决定了写作范式选择：\r \r

  • 高层/大老板：缺时间，要结论和方案 → 命题驱动（"我认为选A方案，因为ROI最高。详细分析见附录"）\r
  • 直属上级/导师：需要理解你的思路 → 信息驱动（展示分析过程，末尾给出倾向判断，邀请讨论）\r
  • 平级/协作方：视目的而定 → 同步进度用信息驱动，请求配合用命题驱动\r
  • 风控/财务等专业审核：需要核对数据源头 → 信息驱动（必须展示完整推导链路）\r \r

详细决策矩阵见 受众→范式映射\r \r

范式选择提示\r

\r 路由到 report-planning 时，提醒用户：\r \r

规划汇报有两种写作范式：\r

  • 信息驱动：现状→问题→根因→趋势→目标→打法（适合需要展示推导过程的场景）\r
  • 命题驱动：核心命题→命题拆解→解决思路→关键问题与解法（适合需要快速给出判断的场景）\r \r 请确认你的汇报对象是谁，我来帮你选择最合适的范式。参考 受众适配指南\r \r 路由到 report-okr 时，先问以下问题再展开：\r \r 请确认是哪种OKR场景：\r
  • OKR制定：新周期开始，需要制定O/KR/KA\r
  • OKR进展汇报：周期中，反映双周/月度执行状态\r
  • OKR复盘：周期结束，总结达成和经验\r \r 路由到其他子 skill 时，不强制选择范式，但提醒用户考虑受众适配。

路由到 report-review + oral-presentation-guide（晋升谈话场景）时：

晋升谈话是述职内容和口头表达的双重准备。建议分两步：

  1. 先用 report-review 梳理内容——你要讲什么、判断是什么、成长是什么
  2. 再用 口头汇报策略 设计表达方式——15分钟版/开场30秒/Q&A准备\r \r

公共参考文件\r

\r 所有子场景均适用，但在不必要的情况下不要加载全部——参考条件化加载指引，按需读取对应文件：\r \r

  • 风格规范 — 语气、用词、禁用词、高级表达技法库、图表使用（写作全程可用，但不需要一次性读完）\r
  • 汇报对象适配 — 范式选择决策矩阵 + 不同层级/背景受众的适配策略（在 Step 1 确认受众后加载对应部分）\r
  • 口头汇报策略 — 不同时长内容适配、开场30秒、Q&A准备、讲述节奏、受众口头适配（仅在用户需要准备口头汇报时加载）\r
  • 技法适配参考 — 各子场景技法适配方式（仅在你帮用户撰写某章并需要决定技法使用方式时，按场景读取对应部分）\r
  • 技法详解 — 11种高级表达技法的完整说明（含示例、适用受众、常见陷阱）；通过技法适配参考确认需要某技法后，按编号按需读取
Usage Guidance
This skill is safe to use for drafting workplace reporting materials based on the provided artifacts. Avoid pasting unnecessary confidential company details, and review the final document source to remove hidden HTML comments or drafting notes before sharing.
Capability Analysis
Type: OpenClaw Skill Name: upward-reporting Version: 1.0.1 The 'upward-reporting' skill bundle is a comprehensive and well-structured set of instructions and templates designed to assist an AI agent in generating professional workplace documents, such as OKRs, technical plans, and post-mortems. The main entry point (SKILL.md) implements a logical routing system to direct the agent to specific sub-skills based on user intent. There is no evidence of malicious code, data exfiltration, unauthorized system access, or harmful prompt injection; all content is strictly aligned with the stated purpose of professional reporting and career development.
Capability Assessment
✓ Purpose & Capability
The artifacts coherently match the stated purpose: routing users to reporting-writing subskills and providing templates, style guidance, audience adaptation, OKR, postmortem, planning, review, and kickoff-document guidance.
ℹ Instruction Scope
Most instructions are scoped to drafting reports and asking clarifying questions. One reference recommends embedding illustration prompts as HTML comments in generated documents, which is disclosed but worth user review before sharing.
✓ Install Mechanism
There is no install spec, no code files, no required binaries, no environment variables, and no declared credentials.
✓ Credentials
The skill does not request local filesystem, network, shell, account, or credential access. It asks for business/reporting context that is proportionate to drafting the requested documents.
✓ Persistence & Privilege
No persistence, background agents, privilege escalation, memory storage, or autonomous account actions are shown in the provided artifacts.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install upward-reporting
  3. After installation, invoke the skill by name or use /upward-reporting
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.1
- 新增“晋升谈话/1v1/面谈准备/年终1on1”等口头汇报相关场景路由，支持内容与口头表达策略的双重准备 - 更新路由优先级，细化晋升谈话与述职场景区分，首次将 `report-review` 与口头汇报策略组合路由 - 明确晋升谈话操作建议：分两步梳理内容与设计表达方式 - 公共参考文件新增“技法详解”，指明加载时机与引导路径 - 文档表述优化，补充和细化场景关键词与适配流程
v1.0.0
- Initial version introducing an entry point and router for workplace reporting scenarios. - Automatically identifies reporting needs and routes to the appropriate subskill: planning, postmortem, review, kickoff, or OKR. - Resolves overlapping trigger keywords with a clear priority system to ensure accurate routing. - Provides universal writing style guidelines and an audience adaptation guide for all reporting types. - Includes scenario-specific guidance and suggests relevant writing paradigms based on the audience. - Conditional loading of reference materials for style, audience adaptation, oral presentation, and technique adaptation.
Metadata
Slug upward-reporting
Version 1.0.1
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 2
Frequently Asked Questions

What is Upward Reporting?

职场汇报文档写作的总入口与路由。当用户说"写汇报"、"写文档"、"帮我写材料"但未明确场景时触发，帮助识别场景并路由到对应子skill。也提供所有汇报场景通用的风格规范和汇报对象适配指南。子skill：report-planning（规划汇报）、report-postmortem（故障复盘）、report-rev... It is an AI Agent Skill for Claude Code / OpenClaw, with 136 downloads so far.

How do I install Upward Reporting?

Run "/install upward-reporting" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Upward Reporting free?

Yes, Upward Reporting is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Upward Reporting support?

Upward Reporting is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Upward Reporting?

It is built and maintained by Sopaco (@sopaco); the current version is v1.0.1.

More Skills
self-improving agent
Captures learnings, errors, and corrections to enable continuous improvement. Use when: (1) A command or operation fails unexpectedly, (2) User corrects Clau...
⬇ 463283 · by pskoett
Skill Vetter
Security-first skill vetting for AI agents. Use before installing any skill from ClawdHub, GitHub, or other sources. Checks for red flags, permission scope, and suspicious patterns.
⬇ 259410 · by spclaudehome
Polymarket
Query Polymarket prediction markets. Check odds, find trending markets, search events, track price movements.
⬇ 232503 · by joelchance
Self-Improving + Proactive Agent
Self-reflection + Self-criticism + Self-learning + Self-organizing memory. Agent evaluates its own work, catches mistakes, and improves permanently. Use when...
⬇ 200423 · by ivangdavila
Github
Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.
⬇ 191115 · by steipete
ontology
Typed knowledge graph for structured agent memory and composable skills. Use when creating/querying entities (Person, Project, Task, Event, Document), linkin...
⬇ 190156 · by oswalpalash

💬 Comments