client-workspace
Create client folder structure in Drive, share docs, check permissions before calls
What this skill does
# Client Workspace
> Create and manage client folders in Google Drive — shared docs, questionnaires, proposals, pre-call checks.
## When to use
- "create workspace for [client]"
- "set up folder for [client]"
- "share doc with [client]"
- "check docs before call with [client]"
- Before any consulting call — verify shared docs are accessible
- After creating a questionnaire, proposal, or contract for a client
## Dependencies
- Other skills: `google-drive`, `query-leads` (CRM lookup)
- External: Python 3, google-api-python-client
## Paths
| What | Path |
|------|------|
| Drive Manager | `$GOOGLE_TOOLS_PATH/drive_manager.py` |
| Token | `$GOOGLE_TOOLS_PATH/token.json` |
| Venv Python | `$GOOGLE_TOOLS_PATH/.venv/bin/python3` |
| CRM People | `$DATA_PATH/sales/crm/contacts/people.csv` |
| CRM Companies | `$DATA_PATH/sales/crm/contacts/companies.csv` |
## Known Folder IDs
| Folder | ID |
|--------|----|
| Clients (root) | `<YOUR_CLIENTS_FOLDER_ID>` |
## Standard Folder Structure
```
Clients/
{CompanyName}/
Discovery/ -- questionnaires, call notes, research
Proposals/ -- scoping docs, estimates, quotes
Contracts/ -- signed agreements, NDAs
Deliverables/ -- work product, reports
```
## How to execute
### Step 1: Create client workspace
```bash
DM="$GOOGLE_TOOLS_PATH/.venv/bin/python3 $GOOGLE_TOOLS_PATH/drive_manager.py"
CLIENTS_ROOT="<YOUR_CLIENTS_FOLDER_ID>"
# Create company folder
$DM create-folder "CompanyName" --parent $CLIENTS_ROOT
# Note the folder ID from output, then create subfolders:
$DM create-folder "Discovery" --parent COMPANY_FOLDER_ID
$DM create-folder "Proposals" --parent COMPANY_FOLDER_ID
$DM create-folder "Contracts" --parent COMPANY_FOLDER_ID
$DM create-folder "Deliverables" --parent COMPANY_FOLDER_ID
```
### Step 2: Create shared doc (questionnaire, proposal, etc.)
Write HTML content to a temp file, then create Google Doc:
```bash
# Create doc from HTML
$DM create-doc "Client J — Pre-call Questionnaire" --folder DISCOVERY_FOLDER_ID --html /tmp/questionnaire.html
# Share with client
$DM share DOC_ID --email [email protected] --role writer --notify --message "Please fill in before our call"
```
### Step 3: Pre-call check
Before any call, verify client has access and check activity:
```bash
# List docs in client folder
$DM list COMPANY_FOLDER_ID
# Check permissions on shared docs
$DM permissions DOC_ID
# Check if client opened/edited the doc
$DM info DOC_ID
# Look at: lastModifiedBy, modifiedTime — if not client, they haven't filled it in
```
### Step 4: After sharing — remove public access if present
Drive API sometimes adds `anyone` link access. Always verify and remove:
```bash
$DM permissions DOC_ID
# If "anyone" permission exists, remove it via Python:
# drive.permissions().delete(fileId=DOC_ID, permissionId='anyoneWithLink').execute()
```
## Questionnaire Templates
### Discovery questionnaire (consulting)
HTML template with sections:
1. **Stack & Team** — current tools, team size, roles
2. **Data** — volumes, formats, examples of ideal output
3. **Priorities** — which automation first, biggest pain points
4. **Open** — anything else before the call
Style: fields with `▸` markers or gray boxes for answers. Use checkboxes (☐) for multiple choice.
### Proposal doc
Create after discovery call with:
1. Executive summary
2. Scope per item (description, hours estimate, price)
3. Timeline with phases
4. Terms (rate, payment schedule)
## Checklist
- [ ] Client folder created under `Clients/`
- [ ] Subfolders created (Discovery, Proposals, Contracts, Deliverables)
- [ ] Shared doc created and shared with client email
- [ ] Public link access removed (only named users)
- [ ] CRM updated with folder link (in company notes or people notes)
- [ ] Pre-call: verified client has opened shared docs
## Related skills
- `google-drive` — underlying Drive API commands
- `call-prep` — call preparation (invoke workspace check as part of prep)
- `client-discovery` — analyzing client requests into scoped proposals
- `query-leads` — CRM data lookup
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.