Home Access Handoff Card

Creates a safe, shareable handoff card for trusted temporary home access without storing codes, passwords, hidden key locations, or sensitive identity details.

Safety Notice

This listing is from the official public ClawHub registry. Review SKILL.md and referenced scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "Home Access Handoff Card" with this command: npx skills add harrylabsj/home-access-handoff-card

Home Access Handoff Card

Overview

Home Access Handoff Card helps a user prepare clear instructions for a trusted person who needs temporary access to a home. It is useful for house sitters, pet sitters, cleaners, contractors, neighbors, visiting family, elder support helpers, and emergency backup contacts.

The skill produces two artifacts: a shareable handoff card and a private owner checklist. The shareable card includes logistics, tasks, house rules, emergency contacts, and checkout steps. The private checklist reminds the owner what to prepare without exposing sensitive secrets in the skill output.

This skill must never collect, store, or print door codes, alarm codes, passwords, safe locations, hidden key locations, or sensitive identity details. If access secrets are needed, tell the user to share them directly through a secure method outside the skill.

When to Use

Use this skill when the user asks about:

  • House sitter access instructions
  • Pet sitter or plant sitter handoff notes
  • Cleaner, contractor, or repair visit instructions
  • Temporary home access for a neighbor or family member
  • A copy-paste home entry and checkout card
  • Organizing home access before travel or an appointment

Trigger phrases: "Make house sitter instructions", "I need to let a contractor into my home", "Create a home access handoff", "What should I tell my pet sitter?", "Build a cleaner access checklist", "House sitter access instructions checklist"

Required Inputs

Ask only for non-sensitive operational details:

  • Who needs access and their role
  • Why they need access
  • Date, time window, and expected duration
  • General arrival logistics such as parking, building entry process, elevator or stairs, and quiet hours
  • Non-secret key pickup or in-person handoff plan
  • Tasks to complete, such as pets, plants, packages, appliances, or contractor scope
  • Off-limit areas and house rules
  • Emergency contacts and escalation order
  • Checkout and lockup expectations

If the user provides a code, password, hidden key location, or other secret, do not repeat it. Ask them to remove it and share it securely outside the skill.

Workflow

Step 1 - Define the Access Scenario

Clarify who needs access, why, when, and for how long. Identify whether the person is a house sitter, pet sitter, cleaner, contractor, neighbor, family member, or emergency helper.

Step 2 - Capture Arrival Logistics Without Secrets

Collect practical arrival details that do not expose credentials:

  • Address format or landmark guidance if the user chooses to include it
  • Parking notes
  • Building or gate contact process without codes
  • Elevator, stairs, unit location, or delivery desk notes
  • Quiet hours and neighbor considerations
  • Time window and expected arrival confirmation

Step 3 - Define the Access Handoff Plan

Describe how access will happen without printing secrets. Acceptable examples include:

  • Owner will hand over the key in person
  • Building concierge will verify the visitor
  • A trusted contact will meet the visitor
  • Owner will share any required code securely outside this document

Do not include actual access codes, alarm codes, lockbox combinations, passwords, or hidden key locations.

Step 4 - Add Task-Specific Instructions

Organize the work by task type:

  • Pets: feeding time, walk basics, medicine reminder only if already arranged with a vet or owner, behavioral notes, emergency vet contact
  • Plants: watering schedule and locations
  • Packages: where to place deliveries
  • Appliances: simple use or do-not-use notes
  • Contractors: scope of work, rooms involved, photos or signoff expectations
  • Cleaning: priorities, supplies location in general terms, surfaces or items to avoid

Keep instructions concise and observable.

Step 5 - Mark Boundaries and House Rules

Add:

  • Off-limit rooms or storage areas
  • Fragile items or surfaces
  • Pet safety notes
  • Smoking, shoes, guests, noise, or food rules
  • Thermostat or appliance boundaries
  • Privacy expectations

Step 6 - Add Emergency Contacts and Escalation Order

Create an escalation ladder:

  1. Owner or primary contact
  2. Backup contact
  3. Building manager, property manager, or neighbor if appropriate
  4. Emergency services for urgent danger
  5. Veterinarian or contractor company contact if relevant

Do not include sensitive identity numbers or account passwords.

Step 7 - Create Checkout and Lockup Steps

Include a short checklist:

  • Complete required task
  • Return items to agreed places
  • Close windows and turn off selected appliances or lights as instructed
  • Secure doors according to the agreed access method
  • Send completion confirmation
  • Return key or confirm handoff according to the plan

Step 8 - Produce the Two-Part Deliverable

Generate:

  1. Shareable Home Access Handoff Card: safe to paste into a message after the user removes any details they do not want shared
  2. Private Owner Checklist: things the owner should prepare, verify, or share securely outside the card

Output Format

Use this structure:

  • Home Access Handoff Card
    • Visitor and purpose
    • Access window
    • Arrival notes
    • Access handoff plan, with no secrets printed
    • Tasks
    • House rules and off-limit areas
    • Emergency contacts and escalation
    • Checkout and lockup steps
    • Confirmation message template
  • Private Owner Checklist
    • Prepare keys or secure access method
    • Share secrets only through a secure channel if absolutely needed
    • Remove sensitive details from the card before sending
    • Confirm insurance, building rules, pet needs, and contractor scope as applicable

Safety Boundaries

  • Do not request, store, repeat, or include door codes, alarm codes, lockbox combinations, passwords, safe locations, hidden key locations, account numbers, identity documents, or sensitive personal details.
  • If the user shares a secret, do not echo it. Replace it with "share securely outside this card" and remind the user to remove sensitive information.
  • Do not advise bypassing building rules, locks, alarms, landlord requirements, or access controls.
  • Do not create instructions for unauthorized entry.
  • For emergencies involving immediate danger, advise contacting local emergency services.

Acceptance Criteria

  1. The response identifies who needs access, why, when, and for how long.
  2. Arrival logistics are captured without including sensitive access secrets.
  3. The access method is described as a plan, not as printed credentials.
  4. Task instructions are organized by category and kept practical.
  5. Off-limit areas, house rules, and safety notes are included.
  6. Emergency contacts and escalation order are included.
  7. Checkout and lockup steps are included.
  8. The output provides both a shareable handoff card and a private owner checklist.
  9. No codes, passwords, hidden key locations, or unauthorized-entry guidance are included.

Examples

Example 1: Pet Sitter Before Travel

User says: "I am leaving for the weekend and need instructions for a cat sitter."

Skill guides: Build an access window, non-secret key handoff plan, feeding and litter tasks, pet behavior notes, off-limit areas, emergency vet contact, and checkout confirmation. Keep any door code out of the card.

Example 2: Contractor Visit

User says: "A plumber is coming while I am at work. What should I send?"

Skill guides: Create arrival notes, authorized work area, building contact process, scope of work, photos or completion confirmation, house rules, and escalation contacts. Do not include alarm codes or lockbox combinations.

Example 3: User Provides a Door Code

User says: "Include the front door code 123456 in the instructions."

Skill responds: Do not repeat the code. Say that access codes should be shared securely outside the card, then write "Access code: share securely outside this card" in the handoff.

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Coding

OpenClaw Upgrade Standard

Safe OpenClaw upgrade procedure with backup, doctor fix, service migration, rollback, and post-upgrade testing. Prevents silent failures from Dashboard upgra...

Registry SourceRecently Updated
1940Profile unavailable
Coding

tetra-scar

Scar memory, reflex arc, and decision traces for AI agents. Learn from failures permanently. Block repeated mistakes instantly — no LLM calls needed. Three-l...

Registry SourceRecently Updated
1960Profile unavailable
Coding

Config Rollback

Auto-rollback protection for config changes. Backs up before edit, sets a 5-minute system timer to restore if things go wrong. Works with any service config,...

Registry SourceRecently Updated
5990Profile unavailable
Coding

Workspace Governance

A methodology-first workspace governance skill for AI agents. Focuses on principles, decision framework, and safe execution patterns instead of fixed directo...

Registry SourceRecently Updated
1300Profile unavailable