Eventkit Integration

v1.0.0

EventKit integration patterns, permission handling, zero-width character steganography, and batch operations for macOS/iOS apps

0· 82·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
medium confidence
Purpose & Capability
Name/description (EventKit, permissions, batch ops, steganography) match the Swift snippets and runtime guidance. No unrelated environment variables, binaries, or installs are requested.
Instruction Scope
Instructions stay focused on EventKit patterns (calendar creation, permission checks, batch fetch/delete, sync binding). However the guidance explicitly recommends embedding invisible zero-width signatures in reminder notes for identity tracking — a covert channel that may leak identifiers when notes sync to cloud/shared calendars. Batch delete and 'self-healing' behavior also require careful guardrails to avoid accidental data loss.
Install Mechanism
Instruction-only skill with no install spec and no code files to write or execute. Lowest install risk.
Credentials
No credentials, environment variables, or filesystem paths are requested. The data access described (EventKit, local model context) is appropriate for the stated purpose.
Persistence & Privilege
Skill is not forced-always; it does not request elevated or persistent platform privileges. Autonomous invocation is allowed by default but not combined with broad credentials or installs.
Assessment
This skill appears to do what it says (EventKit integration) and doesn’t request secrets or install software, but it contains two areas to be cautious about: 1) Zero-width steganography: The skill recommends embedding invisible markers in reminder notes to track identity. That is a covert channel — those markers can be synchronized to iCloud or shared calendars and could leak user or device identifiers. If you plan to use this, ensure explicit user consent, clear privacy disclosures, and consider safer alternatives (signed metadata stored in your app's private database or encrypted metadata fields), and verify App Store/privacy policy compliance. 2) Bulk delete / self-healing logic: The batch delete and zombie purge patterns can remove many reminders. Add safeguards: confirmations, dry-run modes, rate-limits, backups, and robust checks to avoid deleting items created by other apps or users. Test thoroughly on non-production data. Other recommendations: review regex and Unicode handling (ensure the extraction works reliably), ensure permission prompts follow platform guidelines, and log minimal data. If you need greater assurance about potential covert channels or third-party exposure, request the full source files or a code review before installing.

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

latestvk97176bsqyyn0qbamg3f0pwtrh83jz30

License

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

Runtime requirements

📅 Clawdis

Comments