skills/general/create-client-project/SKILL.md
Create a new client project folder with complete structure and templates. Load when user says "create client project", "new client", "add client [name]", "onboard new client", "setup client folder", or "create project for [client]".
npx skillsauth add beam-ai-team/beam-next-skills create-client-projectInstall 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.
Create a standardized client project folder structure with pre-configured templates.
Quickly onboard new clients with a complete folder structure including:
Time saved: ~20 minutes of manual setup per client
Required:
Optional (improves templates):
What's the client name?
> Acme Corporation
Do you have any GTM documentation to include? (paste, file path, or 'skip')
Convert to folder-safe format:
"Acme Corporation" → acme-corporation
Base Location: User specifies or use default project location
[location]/[client-name]/
├── PROJECT_CONTEXT.md # Chronological update log
├── project-state.json # Structured state data
├── README.md # Project overview
│
├── docs/
│ ├── SCOPE_OF_WORK.md # Deliverables & timeline
│ ├── SOLUTION_WORKFLOW.md # Operational procedures
│ ├── TECHNICAL_ARCHITECTURE.md # System design
│ ├── LINEAR_TICKETS.md # Ticket tracking
│ └── SLACK_CHANNELS_SETUP.md # Communication
│
├── meetings/
│ └── transcripts/ # Raw transcripts
│
├── communications/ # Sent messages
│
└── weekly-updates/ # Status reports
PROJECT_CONTEXT.md:
# [Client Name] Project Context
> Quick-reference log of project changes. Newest entries at top.
---
## [Today's Date]
**Project Created**
- Initial setup and folder structure
**Links:**
- [Scope of Work](docs/SCOPE_OF_WORK.md)
- [Technical Architecture](docs/TECHNICAL_ARCHITECTURE.md)
project-state.json:
{
"lastUpdated": "[timestamp]",
"clientName": "[Client Name]",
"clientDomain": "[domain.com]",
"currentPhase": "DISCOVERY",
"recentActivity": [{
"date": "[today]",
"type": "onboarding",
"summary": "Project created"
}],
"nextSteps": [
"Complete kickoff meeting",
"Define scope of work",
"Set up communication channels"
],
"openIssues": [],
"blockers": [],
"team": {
"internal": [],
"client": []
}
}
README.md:
# [Client Name]
## Overview
[Description from GTM docs or placeholder]
## Quick Links
- [Scope of Work](docs/SCOPE_OF_WORK.md)
- [Technical Architecture](docs/TECHNICAL_ARCHITECTURE.md)
- Linear Project: TBD
- Slack Channel: TBD
## Team
**Internal**: TBD
**Client**: [Contact info if provided]
## Status
- **Phase**: Discovery
- **Created**: [Date]
If documentation provided, extract:
SCOPE_OF_WORK.mdREADME.mdTECHNICAL_ARCHITECTURE.mdSCOPE_OF_WORK.mdClient project created: [Client Name]
Location: [path]
Files Created:
- PROJECT_CONTEXT.md
- project-state.json
- README.md
- docs/SCOPE_OF_WORK.md
- docs/SOLUTION_WORKFLOW.md
- docs/TECHNICAL_ARCHITECTURE.md
- docs/LINEAR_TICKETS.md
- docs/SLACK_CHANNELS_SETUP.md
Next Steps:
1. Review and complete SCOPE_OF_WORK.md
2. Create Linear project
3. Set up Slack channels
4. Schedule kickoff meeting
create-client-project/
├── SKILL.md # This file
└── templates/
├── PROJECT_CONTEXT.md # Context template
├── project-state.json # State template
├── README.md # Overview template
└── docs/
├── SCOPE_OF_WORK.md
├── SOLUTION_WORKFLOW.md
├── TECHNICAL_ARCHITECTURE.md
├── LINEAR_TICKETS.md
└── SLACK_CHANNELS_SETUP.md
process-client-meeting - Use after kickoff meetingupdate-project-context - Keep context currentcreate-weekly-update - Start weekly reportingfathom-fetch-meetings - Filter meetings by client domainVersion: 1.0 Owner: Hassaan Ahmed
testing
Audit registry.yaml against disk, validate SKILL.md frontmatter, find duplicates and orphans. Load when user says 'audit skills registry', 'validate beam-next-skills', 'registry drift', 'skills catalog audit', 'check registry yaml'.
tools
All Workable ATS operations — fetch JDs, search candidates, post assessments/reviews. Load when user says "fetch JD", "search workable", "push to workable", "post review", "rate candidate", "workable", "push assessment", "list jobs", or after interview-coach completes an evaluation. Replaces workable-fetch-jd and workable-push-assessment.
data-ai
Load when user mentions "tavily research", "market intelligence", "competitive research", "GTM research", or needs real-time market data for sales, marketing, or vertical strategy.
development
Shared resource library for Slack integration skills. DO NOT load directly - provides common references (setup, API docs, error handling, authentication) and scripts used by slack-connect and individual Slack skills.