Event Manager
v1.0.0小说事件管理工具。创建、编辑、查询事件档案，支持因果链、时间线、多线叙事追踪。Use when: Architect 代理在 Phase 2 需要创建事件架构、管理因果链、规划多线叙事。
⭐ 0· 78·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description (小说事件管理工具) matches the packaged files and code: scripts/manage_events.py implements create/list/query/update/delete/export of event YAMLs and uses provided templates. No unrelated binaries, services, or credentials are requested.
Instruction Scope
SKILL.md instructs installing the listed Python deps and running the included CLI script against a project directory. The runtime instructions only reference local paths (skill workspace, project directory, events/*.yml) and the code reads/writes YAML files and prints output. Deletion prompts the user for confirmation before removing files.
Install Mechanism
There is no automated install spec; SKILL.md recommends running pip3 install -r requirements.txt --user. requirements.txt lists common packages (pyyaml, rich) from PyPI. No downloads from arbitrary URLs or archive extraction are present in the bundle.
Credentials
The skill declares no required environment variables, credentials, or config paths. The code does not access environment credentials and only operates on project/event directories and local config templates.
Persistence & Privilege
always is false and model invocation is normal. The skill does not request permanent/system-level presence or modify other skills' configs. It writes event files within the project/events directory (expected behavior).
Assessment
This package appears coherent and local-file-focused, but take these basic precautions before installing/running: (1) Review scripts/manage_events.py yourself (it is included) to confirm behavior (you already did); (2) Back up any existing events/important YAMLs in your target project directory before running create/update/delete; delete operations prompt for confirmation but it's good to have backups; (3) Installing requirements via pip will install packages into your user environment — consider using a virtualenv to avoid impacting system/site packages; (4) The registry owner is unknown and there is no homepage — consider this when trusting future updates or running unreviewed code from unknown sources. If you want, I can scan the remaining/truncated portion of manage_events.py or run a line-by-line review of any file you point to.Like a lobster shell, security has layers — review code before you run it.
latestvk972ywqzb83r25wgzjnwr7t0418414s9
License
MIT-0
Free to use, modify, and redistribute. No attribution required.