Couple
v1.0.0Strengthen relationships with milestone tracking, personalized celebrations, date planning, and shared memory across all relationship stages.
⭐ 0· 555·0 current·0 all-time
byIván@ivangdavila
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
Name/description (relationship milestones, date planning, shared memory) align with the files and instructions: templates, ideas, milestones, and a local ~/couple/ memory. Nothing in the package asks for unrelated credentials, binaries, or remote endpoints. Minor mismatch: the skill claims safe handling of partner data and support for 'both partners' usage, but provides no technical mechanism (separate files, encryption, or access controls) to enforce per-partner privacy.
Instruction Scope
SKILL.md explicitly instructs the agent to read/write files in ~/couple/ (memory.md, timeline.md, ideas.md) and even suggests running mkdir in initial setup. That scope is consistent with the purpose. Concern: the guidance contains policy-like restrictions (never store partner data without consent, never store health/financial/intimate data) but those are advisory only — nothing in the instructions enforces them. The 'Both Partners Welcome' guidance expects separated preferences while the architecture lists a single set of files, which creates an operational ambiguity about who can read what.
Install Mechanism
Instruction-only skill with no install spec and no code files. This is low-risk from an installation/execution perspective — nothing is downloaded or written by an installer.
Credentials
The skill requests no environment variables, credentials, or special config paths. That is proportionate to a local, file-backed relationship planner.
Persistence & Privilege
always:false and no special privileges are requested. The agent may invoke the skill autonomously (platform default). The skill stores data under ~/couple/, which persists across sessions — be aware this creates a local data footprint (plain markdown files) that could be backed up or read by other processes or users on the system.
What to consider before installing
This skill appears to do what it says: suggest dates, track milestones, and store notes locally in ~/couple/ as plain markdown. Before installing, consider: 1) Local storage: all data lives in ~/couple/ by design — do not store intimate, health, financial, or credential information there. 2) Multi-user privacy: the skill states it supports 'both partners' but does not provide a technical separation mechanism; if two people share the same OS account the files are accessible to both. Consider using per-user subdirectories (~/couple/alice, ~/couple/bob) or file permissions. 3) Backups and sync: markdown files may be included in automatic backups or cloud sync (e.g., Dropbox, iCloud) — exclude them if you need privacy. 4) Audit origin: the skill has no homepage and unknown source; if provenance matters, prefer skills with a verifiable source. 5) Behavior expectations: the SKILL.md contains advisory rules (don’t store partner data without consent); these are not enforced by code — the agent could still record whatever the user asks it to. If you proceed, inspect ~/couple/ after first use, set restrictive filesystem permissions, and avoid entering sensitive categories the skill itself says it should not store.Like a lobster shell, security has layers — review code before you run it.
latestvk97fs8b4j8dz742bd6p9hs5p098184cx
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
💑 Clawdis
OSLinux · macOS · Windows