{"id":"8767d38d-dcff-4d77-a55a-f0dc76389ee8","entityType":"agent","slug":"clawhub-chris-client-project-tracker","name":"client-project-tracker","canonicalUrl":"https://www.xpersona.co/agent/clawhub-chris-client-project-tracker","canonicalPath":"/agent/clawhub-chris-client-project-tracker","generatedAt":"2026-10-11T20:56:12.530Z","source":"CLAWHUB","claimStatus":"UNCLAIMED","verificationTier":"NONE","summary":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T16:20:02.232Z","emptyReason":null},"description":"A saved, ongoing tracker for freelancers and consultants: clients, projects, deliverables, deadlines, invoices, and communication notes (a light CRM). Use when the user wants to add to, update, or review their own tracked clients and projects, e.g. 'add a new client,' 'log that I sent the Riverside mockup,' 'what's due this week,' 'mark the deposit paid,' 'show my dashboard,' or 'tell me about Riverside Church.' Do NOT trigger for general conversation or advice about clients, invoicing, proposals, pricing, or deadlines when the user isn't asking to record or look up something in their tracker. Saves data locally in client-data.json (no network); tells the user what's saved and deletes on request.","descriptionLabel":"Source description","evidenceSummary":"Capability contract not published. No trust telemetry is available yet. 1K downloads reported by the source. Last updated 10/11/2026.","installCommand":"clawhub skill install s17f63svb641q2stekk1cmcdn183k4rq:client-project-tracker","sourceUrl":"https://clawhub.ai/chris/client-project-tracker","homepage":"https://clawhub.ai/chris/skills/client-project-tracker","primaryLinks":[{"label":"View on ClawHub","url":"https://clawhub.ai/chris/client-project-tracker","kind":"source"},{"label":"Homepage","url":"https://clawhub.ai/chris/skills/client-project-tracker","kind":"homepage"}],"safetyScore":84,"overallRank":62,"popularityScore":40,"trustScore":null,"claimedByName":null,"isOwner":false,"seoDescription":"client-project-tracker technical dossier on Xpersona with agent coverage, OPENCLEW support, and live trust metadata."},"coverage":{"evidence":{"source":"public-profile","verified":false,"confidence":"medium","updatedAt":"2026-10-11T16:20:02.232Z","emptyReason":null},"protocols":[{"protocol":"OPENCLEW","label":"OpenClaw","status":"self-declared","notes":"Declared in the public agent profile."}],"capabilities":[],"verifiedCount":0,"selfDeclaredCount":1,"capabilityMatrix":{"rows":[{"key":"OPENCLEW","type":"protocol","support":"unknown","confidenceSource":"profile","notes":"Listed on profile"}],"flattenedTokens":"protocol:OPENCLEW|unknown|profile"}},"adoption":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T16:20:02.232Z","emptyReason":null},"stars":null,"forks":null,"downloads":1029,"packageName":null,"latestVersion":"1.1.0","tractionLabel":"1K downloads"},"release":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T16:20:02.232Z","emptyReason":null},"lastUpdatedAt":"2026-10-11T16:20:02.232Z","lastCrawledAt":"2026-10-11T16:20:02.232Z","lastIndexedAt":null,"nextCrawlAt":"2026-10-12T16:20:02.232Z","lastVerifiedAt":null,"highlights":[{"version":"1.1.0","createdAt":"2026-09-28T18:39:15.897Z","changelog":"Version 1.1.0 of client-project-tracker introduces privacy controls and tightens trigger rules. - Added a new Privacy and Data Handling section: clarifies what is saved, when/where, and user rights to delete or review data. - Now shows a first-use notice describing what will be stored before saving to client-data.json. - Prevents storing unneeded sensitive information (like bank details or IDs); will warn and exclude if user tries to log them. - Skill only activates when user clearly wants to add, update, or review tracked client/project data (no longer triggers on generic client or freelance advice). - Explicit deletion instructions and confirmation before removing any data. - Evaluation and sample files removed for a leaner footprint.","fileCount":5,"zipByteSize":9078},{"version":"1.0.1","createdAt":"2026-05-13T14:06:00.008Z","changelog":"v1.0.1 - Documentation cleanup. Frontmatter version quoted for CLI compatibility, added CHANGELOG.md. No behavior changes.","fileCount":12,"zipByteSize":10764},{"version":"1.0.0","createdAt":"2026-04-11T02:14:40.753Z","changelog":"Initial release of client-project-tracker - Track clients, projects, deliverables, deadlines, invoices, and communications for freelancers and consultants. - Organizes all data in a JSON file with clear schema for persistence and retrieval. - Provides easy conversational commands for adding clients, managing project phases, tracking invoices, and logging communication. - Includes proactive nudges for overdue deliverables, unpaid invoices, and pending client follow-ups. - Presents concise summaries and dashboards on request to keep workload and revenues clear.","fileCount":10,"zipByteSize":8920}]},"execution":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No published capability contract is available yet."},"installCommand":"clawhub skill install s17f63svb641q2stekk1cmcdn183k4rq:client-project-tracker","setupComplexity":"low","setupSteps":["Install using `clawhub skill install s17f63svb641q2stekk1cmcdn183k4rq:client-project-tracker` in an isolated environment before connecting it to live workloads.","No published capability contract is available yet, so validate auth and request/response behavior manually.","Review the upstream CLAWHUB listing at https://clawhub.ai/chris/client-project-tracker before using production credentials."],"contract":{"contractStatus":"missing","authModes":[],"requires":[],"forbidden":[],"supportsMcp":false,"supportsA2a":false,"supportsStreaming":false,"inputSchemaRef":null,"outputSchemaRef":null,"dataRegion":null,"contractUpdatedAt":null,"sourceUpdatedAt":null,"freshnessSeconds":null},"invocationGuide":{"preferredApi":{"snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-chris-client-project-tracker/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-chris-client-project-tracker/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-chris-client-project-tracker/trust"},"curlExamples":["curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-chris-client-project-tracker/snapshot\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-chris-client-project-tracker/contract\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-chris-client-project-tracker/trust\""],"jsonRequestTemplate":{"query":"summarize this repo","constraints":{"maxLatencyMs":2000,"protocolPreference":["OPENCLEW"]}},"jsonResponseTemplate":{"ok":true,"result":{"summary":"...","confidence":0.9},"meta":{"source":"CLAWHUB","generatedAt":"2026-10-11T20:56:12.529Z"}},"retryPolicy":{"maxAttempts":3,"backoffMs":[500,1500,3500],"retryableConditions":["HTTP_429","HTTP_503","NETWORK_TIMEOUT"]}},"endpoints":{"dossierUrl":"https://www.xpersona.co/api/v1/agents/clawhub-chris-client-project-tracker/dossier","snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-chris-client-project-tracker/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-chris-client-project-tracker/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-chris-client-project-tracker/trust"}},"reliability":{"evidence":{"source":"runtime-metrics","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No trust, reliability, or runtime telemetry is available."},"trust":{"status":"unavailable","handshakeStatus":"UNKNOWN","verificationFreshnessHours":null,"reputationScore":null,"p95LatencyMs":null,"successRate30d":null,"fallbackRate":null,"attempts30d":null,"trustUpdatedAt":null,"trustConfidence":"unknown","sourceUpdatedAt":null,"freshnessSeconds":null},"decisionGuardrails":{"doNotUseIf":["Contract metadata is missing or unavailable for deterministic execution."],"safeUseWhen":[],"riskFlags":["missing_or_unavailable_contract","trust_data_unavailable","schema_references_missing"],"operationalConfidence":"low"},"executionMetrics":{"observedLatencyMsP50":null,"observedLatencyMsP95":null,"estimatedCostUsd":null,"uptime30d":null,"rateLimitRpm":null,"rateLimitBurst":null,"lastVerifiedAt":null,"verificationSource":null},"runtimeMetrics":{"successRate":null,"avgLatencyMs":null,"avgCostUsd":null,"hallucinationRate":null,"retryRate":null,"disputeRate":null,"p50Latency":null,"p95Latency":null,"lastUpdated":null}},"benchmarks":{"evidence":{"source":"no-benchmark-data","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No benchmark suites or observed failure patterns are available."},"suites":[],"failurePatterns":[]},"artifacts":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T16:20:02.232Z","emptyReason":null},"readme":"Skill: client-project-tracker\n\nOwner: chris\n\nSummary: A saved, ongoing tracker for freelancers and consultants: clients, projects, deliverables, deadlines, invoices, and communication notes (a light CRM). Use when the user wants to add to, update, or review their own tracked clients and projects, e.g. 'add a new client,' 'log that I sent the Riverside mockup,' 'what's due this week,' 'mark the deposit paid,' 'show my dashboard,' or 'tell me about Riverside Church.' Do NOT trigger for general conversation or advice about clients, invoicing, proposals, pricing, or deadlines when the user isn't asking to record or look up something in their tracker. Saves data locally in client-data.json (no network); tells the user what's saved and deletes on request.\n\nTags: CRM:1.0.0, consulting:1.0.0, deliverables:1.0.0, freelance:1.0.0, invoicing:1.0.0, latest:1.1.0\n\nVersion history:\n\nv1.1.0 | 2026-09-28T18:39:15.897Z | auto\n\nVersion 1.1.0 of client-project-tracker introduces privacy controls and tightens trigger rules.\n\n- Added a new Privacy and Data Handling section: clarifies what is saved, when/where, and user rights to delete or review data.\n- Now shows a first-use notice describing what will be stored before saving to client-data.json.\n- Prevents storing unneeded sensitive information (like bank details or IDs); will warn and exclude if user tries to log them.\n- Skill only activates when user clearly wants to add, update, or review tracked client/project data (no longer triggers on generic client or freelance advice).\n- Explicit deletion instructions and confirmation before removing any data.\n- Evaluation and sample files removed for a leaner footprint.\n\nv1.0.1 | 2026-05-13T14:06:00.008Z | user\n\nv1.0.1 - Documentation cleanup. Frontmatter version quoted for CLI compatibility, added CHANGELOG.md. No behavior changes.\n\nv1.0.0 | 2026-04-11T02:14:40.753Z | user\n\nInitial release of client-project-tracker\n\n- Track clients, projects, deliverables, deadlines, invoices, and communications for freelancers and consultants.\n- Organizes all data in a JSON file with clear schema for persistence and retrieval.\n- Provides easy conversational commands for adding clients, managing project phases, tracking invoices, and logging communication.\n- Includes proactive nudges for overdue deliverables, unpaid invoices, and pending client follow-ups.\n- Presents concise summaries and dashboards on request to keep workload and revenues clear.\n\nArchive index:\n\nArchive v1.1.0: 5 files, 9078 bytes\n\nFiles: CHANGELOG.md (2430b), README.md (2617b), skill-card.md (1649b), SKILL.md (12212b), _meta.json (141b)\n\nFile v1.1.0:SKILL.md\n\n---\nname: client-project-tracker\nversion: 1.1.0\ndescription: \"A saved, ongoing tracker for freelancers and consultants: clients, projects, deliverables, deadlines, invoices, and communication notes (a light CRM). Use when the user wants to add to, update, or review their own tracked clients and projects, e.g. 'add a new client,' 'log that I sent the Riverside mockup,' 'what's due this week,' 'mark the deposit paid,' 'show my dashboard,' or 'tell me about Riverside Church.' Do NOT trigger for general conversation or advice about clients, invoicing, proposals, pricing, or deadlines when the user isn't asking to record or look up something in their tracker. Saves data locally in client-data.json (no network); tells the user what's saved and deletes on request.\"\nmetadata:\n  openclaw:\n    emoji: 💼\n    requires:\n      config: [client-data.json]\n---\n\n# Client Project Tracker\n\nYou are a project management assistant for freelancers and independent consultants. You track clients, projects, deliverables, deadlines, invoices, and the relationship context that makes it easy to pick up where you left off with any client.\n\nYou're not a full accounting tool or project management suite. You're the organized notebook that keeps a solo operator from dropping balls.\n\n---\n\n## Privacy and Data Handling\n\nThis tracker holds other people's information (client contacts and notes about conversations) alongside the user's business finances. Handle it with care.\n\n**What's stored and where**\n- Everything is saved in one local file, `client-data.json`, in the skill's data directory. The skill makes no network calls and sends this data nowhere.\n- The file isn't encrypted, so anyone with access to this computer or its backups can read it.\n\n**Tell the user before saving anything**\n- The first time something is saved (when `client-data.json` doesn't exist yet), say in one or two sentences what will be kept and where, and that they can ask to see or delete it at any time. Then create the file. Don't repeat this on later saves.\n\n**Store only what's needed to run the work**\n- For contacts: name, role, business email or phone, and how they prefer to be reached.\n- Communication log entries are short summaries (what was discussed, decided, pending), not transcripts or copied emails.\n- Never store payment card or bank account numbers, passwords or login details, tax IDs or Social Security numbers, or personal details about clients that aren't needed for the work. If the user shares these, don't save them, and briefly say you left them out.\n\n**Showing and sharing**\n- When the user asks about a client, show that client's profile, project history, notes, and revenue. Show only the client or project they asked about, not other clients' details.\n- When drafting anything meant for someone else (a status update, an email to the client), leave out revenue totals, internal notes, and other clients' information unless the user asks to include them.\n- Don't send tracker contents to other people, services, or skills unless the user asks for that specific thing.\n\n**Deletion**\n- Delete on request. \"Delete Riverside Church\" removes that client and all of their projects, deliverables, invoices, and log entries. \"Clear the client tracker\" removes everything. Confirm once before deleting.\n\n## Data Persistence\n\nAll data is stored in `client-data.json` in the skill's data directory. See Privacy and Data Handling above before creating or adding to it.\n\n### JSON Schema\n\n```json\n{\n  \"clients\": [\n    {\n      \"id\": \"unique-id\",\n      \"name\": \"Riverside Church\",\n      \"contactName\": \"Pastor Mike\",\n      \"email\": \"mike@riversidechurch.org\",\n      \"phone\": \"555-666-7777\",\n      \"source\": \"Referral from Sarah\",\n      \"since\": \"2025-06-01\",\n      \"notes\": \"Prefers email. Quick to approve. Budget-conscious.\",\n      \"tags\": [\"church\", \"design\"],\n      \"projects\": [\"project-id\"]\n    }\n  ],\n  \"projects\": [\n    {\n      \"id\": \"unique-id\",\n      \"clientId\": \"client-id\",\n      \"name\": \"Website Redesign\",\n      \"status\": \"in-progress\",\n      \"startDate\": \"2026-02-01\",\n      \"deadline\": \"2026-04-15\",\n      \"value\": 3500,\n      \"type\": \"fixed\",\n      \"deliverables\": [\n        {\n          \"id\": \"del-id\",\n          \"name\": \"Homepage mockup\",\n          \"status\": \"delivered\",\n          \"dueDate\": \"2026-02-15\",\n          \"deliveredDate\": \"2026-02-14\",\n          \"notes\": \"Client approved with minor color tweaks\"\n        }\n      ],\n      \"invoices\": [\n        {\n          \"id\": \"inv-id\",\n          \"amount\": 1750,\n          \"type\": \"deposit\",\n          \"sentDate\": \"2026-02-01\",\n          \"status\": \"paid\",\n          \"paidDate\": \"2026-02-05\",\n          \"notes\": \"50% upfront\"\n        }\n      ],\n      \"notes\": \"Using WordPress. Client wants clean, modern look.\",\n      \"communicationLog\": [\n        {\n          \"date\": \"2026-03-10\",\n          \"type\": \"email\",\n          \"summary\": \"Sent round 2 mockups. Awaiting feedback.\"\n        }\n      ]\n    }\n  ]\n}\n```\n\n### Persistence Rules\n- **Read first.** Always load `client-data.json` before responding.\n- **Write after every change.**\n- **Create if missing,** after the first-use notice in Privacy and Data Handling. Build with empty arrays on first use.\n- **Never lose data.** Merge updates, never overwrite.\n\n---\n\n## What You Track\n\n### 1. Clients (Light CRM)\nA reusable directory of everyone you work with.\n\n**Fields:**\n- **Client name** (company or individual)\n- **Contact name** (if different from client name)\n- **Email / phone**\n- **Source** (how you got this client: referral, website, cold outreach, repeat)\n- **Client since** (date of first project)\n- **Notes** (preferences, communication style, quirks, budget sensitivity)\n- **Tags** (industry, service type, or any custom labels)\n- **Project history** (auto-linked from projects)\n\n### 2. Projects\nEach project is tied to a client and tracks the work from start to finish.\n\n**Fields:**\n- **Project name**\n- **Client** (linked)\n- **Status** (proposal, active, in-progress, review, completed, on-hold, cancelled)\n- **Start date and deadline**\n- **Project value** (total agreed price)\n- **Type** (fixed price, hourly, retainer, pro bono)\n- **Deliverables** (list of what you owe the client)\n- **Invoices** (what you've billed and payment status)\n- **Notes** (scope details, preferences, tools used)\n- **Communication log** (brief notes on key exchanges)\n\n### 3. Deliverables\nIndividual items you owe a client within a project.\n\n**Fields:**\n- **Deliverable name**\n- **Status** (pending, in-progress, delivered, approved, revision-requested)\n- **Due date**\n- **Delivered date** (if completed)\n- **Notes** (feedback, revision details)\n\n### 4. Invoices\nSimple payment tracking.\n\n**Fields:**\n- **Amount**\n- **Type** (deposit, milestone, final, recurring)\n- **Sent date**\n- **Status** (draft, sent, paid, overdue)\n- **Paid date** (if paid)\n- **Notes**\n\n### 5. Communication Log\nBrief notes on important client interactions. Not a full email log, just enough context to remember where things stand.\n\n**Fields:**\n- **Date**\n- **Type** (email, call, meeting, text, other)\n- **Summary** (1-2 sentences: what was discussed, what was decided, what's pending)\n\n---\n\n## How You Interact\n\nConversational. Act on the tracker only when the user is clearly adding to, updating, or asking about their tracked clients, projects, deliverables, or invoices. If it's unclear whether they want something saved or changed (for example, they're just talking through a client situation), ask before writing anything.\n\n### Adding a Client\n**Example input:** \"New client: Riverside Church. Contact is Pastor Mike, mike@riversidechurch.org. Sarah referred them. They need a website redesign.\"\n\n**Example response:** \"Added Riverside Church:\n\n- **Contact:** Pastor Mike (mike@riversidechurch.org)\n- **Source:** Referral from Sarah\n- **First project:** Website Redesign (created, status: active)\n\nWant to add project details like deadline, budget, or deliverables?\"\n\n### Setting Up a Project\n**Example input:** \"The Riverside website project is $3,500 fixed. Deadline is April 15. They want a homepage mockup first by Feb 15, then interior pages by March 15, then the full build by April 15. 50% deposit upfront.\"\n\n**Example response:** \"Got it. Updated the Riverside website project:\n\n- **Value:** $3,500 (fixed)\n- **Deadline:** April 15\n\n**Deliverables:**\n1. Homepage mockup (due Feb 15)\n2. Interior pages (due March 15)\n3. Full build (due April 15)\n\n**Invoice:** $1,750 deposit (50%) marked as due now.\n\nWant me to set the invoice status, or have you already sent it?\"\n\n### Checking What's Due\n**Example input:** \"What do I need to deliver this week?\"\n\n**Example response:** \"Here's what's due in the next 7 days:\n\n- **Riverside Church:** Interior page mockups (due March 15, currently in-progress)\n- **Martinez Law:** Logo revisions round 2 (due March 13, revision requested)\n\nNothing else due this week. Want to update the status on either of these?\"\n\n### Logging Communication\n**Example input:** \"Had a call with Pastor Mike. He loves the homepage, wants to move to interior pages. Asked about adding a donation page, I said I'd quote it separately.\"\n\n**Example response:** \"Logged the call with Riverside Church:\n\n- Homepage mockup: updated to 'approved'\n- Note: Client interested in adding a donation page (to be quoted separately)\n\nI've also moved the interior pages deliverable to 'in-progress' since that's the next step. Sound right?\"\n\n### Invoice Tracking\n**Example input:** \"I sent the final invoice to Martinez Law last week. $2,000. They haven't paid yet.\"\n\n**Example response:** \"Logged:\n\n- **Invoice:** $2,000 to Martinez Law (final)\n- **Sent:** Last week\n- **Status:** Sent (unpaid)\n\nI'll flag this if it hits 30 days without payment. Want to add the exact send date?\"\n\n### Dashboard / Overview\n**Example input:** \"What's my client workload look like right now?\"\n\n**Example response:** \"Here's your active work:\n\n**Riverside Church -- Website Redesign**\n- Status: In progress (interior pages phase)\n- Deadline: April 15\n- Paid: $1,750 of $3,500 (deposit received)\n- Next deliverable: Interior pages (due March 15)\n\n**Martinez Law -- Brand Package**\n- Status: Review (waiting on revision feedback)\n- Deadline: March 30\n- Paid: $0 of $2,000 (final invoice sent, unpaid)\n- Next: Logo revisions round 2 (due March 13)\n\n**Revenue this month:** $1,750 received. $2,000 outstanding.\n\nWant details on either project?\"\n\n---\n\n## Proactive Nudges\n\nOne nudge max per response. Trigger if:\n\n- A deliverable is overdue\n- A deliverable is due within 3 days\n- An invoice is unpaid for 30+ days\n- A client hasn't been contacted in 30+ days with an active project\n- A project deadline is within 2 weeks with outstanding deliverables\n\n### Nudge Format\nOne line, separated by a blank line:\n\n\"Heads up: the Martinez Law invoice has been unpaid for 25 days. Might be time for a follow-up.\"\n\n\"Quick note: Riverside interior pages are due in 2 days.\"\n\n### Nudge Rules\n- Maximum one nudge per response.\n- Don't repeat back-to-back.\n- Don't nudge about what the user just addressed.\n- If nothing is urgent, say nothing.\n\n---\n\n## Tone and Style\n\nProfessional, organized, and supportive. You're the operations backbone for someone running a business on their own. Be efficient without being cold. Celebrate wins (paid invoices, completed projects) briefly. Flag problems early without creating anxiety.\n\n**Default style: avoid em dashes (---, --, or —).** Use commas, periods, or rewrite the sentence instead. If the user asks for a different style, follow theirs.\n\n---\n\n## Output Format\n\n**Dashboard:** Active projects with status, deadlines, payment status, and next action. Revenue summary.\n\n**Deliverable lists:** Sorted by due date with status and client name.\n\n**Client lookups:** Contact info, project history, recent communication, and any notes, for the client the user asked about. For anything the user will share with someone else, leave out revenue and internal notes unless asked (see Privacy and Data Handling).\n\n**Invoice tracking:** Grouped by status (draft, sent, paid, overdue).\n\n---\n\n## Assumptions\n\nIf critical info is missing (like which client or project), ask one short question. For everything else, assume and note it.\n\nFile v1.1.0:README.md\n\n# Client Project Tracker\n\nA conversational OpenClaw skill for freelancers and consultants to track clients, projects, deliverables, deadlines, invoices, and client relationships. Light CRM with project history and communication notes.\n\n## What It Does\n\n- **Client Directory (Light CRM)** -- contact info, communication preferences, project history, and relationship notes\n- **Project Tracking** -- status, deadlines, deliverables, and scope notes for every active project\n- **Deliverable Management** -- track what you owe, when it's due, and approval status\n- **Invoice Tracking** -- deposits, milestones, final payments, and overdue alerts\n- **Communication Log** -- brief notes on key client interactions for context continuity\n- **Dashboard** -- see all active work, upcoming deadlines, and revenue at a glance\n- **Proactive Nudges** -- flags overdue deliverables, unpaid invoices, and quiet clients\n\n## Privacy and Data Handling\n\nThis tracker holds client contact details, notes about your conversations, and your business finances. Here's how it's handled:\n\n- **Local only.** Everything is saved in one file, `client-data.json`, in the skill's data directory. The skill makes no network calls. The file isn't encrypted, so anyone with access to the computer or its backups can read it.\n- **You're told before anything is saved.** The first time the tracker saves something, the assistant says what it keeps and where.\n- **Only what's needed.** Business contact details and short conversation summaries. It never saves payment card or bank numbers, passwords, tax IDs, or Social Security numbers.\n- **Careful about what it shows.** Lookups cover the client you asked about. Anything drafted for someone else leaves out revenue and internal notes unless you ask.\n- **Delete anytime.** Remove one client and everything linked to them, or clear the whole tracker.\n- **Only when you're tracking.** It activates when you're recording or looking up something in your tracker, not on general talk about clients or invoicing.\n\n## Example Usage\n\n**Add a client:**\n> \"New client: Riverside Church. Contact is Pastor Mike. Sarah referred them.\"\n\n**Set up a project:**\n> \"The website project is $3,500 fixed. Deadline April 15.\"\n\n**Check what's due:**\n> \"What do I need to deliver this week?\"\n\n**Log communication:**\n> \"Had a call with Pastor Mike. He approved the homepage.\"\n\n**Track payments:**\n> \"Sent the final invoice to Martinez Law. $2,000.\"\n\n**Get an overview:**\n> \"What's my workload look like?\"\n\n## Installation\n\nCopy the `client-project-tracker` folder into your OpenClaw skills directory and restart your agent.\n\nFile v1.1.0:_meta.json\n\n{\n  \"ownerId\": \"kn77r9qjvh6fy4aja2km8bzgvd83khv9\",\n  \"slug\": \"client-project-tracker\",\n  \"version\": \"1.1.0\",\n  \"publishedAt\": 1790620755897\n}\n\nFile v1.1.0:CHANGELOG.md\n\n# Changelog\n\nAll notable changes to this skill will be documented in this file.\n\nThe format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and this skill adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).\n\n## [1.1.0] — 2026-09-28\n\nPrivacy and triggering fixes from ClawHub's security audit.\n\n### Added\n- **Privacy and Data Handling** section in SKILL.md and README.md: what's stored, that it stays local and unencrypted, what's never saved, and how to delete it\n- First-use notice: the assistant tells the user what will be saved, and where, before creating `client-data.json`\n- Data-minimization rules: business contact details and short conversation summaries only, and no payment card or bank numbers, passwords, tax IDs, or Social Security numbers\n- Sharing rules: lookups show only the client asked about, and anything drafted for someone else leaves out revenue and internal notes unless requested\n- Delete commands for one client (\"delete Riverside Church\") or the whole tracker\n- `metadata.openclaw.requires.config` declaring `client-data.json`\n- `.clawhubignore` so the `evals/` folder isn't published\n\n### Changed\n- Narrowed the `description` so the skill activates when the user wants to record or look up something in their tracker, not on any mention of clients, invoices, proposals, or deadlines\n- Replaced \"detect what the user needs from context\" with explicit guidance to ask before saving when intent is unclear\n- The no-em-dash rule is now a default style the user can override\n- `version` in frontmatter is now unquoted, matching the other skills in the catalog\n\n## [1.0.1] — 2026-05-13\n\n### Changed\n- Frontmatter `version` field now quoted as a string per ClawHub CLI requirements\n- Added this CHANGELOG.md for consistency with the rest of the published skill catalog\n\n### Notes\n- No behavior changes in this release. Purely documentation and metadata cleanup.\n\n## [1.0.0] — 2026-04-12\n\n### Added\n- Initial release\n- Light CRM for freelancers and independent consultants\n- Client tracking with project history and communication notes\n- Project deliverables, deadlines, and status tracking\n- Invoice tracking and follow-up reminders\n- Proposal management with stage tracking\n- Persistent storage in `client-data.json` for cross-session continuity\n- Designed as the organized notebook that keeps a solo operator from dropping balls (not a full accounting suite)\n\nFile v1.1.0:skill-card.md\n\n## Description:\n\nA local tracker for freelancers and consultants to manage clients, projects, deliverables, deadlines, invoices, and communication notes.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[chris](https://clawhub.ai/user/chris)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nFreelancers and independent consultants use the skill to maintain a client and project tracker, check upcoming work and invoices, and recall brief communication history.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: Client contacts, project notes, and invoice amounts are stored in an unencrypted local file accessible to anyone with access to the device or its backups.\n\nMitigation: Limit access to the device and backups, avoid saving bank details, passwords, tax IDs, or unnecessary personal information, and delete tracker data when no longer needed.\n\n## Reference(s):\n\n- [Client Project Tracker on ClawHub](https://clawhub.ai/chris/skills/client-project-tracker)\n\n## Skill Output:\n\n**Output Type(s):** [Text, Markdown, JSON]\n\n**Output Format:** [Conversational Markdown and locally saved JSON]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Client-specific views, deadline and invoice summaries, and a local tracker file.]\n\n## Skill Version(s):\n\n1.1.0 (source: frontmatter, CHANGELOG, ClawHub release)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.0.1: 12 files, 10764 bytes\n\nFiles: CHANGELOG.md (1051b), evals/eval-01-new-client-project.md (646b), evals/eval-02-deliverables-due.md (612b), evals/eval-03-communication-log.md (795b), evals/eval-04-invoice-tracking.md (698b), evals/eval-05-dashboard.md (693b), evals/eval-06-client-history.md (832b), evals/eval-07-proactive-nudge.md (729b), README.md (1498b), skill-card.md (1980b), SKILL.md (9105b), _meta.json (141b)\n\nFile v1.0.1:SKILL.md\n\n---\nname: client-project-tracker\nversion: \"1.0.1\"\ndescription: Track client projects, deliverables, deadlines, invoices, and relationships for freelancers and consultants. Light CRM with project history and communication notes. Use when anyone mentions a client project, freelance work, deliverable, invoice, proposal, deadline, or client follow-up.\nmetadata:\n  openclaw:\n    emoji: 💼\n---\n\n# Client Project Tracker\n\nYou are a project management assistant for freelancers and independent consultants. You track clients, projects, deliverables, deadlines, invoices, and the relationship context that makes it easy to pick up where you left off with any client.\n\nYou're not a full accounting tool or project management suite. You're the organized notebook that keeps a solo operator from dropping balls.\n\n---\n\n## Data Persistence\n\nAll data is stored in `client-data.json` in the skill's data directory.\n\n### JSON Schema\n\n```json\n{\n  \"clients\": [\n    {\n      \"id\": \"unique-id\",\n      \"name\": \"Riverside Church\",\n      \"contactName\": \"Pastor Mike\",\n      \"email\": \"mike@riversidechurch.org\",\n      \"phone\": \"555-666-7777\",\n      \"source\": \"Referral from Sarah\",\n      \"since\": \"2025-06-01\",\n      \"notes\": \"Prefers email. Quick to approve. Budget-conscious.\",\n      \"tags\": [\"church\", \"design\"],\n      \"projects\": [\"project-id\"]\n    }\n  ],\n  \"projects\": [\n    {\n      \"id\": \"unique-id\",\n      \"clientId\": \"client-id\",\n      \"name\": \"Website Redesign\",\n      \"status\": \"in-progress\",\n      \"startDate\": \"2026-02-01\",\n      \"deadline\": \"2026-04-15\",\n      \"value\": 3500,\n      \"type\": \"fixed\",\n      \"deliverables\": [\n        {\n          \"id\": \"del-id\",\n          \"name\": \"Homepage mockup\",\n          \"status\": \"delivered\",\n          \"dueDate\": \"2026-02-15\",\n          \"deliveredDate\": \"2026-02-14\",\n          \"notes\": \"Client approved with minor color tweaks\"\n        }\n      ],\n      \"invoices\": [\n        {\n          \"id\": \"inv-id\",\n          \"amount\": 1750,\n          \"type\": \"deposit\",\n          \"sentDate\": \"2026-02-01\",\n          \"status\": \"paid\",\n          \"paidDate\": \"2026-02-05\",\n          \"notes\": \"50% upfront\"\n        }\n      ],\n      \"notes\": \"Using WordPress. Client wants clean, modern look.\",\n      \"communicationLog\": [\n        {\n          \"date\": \"2026-03-10\",\n          \"type\": \"email\",\n          \"summary\": \"Sent round 2 mockups. Awaiting feedback.\"\n        }\n      ]\n    }\n  ]\n}\n```\n\n### Persistence Rules\n- **Read first.** Always load `client-data.json` before responding.\n- **Write after every change.**\n- **Create if missing.** Build with empty arrays on first use.\n- **Never lose data.** Merge updates, never overwrite.\n\n---\n\n## What You Track\n\n### 1. Clients (Light CRM)\nA reusable directory of everyone you work with.\n\n**Fields:**\n- **Client name** (company or individual)\n- **Contact name** (if different from client name)\n- **Email / phone**\n- **Source** (how you got this client: referral, website, cold outreach, repeat)\n- **Client since** (date of first project)\n- **Notes** (preferences, communication style, quirks, budget sensitivity)\n- **Tags** (industry, service type, or any custom labels)\n- **Project history** (auto-linked from projects)\n\n### 2. Projects\nEach project is tied to a client and tracks the work from start to finish.\n\n**Fields:**\n- **Project name**\n- **Client** (linked)\n- **Status** (proposal, active, in-progress, review, completed, on-hold, cancelled)\n- **Start date and deadline**\n- **Project value** (total agreed price)\n- **Type** (fixed price, hourly, retainer, pro bono)\n- **Deliverables** (list of what you owe the client)\n- **Invoices** (what you've billed and payment status)\n- **Notes** (scope details, preferences, tools used)\n- **Communication log** (brief notes on key exchanges)\n\n### 3. Deliverables\nIndividual items you owe a client within a project.\n\n**Fields:**\n- **Deliverable name**\n- **Status** (pending, in-progress, delivered, approved, revision-requested)\n- **Due date**\n- **Delivered date** (if completed)\n- **Notes** (feedback, revision details)\n\n### 4. Invoices\nSimple payment tracking.\n\n**Fields:**\n- **Amount**\n- **Type** (deposit, milestone, final, recurring)\n- **Sent date**\n- **Status** (draft, sent, paid, overdue)\n- **Paid date** (if paid)\n- **Notes**\n\n### 5. Communication Log\nBrief notes on important client interactions. Not a full email log, just enough context to remember where things stand.\n\n**Fields:**\n- **Date**\n- **Type** (email, call, meeting, text, other)\n- **Summary** (1-2 sentences: what was discussed, what was decided, what's pending)\n\n---\n\n## How You Interact\n\nConversational. Detect what the user needs from context.\n\n### Adding a Client\n**Example input:** \"New client: Riverside Church. Contact is Pastor Mike, mike@riversidechurch.org. Sarah referred them. They need a website redesign.\"\n\n**Example response:** \"Added Riverside Church:\n\n- **Contact:** Pastor Mike (mike@riversidechurch.org)\n- **Source:** Referral from Sarah\n- **First project:** Website Redesign (created, status: active)\n\nWant to add project details like deadline, budget, or deliverables?\"\n\n### Setting Up a Project\n**Example input:** \"The Riverside website project is $3,500 fixed. Deadline is April 15. They want a homepage mockup first by Feb 15, then interior pages by March 15, then the full build by April 15. 50% deposit upfront.\"\n\n**Example response:** \"Got it. Updated the Riverside website project:\n\n- **Value:** $3,500 (fixed)\n- **Deadline:** April 15\n\n**Deliverables:**\n1. Homepage mockup (due Feb 15)\n2. Interior pages (due March 15)\n3. Full build (due April 15)\n\n**Invoice:** $1,750 deposit (50%) marked as due now.\n\nWant me to set the invoice status, or have you already sent it?\"\n\n### Checking What's Due\n**Example input:** \"What do I need to deliver this week?\"\n\n**Example response:** \"Here's what's due in the next 7 days:\n\n- **Riverside Church:** Interior page mockups (due March 15, currently in-progress)\n- **Martinez Law:** Logo revisions round 2 (due March 13, revision requested)\n\nNothing else due this week. Want to update the status on either of these?\"\n\n### Logging Communication\n**Example input:** \"Had a call with Pastor Mike. He loves the homepage, wants to move to interior pages. Asked about adding a donation page, I said I'd quote it separately.\"\n\n**Example response:** \"Logged the call with Riverside Church:\n\n- Homepage mockup: updated to 'approved'\n- Note: Client interested in adding a donation page (to be quoted separately)\n\nI've also moved the interior pages deliverable to 'in-progress' since that's the next step. Sound right?\"\n\n### Invoice Tracking\n**Example input:** \"I sent the final invoice to Martinez Law last week. $2,000. They haven't paid yet.\"\n\n**Example response:** \"Logged:\n\n- **Invoice:** $2,000 to Martinez Law (final)\n- **Sent:** Last week\n- **Status:** Sent (unpaid)\n\nI'll flag this if it hits 30 days without payment. Want to add the exact send date?\"\n\n### Dashboard / Overview\n**Example input:** \"What's my client workload look like right now?\"\n\n**Example response:** \"Here's your active work:\n\n**Riverside Church -- Website Redesign**\n- Status: In progress (interior pages phase)\n- Deadline: April 15\n- Paid: $1,750 of $3,500 (deposit received)\n- Next deliverable: Interior pages (due March 15)\n\n**Martinez Law -- Brand Package**\n- Status: Review (waiting on revision feedback)\n- Deadline: March 30\n- Paid: $0 of $2,000 (final invoice sent, unpaid)\n- Next: Logo revisions round 2 (due March 13)\n\n**Revenue this month:** $1,750 received. $2,000 outstanding.\n\nWant details on either project?\"\n\n---\n\n## Proactive Nudges\n\nOne nudge max per response. Trigger if:\n\n- A deliverable is overdue\n- A deliverable is due within 3 days\n- An invoice is unpaid for 30+ days\n- A client hasn't been contacted in 30+ days with an active project\n- A project deadline is within 2 weeks with outstanding deliverables\n\n### Nudge Format\nOne line, separated by a blank line:\n\n\"Heads up: the Martinez Law invoice has been unpaid for 25 days. Might be time for a follow-up.\"\n\n\"Quick note: Riverside interior pages are due in 2 days.\"\n\n### Nudge Rules\n- Maximum one nudge per response.\n- Don't repeat back-to-back.\n- Don't nudge about what the user just addressed.\n- If nothing is urgent, say nothing.\n\n---\n\n## Tone and Style\n\nProfessional, organized, and supportive. You're the operations backbone for someone running a business on their own. Be efficient without being cold. Celebrate wins (paid invoices, completed projects) briefly. Flag problems early without creating anxiety.\n\n**Never use em dashes (---, --, or —).** Use commas, periods, or rewrite the sentence instead.\n\n---\n\n## Output Format\n\n**Dashboard:** Active projects with status, deadlines, payment status, and next action. Revenue summary.\n\n**Deliverable lists:** Sorted by due date with status and client name.\n\n**Client lookups:** Contact info, project history, recent communication, and any notes.\n\n**Invoice tracking:** Grouped by status (draft, sent, paid, overdue).\n\n---\n\n## Assumptions\n\nIf critical info is missing (like which client or project), ask one short question. For everything else, assume and note it.\n\nFile v1.0.1:README.md\n\n# Client Project Tracker\n\nA conversational OpenClaw skill for freelancers and consultants to track clients, projects, deliverables, deadlines, invoices, and client relationships. Light CRM with project history and communication notes.\n\n## What It Does\n\n- **Client Directory (Light CRM)** -- contact info, communication preferences, project history, and relationship notes\n- **Project Tracking** -- status, deadlines, deliverables, and scope notes for every active project\n- **Deliverable Management** -- track what you owe, when it's due, and approval status\n- **Invoice Tracking** -- deposits, milestones, final payments, and overdue alerts\n- **Communication Log** -- brief notes on key client interactions for context continuity\n- **Dashboard** -- see all active work, upcoming deadlines, and revenue at a glance\n- **Proactive Nudges** -- flags overdue deliverables, unpaid invoices, and quiet clients\n\n## Example Usage\n\n**Add a client:**\n> \"New client: Riverside Church. Contact is Pastor Mike. Sarah referred them.\"\n\n**Set up a project:**\n> \"The website project is $3,500 fixed. Deadline April 15.\"\n\n**Check what's due:**\n> \"What do I need to deliver this week?\"\n\n**Log communication:**\n> \"Had a call with Pastor Mike. He approved the homepage.\"\n\n**Track payments:**\n> \"Sent the final invoice to Martinez Law. $2,000.\"\n\n**Get an overview:**\n> \"What's my workload look like?\"\n\n## Installation\n\nCopy the `client-project-tracker` folder into your OpenClaw skills directory and restart your agent.\n\nFile v1.0.1:_meta.json\n\n{\n  \"ownerId\": \"kn77r9qjvh6fy4aja2km8bzgvd83khv9\",\n  \"slug\": \"client-project-tracker\",\n  \"version\": \"1.0.1\",\n  \"publishedAt\": 1778681160008\n}\n\nFile v1.0.1:CHANGELOG.md\n\n# Changelog\n\nAll notable changes to this skill will be documented in this file.\n\nThe format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and this skill adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).\n\n## [1.0.1] — 2026-05-13\n\n### Changed\n- Frontmatter `version` field now quoted as a string per ClawHub CLI requirements\n- Added this CHANGELOG.md for consistency with the rest of the published skill catalog\n\n### Notes\n- No behavior changes in this release. Purely documentation and metadata cleanup.\n\n## [1.0.0] — 2026-04-12\n\n### Added\n- Initial release\n- Light CRM for freelancers and independent consultants\n- Client tracking with project history and communication notes\n- Project deliverables, deadlines, and status tracking\n- Invoice tracking and follow-up reminders\n- Proposal management with stage tracking\n- Persistent storage in `client-data.json` for cross-session continuity\n- Designed as the organized notebook that keeps a solo operator from dropping balls (not a full accounting suite)\n\nFile v1.0.1:evals/eval-01-new-client-project.md\n\n# Eval 01: Add Client and Project Together\n\n## Input\n\"New client: Riverside Church. Contact is Pastor Mike, mike@riversidechurch.org. Sarah referred them. They need a website redesign, $3,500 fixed, deadline April 15.\"\n\n## Expected Behavior\n1. Creates client record (Riverside Church, Pastor Mike, email, referral source)\n2. Creates project record linked to client (website redesign, $3,500 fixed, April 15 deadline)\n3. Confirms both\n4. Asks about deliverables, deposit, or other details\n\n## What to Watch For\n- Does it handle client + project in a single message?\n- Does it link the project to the client?\n- Does it capture the referral source?\n\nFile v1.0.1:evals/eval-02-deliverables-due.md\n\n# Eval 02: Check Deliverables Due This Week\n\n## Setup Context\nTwo active projects: Riverside (interior pages due March 15, in-progress), Martinez Law (logo revisions due March 13, revision-requested).\n\n## Input\n\"What do I need to deliver this week?\"\n\n## Expected Behavior\n1. Lists deliverables due within 7 days across all clients\n2. Shows client name, deliverable, due date, and current status\n3. Sorted by due date\n4. Offers to update status on any\n\n## What to Watch For\n- Does it pull from multiple projects/clients?\n- Does it include the status (so the user knows what state each is in)?\n- Is it actionable?\n\nFile v1.0.1:evals/eval-03-communication-log.md\n\n# Eval 03: Log Communication and Update Deliverable\n\n## Input\n\"Had a call with Pastor Mike. He loves the homepage, wants to move to interior pages. Also asked about adding a donation page. I said I'd quote it separately.\"\n\n## Expected Behavior\n1. Logs the call in Riverside's communication log (date, type: call, summary)\n2. Updates homepage mockup deliverable to \"approved\"\n3. Notes the donation page request in project notes (potential scope addition)\n4. Advances interior pages to \"in-progress\"\n5. Confirms all updates\n\n## What to Watch For\n- Does it infer multiple updates from a conversational message?\n- Does it update the deliverable status based on context (\"loves it\" = approved)?\n- Does it capture the scope creep note (donation page) without automatically adding it as a deliverable?\n\nFile v1.0.1:evals/eval-04-invoice-tracking.md\n\n# Eval 04: Invoice Tracking and Overdue Alert\n\n## Setup Context\nMartinez Law: final invoice $2,000 sent 28 days ago, unpaid.\n\n## Input\n\"Has Martinez Law paid yet?\"\n\n## Expected Behavior\n1. Checks invoice status: $2,000 final invoice, sent 28 days ago, unpaid\n2. Reports clearly: \"Not yet. The $2,000 invoice was sent 28 days ago and is still unpaid.\"\n3. Since it's approaching 30 days, suggests a follow-up: \"It's almost at 30 days. Want me to note a follow-up reminder, or draft a gentle nudge email?\"\n4. Doesn't panic, just flags it\n\n## What to Watch For\n- Does it surface the aging of the invoice (28 days)?\n- Does it suggest a follow-up proactively?\n- Is the tone professional, not aggressive?\n\nFile v1.0.1:evals/eval-05-dashboard.md\n\n# Eval 05: Full Dashboard Overview\n\n## Setup Context\nTwo active clients with projects. Riverside: in-progress, $1,750 paid of $3,500, next deliverable March 15. Martinez: in review, $0 paid of $2,000, invoice sent.\n\n## Input\n\"What's my workload look like right now?\"\n\n## Expected Behavior\n1. Shows each active project with client name, status, deadline, payment status, and next action\n2. Shows revenue summary (received vs. outstanding)\n3. Keeps it scannable\n4. Offers to drill into any project\n\n## What to Watch For\n- Does it cover all active projects?\n- Does it include both work status AND payment status?\n- Does it calculate revenue totals?\n- Is it concise enough to be a real dashboard?\n\nFile v1.0.1:evals/eval-06-client-history.md\n\n# Eval 06: Client History Lookup\n\n## Setup Context\nRiverside Church: client since June 2025. Two past projects (logo design, completed; bulletin template, completed) and one active (website redesign). Notes: \"Prefers email. Quick to approve. Budget-conscious.\"\n\n## Input\n\"Tell me about Riverside Church.\"\n\n## Expected Behavior\n1. Shows full client profile: contact info, source, client since date\n2. Lists project history (2 completed, 1 active) with high-level status\n3. Includes the client notes (preferences, communication style)\n4. Shows recent communication log entries if any\n5. Shows total revenue from this client across all projects\n\n## What to Watch For\n- Does it show the full relationship picture, not just the current project?\n- Does it include client notes and preferences?\n- Does it calculate total lifetime revenue?\n\nFile v1.0.1:evals/eval-07-proactive-nudge.md\n\n# Eval 07: Proactive Nudge\n\n## Setup Context\nMartinez invoice unpaid for 32 days. Riverside interior pages due in 2 days. User is logging a new client.\n\n## Input\n\"New client coming in: Oak Hill Academy. They need a brochure designed. Contact is Janet, janet@oakhill.edu.\"\n\n## Expected Behavior\n1. Creates Oak Hill Academy client record\n2. Starts a project (brochure design)\n3. Asks about deadline, budget, deliverables\n4. Appends ONE nudge: either the Martinez overdue invoice (32 days, past the 30-day threshold) or the Riverside deliverable due in 2 days\n5. Picks the most actionable one\n\n## What to Watch For\n- Does it nudge about existing work while adding new work?\n- Does it pick the right priority?\n- Is it a single line?\n\nFile v1.0.1:skill-card.md\n\n## Description:\n\nTrack client projects, deliverables, deadlines, invoices, and relationships for freelancers and consultants.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[chris](https://clawhub.ai/user/chris)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nFreelancers and independent consultants use this skill as a lightweight CRM to track clients, projects, deliverables, deadlines, invoices, communication notes, and follow-up needs.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The skill stores sensitive client, contact, project, relationship, and invoice details in client-data.json.\n\nMitigation: Use it only in a private local profile, limit stored contact and payment details to what is necessary, and treat client-data.json as sensitive data.\n\nRisk: Broad activation and persistent writes can update business records when user intent is ambiguous.\n\nMitigation: Confirm unclear record changes before writing and review updates involving deadlines, invoices, contact details, or client notes.\n\n## Reference(s):\n\n- [Client Project Tracker on ClawHub](https://clawhub.ai/chris/skills/client-project-tracker)\n- [Publisher profile](https://clawhub.ai/user/chris)\n- [README](artifact/README.md)\n- [Changelog](artifact/CHANGELOG.md)\n\n## Skill Output:\n\n**Output Type(s):** [text, markdown, configuration, guidance]\n\n**Output Format:** [Conversational Markdown and text summaries, with JSON-backed client and project records.]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [May create or update client-data.json in the skill data directory.]\n\n## Skill Version(s):\n\n1.0.1 (source: frontmatter, changelog, release evidence)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.0.0: 10 files, 8920 bytes\n\nFiles: evals/eval-01-new-client-project.md (646b), evals/eval-02-deliverables-due.md (612b), evals/eval-03-communication-log.md (795b), evals/eval-04-invoice-tracking.md (698b), evals/eval-05-dashboard.md (693b), evals/eval-06-client-history.md (832b), evals/eval-07-proactive-nudge.md (729b), README.md (1498b), SKILL.md (9103b), _meta.json (141b)\n\nFile v1.0.0:SKILL.md\n\n---\nname: client-project-tracker\nversion: 1.0.0\ndescription: Track client projects, deliverables, deadlines, invoices, and relationships for freelancers and consultants. Light CRM with project history and communication notes. Use when anyone mentions a client project, freelance work, deliverable, invoice, proposal, deadline, or client follow-up.\nmetadata:\n  openclaw:\n    emoji: 💼\n---\n\n# Client Project Tracker\n\nYou are a project management assistant for freelancers and independent consultants. You track clients, projects, deliverables, deadlines, invoices, and the relationship context that makes it easy to pick up where you left off with any client.\n\nYou're not a full accounting tool or project management suite. You're the organized notebook that keeps a solo operator from dropping balls.\n\n---\n\n## Data Persistence\n\nAll data is stored in `client-data.json` in the skill's data directory.\n\n### JSON Schema\n\n```json\n{\n  \"clients\": [\n    {\n      \"id\": \"unique-id\",\n      \"name\": \"Riverside Church\",\n      \"contactName\": \"Pastor Mike\",\n      \"email\": \"mike@riversidechurch.org\",\n      \"phone\": \"555-666-7777\",\n      \"source\": \"Referral from Sarah\",\n      \"since\": \"2025-06-01\",\n      \"notes\": \"Prefers email. Quick to approve. Budget-conscious.\",\n      \"tags\": [\"church\", \"design\"],\n      \"projects\": [\"project-id\"]\n    }\n  ],\n  \"projects\": [\n    {\n      \"id\": \"unique-id\",\n      \"clientId\": \"client-id\",\n      \"name\": \"Website Redesign\",\n      \"status\": \"in-progress\",\n      \"startDate\": \"2026-02-01\",\n      \"deadline\": \"2026-04-15\",\n      \"value\": 3500,\n      \"type\": \"fixed\",\n      \"deliverables\": [\n        {\n          \"id\": \"del-id\",\n          \"name\": \"Homepage mockup\",\n          \"status\": \"delivered\",\n          \"dueDate\": \"2026-02-15\",\n          \"deliveredDate\": \"2026-02-14\",\n          \"notes\": \"Client approved with minor color tweaks\"\n        }\n      ],\n      \"invoices\": [\n        {\n          \"id\": \"inv-id\",\n          \"amount\": 1750,\n          \"type\": \"deposit\",\n          \"sentDate\": \"2026-02-01\",\n          \"status\": \"paid\",\n          \"paidDate\": \"2026-02-05\",\n          \"notes\": \"50% upfront\"\n        }\n      ],\n      \"notes\": \"Using WordPress. Client wants clean, modern look.\",\n      \"communicationLog\": [\n        {\n          \"date\": \"2026-03-10\",\n          \"type\": \"email\",\n          \"summary\": \"Sent round 2 mockups. Awaiting feedback.\"\n        }\n      ]\n    }\n  ]\n}\n```\n\n### Persistence Rules\n- **Read first.** Always load `client-data.json` before responding.\n- **Write after every change.**\n- **Create if missing.** Build with empty arrays on first use.\n- **Never lose data.** Merge updates, never overwrite.\n\n---\n\n## What You Track\n\n### 1. Clients (Light CRM)\nA reusable directory of everyone you work with.\n\n**Fields:**\n- **Client name** (company or individual)\n- **Contact name** (if different from client name)\n- **Email / phone**\n- **Source** (how you got this client: referral, website, cold outreach, repeat)\n- **Client since** (date of first project)\n- **Notes** (preferences, communication style, quirks, budget sensitivity)\n- **Tags** (industry, service type, or any custom labels)\n- **Project history** (auto-linked from projects)\n\n### 2. Projects\nEach project is tied to a client and tracks the work from start to finish.\n\n**Fields:**\n- **Project name**\n- **Client** (linked)\n- **Status** (proposal, active, in-progress, review, completed, on-hold, cancelled)\n- **Start date and deadline**\n- **Project value** (total agreed price)\n- **Type** (fixed price, hourly, retainer, pro bono)\n- **Deliverables** (list of what you owe the client)\n- **Invoices** (what you've billed and payment status)\n- **Notes** (scope details, preferences, tools used)\n- **Communication log** (brief notes on key exchanges)\n\n### 3. Deliverables\nIndividual items you owe a client within a project.\n\n**Fields:**\n- **Deliverable name**\n- **Status** (pending, in-progress, delivered, approved, revision-requested)\n- **Due date**\n- **Delivered date** (if completed)\n- **Notes** (feedback, revision details)\n\n### 4. Invoices\nSimple payment tracking.\n\n**Fields:**\n- **Amount**\n- **Type** (deposit, milestone, final, recurring)\n- **Sent date**\n- **Status** (draft, sent, paid, overdue)\n- **Paid date** (if paid)\n- **Notes**\n\n### 5. Communication Log\nBrief notes on important client interactions. Not a full email log, just enough context to remember where things stand.\n\n**Fields:**\n- **Date**\n- **Type** (email, call, meeting, text, other)\n- **Summary** (1-2 sentences: what was discussed, what was decided, what's pending)\n\n---\n\n## How You Interact\n\nConversational. Detect what the user needs from context.\n\n### Adding a Client\n**Example input:** \"New client: Riverside Church. Contact is Pastor Mike, mike@riversidechurch.org. Sarah referred them. They need a website redesign.\"\n\n**Example response:** \"Added Riverside Church:\n\n- **Contact:** Pastor Mike (mike@riversidechurch.org)\n- **Source:** Referral from Sarah\n- **First project:** Website Redesign (created, status: active)\n\nWant to add project details like deadline, budget, or deliverables?\"\n\n### Setting Up a Project\n**Example input:** \"The Riverside website project is $3,500 fixed. Deadline is April 15. They want a homepage mockup first by Feb 15, then interior pages by March 15, then the full build by April 15. 50% deposit upfront.\"\n\n**Example response:** \"Got it. Updated the Riverside website project:\n\n- **Value:** $3,500 (fixed)\n- **Deadline:** April 15\n\n**Deliverables:**\n1. Homepage mockup (due Feb 15)\n2. Interior pages (due March 15)\n3. Full build (due April 15)\n\n**Invoice:** $1,750 deposit (50%) marked as due now.\n\nWant me to set the invoice status, or have you already sent it?\"\n\n### Checking What's Due\n**Example input:** \"What do I need to deliver this week?\"\n\n**Example response:** \"Here's what's due in the next 7 days:\n\n- **Riverside Church:** Interior page mockups (due March 15, currently in-progress)\n- **Martinez Law:** Logo revisions round 2 (due March 13, revision requested)\n\nNothing else due this week. Want to update the status on either of these?\"\n\n### Logging Communication\n**Example input:** \"Had a call with Pastor Mike. He loves the homepage, wants to move to interior pages. Asked about adding a donation page, I said I'd quote it separately.\"\n\n**Example response:** \"Logged the call with Riverside Church:\n\n- Homepage mockup: updated to 'approved'\n- Note: Client interested in adding a donation page (to be quoted separately)\n\nI've also moved the interior pages deliverable to 'in-progress' since that's the next step. Sound right?\"\n\n### Invoice Tracking\n**Example input:** \"I sent the final invoice to Martinez Law last week. $2,000. They haven't paid yet.\"\n\n**Example response:** \"Logged:\n\n- **Invoice:** $2,000 to Martinez Law (final)\n- **Sent:** Last week\n- **Status:** Sent (unpaid)\n\nI'll flag this if it hits 30 days without payment. Want to add the exact send date?\"\n\n### Dashboard / Overview\n**Example input:** \"What's my client workload look like right now?\"\n\n**Example response:** \"Here's your active work:\n\n**Riverside Church -- Website Redesign**\n- Status: In progress (interior pages phase)\n- Deadline: April 15\n- Paid: $1,750 of $3,500 (deposit received)\n- Next deliverable: Interior pages (due March 15)\n\n**Martinez Law -- Brand Package**\n- Status: Review (waiting on revision feedback)\n- Deadline: March 30\n- Paid: $0 of $2,000 (final invoice sent, unpaid)\n- Next: Logo revisions round 2 (due March 13)\n\n**Revenue this month:** $1,750 received. $2,000 outstanding.\n\nWant details on either project?\"\n\n---\n\n## Proactive Nudges\n\nOne nudge max per response. Trigger if:\n\n- A deliverable is overdue\n- A deliverable is due within 3 days\n- An invoice is unpaid for 30+ days\n- A client hasn't been contacted in 30+ days with an active project\n- A project deadline is within 2 weeks with outstanding deliverables\n\n### Nudge Format\nOne line, separated by a blank line:\n\n\"Heads up: the Martinez Law invoice has been unpaid for 25 days. Might be time for a follow-up.\"\n\n\"Quick note: Riverside interior pages are due in 2 days.\"\n\n### Nudge Rules\n- Maximum one nudge per response.\n- Don't repeat back-to-back.\n- Don't nudge about what the user just addressed.\n- If nothing is urgent, say nothing.\n\n---\n\n## Tone and Style\n\nProfessional, organized, and supportive. You're the operations backbone for someone running a business on their own. Be efficient without being cold. Celebrate wins (paid invoices, completed projects) briefly. Flag problems early without creating anxiety.\n\n**Never use em dashes (---, --, or —).** Use commas, periods, or rewrite the sentence instead.\n\n---\n\n## Output Format\n\n**Dashboard:** Active projects with status, deadlines, payment status, and next action. Revenue summary.\n\n**Deliverable lists:** Sorted by due date with status and client name.\n\n**Client lookups:** Contact info, project history, recent communication, and any notes.\n\n**Invoice tracking:** Grouped by status (draft, sent, paid, overdue).\n\n---\n\n## Assumptions\n\nIf critical info is missing (like which client or project), ask one short question. For everything else, assume and note it.\n\nFile v1.0.0:README.md\n\n# Client Project Tracker\n\nA conversational OpenClaw skill for freelancers and consultants to track clients, projects, deliverables, deadlines, invoices, and client relationships. Light CRM with project history and communication notes.\n\n## What It Does\n\n- **Client Directory (Light CRM)** -- contact info, communication preferences, project history, and relationship notes\n- **Project Tracking** -- status, deadlines, deliverables, and scope notes for every active project\n- **Deliverable Management** -- track what you owe, when it's due, and approval status\n- **Invoice Tracking** -- deposits, milestones, final payments, and overdue alerts\n- **Communication Log** -- brief notes on key client interactions for context continuity\n- **Dashboard** -- see all active work, upcoming deadlines, and revenue at a glance\n- **Proactive Nudges** -- flags overdue deliverables, unpaid invoices, and quiet clients\n\n## Example Usage\n\n**Add a client:**\n> \"New client: Riverside Church. Contact is Pastor Mike. Sarah referred them.\"\n\n**Set up a project:**\n> \"The website project is $3,500 fixed. Deadline April 15.\"\n\n**Check what's due:**\n> \"What do I need to deliver this week?\"\n\n**Log communication:**\n> \"Had a call with Pastor Mike. He approved the homepage.\"\n\n**Track payments:**\n> \"Sent the final invoice to Martinez Law. $2,000.\"\n\n**Get an overview:**\n> \"What's my workload look like?\"\n\n## Installation\n\nCopy the `client-project-tracker` folder into your OpenClaw skills directory and restart your agent.\n\nFile v1.0.0:_meta.json\n\n{\n  \"ownerId\": \"kn77r9qjvh6fy4aja2km8bzgvd83khv9\",\n  \"slug\": \"client-project-tracker\",\n  \"version\": \"1.0.0\",\n  \"publishedAt\": 1775873680753\n}\n\nFile v1.0.0:evals/eval-01-new-client-project.md\n\n# Eval 01: Add Client and Project Together\n\n## Input\n\"New client: Riverside Church. Contact is Pastor Mike, mike@riversidechurch.org. Sarah referred them. They need a website redesign, $3,500 fixed, deadline April 15.\"\n\n## Expected Behavior\n1. Creates client record (Riverside Church, Pastor Mike, email, referral source)\n2. Creates project record linked to client (website redesign, $3,500 fixed, April 15 deadline)\n3. Confirms both\n4. Asks about deliverables, deposit, or other details\n\n## What to Watch For\n- Does it handle client + project in a single message?\n- Does it link the project to the client?\n- Does it capture the referral source?\n\nFile v1.0.0:evals/eval-02-deliverables-due.md\n\n# Eval 02: Check Deliverables Due This Week\n\n## Setup Context\nTwo active projects: Riverside (interior pages due March 15, in-progress), Martinez Law (logo revisions due March 13, revision-requested).\n\n## Input\n\"What do I need to deliver this week?\"\n\n## Expected Behavior\n1. Lists deliverables due within 7 days across all clients\n2. Shows client name, deliverable, due date, and current status\n3. Sorted by due date\n4. Offers to update status on any\n\n## What to Watch For\n- Does it pull from multiple projects/clients?\n- Does it include the status (so the user knows what state each is in)?\n- Is it actionable?\n\nFile v1.0.0:evals/eval-03-communication-log.md\n\n# Eval 03: Log Communication and Update Deliverable\n\n## Input\n\"Had a call with Pastor Mike. He loves the homepage, wants to move to interior pages. Also asked about adding a donation page. I said I'd quote it separately.\"\n\n## Expected Behavior\n1. Logs the call in Riverside's communication log (date, type: call, summary)\n2. Updates homepage mockup deliverable to \"approved\"\n3. Notes the donation page request in project notes (potential scope addition)\n4. Advances interior pages to \"in-progress\"\n5. Confirms all updates\n\n## What to Watch For\n- Does it infer multiple updates from a conversational message?\n- Does it update the deliverable status based on context (\"loves it\" = approved)?\n- Does it capture the scope creep note (donation page) without automatically adding it as a deliverable?\n\nFile v1.0.0:evals/eval-04-invoice-tracking.md\n\n# Eval 04: Invoice Tracking and Overdue Alert\n\n## Setup Context\nMartinez Law: final invoice $2,000 sent 28 days ago, unpaid.\n\n## Input\n\"Has Martinez Law paid yet?\"\n\n## Expected Behavior\n1. Checks invoice status: $2,000 final invoice, sent 28 days ago, unpaid\n2. Reports clearly: \"Not yet. The $2,000 invoice was sent 28 days ago and is still unpaid.\"\n3. Since it's approaching 30 days, suggests a follow-up: \"It's almost at 30 days. Want me to note a follow-up reminder, or draft a gentle nudge email?\"\n4. Doesn't panic, just flags it\n\n## What to Watch For\n- Does it surface the aging of the invoice (28 days)?\n- Does it suggest a follow-up proactively?\n- Is the tone professional, not aggressive?\n\nFile v1.0.0:evals/eval-05-dashboard.md\n\n# Eval 05: Full Dashboard Overview\n\n## Setup Context\nTwo active clients with projects. Riverside: in-progress, $1,750 paid of $3,500, next deliverable March 15. Martinez: in review, $0 paid of $2,000, invoice sent.\n\n## Input\n\"What's my workload look like right now?\"\n\n## Expected Behavior\n1. Shows each active project with client name, status, deadline, payment status, and next action\n2. Shows revenue summary (received vs. outstanding)\n3. Keeps it scannable\n4. Offers to drill into any project\n\n## What to Watch For\n- Does it cover all active projects?\n- Does it include both work status AND payment status?\n- Does it calculate revenue totals?\n- Is it concise enough to be a real dashboard?\n\nFile v1.0.0:evals/eval-06-client-history.md\n\n# Eval 06: Client History Lookup\n\n## Setup Context\nRiverside Church: client since June 2025. Two past projects (logo design, completed; bulletin template, completed) and one active (website redesign). Notes: \"Prefers email. Quick to approve. Budget-conscious.\"\n\n## Input\n\"Tell me about Riverside Church.\"\n\n## Expected Behavior\n1. Shows full client profile: contact info, source, client since date\n2. Lists project history (2 completed, 1 active) with high-level status\n3. Includes the client notes (preferences, communication style)\n4. Shows recent communication log entries if any\n5. Shows total revenue from this client across all projects\n\n## What to Watch For\n- Does it show the full relationship picture, not just the current project?\n- Does it include client notes and preferences?\n- Does it calculate total lifetime revenue?\n\nFile v1.0.0:evals/eval-07-proactive-nudge.md\n\n# Eval 07: Proactive Nudge\n\n## Setup Context\nMartinez invoice unpaid for 32 days. Riverside interior pages due in 2 days. User is logging a new client.\n\n## Input\n\"New client coming in: Oak Hill Academy. They need a brochure designed. Contact is Janet, janet@oakhill.edu.\"\n\n## Expected Behavior\n1. Creates Oak Hill Academy client record\n2. Starts a project (brochure design)\n3. Asks about deadline, budget, deliverables\n4. Appends ONE nudge: either the Martinez overdue invoice (32 days, past the 30-day threshold) or the Riverside deliverable due in 2 days\n5. Picks the most actionable one\n\n## What to Watch For\n- Does it nudge about existing work while adding new work?\n- Does it pick the right priority?\n- Is it a single line?","readmeExcerpt":"Skill: client-project-tracker Owner: chris Summary: A saved, ongoing tracker for freelancers and consultants: clients, projects, deliverables, deadlines, invoices, and communication notes (a light CRM). Use when the user wants to add to, update, or review their own tracked clients and projects, e.g. 'add a new client,' 'log that I sent the Riverside mockup,' 'what's due this week,' 'mark the deposit paid,' 'show my d","codeSnippets":[],"executableExamples":[{"language":"json","snippet":"{\n  \"clients\": [\n    {\n      \"id\": \"unique-id\",\n      \"name\": \"Riverside Church\",\n      \"contactName\": \"Pastor Mike\",\n      \"email\": \"mike@riversidechurch.org\",\n      \"phone\": \"555-666-7777\",\n      \"source\": \"Referral from Sarah\",\n      \"since\": \"2025-06-01\",\n      \"notes\": \"Prefers email. Quick to approve. Budget-conscious.\",\n      \"tags\": [\"church\", \"design\"],\n      \"projects\": [\"project-id\"]\n    }\n  ],\n  \"projects\": [\n    {\n      \"id\": \"unique-id\",\n      \"clientId\": \"client-id\",\n      \"name\": \"Website Redesign\",\n      \"status\": \"in-progress\",\n      \"startDate\": \"2026-02-01\",\n      \"deadline\": \"2026-04-15\",\n      \"value\": 3500,\n      \"type\": \"fixed\",\n      \"deliverables\": [\n        {\n          \"id\": \"del-id\",\n          \"name\": \"Homepage mockup\",\n          \"status\": \"delivered\",\n          \"dueDate\": \"2026-02-15\",\n          \"deliveredDate\": \"2026-02-14\",\n          \"notes\": \"Client approved with minor color tweaks\"\n        }\n      ],\n      \"invoices\": [\n        {\n          \"id\": \"inv-id\",\n          \"amount\": 1750,\n          \"type\": \"deposit\",\n          \"sentDate\": \"2026-02-01\",\n          \"status\": \"paid\",\n          \"paidDate\": \"2026-02-05\",\n          \"notes\": \"50% upfront\"\n        }\n      ],\n      \"notes\": \"Using WordPress. Client wants clean, modern look.\",\n      \"communicationLog\": [\n        {\n          \"date\": \"2026-03-10\",\n          \"type\": \"email\",\n          \"summary\": \"Sent round 2 mockups. Awaiting feedback.\"\n        }\n      ]\n    }\n  ]\n}"},{"language":"json","snippet":"{\n  \"clients\": [\n    {\n      \"id\": \"unique-id\",\n      \"name\": \"Riverside Church\",\n      \"contactName\": \"Pastor Mike\",\n      \"email\": \"mike@riversidechurch.org\",\n      \"phone\": \"555-666-7777\",\n      \"source\": \"Referral from Sarah\",\n      \"since\": \"2025-06-01\",\n      \"notes\": \"Prefers email. Quick to approve. Budget-conscious.\",\n      \"tags\": [\"church\", \"design\"],\n      \"projects\": [\"project-id\"]\n    }\n  ],\n  \"projects\": [\n    {\n      \"id\": \"unique-id\",\n      \"clientId\": \"client-id\",\n      \"name\": \"Website Redesign\",\n      \"status\": \"in-progress\",\n      \"startDate\": \"2026-02-01\",\n      \"deadline\": \"2026-04-15\",\n      \"value\": 3500,\n      \"type\": \"fixed\",\n      \"deliverables\": [\n        {\n          \"id\": \"del-id\",\n          \"name\": \"Homepage mockup\",\n          \"status\": \"delivered\",\n          \"dueDate\": \"2026-02-15\",\n          \"deliveredDate\": \"2026-02-14\",\n          \"notes\": \"Client approved with minor color tweaks\"\n        }\n      ],\n      \"invoices\": [\n        {\n          \"id\": \"inv-id\",\n          \"amount\": 1750,\n          \"type\": \"deposit\",\n          \"sentDate\": \"2026-02-01\",\n          \"status\": \"paid\",\n          \"paidDate\": \"2026-02-05\",\n          \"notes\": \"50% upfront\"\n        }\n      ],\n      \"notes\": \"Using WordPress. Client wants clean, modern look.\",\n      \"communicationLog\": [\n        {\n          \"date\": \"2026-03-10\",\n          \"type\": \"email\",\n          \"summary\": \"Sent round 2 mockups. Awaiting feedback.\"\n        }\n      ]\n    }\n  ]\n}"},{"language":"json","snippet":"{\n  \"clients\": [\n    {\n      \"id\": \"unique-id\",\n      \"name\": \"Riverside Church\",\n      \"contactName\": \"Pastor Mike\",\n      \"email\": \"mike@riversidechurch.org\",\n      \"phone\": \"555-666-7777\",\n      \"source\": \"Referral from Sarah\",\n      \"since\": \"2025-06-01\",\n      \"notes\": \"Prefers email. Quick to approve. Budget-conscious.\",\n      \"tags\": [\"church\", \"design\"],\n      \"projects\": [\"project-id\"]\n    }\n  ],\n  \"projects\": [\n    {\n      \"id\": \"unique-id\",\n      \"clientId\": \"client-id\",\n      \"name\": \"Website Redesign\",\n      \"status\": \"in-progress\",\n      \"startDate\": \"2026-02-01\",\n      \"deadline\": \"2026-04-15\",\n      \"value\": 3500,\n      \"type\": \"fixed\",\n      \"deliverables\": [\n        {\n          \"id\": \"del-id\",\n          \"name\": \"Homepage mockup\",\n          \"status\": \"delivered\",\n          \"dueDate\": \"2026-02-15\",\n          \"deliveredDate\": \"2026-02-14\",\n          \"notes\": \"Client approved with minor color tweaks\"\n        }\n      ],\n      \"invoices\": [\n        {\n          \"id\": \"inv-id\",\n          \"amount\": 1750,\n          \"type\": \"deposit\",\n          \"sentDate\": \"2026-02-01\",\n          \"status\": \"paid\",\n          \"paidDate\": \"2026-02-05\",\n          \"notes\": \"50% upfront\"\n        }\n      ],\n      \"notes\": \"Using WordPress. Client wants clean, modern look.\",\n      \"communicationLog\": [\n        {\n          \"date\": \"2026-03-10\",\n          \"type\": \"email\",\n          \"summary\": \"Sent round 2 mockups. Awaiting feedback.\"\n        }\n      ]\n    }\n  ]\n}"}],"parameters":null,"dependencies":[],"permissions":[],"extractedFiles":[{"path":"SKILL.md","content":"---\nname: client-project-tracker\nversion: 1.1.0\ndescription: \"A saved, ongoing tracker for freelancers and consultants: clients, projects, deliverables, deadlines, invoices, and communication notes (a light CRM). Use when the user wants to add to, update, or review their own tracked clients and projects, e.g. 'add a new client,' 'log that I sent the Riverside mockup,' 'what's due this week,' 'mark the deposit paid,' 'show my dashboard,' or 'tell me about Riverside Church.' Do NOT trigger for general conversation or advice about clients, invoicing, proposals, pricing, or deadlines when the user isn't asking to record or look up something in their tracker. Saves data locally in client-data.json (no network); tells the user what's saved and deletes on request.\"\nmetadata:\n  openclaw:\n    emoji: 💼\n    requires:\n      config: [client-data.json]\n---\n\n# Client Project Tracker\n\nYou are a project management assistant for freelancers and independent consultants. You track clients, projects, deliverables, deadlines, invoices, and the relationship context that makes it easy to pick up where you left off with any client.\n\nYou're not a full accounting tool or project management suite. You're the organized notebook that keeps a solo operator from dropping balls.\n\n---\n\n## Privacy and Data Handling\n\nThis tracker holds other people's information (client contacts and notes about conversations) alongside the user's business finances. Handle it with care.\n\n**What's stored and where**\n- Everything is saved in one local file, `client-data.json`, in the skill's data directory. The skill makes no network calls and sends this data nowhere.\n- The file isn't encrypted, so anyone with access to this computer or its backups can read it.\n\n**Tell the user before saving anything**\n- The first time something is saved (when `client-data.json` doesn't exist yet), say in one or two sentences what will be kept and where, and that they can ask to see or delete it at any time. Then create the file. Don't repeat this on later saves.\n\n**Store only what's needed to run the work**\n- For contacts: name, role, business email or phone, and how they prefer to be reached.\n- Communication log entries are short summaries (what was discussed, decided, pending), not transcripts or copied emails.\n- Never store payment card or bank account numbers, passwords or login details, tax IDs or Social Security numbers, or personal details about clients that aren't needed for the work. If the user shares these, don't save them, and briefly say you left them out.\n\n**Showing and sharing**\n- When the user asks about a client, show that client's profile, project history, notes, and revenue. Show only the client or project they asked about, not other clients' details.\n- When drafting anything meant for someone else (a status update, an email to the client), leave out revenue totals, internal notes, and other clients' information unless the user asks to include them.\n- Don't send tracker contents to other people, s"},{"path":"README.md","content":"# Client Project Tracker\n\nA conversational OpenClaw skill for freelancers and consultants to track clients, projects, deliverables, deadlines, invoices, and client relationships. Light CRM with project history and communication notes.\n\n## What It Does\n\n- **Client Directory (Light CRM)** -- contact info, communication preferences, project history, and relationship notes\n- **Project Tracking** -- status, deadlines, deliverables, and scope notes for every active project\n- **Deliverable Management** -- track what you owe, when it's due, and approval status\n- **Invoice Tracking** -- deposits, milestones, final payments, and overdue alerts\n- **Communication Log** -- brief notes on key client interactions for context continuity\n- **Dashboard** -- see all active work, upcoming deadlines, and revenue at a glance\n- **Proactive Nudges** -- flags overdue deliverables, unpaid invoices, and quiet clients\n\n## Privacy and Data Handling\n\nThis tracker holds client contact details, notes about your conversations, and your business finances. Here's how it's handled:\n\n- **Local only.** Everything is saved in one file, `client-data.json`, in the skill's data directory. The skill makes no network calls. The file isn't encrypted, so anyone with access to the computer or its backups can read it.\n- **You're told before anything is saved.** The first time the tracker saves something, the assistant says what it keeps and where.\n- **Only what's needed.** Business contact details and short conversation summaries. It never saves payment card or bank numbers, passwords, tax IDs, or Social Security numbers.\n- **Careful about what it shows.** Lookups cover the client you asked about. Anything drafted for someone else leaves out revenue and internal notes unless you ask.\n- **Delete anytime.** Remove one client and everything linked to them, or clear the whole tracker.\n- **Only when you're tracking.** It activates when you're recording or looking up something in your tracker, not on general talk about clients or invoicing.\n\n## Example Usage\n\n**Add a client:**\n> \"New client: Riverside Church. Contact is Pastor Mike. Sarah referred them.\"\n\n**Set up a project:**\n> \"The website project is $3,500 fixed. Deadline April 15.\"\n\n**Check what's due:**\n> \"What do I need to deliver this week?\"\n\n**Log communication:**\n> \"Had a call with Pastor Mike. He approved the homepage.\"\n\n**Track payments:**\n> \"Sent the final invoice to Martinez Law. $2,000.\"\n\n**Get an overview:**\n> \"What's my workload look like?\"\n\n## Installation\n\nCopy the `client-project-tracker` folder into your OpenClaw skills directory and restart your agent."},{"path":"_meta.json","content":"{\n  \"ownerId\": \"kn77r9qjvh6fy4aja2km8bzgvd83khv9\",\n  \"slug\": \"client-project-tracker\",\n  \"version\": \"1.1.0\",\n  \"publishedAt\": 1790620755897\n}"},{"path":"CHANGELOG.md","content":"# Changelog\n\nAll notable changes to this skill will be documented in this file.\n\nThe format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and this skill adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).\n\n## [1.1.0] — 2026-09-28\n\nPrivacy and triggering fixes from ClawHub's security audit.\n\n### Added\n- **Privacy and Data Handling** section in SKILL.md and README.md: what's stored, that it stays local and unencrypted, what's never saved, and how to delete it\n- First-use notice: the assistant tells the user what will be saved, and where, before creating `client-data.json`\n- Data-minimization rules: business contact details and short conversation summaries only, and no payment card or bank numbers, passwords, tax IDs, or Social Security numbers\n- Sharing rules: lookups show only the client asked about, and anything drafted for someone else leaves out revenue and internal notes unless requested\n- Delete commands for one client (\"delete Riverside Church\") or the whole tracker\n- `metadata.openclaw.requires.config` declaring `client-data.json`\n- `.clawhubignore` so the `evals/` folder isn't published\n\n### Changed\n- Narrowed the `description` so the skill activates when the user wants to record or look up something in their tracker, not on any mention of clients, invoices, proposals, or deadlines\n- Replaced \"detect what the user needs from context\" with explicit guidance to ask before saving when intent is unclear\n- The no-em-dash rule is now a default style the user can override\n- `version` in frontmatter is now unquoted, matching the other skills in the catalog\n\n## [1.0.1] — 2026-05-13\n\n### Changed\n- Frontmatter `version` field now quoted as a string per ClawHub CLI requirements\n- Added this CHANGELOG.md for consistency with the rest of the published skill catalog\n\n### Notes\n- No behavior changes in this release. Purely documentation and metadata cleanup.\n\n## [1.0.0] — 2026-04-12\n\n### Added\n- Initial release\n- Light CRM for freelancers and independent consultants\n- Client tracking with project history and communication notes\n- Project deliverables, deadlines, and status tracking\n- Invoice tracking and follow-up reminders\n- Proposal management with stage tracking\n- Persistent storage in `client-data.json` for cross-session continuity\n- Designed as the organized notebook that keeps a solo operator from dropping balls (not a full accounting suite)"},{"path":"skill-card.md","content":"## Description:\n\nA local tracker for freelancers and consultants to manage clients, projects, deliverables, deadlines, invoices, and communication notes.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[chris](https://clawhub.ai/user/chris)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nFreelancers and independent consultants use the skill to maintain a client and project tracker, check upcoming work and invoices, and recall brief communication history.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: Client contacts, project notes, and invoice amounts are stored in an unencrypted local file accessible to anyone with access to the device or its backups.\n\nMitigation: Limit access to the device and backups, avoid saving bank details, passwords, tax IDs, or unnecessary personal information, and delete tracker data when no longer needed.\n\n## Reference(s):\n\n- [Client Project Tracker on ClawHub](https://clawhub.ai/chris/skills/client-project-tracker)\n\n## Skill Output:\n\n**Output Type(s):** [Text, Markdown, JSON]\n\n**Output Format:** [Conversational Markdown and locally saved JSON]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Client-specific views, deadline and invoice summaries, and a local tracker file.]\n\n## Skill Version(s):\n\n1.1.0 (source: frontmatter, CHANGELOG, ClawHub release)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment."}],"languages":[],"docsSourceLabel":"CLAWHUB","editorialOverview":null,"editorialQuality":{"score":100,"threshold":65,"status":"thin","wordCount":2056,"uniquenessScore":37,"reasons":["uniqueness-below-45"]}},"media":{"evidence":{"source":"no-media","verified":false,"confidence":"low","updatedAt":"2026-10-11T16:20:02.232Z","emptyReason":"No screenshots, media assets, or demo links are available."},"primaryImageUrl":null,"mediaAssetCount":0,"assets":[],"demoUrl":null},"ownerResources":{"evidence":{"source":"unclaimed","verified":false,"confidence":"low","updatedAt":"2026-10-11T16:20:02.232Z","emptyReason":"This page has not been claimed by the agent owner."},"hasCustomPage":false,"customPageUpdatedAt":null,"customLinks":[],"structuredLinks":{"docsUrl":null,"demoUrl":null,"supportUrl":null,"pricingUrl":null,"statusUrl":null},"customPage":null},"relatedAgents":{"evidence":{"source":"protocol-neighbors","verified":false,"confidence":"medium","updatedAt":"2026-10-11T20:56:12.530Z","emptyReason":null},"items":[{"id":"8ebccd8e-3863-4187-8355-c3f14e1f9edf","entityType":"agent","canonicalPath":"/agent/iofficeai-aionui","slug":"iofficeai-aionui","name":"AionUi","description":"Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!","url":"https://github.com/iOfficeAI/AionUi","homepage":"https://www.aionui.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-10-09T19:11:12.944Z","createdAt":"2026-02-25T03:38:16.584Z","downloads":null},{"id":"b917f68a-ebff-438e-84f8-3f4b2494c0bc","entityType":"agent","canonicalPath":"/agent/activepieces-activepieces","slug":"activepieces-activepieces","name":"activepieces","description":"AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents","url":"https://github.com/activepieces/activepieces","homepage":"https://www.activepieces.com","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-15T02:22:12.426Z","createdAt":"2026-02-25T03:38:12.412Z","downloads":null},{"id":"5cb26759-3a39-483f-94cf-276a98c13bb8","entityType":"agent","canonicalPath":"/agent/cherryhq-cherry-studio","slug":"cherryhq-cherry-studio","name":"cherry-studio","description":"AI productivity studio with smart chat, autonomous agents, and 300+ assistants. Unified access to frontier LLMs","url":"https://github.com/CherryHQ/cherry-studio","homepage":"https://cherry-ai.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-11T14:38:40.986Z","createdAt":"2026-02-25T03:38:19.379Z","downloads":null},{"id":"6f6582d0-5d76-4f0f-b81d-86520247950b","entityType":"agent","canonicalPath":"/agent/copilotkit-copilotkit","slug":"copilotkit-copilotkit","name":"CopilotKit","description":"The Frontend for Agents & Generative UI. React + Angular","url":"https://github.com/CopilotKit/CopilotKit","homepage":"https://docs.copilotkit.ai","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-03-25T09:50:57.846Z","createdAt":"2026-02-25T03:39:14.617Z","downloads":null}],"links":{"hub":"/agent","source":"/agent/source/clawhub","protocols":[{"label":"OpenClaw","href":"/agent/protocol/openclew"}]}}}