AugmentClaude

TrailSnap Agent

Search and organize your TrailSnap photo library to find memories, build timelines, and plan albums.

Installation

  1. Make sure Claude is on your device and in your terminal.

    Skills load from ~/.claude/skills/ when Claude Code starts up — so you need it on your machine first. If you don't have it yet, install it once with the command below, then run claude in any terminal to verify.

    One-time setup
    npm i -g @anthropic-ai/claude-code

    Already have it? Skip ahead.

  2. Paste into Claude Code or into your terminal.

    This copies the whole skill folder into ~/.claude/skills/trailsnap-agent-lc044/ — the SKILL.md plus any scripts, reference docs, or templates the skill ships with. Safe default: works for every skill.

    Faster alternative (instruction-only skills)

    Skips the clone and grabs only the SKILL.md file. Don't use this if the skill ships Python scripts, reference markdowns, or asset templates — they won't be downloaded and the skill will fail when it tries to load them.

    Quick install (SKILL.md only)
    Sign up to copy
  3. Restart Claude Code.

    Quit and reopen Claude Code (or any other agent that loads from ~/.claude/skills/). New skills are picked up on startup.

  4. Just ask Claude.

    Skills auto-activate when your request matches the skill's description — no slash command needed. Trigger phrases live in the skill's own frontmatter; you can read them in the “What this skill does” section above.

Prefer to read the source first? Open on GitHub.

When Claude uses it

Query a user's TrailSnap photo library through scoped MCP tools to find photos, reconstruct memories, build person timelines, create evidence-backed narratives, or propose an album plan for explicit in-app approval. Use for the user's own TrailSnap library; never claim a proposal was executed or changed the library.

What this skill does

TrailSnap Agent

Use the trailsnap_* tools supplied by the TrailSnap Pi extension. Query tools are read-only and all tools are scoped to the Agent Token owner. trailsnap_propose_album_organization only records a pending plan; it never executes it.

  • Start with the narrowest tool that answers the request. Use trailsnap_investigate_memory for fuzzy recollections and trailsnap_get_person_timeline only after resolving an identity_id with trailsnap_list_people.
  • Treat candidate memories, inferred places, descriptions, and identified people as evidence to present with uncertainty, not confirmed facts.
  • Paginate when the first result says more data is available. Avoid dumping large raw result sets; select representative photos and explain the selection.
  • Preserve returned photo IDs and absolute thumbnail URLs when producing Markdown or HTML. Never invent a media URL or expose a local file path.
  • Only call trailsnap_propose_album_organization when the user asks to organize or save the selected photos and the token has albums:propose. Return its approval_url and state clearly that nothing changes until the user confirms in TrailSnap.
  • Never attempt to execute or approve a plan. Do not say that a photo, album, tag, date, or file was changed based on a proposal response.

For request-specific sequencing and output guidance, read references/workflows.md.

Related skills