← Back to Skills Marketplace
ivangdavila

Clients

by Iván · GitHub ↗ · v1.0.0
linuxdarwinwin32 ✓ Security Clean
1048
Downloads
2
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install clients
Description
Build a personal client system for tracking relationships, projects, documents, and history.
README (SKILL.md)

Core Behavior

  • User mentions client → offer to create/update profile
  • User needs context → surface relevant history
  • User shares document → help associate to client
  • Create ~/clients/ as workspace

File Structure

~/clients/
├── active/
│   └── acme-corp/
│       ├── profile.md
│       ├── projects/
│       ├── documents/
│       ├── communications/
│       └── notes.md
├── past/
├── leads/
└── templates/

Client Folder Structure

acme-corp/
├── profile.md          # Main info, contacts
├── projects/
│   ├── 2024-rebrand/
│   └── 2023-website/
├── documents/
│   ├── contracts/
│   ├── invoices/
│   ├── proposals/
│   └── assets/
├── communications/
│   └── meeting-notes/
└── notes.md            # Quick notes, observations

Client Profile

# profile.md
## Company
Acme Corp
Industry: E-commerce
Website: acme.com
Since: 2022

## Contacts
### Primary
Sarah Chen — VP Product
[email protected] | +1 555-0123
Best channel: Slack

### Others
- Mike Torres — Engineering
- Lisa Park — Finance/Invoicing

## Preferences
- Communication: Slack, quick responses
- Meetings: Tuesdays, mornings
- Decisions: Needs CEO approval over $5k

## Key Info
- Payment terms: Net 30
- Timezone: PST
- Fiscal year ends: December

Projects

# projects/2024-rebrand/project.md
## Overview
Scope: Full brand refresh
Budget: $25,000
Timeline: Feb - April 2024
Status: In progress

## Milestones
- [x] Discovery
- [x] Brand strategy
- [ ] Visual identity — due Feb 20
- [ ] Guidelines

## Team
- Lead: Sarah
- Stakeholders: CEO, Marketing

## Deliverables
/documents/deliverables/

## Notes
Scope expanded to include motion graphics (+$5k approved)

Documents Organization

documents/
├── contracts/
│   └── 2024-service-agreement.pdf
├── invoices/
│   ├── INV-2024-001.pdf
│   └── INV-2024-002.pdf
├── proposals/
│   └── rebrand-proposal-v2.pdf
├── assets/
│   └── brand-files/
└── received/
    └── their-materials/

Communications Log

# communications/log.md
## 2024-02-10 — Call with Sarah
- Reviewed wireframes, approved with minor changes
- Budget discussion: approved motion graphics add-on
- Next: send revised timeline by Friday

## 2024-02-03 — Email thread
- Sent proposal v2
- Questions about timeline, addressed

Quick Notes

# notes.md
## Observations
- Prefers visual presentations over documents
- CEO is hands-off until final review
- Always pays on time
- Referred two other clients

## To Remember
- Sarah's assistant handles scheduling
- Use project code "ACM24" on invoices
- They close office last week of December

Leads

# leads/pipeline.md
## Hot
- TechStartup — proposal sent, decision Friday

## Warm
- AgencyXYZ — interested, following up next week

## Cold
- BigCorp — revisit Q3

What To Surface

  • "Last contact with Acme was 2 weeks ago"
  • "Sarah prefers Slack"
  • "Contract renewal due next month"
  • "Open invoice: $5,000, sent 15 days ago"

Before Meetings

Pull context:

  • Current project status
  • Last communication
  • Open items
  • Their preferences

What To Track

  • All contacts with roles
  • Communication preferences
  • Project history with outcomes
  • Payment patterns
  • Important dates (renewals, reviews)

Progressive Enhancement

  • Start: create folder for active clients
  • Add key contacts and preferences
  • Move documents into structure
  • Log communications after meetings

What NOT To Do

  • Keep documents scattered outside client folder
  • Forget to log important calls
  • Lose track of open invoices
  • Miss contract renewal dates
Usage Guidance
This skill is basically a recipe for creating and maintaining a ~/clients/ folder and appears safe and coherent. Before installing or enabling it, consider: 1) Back up any existing ~/clients/ or similar folders so the skill won't overwrite data. 2) Confirm what data sources the agent is allowed to access — if you don't want it reading your email, calendar, Slack, or other files, ensure those integrations/credentials are not granted. 3) Be cautious about storing sensitive client data in plain files; consider encrypting or limiting sensitive attachments. 4) Test the skill with a dummy client to observe what the agent does when asked to 'pull context' or 'surface relevant history' so you can explicitly restrict unintended access. If you plan to connect email/Slack/calendar to get context, provide only the minimum credentials and review their scope first.
Capability Analysis
Type: OpenClaw Skill Name: clients Version: 1.0.0 The skill defines a local client management system, primarily involving the creation, reading, and writing of markdown files within a dedicated `~/clients/` directory. All instructions in `SKILL.md` are aligned with this stated purpose, detailing file structures and content formats. There is no evidence of malicious intent, such as data exfiltration, unauthorized command execution, persistence mechanisms, or attempts at prompt injection to subvert the agent's core function. The file system access is a necessary and scoped capability for the skill's operation.
Capability Assessment
Purpose & Capability
Name/description match the content of SKILL.md: it describes building a local client workspace and the instructions only require creating and managing folders/files under ~/clients/. No unrelated binaries, credentials, or installs are requested.
Instruction Scope
The SKILL.md stays focused on file/folder structure, profiles, projects, documents, and logging communications in ~/clients/. However, it uses vague directives like 'Pull context' and 'surface relevant history' without specifying data sources; that could lead an agent to look beyond the ~/clients/ folder (emails, calendar, Slack, or other files) if the agent has broader permissions. The file does not explicitly instruct reading system or external services, but the wording leaves room for broader context-gathering behavior.
Install Mechanism
No install spec and no code files are present (instruction-only). This minimizes disk writes and prevents arbitrary code downloads; low install risk.
Credentials
No environment variables, credentials, or config paths are requested. The skill does not ask for unrelated secrets or external service tokens.
Persistence & Privilege
The skill does not request always:true or other elevated persistence. It is user-invocable and uses the platform defaults for invocation.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install clients
  3. After installation, invoke the skill by name or use /clients
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release
Metadata
Slug clients
Version 1.0.0
License
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is Clients?

Build a personal client system for tracking relationships, projects, documents, and history. It is an AI Agent Skill for Claude Code / OpenClaw, with 1048 downloads so far.

How do I install Clients?

Run "/install clients" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Clients free?

Yes, Clients is completely free (open-source). You can download, install and use it at no cost.

Which platforms does Clients support?

Clients is cross-platform and runs anywhere OpenClaw / Claude Code is available (linux, darwin, win32).

Who created Clients?

It is built and maintained by Iván (@ivangdavila); the current version is v1.0.0.

💬 Comments