Roadmap Communicator

v2.1.1

Use when preparing roadmap narratives, release notes, changelogs, or stakeholder updates tailored for executives, engineering teams, and customers.

0· 257·5 current·5 all-time
byAlireza Rezvani@alirezarezvani
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Pending
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The name/description (roadmap, release notes, changelogs) align with the included templates and a changelog generator script. There are no unrelated binaries, environment variables, or config paths requested. Source/homepage are missing (author unknown), but that doesn't make the capability inconsistent.
Instruction Scope
SKILL.md instructs the agent to produce communication artifacts and optionally run the provided changelog_generator.py to read git commit messages. The script only reads git commit subjects (or stdin/demo) and formats them; it does not access other files, environment variables, or external endpoints.
Install Mechanism
No install spec; this is instruction-only with an included Python script. No downloads or extracted archives. The script is runnable with system Python and expects git on PATH if used.
Credentials
No required environment variables, credentials, or config paths are declared or used. The only runtime dependency is git (checked at runtime) and python3, which are appropriate for the stated functionality.
Persistence & Privilege
always is false and the skill does not request permanent or system-wide changes. There is no code that modifies other skills or agent configuration.
Assessment
This skill appears coherent and limited in scope, but exercise normal caution before enabling code from an unknown author: 1) The included script reads your git commit messages — those can contain sensitive info, so review the output before sharing externally. 2) Inspect scripts locally (you can read scripts/changelog_generator.py, which is small and clear) and run them in a trusted environment. 3) Ensure git and python3 are present and that you run the script in the intended repository or with --stdin/--demo to avoid exposing unrelated commit history. If you need provenance, ask the publisher for a homepage or source repository before broad deployment.

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

latestvk972sm7b02pg7mn3rntg6078b182qv6r

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments