Couple

Strengthen relationships with milestone tracking, personalized celebrations, date planning, and shared memory across all relationship stages.

Security Scan

The skill is generally coherent with its stated purpose (local relationship planning stored in ~/couple/), but there are a few mismatches around privacy enforcement and multi-user separation that you should understand before installing.

Purpose & 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.

When to Use

User needs help with relationship milestones, date ideas, anniversary planning, shared memories, or coordinating as a couple. Agent maintains relationship context and suggests personalized actions.

Architecture

Memory lives in ~/couple/. See memory-template.md for setup.

~/couple/
├── memory.md          # HOT: active context, preferences
├── timeline.md        # Milestones, anniversaries, firsts
├── ideas.md           # Saved date/gift ideas
└── archive/           # Past years, old notes

Quick Reference

Topic	File
Memory setup	memory-template.md
Milestone tracking	milestones.md
Date and gift ideas	activities.md
Security limits	boundaries.md

Scope

This skill ONLY:

• Stores relationship dates and milestones in ~/couple/
• Suggests ideas for dates, gifts, celebrations
• Tracks user's own preferences and notes
• Helps plan shared activities

This skill NEVER:

• Tracks location or monitors partner activity
• Stores information about partner without their input
• Offers manipulation or persuasion techniques
• Replaces direct communication between partners
• Stores health, financial, or intimate data

Self-Modification

This skill NEVER modifies its own SKILL.md. All data stored in ~/couple/ directory.

Core Rules

1. Check Memory First

Before suggesting dates/gifts, read ~/couple/memory.md for partner preferences and past activities.

2. Milestone Alerts

Days Before	Action
14	Mention upcoming milestone, start planning
7	Suggest specific gift/activity ideas
1	Final reminder with logistics

3. Personalize Everything

Never suggest generic "flowers and dinner". Use stored preferences:

• Partner's interests from memory.md
• Past successful dates from timeline.md
• Budget constraints if mentioned

4. Stage-Aware Suggestions

Stage	Focus
New (0-1 year)	First experiences, learning each other
Established (1-5 years)	Maintaining spark, routines
Long-term (5+ years)	Renewal, bucket list, legacy
Distance	Virtual activities, countdowns, visit planning
With kids	Quality time, coordination, reconnection

5. Budget Respect

Always ask budget before suggesting. Default to creative/free ideas if unspecified.

6. Both Partners Welcome

If both partners use the skill, maintain separate preferences while enabling shared planning.

Common Traps

• Suggesting things partner dislikes (didn't check memory) → Always read preferences first
• Generic anniversary ideas → Reference their specific history
• Forgetting timezone for LDR couples → Store and use both timezones
• Overplanning without user input → Suggest, don't dictate