contacts

Name: contacts
Availability: InStock
Author: frostmoore

Store and search personal contacts in memory by name.

Updated Apr 5, 2026

Search Tags:#search #delete #memory #update #in-memory #contacts #lookup

Ready to run

npx skills add https://github.com/Frostmoore/falmingdragon --skill contacts-frostmoore

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: contacts
Source: https://github.com/Frostmoore/falmingdragon/tree/main/skills/contacts
Command: npx skills add https://github.com/Frostmoore/falmingdragon --skill contacts-frostmoore

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Managing a handful of personal contacts across agent sessions can be cumbersome without a lightweight, in-memory store. This skill provides a fast, session-scoped way to add, retrieve, and remove contact records without persistence.

Core Features & Use Cases

Add a contact with a name and optional details (email, phone) stored in the in-memory namespace "contacts".
Find contacts by exact or partial name, returning matching entries.
Delete a contact by name to remove its record from memory.

Quick Start

Add a contact named John Doe with email [email protected] to memory namespace contacts.

Frequently Asked Questions about contacts

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I store and search personal contacts in memory during an agent session?▼

You can store and search personal contacts in memory by adding records with a name and optional details like email or phone to a session-scoped namespace. The system normalizes keys to lowercase hyphenated names for fast lookup and supports JSON or plain text records.

What is the best way to manage session-scoped contacts without a persistent database?▼

Managing session-scoped contacts without a persistent database is best handled by an in-memory store that uses memory_read and memory_write tools. This approach allows you to quickly add, find, and delete contact records on the fly without needing external storage.

Can I find a contact using a partial name lookup?▼

Yes, you can find a contact using a partial name lookup. The in-memory contact management system supports searching by exact or partial name, returning all matching entries stored in the memory namespace.

Does the in-memory contacts approach support deleting records by name?▼

Yes, the in-memory contacts approach supports deleting records by name. You can remove a specific contact's record from memory to keep your session-scoped contact list accurate and up to date.

What format should I use when adding a new contact to the in-memory store?▼

When adding a new contact to the in-memory store, you can use either JSON or plain text records. The contact's name is required and serves as the key, while optional details like email and phone can be included within the record.

When should I not use an in-memory contact store for agent sessions?▼

You should not use an in-memory contact store when you need long-term data persistence across different agent sessions. Because it relies on session-scoped memory, all stored contacts and their details will be lost once the current session terminates.