plugins/utilities/skills/cowork-setup/SKILL.md
Creates `~/Claude-shared/` (user-level shared context — about-me, voice, working-rules, projects-index) and per-project scaffolding in `~/Projects/<name>/` for Claude Cowork non-development projects (marketing, copywriting, strategy, concepts, research). Lightweight alternative to development:projectsetup. Use when user says "setup cowork project", "nový cowork projekt", "nastav coworku", "cowork init", or starting non-dev work in Cowork desktop app. NOT for development projects (use development:projectsetup) or for adding workflow optimizations to existing setup (use workflow-optimization).
npx skillsauth add petrogurcak/skills cowork-setupInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Announce at start: "Používám cowork-setup skill pro [init shared layer | nastavení projektu <name>]."
projectsetup skill but it's overkill for content/marketing workDON'T use this skill:
development:projectsetupworkflow-optimization| Mode | Trigger | Frequency |
| ------------------ | ----------------------------- | --------------- |
| A: Init shared | cowork-setup --init-shared | ONCE per user |
| B: Per-project | cowork-setup <project-name> | Per new project |
If user runs Mode B but ~/Claude-shared/ doesn't exist → stop with: "Run cowork-setup --init-shared first."
cowork-setup --init-sharedRun ONCE per user. Creates ~/Claude-shared/ shared context layer.
If ~/Claude-shared/ exists, prompt:
Track intent marker. Before any mkdir, save list of paths skill will create. On user cancel mid-flow, delete ONLY those paths. Never touch pre-existing files.
Create directory structure:
mkdir -p ~/Claude-shared/templates ~/Claude-shared/archive
Write working-rules.md — copy verbatim from templates/working-rules.md. No Q&A, no substitution.
Q&A for about-me.md (3 short questions):
<NAME>, <ROLE><MISSION><WORK_BLOCKS>Optimization: Pokud existuje ~/.claude/CLAUDE.md se sekcí # ME, extract values + ask "Použít tyhle hodnoty?" → user confirm/edit.
<TOOLS_CONTEXT> = optional, extract from ~/.claude/CLAUDE.md "Focus Areas" if present, else empty.
Substitute placeholders in templates/about-me.md.template → write to ~/Claude-shared/about-me.md.
Voice extraction sub-procedure (see "Voice Extraction" section below):
copywriting:brand-voice skill (Q&A mode, ~30 min)templates/voice-and-style.md.template to ~/Claude-shared/voice-and-style.md as-isInitialize projects-index.md — copy verbatim from templates/projects-index.md.
Generate Cowork Global Instructions text. Print to terminal:
I am <NAME>. When I open a Cowork project:
1. Read ~/Claude-shared/projects-index.md, find current project, summarize: last date, what was done, next step.
2. Follow rules in ~/Claude-shared/working-rules.md.
3. Apply voice from ~/Claude-shared/voice-and-style.md.
4. Never delete files without explicit confirmation.
5. File naming: YYYY-MM-DD-slug.md.
Followed by: "→ Open Cowork desktop app → Settings → Cowork → Global Instructions → paste this text."
Print UI linkage instructions:
"When creating a new project in Cowork: Add Context →
~/Claude-shared/AND your project folder."
GitHub bridge setup (optional, strongly recommended for claude.ai chat sync). Ask: "Init git + push to GitHub? [yes/no/later]"
gh auth status — if fail, instruct gh auth login and pause. (b) Ask repo path (default <gh-user>/claude-shared). (c) Write .gitignore from templates/gitignore.template. (d) Skip init if .git/ exists, else: cd ~/Claude-shared && git init && git branch -m main && git add . && git commit -m "init: shared context layer" && gh repo create <REPO> --private --source=. --push. (e) Append templates/working-rules-git-addendum.md.template to working-rules.md. (f) Print: "claude.ai → Settings → Connectors → Add GitHub → Authorize → Find <REPO>. Per-Project: Sources → GitHub → Select <REPO>."Used in Mode A step 5 when user has writing samples. Grounds voice in real texts vs. Q&A.
User provides 3-7 samples (file paths / URLs / inline text). Recommended: 2-4 newsletters, 3-5 IG captions, 1-2 web pages, 1-2 sales/product examples.
Analyze all samples and extract 6 dimensions:
| Dimension | What to extract | | -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- | | Tone | Formality 1-5, energy 1-5, humor (none/light/heavy), expertise level | | Vocabulary | 10-20 preferred words, 5-10 banned words | | Sentence structure | Avg length, fragmentation yes/no, parataxis vs hypotaxis | | Brand codes | Recurring phrases (≥2 occurrences across samples) with example contexts | | Anti-AI patterns | Words/structures to avoid (em-dash overuse, "delight", "robust", "leverage") | | Per-channel adaptation | Differences between channels — ONLY if samples cover ≥2 channels. If 1 channel only, OMIT this section from output (do not write TBD placeholder). |
Write to ~/Claude-shared/voice-and-style.md (NOT the empty template) with sections in order: Tone (formality/energy/humor/expertise) → Vocabulary (preferred/banned lists) → Sentence patterns (with 1-2 examples each) → Brand codes (recurring phrases with contexts) → Anti-AI patterns (what to avoid + why) → Per-channel (omit entirely if 1 channel) → Source samples (files/URLs analyzed with date).
Show draft to user → ask: "OK / change specific section / regenerate with different samples".
copywriting:brand-voice skill (Q&A) or skip (write empty template).cowork-setup <project-name>Run for each new Cowork project. Creates ~/Projects/<project-name>/ and appends entry to ~/Claude-shared/projects-index.md.
~/Claude-shared/ doesn't exist → stop: "Run cowork-setup --init-shared first."~/Projects/<project-name>/ exists → stop: "Already exists. Choose another name."Q&A for about-project.md (4 questions):
<GOAL><DEADLINE><DELIVERABLES_LIST> (parse user list as bulleted markdown)~/Claude-shared/projects-index.md, suggest matches via string similarity in project name (split on -, match shared tokens). User confirms/edits/skips. → <RELATED_POINTERS>Create structure:
mkdir -p ~/Projects/<project-name>/OUTPUTS ~/Projects/<project-name>/REFERENCES
Write about-project.md — substitute placeholders in templates/about-project.md.template, write to ~/Projects/<project-name>/about-project.md.
Append entry to ~/Claude-shared/projects-index.md in ## Active section:
FIRST_DELIVERABLE=$(echo "$DELIVERABLES_LIST" | head -1 | sed 's/^- //')
ENTRY="- $(date +%Y-%m-%d) | <project-name> | started | next: $FIRST_DELIVERABLE"
awk -v entry="$ENTRY" '/^## Active$/{print; print entry; next}1' ~/Claude-shared/projects-index.md > /tmp/idx.tmp && mv /tmp/idx.tmp ~/Claude-shared/projects-index.md
No manual user step. Skill writes directly.
Print UI linkage instructions:
"Open Cowork → New Project → Context → Add Folder:
- ~/Claude-shared/
- ~/Projects/<project-name>/ Set project name in UI: <project-name>"
| Situation | Skill behavior |
| -------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| ~/Claude-shared/ exists, user runs --init-shared | 3-way prompt: Reinit / Update single file / Cancel (default) |
| ~/Projects/<name>/ exists | Stop, suggest different name |
| Mode B but ~/Claude-shared/ missing | Stop, instruct to run --init-shared first |
| Voice extraction: no samples provided | Fallback to copywriting:brand-voice Q&A or skip |
| Voice extraction: WebFetch fail | Continue with remaining samples, notify user |
| projects-index.md append fail (file locked) | Retry once, else warn user + print line for manual paste |
| User cancels mid-flow Q&A | Use intent marker — delete ONLY paths skill created in this session. Never touch pre-existing files. If no mkdir ran yet → no-op. |
| Step 9: gh auth status fails / .git/ exists / gh repo create rejects | Auth fail → instruct gh auth login + retry. .git/ exists → skip init, verify remote. Repo exists → ask "Use existing?" + git remote add origin + push. |
<project-name> → stop, suggest different namemv)development:projectsetup)brand-voice, audience wrappers) — Cowork calls skills directlyprojects-index.md — Cowork updates it via working-rules.mdREFERENCES/ from Design)development
Builds a pre-launch social proof strategy through structured beta programs using D'Souza Brain Audit interviews. Use when launching new products/services and need compelling testimonials, planning a beta cohort, designing interview questions to harvest objection-busting social proof, improving video testimonials for landing pages, or designing case studies with metrics. Trigger phrases include "beta tester program for testimonials", "pre-launch social proof", "Brain Audit testimonial framework", "case study harvest", "reverse testimonial", "video testimonial mechanics", "social proof landing page", "sběr referencí", "beta tester program", "testimonial pro landing page", "social proof před launchem", "rozhovor s klientem", "case study sběr", "reference před spuštěním". NOT for ongoing case study production (use growth-hacking case-study approach), offer design (use offer-creation), or conversion optimization (use ux-optimization).
development
Use when planning a product launch and the product type is unclear or could be either generic (SaaS/app/physical) or info-product. Routes between marketing:launch-strategy (generic launches) and marketing:info-product-launch (courses, memberships, ebooks, cohorts, communities). Trigger phrases - "launch", "spuštění", "go-to-market", "product launch", "release strategy", "uvedení na trh", "launch plan", "spuštění produktu", "launch sequence", "launch strategy". Do NOT trigger when product type is already clear (use specific skill directly).
testing
Specialized 8-week launch cadence for info-products — online courses, cohort programs, memberships, communities, ebooks, masterminds. Combines Jeff Walker's Product Launch Formula (Seed/Internal/JV variants, PLC sequence, open-cart day-by-day) with Stu McLaren's membership mechanics (closed cart, Success Path) and Hormozi Grand Slam Offer stacking. Use when planning "launch online kurzu", "info-product launch", "PLF launch", "course launch", "membership launch", "cohort launch", "ebook launch", "open cart close cart", "8-week launch of online course", "beta cohort to launch sequence", "spuštění kurzu", "launch členské sekce", "open cart strategie". Differentiates from marketing:launch-strategy (generic SaaS/app launches) — info-product-specific. NOT for SaaS launches, physical products, or services.
development
Use when releasing an Expo/React Native mobile app to App Store and Google Play - covers eas submit, ASC "Submit for Review", Play promote Internal→Production, OTA update, and decoding common silent failures (Apple agreement expiry, missing English locale, Background Location declaration, web bundle failure on react-native-maps).