JustCalendar

v1.0.2

Use this skill when a user needs to install, authenticate, or operate the Just Calendar CLI against https://justcalendar.ai, including generating an agent to...

0· 261·0 current·0 all-time
byAndré Almeida@andredalmeida
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The name/description state a Node.js CLI that uses a backend token and Google Drive for calendar files; SKILL.md only instructs installing the CLI (npm or GitHub) and operating it against https://justcalendar.ai and Google Drive. There are no environment variables, unrelated binaries, or requests that don't match the stated purpose.
Instruction Scope
Instructions remain within the CLI/calendar scope, but they explicitly show passing the generated token on the command line (justcalendar login --token <TOKEN> --url ...). That is functional but has a security/privacy downside (shell history and process-list exposure). The doc also references local config (~/.justcalendar-cli/config.json) and Drive-backed files, which is expected for this tool.
Install Mechanism
This is an instruction-only skill (no install spec). It suggests installing via npm or cloning a GitHub repo (SSH URL). Those are standard methods and no arbitrary/external archive downloads or obscure URLs are present. User should still verify package authenticity before global npm installs.
Credentials
No environment variables or unrelated credentials are requested. The single required secret is the one-time agent token generated by the web UI — appropriate for the stated workflow — but the provided usage pattern (token as a CLI argument) can expose the secret unnecessarily. The skill does not request additional unrelated keys or config paths.
Persistence & Privilege
always is false and the skill is instruction-only; it doesn't request persistent platform privileges or modify other skills. The CLI itself will persist its own config under ~/.justcalendar-cli, which is expected for a CLI tool.
Assessment
This skill appears to describe and document a legitimate CLI and is coherent with its stated purpose, but take the following precautions before installing or using it: - Verify provenance: confirm the npm package name and publisher (npmjs.com) or the GitHub repository owner before running npm install -g or git clone. Malicious packages can be published under similar names. - Token handling: avoid pasting the token directly into a shell command if you can. Passing credentials on the command line can expose them in shell history and to other users on the same machine (ps). Prefer interactive login, environment variables, or storing the token in the CLI's config if the tool supports secure storage. If you must use the CLI argument, remove the command from shell history and rotate/revoke the token if it may have been exposed. - Least privilege: review what Google Drive permissions the Just Calendar web app requests when you connect it (ideally read/write limited to a justcalendar folder). Only grant permissions you understand and are comfortable with. - Review local config: the CLI writes ~/.justcalendar-cli/config.json and expects JustCalendar.ai files in Drive; inspect these files if you want to verify stored tokens or data before trusting them. - If you install globally, prefer verifying package integrity (checksums, signed releases) or installing in a virtual environment/container if you're unsure. If you want, I can: (1) show commands to install safely in a local project rather than globally, (2) suggest safer ways to provide the token (env var or interactive prompt) depending on what the CLI supports, or (3) help verify the npm/GitHub package metadata before you install.

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

latestvk97fmyagwg2fc2v341h3jntsts827axr

License

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

Comments