ClawHub

Summary Time

v1.0.3

Use this skill when the user wants the current local time written into a.txt in the current workspace directory, then wants the agent to fetch www.bytedance....

⭐ 0· 132·0 current·0 all-time
by@plusplus7

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for plusplus7/summary-time.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Summary Time" (plusplus7/summary-time) from ClawHub.
Skill page: https://clawhub.ai/plusplus7/summary-time
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 summary-time

ClawHub CLI

Package manager switcher

npx clawhub@latest install summary-time
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
The name/description match the SKILL.md steps. No environment variables, binaries, or installs are requested that would be unrelated to writing files and performing a single web fetch.
✓
Instruction Scope
Instructions are narrowly scoped: get local time via a system tool, write a.txt, call web_fetch on the single specified host, summarize to b.txt, and leave both files. The skill does not instruct reading other files, reading environment variables, or sending data to third-party endpoints beyond the specified web_fetch host.
✓
Install Mechanism
No install spec and no code files; this is instruction-only so nothing is added to disk at install time beyond the runtime writes in the current workspace.
✓
Credentials
No credentials or environment variables are required. The requested actions (local time and a web fetch) do not need secrets or elevated access.
✓
Persistence & Privilege
always:false and the skill does not request persistent system-wide privileges or modify other skills. It will write/overwrite a.txt and b.txt in the current workspace when invoked.
Assessment
This skill is internally consistent and low-risk: it will overwrite or create a.txt and b.txt in the current workspace and perform a single web fetch to www.bytedance.com. Before installing, confirm you are comfortable with (1) the agent having permission to write in the current workspace (it will overwrite those filenames), and (2) the agent fetching external web content (the fetched page may contain arbitrary data that the agent will summarize). The skill requests no credentials and has no install steps. If you do not want network access or file writes, do not enable the skill or restrict the workspace used.

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

latestvk974krp5084dthgj7x3cmw7z8583n82m
132downloads
0stars
4versions
Updated 1mo ago
v1.0.3
MIT-0
@plusplus7
latest
Download

Summary Time Keep

Overview

This skill performs a tiny filesystem action sequence in the current workspace directory. It writes the current local timestamp into a.txt, then uses web_fetch to inspect www.bytedance.com, writes a concise summary of the returned content into b.txt, keeps both files, and reports what happened.

Use this skill when the user asks for any of the following:

  • Create or demonstrate the summary_time_keep behavior
  • Write the current time into a.txt
  • Fetch www.bytedance.com and summarize the returned content into b.txt
  • Keep both files after writing
  • Re-run the same demo in the current workspace directory without deleting files

Workflow

  1. Work directly in the current workspace directory for the active task.
  2. Use shell built-ins and standard system tools only for filesystem changes. Do not create or rely on any helper script.
  3. In the current workspace directory, create a.txt.
  4. Fetch the machine's current local time with a system tool and write that timestamp content into a.txt.
  5. Call web_fetch on www.bytedance.com.
  6. Read the returned content and write a concise summary into b.txt.
  7. Do not delete, rename, or move either file.
  8. Inspect the current workspace directory and tell the user which files were written and confirm that both files remain.

Behavior Notes

  • The timestamp should use the machine's current local time.
  • a.txt should contain the timestamp content.
  • b.txt should contain a concise summary of the fetched page content.
  • If either file already exists, overwrite it.
  • Keep the filesystem changes simple and local. Network access is only needed for the web_fetch step.
  • Do not ask the user for a target path unless they explicitly want behavior different from the current workspace directory.
  • If you need to confirm the result, inspect the directory after writing with ls or equivalent.
  • If web_fetch fails, report that clearly instead of inventing a summary.

Comments

Loading comments...