← 返回 Skills 市场
shanjiaming

Writing Style Iterator

作者 shanjiaming · GitHub ↗ · v0.1.0
cross-platform ⚠ suspicious
896
总下载
0
收藏
4
当前安装
1
版本数
在 OpenClaw 中安装
/install writing-style-iterator
功能描述
个性化写作风格记忆系统。在帮用户写作时,加载用户的写作风格 按用户偏好生成内容,并从用户的修改中自动提取风格规则,不断学习用户的写作风格,越用越好用。 当用户的请求涉及写作、改写、润色等文字创作场景时自动激活。
安全使用建议
This skill appears to implement a local, git-backed writing-style memory that reads and writes your files and keeps a history. Before installing or enabling it consider: - The skill will create ~/.writing-style-iterator and commit copies of whatever files you let it handle; check and approve this directory and its retention policy. Back up important files first. - The SKILL.md expects git and standard shell tools but the skill metadata doesn't declare them — confirm the runtime environment has the expected tools and that you trust them. - The instructions tell the agent to modify user files without asking ('Don't ask Y/N'). If you want control, require the skill to prompt before writing or limit it to producing suggestions only. - Limit the skill's scope: prefer configuring explicit directories it may operate on (e.g., a project folder) rather than allowing arbitrary absolute paths. - Ask the author (or require an updated skill) to: (1) declare required binaries (git, diff, cp), (2) declare the config path (~/.writing-style-iterator), (3) remove the 'do-not-ask' mandate or make it configurable, and (4) provide a homepage/source and code review so you can inspect how diffs and rule-extraction are implemented. If you cannot get these changes, treat the skill as high-risk: either run it in a restricted environment or do not enable autonomous invocation and require explicit user consent for every file-write operation.
功能分析
Type: OpenClaw Skill Name: writing-style-iterator Version: 0.1.0 The skill bundle is classified as suspicious due to multiple shell injection vulnerabilities present in the `SKILL.md` instructions. Commands like `cp`, `diff`, and `git commit` incorporate unsanitized placeholders such as `<用户文件的绝对路径>`, `<用户文件>`, `<文件名>`, and `<修改摘要>`. If the OpenClaw agent does not rigorously sanitize these inputs before execution, a malicious user could inject arbitrary shell commands, leading to Remote Code Execution (RCE). While there is no explicit evidence of intentional malicious behavior like data exfiltration or backdoor installation, the severe RCE risk stemming from these vulnerabilities warrants a 'suspicious' classification.
能力评估
Purpose & Capability
The declared purpose (writing-style memory) aligns with the workflow (reading drafts, extracting rules, updating a style file). However, the SKILL.md requires filesystem operations (reading/writing arbitrary user files, creating ~/.writing-style-iterator, committing with git) but the skill metadata declares no required binaries or config paths. The absence of declared requirements (git, cp, diff, bash tools, and the ~/.writing-style-iterator path) is an incoherence.
Instruction Scope
The instructions explicitly tell the agent to read arbitrary absolute user file paths, copy them into a dot-directory, compute diffs, update user files, and auto-commit changes. It also instructs 'Don't ask Y/N. Directly do then notify.' That grants the agent broad discretion to modify user files without explicit per-change consent — scope creep relative to a typical 'suggest edits' assistant and a user-safety risk.
Install Mechanism
This is an instruction-only skill with no install spec (lowest install risk). However, the runtime commands assume git and standard Unix tools are present; the metadata does not declare those as required binaries. The lack of declared runtime dependencies is a mismatch to the instructions and should be fixed.
Credentials
No environment variables or credentials are requested (appropriate). But the skill implicitly requires access to the user's filesystem and a home-dot directory (~/.writing-style-iterator). That required config path is not listed in metadata. Also, the skill makes no distinction between safe/unsafe files — it will operate on any absolute path supplied, which is disproportionate unless constrained or explicitly consented-to by the user.
Persistence & Privilege
always:false is appropriate. Still, the skill's runtime rule to 'automatically activate' for any writing/rewriting request combined with the instruction 'Don't ask Y/N. Directly do' plus the platform default that agents may invoke skills autonomously increases the risk of unexpected automatic file changes. The skill instructs creating persistent local state (a git repo with drafts and style history), which is reasonable for the feature but should be declared and subject to explicit user consent.
如何使用
  1. 确保已安装 OpenClaw(本地或 Docker 部署)
  2. 在对话框中输入安装命令:/install writing-style-iterator
  3. 安装完成后,直接呼叫该 Skill 的名称或使用 /writing-style-iterator 触发
  4. 根据 Skill 的参数说明提供必要输入,即可获得结构化输出
版本历史
v0.1.0
- Initial release of writing-style-iterator: a personalized writing style memory system. - Automatically loads and applies user writing style rules from `~/.writing-style-iterator/style.md` during writing-related tasks. - Learns user preferences by extracting style rules from edits and feedback, continuously updating `style.md`. - Saves drafts and supports diff-based workflow for iterative writing and style adaptation. - Enables easy rollback and history tracking of both drafts and style configuration using Git. - Designed for seamless integration with writing, rewriting, tone adjustment, and translation requests.
元数据
Slug writing-style-iterator
版本 0.1.0
许可证
累计安装 4
当前安装数 4
历史版本数 1
常见问题

Writing Style Iterator 是什么?

个性化写作风格记忆系统。在帮用户写作时,加载用户的写作风格 按用户偏好生成内容,并从用户的修改中自动提取风格规则,不断学习用户的写作风格,越用越好用。 当用户的请求涉及写作、改写、润色等文字创作场景时自动激活。 它是一个面向 Claude Code / OpenClaw 的 AI Agent Skill 插件,目前累计下载 896 次。

如何安装 Writing Style Iterator?

在 OpenClaw 或 Claude Code 对话框中运行命令「/install writing-style-iterator」即可一键安装,无需额外配置。

Writing Style Iterator 是免费的吗?

是的,Writing Style Iterator 完全免费(开源免费),可自由下载、安装和使用。

Writing Style Iterator 支持哪些平台?

Writing Style Iterator 跨平台运行,可在任意部署了 OpenClaw / Claude Code 的环境中使用(cross-platform)。

谁开发了 Writing Style Iterator?

由 shanjiaming(@shanjiaming)开发并维护,当前版本 v0.1.0。

💬 留言讨论