Freelance Client Boundary Kit

# Freelance Client Boundary Kit

Safety Notice

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

Copy this and send it to your AI assistant to learn

Install skill "Freelance Client Boundary Kit" with this command: npx skills add harrylabsj/freelance-client-boundary-kit

Freelance Client Boundary Kit

Reusable scripts and checklists for scope creep, revisions, rush requests, payment follow-ups, and client expectation resets.

When to Use

Use this skill when you need a practical workflow for freelance, client boundary, scope creep, revision. It is designed for freelancers, consultants, creators, and small studios managing client communication and project boundaries.

What This Skill Does

The assistant should help the user move from messy facts to a structured, ready-to-use plan:

  1. Clarify — Clarify the original agreement, current issue, stakes, and desired boundary
  2. Diagnose — Diagnose whether the issue is scope creep, revision control, timeline pressure, payment delay, or communication drift
  3. Draft — Draft firm but professional scripts for email, chat, or call preparation
  4. Create — Create boundary options with trade-offs: accommodate, paid change order, defer, or decline
  5. Prepare — Prepare a post-issue process improvement checklist for future contracts and onboarding

How to Run the Workflow

1. Intake

Ask concise questions about the situation, timeline, people involved, documents available, desired outcome, constraints, and urgency. If the user pastes messy notes, first separate facts, assumptions, open questions, and missing evidence.

2. Organize

Transform the input into a structured artifact. Use tables and checklists where helpful. Prefer concrete fields such as date, owner, reference number, evidence, next step, deadline, risk, and status.

3. Draft

Provide ready-to-edit drafts: email, chat message, phone-call script, checklist, timeline, decision memo, or agreement language depending on the user's need. Offer a short version and a more detailed version when communication is involved.

4. Verify

Before finalizing, list assumptions, facts to verify, official sources to check, missing information, and places where the user should not rely on the assistant alone.

Suggested Output Formats

  • Situation summary
  • Evidence / document checklist
  • Timeline
  • Action table
  • Message or script draft
  • Risks and assumptions
  • Next 3 steps

Example Prompts

  • "Help me organize this situation into a clear plan: ..."
  • "Turn these notes into a checklist and message draft: ..."
  • "What facts should I verify before acting?"
  • "Make this more calm, concise, and firm."

Safety and Boundaries

This skill provides communication and process support only. It is not legal, tax, accounting, debt-collection, or contract advice. Users should consult qualified professionals for contracts, disputes, collections, or regulated business issues.

Do not invent facts, policies, deadlines, rights, prices, commitments, or outcomes. When uncertain, label uncertainty clearly and tell the user what to verify.

Source Transparency

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

Related Skills

Related by shared tags or category signals.

Coding

xfetch

Use xfetch CLI to fetch X/Twitter data - tweets, user profiles, search results, timelines, lists, DMs, and notifications. Use this skill whenever you need to...

Registry SourceRecently Updated
Coding

Ag Model Usage

Use CodexBar CLI local cost usage to summarize per-model usage for Codex or Claude, including the current (most recent) model or a full model breakdown. Trig...

Registry SourceRecently Updated
Coding

MemOS Cloud Integration

Recall memories from MemOS Cloud before responding. Use this skill when you need context about user's previous conversations, preferences, or decisions.

Registry SourceRecently Updated
Coding

shortaaa

Generate images with FLUX models (Black Forest Labs) via inference.sh CLI. Models: FLUX Dev LoRA, FLUX.2 Klein LoRA with custom style adaptation. Capabilitie...

Registry SourceRecently Updated