Internship Daily Reflection

v1.0.0

将实习中的零散记录、聊天片段和任务笔记整理成可直接粘贴的中文日报或进展汇报。适用于写日报、整理今天任务、发给导师或 leader 的进展同步,以及填写“计划阶段、汇报阶段、进展状态、进展情况、问题及原因”等固定字段。

1· 90·0 current·0 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for npccxx/internship-daily-reflection.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Internship Daily Reflection" (npccxx/internship-daily-reflection) from ClawHub.
Skill page: https://clawhub.ai/npccxx/internship-daily-reflection
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install internship-daily-reflection

ClawHub CLI

Package manager switcher

npx clawhub@latest install internship-daily-reflection
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The name/description, SKILL.md, index.js, templates, and examples all implement the stated purpose (organize notes into Chinese reports). No unrelated dependencies, env vars, or binaries are required.
Instruction Scope
SKILL.md narrowly describes how to parse input, ask up to four follow-up questions if data is missing, and produce two templates. The runtime code follows that: it builds a prompt and either calls the provided runtime model or falls back to a local renderer. Instructions do not ask to read files or environment variables outside the provided inputs.
Install Mechanism
There is no install spec or remote download. The package contains a small index.js and supporting markdown files; nothing is fetched from external URLs or written to unexpected locations.
Credentials
The skill requires no environment variables, keys, or config paths. The code optionally uses a provided runtime model client via the context (model.generate / model.complete), which is expected for an LLM-backed skill.
Persistence & Privilege
always is false, the skill is user-invocable, and model invocation is enabled (normal). The skill does not modify other skills or system settings and does not request persistent privileges.
Assessment
This skill appears to do exactly what it says: organize scattered internship notes into structured Chinese reports and ask follow‑ups when needed. It does not request credentials or download code. Note that it will call the agent's runtime model (context.model) when available — so outputs depend on that model and could still contain subtle inaccuracies or hallucinations. If you will feed sensitive or private content into the skill, be aware the content may be included in prompts sent to your runtime model provider. Otherwise it is coherent and proportionate to its purpose.

Like a lobster shell, security has layers — review code before you run it.

Runtime requirements

📝 Clawdis
latestvk97dh04jqj3513tc3ynkb5qw5584s5dc
90downloads
1stars
1versions
Updated 2w ago
v1.0.0
MIT-0

Internship Daily Reflection

适用场景

当用户需要以下内容时,使用本技能:

  • 日报、站会更新、实习进展同步
  • 将零散聊天记录/笔记整理成结构化汇报
  • 准备发给导师、leader 的当日进展说明
  • 填写带固定字段的汇报系统(如“进展情况/问题及原因”)

工作流程

  1. 先识别输入材料:任务清单、聊天片段、提交记录、学习笔记。
  2. 提取事实并去重:做了什么、进度如何、问题是什么、原因是什么。
  3. 优先输出“汇报系统字段版”,保证可以直接粘贴。
  4. 若关键信息缺失,先追问再输出。

缺失信息追问

当以下信息缺失时,最多追问 4 个关键问题:

  • 计划阶段(例如:4月2周)和汇报阶段(例如:周一)是什么?
  • 进展状态是“正常推进 / 推进滞后 / 已完成”中的哪一个?
  • 进展情况里最关键的 2-4 个事实是什么?
  • 是否存在“问题及原因”?如果有,分别是什么?

如果用户不补充,明确标注“待补充”,不要编造事实。

输出要求

  • 默认语言:中文
  • 风格:复盘成长型(不止描述结果,也说明问题与改进)
  • 语气:专业、清晰、可直接转发给导师或 leader
  • 优先使用可验证表述(避免夸张、避免空话)
  • 当用户明确说“填系统/表单”时,只输出字段内容,不附加长解释

固定输出模板(汇报系统字段版)

优先按以下结构输出,字段名与系统保持一致:

汇报单位:<默认沿用用户提供;未知则写“待补充”>
计划阶段:<如 4月2周>
汇报阶段:<如 周一>
进展状态:<正常推进/推进滞后/已完成>

进展情况:
1) <任务或子目标>:<动作>,<结果/产出>。
2) <任务或子目标>:<动作>,<结果/产出>。
3) <如有明日安排,可写下一步>。

问题及原因:
- <问题1>:<原因>;<当前影响/处理状态>。
- <问题2>:<原因>;<当前影响/处理状态>。

(可选)汇报附件:
- <文件名或链接;无则写“无”>

备用输出模板(聊天汇报版)

如果用户明确不要字段版,再使用这个结构:

# 实习日报(YYYY-MM-DD)
## 1) 今日完成事项
## 2) 项目进度
## 3) 问题与阻塞
## 4) 解决方案与尝试
## 5) 时间投入
## 6) 明日计划

针对智能体/OpenClaw/Skill 学习的增强规则

如果内容涉及智能体、OpenClaw、Skill 学习,补充一段简短学习复盘:

  • 今日新概念:学到了什么
  • 实操进展:完成了哪一步部署/配置/调试
  • 卡点与原因:环境、配置、依赖或理解问题
  • 明日突破点:下一步最关键动作

将该段优先合并到“进展情况”与“问题及原因”中,避免字段过多导致无法粘贴表单。

示例触发语

  • “帮我把今天实习内容整理成日报”
  • “我笔记很乱,整理成能发给导师的进展更新”
  • “这是我今天做的 openclaw 学习记录,帮我总结”
  • “按汇报系统格式帮我生成:计划阶段、汇报阶段、进展状态、进展情况、问题及原因”

Comments

Loading comments...