crewly 1.1.2 → 1.2.0

package/config/templates/code-review-team/README.md

@@ -0,0 +1,176 @@
+# Code Review Pipeline — Quick Start
+
+## Overview
+
+An AI team that automatically reviews pull requests for code quality, security vulnerabilities, and test coverage. Produces structured, actionable review feedback with a clear verdict.
+
+**Target Users**: SaaS teams, dev agencies, engineering organizations
+**Team Size**: 2 agents (Senior Reviewer + Security Auditor)
+
+## Prerequisites
+
+- Crewly installed and running (`npx crewly start`)
+- Git repository with PR workflow (GitHub, GitLab, or Bitbucket)
+
+## Quick Start
+
+```bash
+# 1. Create the team from template
+npx crewly create-team --template code-review-team
+
+# 2. Start the team in your project directory
+npx crewly start --project /path/to/your/repo
+```
+
+## Required Skills
+
+| Skill | Purpose | Config Required |
+|-------|---------|----------------|
+| `code-review` | Analyze git diffs for quality, style, complexity | None |
+| `test-runner` | Run test suite and verify coverage | None |
+| `bug-triage` | Classify and prioritize security findings | None |
+| `git-commit-helper` | Analyze commit messages for conventional format | None |
+
+## Optional Skills
+
+| Skill | Purpose |
+|-------|---------|
+| `send-pdf-to-slack` | Post review summary to Slack channel |
+| `daily-standup-report` | Daily PR review activity summary |
+
+## Workflow
+
+```
+  New PR Detected
+       │
+       ▼
+  Senior Reviewer                Security Auditor
+       │                              │
+       ├─ Run code-review skill        │
+       ├─ Analyze architecture         │
+       ├─ Check naming, patterns       │
+       ├─ Review error handling        │
+       │                              │
+       ├─ Run test-runner skill        │
+       ├─ Verify tests pass            │
+       ├─ Check coverage threshold     │
+       │                              │
+       │         Parallel              │
+       │──────────────────────────────▶│
+       │                              ├─ Scan for OWASP Top 10
+       │                              ├─ Check for secrets
+       │                              ├─ Review auth/authz
+       │                              ├─ Classify findings
+       │                              │  (bug-triage skill)
+       │                              │
+       │◀─────── Security Report ─────┤
+       │                              │
+       ├─ Consolidate all findings     │
+       ├─ Produce final verdict        │
+       │  (approve / request changes)  │
+       │                              │
+       └─ Post review comment ─────────┘
+```
+
+## Expected Output Examples
+
+### Code Quality Review (from Senior Reviewer)
+```markdown
+## Code Review: PR #142 — Add user preferences API
+
+### Summary
+**Verdict**: REQUEST CHANGES (2 blockers, 3 suggestions)
+
+**Files changed**: 6 | **Lines**: +284 / -12
+**Tests**: 14 passing, 0 failing | **Coverage**: 87% (+3%)
+
+### Findings
+
+#### Blockers
+1. **Missing input validation** — `preferences.controller.ts:45`
+   The `updatePreferences` handler accepts raw body without validation.
+   Any malformed JSON crashes the service with unhandled TypeError.
+   **Fix**: Add Zod schema validation before processing.
+
+2. **N+1 query in getAll** — `preferences.service.ts:78`
+   Loading preferences with `Promise.all(users.map(u => getPrefs(u.id)))`.
+   With 1000 users this fires 1000 queries.
+   **Fix**: Batch query with `WHERE user_id IN (...)`.
+
+#### Suggestions
+1. **Consider extracting preference keys to constants** — `preferences.types.ts:12`
+   String literals `'theme'`, `'language'`, `'timezone'` appear 4 times.
+   Extract to a `PREFERENCE_KEYS` constant.
+
+2. **Add JSDoc to public methods** — `preferences.service.ts`
+   3 public methods missing documentation. Project convention requires JSDoc.
+
+3. **Test edge case: empty preferences object** — `preferences.service.test.ts`
+   No test for `updatePreferences({})`. Should return 400 or no-op.
+
+### Test Results
+✅ All 14 tests passing
+✅ Coverage: 87% (above 80% threshold)
+⚠️ Missing edge case test (see suggestion #3)
+```
+
+### Security Assessment (from Security Auditor)
+```markdown
+## Security Assessment: PR #142
+
+### Risk Rating: MEDIUM (1 high, 1 low finding)
+
+### Findings
+
+| # | Severity | Category | Location | Description |
+|---|----------|----------|----------|-------------|
+| 1 | HIGH | Injection | `preferences.controller.ts:45` | No input validation — potential NoSQL injection if using MongoDB, or payload manipulation with any DB. Aligns with OWASP A03:2021 (Injection). |
+| 2 | LOW | Information Disclosure | `preferences.controller.ts:67` | Error response includes full stack trace in non-production. Recommend stripping in all environments. |
+
+### Remediation
+1. **[HIGH] Add input validation**: Use Zod or Joi to validate request body schema before processing. Whitelist allowed preference keys.
+2. **[LOW] Strip stack traces**: Use error middleware that omits stack traces regardless of NODE_ENV.
+
+### Checks Passed
+- ✅ No hardcoded secrets or API keys
+- ✅ Authentication middleware present on all routes
+- ✅ No use of `eval()` or dynamic code execution
+- ✅ Dependencies have no known CVEs (checked via `npm audit`)
+
+### Recommendation: BLOCK until HIGH finding is resolved
+```
+
+### Final Verdict (from Senior Reviewer)
+```markdown
+## Final Review: PR #142 — Add user preferences API
+
+**Verdict**: ❌ REQUEST CHANGES
+
+### Consolidated Findings
+- 🔴 2 Blockers (1 code quality + 1 security HIGH)
+- 🟡 3 Suggestions
+- 🟢 Tests passing, coverage above threshold
+
+### Required Before Merge
+1. Add input validation with Zod schema (blocks both code quality + security findings)
+2. Fix N+1 query in `getAll`
+
+### Nice to Have
+3. Extract preference key constants
+4. Add JSDoc to public methods
+5. Add empty-object edge case test
+
+### What's Good
+- Clean API design following RESTful conventions
+- Good test coverage (87%)
+- Proper error handling in happy path
+- Consistent with existing codebase patterns
+```
+
+## Customization
+
+- **Add linting**: Include quality gates for ESLint/Prettier checks
+- **Adjust thresholds**: Modify coverage requirements in Senior Reviewer's prompt
+- **Add CI integration**: Trigger review on GitHub webhook events
+- **Scale**: Add a third agent for performance review (benchmarks, load testing)
+- **Customize rules**: Edit Security Auditor's prompt to focus on your tech stack's specific vulnerabilities

package/config/templates/code-review-team/team-config.json

@@ -0,0 +1,16 @@
+{
+  "name": "Code Review Pipeline",
+  "description": "AI team that automatically reviews pull requests for code quality, security vulnerabilities, and test coverage. Built for SaaS teams, dev shops, and any team that wants faster, more consistent code reviews.",
+  "members": [
+    {
+      "name": "Senior Reviewer",
+      "role": "architect",
+      "systemPrompt": "You are the senior code reviewer on a code review team. You review pull requests for architecture, code quality, maintainability, and adherence to project conventions. Use the code-review skill to analyze git diffs and produce structured reviews. Use the test-runner skill to verify test coverage and ensure all tests pass. Focus on: naming conventions, separation of concerns, error handling, performance implications, and API design. Coordinate with the Security Auditor on security findings. Produce a final review verdict (approve / request changes) with clear, actionable feedback."
+    },
+    {
+      "name": "Security Auditor",
+      "role": "qa-engineer",
+      "systemPrompt": "You are the security auditor on a code review team. You scan every PR for security vulnerabilities: injection flaws (SQL, XSS, command injection), authentication/authorization issues, secrets exposure, insecure dependencies, and OWASP Top 10 violations. Use the code-review skill with security focus to analyze changes. Use the bug-triage skill to classify and prioritize any findings. Produce a security assessment for each PR: list of findings (severity + remediation), overall risk rating, and approval/block recommendation. Coordinate with the Senior Reviewer on the final review verdict."
+    }
+  ]
+}

package/config/templates/code-review-team.json

@@ -0,0 +1,62 @@
+{
+  "id": "code-review-team",
+  "name": "Code Review Pipeline",
+  "description": "AI team that automatically reviews pull requests for code quality, security vulnerabilities, and test coverage. Built for SaaS teams, dev shops, and any team that wants faster, more consistent code reviews.",
+  "category": "development",
+  "targetVertical": "SaaS Team / Dev Agency / Engineering Org",
+  "members": [
+    {
+      "name": "Senior Reviewer",
+      "role": "architect",
+      "systemPrompt": "You are the senior code reviewer on a code review team. You review pull requests for architecture, code quality, maintainability, and adherence to project conventions. Use the code-review skill to analyze git diffs and produce structured reviews. Use the test-runner skill to verify test coverage and ensure all tests pass. Focus on: naming conventions, separation of concerns, error handling, performance implications, and API design. Coordinate with the Security Auditor on security findings. Produce a final review verdict (approve / request changes) with clear, actionable feedback."
+    },
+    {
+      "name": "Security Auditor",
+      "role": "qa-engineer",
+      "systemPrompt": "You are the security auditor on a code review team. You scan every PR for security vulnerabilities: injection flaws (SQL, XSS, command injection), authentication/authorization issues, secrets exposure, insecure dependencies, and OWASP Top 10 violations. Use the code-review skill with security focus to analyze changes. Use the bug-triage skill to classify and prioritize any findings. Produce a security assessment for each PR: list of findings (severity + remediation), overall risk rating, and approval/block recommendation. Coordinate with the Senior Reviewer on the final review verdict."
+    }
+  ],
+  "requiredSkills": [
+    "code-review",
+    "test-runner",
+    "bug-triage",
+    "git-commit-helper"
+  ],
+  "optionalSkills": [
+    "send-pdf-to-slack",
+    "daily-standup-report"
+  ],
+  "workflow": {
+    "name": "PR Review Pipeline",
+    "steps": [
+      {
+        "step": 1,
+        "name": "PR Detection & Initial Analysis",
+        "owner": "Senior Reviewer",
+        "description": "Detect new or updated PR. Run code-review skill on the diff to produce structured analysis of changes.",
+        "output": "Structured code review (markdown) with findings by category"
+      },
+      {
+        "step": 2,
+        "name": "Test Verification",
+        "owner": "Senior Reviewer",
+        "description": "Run test suite via test-runner skill. Verify all tests pass and coverage meets threshold.",
+        "output": "Test results with coverage report"
+      },
+      {
+        "step": 3,
+        "name": "Security Scan",
+        "owner": "Security Auditor",
+        "description": "Analyze changes for security vulnerabilities. Classify findings by severity using bug-triage skill.",
+        "output": "Security assessment (findings list + severity + risk rating)"
+      },
+      {
+        "step": 4,
+        "name": "Final Verdict",
+        "owner": "Senior Reviewer",
+        "description": "Consolidate code quality review + test results + security assessment. Produce final verdict with actionable feedback.",
+        "output": "PR review comment (approve / request changes) with consolidated feedback"
+      }
+    ]
+  }
+}

package/config/templates/content-generation-team/README.md

@@ -0,0 +1,128 @@
+# Content Generation Studio — Quick Start
+
+## Overview
+
+An AI team that automatically produces SEO-optimized blog posts, social media content, and cover images. The team follows a structured pipeline: research → draft → review → publish.
+
+**Target Users**: Content agencies, solo creators, marketing teams
+**Team Size**: 3 agents (Content Strategist + Writer + Editor)
+
+## Prerequisites
+
+- Crewly installed and running (`npx crewly start`)
+- Gemini API key configured (required for `nano-banana-image` skill)
+
+## Quick Start
+
+```bash
+# 1. Create the team from template
+npx crewly create-team --template content-generation-team
+
+# 2. Start the team
+npx crewly start
+```
+
+## Required Skills
+
+| Skill | Purpose | Config Required |
+|-------|---------|----------------|
+| `seo-blog-writer` | Generate SEO-optimized blog structures | None |
+| `social-media-post` | Create platform-optimized social posts (X, LinkedIn, Reddit) | None |
+| `nano-banana-image` | Generate cover images and visuals | `GEMINI_API_KEY` |
+| `feedback-analyzer` | Analyze audience feedback for content improvement | None |
+
+## Optional Skills
+
+| Skill | Purpose |
+|-------|---------|
+| `send-pdf-to-slack` | Share formatted content reports via Slack |
+| `daily-standup-report` | Daily team activity summary |
+
+## Workflow
+
+```
+Content Strategist          Writer              Editor
+      │                       │                   │
+      ├─ Research topics       │                   │
+      ├─ Keyword analysis      │                   │
+      ├─ Create content brief  │                   │
+      │         │              │                   │
+      │         └──────────────▶                   │
+      │                        ├─ Write blog post  │
+      │                        ├─ Create social    │
+      │                        │   posts           │
+      │                        ├─ Generate images  │
+      │                        │         │         │
+      │                        │         └─────────▶
+      │                        │                   ├─ Review quality
+      │                        │                   ├─ Check SEO
+      │                        │                   ├─ Verify accuracy
+      │                        │                   │
+      │                        │◀── Approved ──────┤
+      │                        │  or revisions     │
+      │                        ├─ Publish content  │
+      │                        └───────────────────┘
+```
+
+## Expected Output Examples
+
+### Blog Post (from Writer)
+```markdown
+# 10 Ways AI Is Transforming Small Business Operations in 2026
+
+*Meta: Discover how AI automation is helping SMBs reduce costs by 40%...*
+
+## Introduction
+...
+
+## 1. Automated Customer Support
+...
+
+## Conclusion
+...
+
+**Keywords**: AI small business, AI automation, SMB operations
+**Word count**: ~1,500
+**Reading time**: 7 min
+```
+
+### Social Media Posts (from Writer)
+```
+[X/Twitter]
+AI is quietly transforming how small businesses operate.
+
+We analyzed 10 real use cases where SMBs cut costs by 40%+ using AI teams.
+
+The surprising part? Most started in under a week.
+
+Thread 🧵👇
+
+---
+
+[LinkedIn]
+I've been watching a quiet revolution in small business operations.
+
+AI teams — not single chatbots, but coordinated groups of AI agents —
+are now handling tasks that used to require 3-5 employees...
+```
+
+### Content Brief (from Strategist)
+```markdown
+## Content Brief: AI for SMB Operations
+
+**Target keyword**: "AI small business automation"
+**Search volume**: 2,400/mo | **Difficulty**: Medium
+**Target audience**: SMB owners, ops managers
+**Content type**: Listicle (10 items)
+**Word count target**: 1,200-1,800
+**Tone**: Practical, data-driven, accessible
+**CTA**: Free trial signup
+**Competitor gaps**: Most articles are theoretical — we add real ROI data
+```
+
+## Customization
+
+- **Add platforms**: Modify Writer's `systemPrompt` to include additional platforms
+- **Change tone**: Adjust Strategist's brief template for different brand voices
+- **Scale up**: Add a second Writer agent for higher content volume
+- **Add distribution**: Include `send-pdf-to-slack` for team notification on publish

package/config/templates/content-generation-team/team-config.json

@@ -0,0 +1,21 @@
+{
+  "name": "Content Generation Studio",
+  "description": "AI team that automatically produces SEO-optimized blog posts, social media content, and accompanying images. Ideal for content agencies, solo creators, and marketing teams.",
+  "members": [
+    {
+      "name": "Content Strategist",
+      "role": "content-strategist",
+      "systemPrompt": "You are the content strategist on a content generation team. Your job is to research topics, identify high-value keywords, and create content briefs. You define the content calendar, set quality standards, and review all output before publication. Use the seo-blog-writer skill to generate optimized content structures. Coordinate with the Writer for drafts and the Editor for quality assurance."
+    },
+    {
+      "name": "Writer",
+      "role": "generalist",
+      "systemPrompt": "You are the writer on a content generation team. You take content briefs from the Strategist and produce full-length blog posts, social media copy, and marketing materials. Use the social-media-post skill to create platform-optimized posts for X, LinkedIn, and Reddit. Use the nano-banana-image skill to generate accompanying visuals. Focus on engaging, accurate, on-brand content that follows the brief's keyword and structure guidelines."
+    },
+    {
+      "name": "Editor",
+      "role": "qa",
+      "systemPrompt": "You are the editor on a content generation team. You review all content produced by the Writer for accuracy, tone consistency, SEO compliance, and brand voice. Check keyword placement, readability, and factual correctness. Approve content for publication or send back with specific revision notes. Use the feedback-analyzer skill to incorporate audience feedback into content improvements."
+    }
+  ]
+}

package/config/templates/content-generation-team.json

@@ -0,0 +1,67 @@
+{
+  "id": "content-generation-team",
+  "name": "Content Generation Studio",
+  "description": "AI team that automatically produces SEO-optimized blog posts, social media content, and accompanying images. Ideal for content agencies, solo creators, and marketing teams.",
+  "category": "content",
+  "targetVertical": "Content Agency / Solo Creator / Marketing Team",
+  "members": [
+    {
+      "name": "Content Strategist",
+      "role": "content-strategist",
+      "systemPrompt": "You are the content strategist on a content generation team. Your job is to research topics, identify high-value keywords, and create content briefs. You define the content calendar, set quality standards, and review all output before publication. Use the seo-blog-writer skill to generate optimized content structures. Coordinate with the Writer for drafts and the Editor for quality assurance."
+    },
+    {
+      "name": "Writer",
+      "role": "generalist",
+      "systemPrompt": "You are the writer on a content generation team. You take content briefs from the Strategist and produce full-length blog posts, social media copy, and marketing materials. Use the social-media-post skill to create platform-optimized posts for X, LinkedIn, and Reddit. Use the nano-banana-image skill to generate accompanying visuals. Focus on engaging, accurate, on-brand content that follows the brief's keyword and structure guidelines."
+    },
+    {
+      "name": "Editor",
+      "role": "qa",
+      "systemPrompt": "You are the editor on a content generation team. You review all content produced by the Writer for accuracy, tone consistency, SEO compliance, and brand voice. Check keyword placement, readability, and factual correctness. Approve content for publication or send back with specific revision notes. Use the feedback-analyzer skill to incorporate audience feedback into content improvements."
+    }
+  ],
+  "requiredSkills": [
+    "seo-blog-writer",
+    "social-media-post",
+    "nano-banana-image",
+    "feedback-analyzer"
+  ],
+  "optionalSkills": [
+    "send-pdf-to-slack",
+    "daily-standup-report"
+  ],
+  "workflow": {
+    "name": "Content Production Pipeline",
+    "steps": [
+      {
+        "step": 1,
+        "name": "Topic Research & Brief",
+        "owner": "Content Strategist",
+        "description": "Research trending topics, analyze keywords, create content brief with target keywords, structure, and audience.",
+        "output": "Content brief (markdown)"
+      },
+      {
+        "step": 2,
+        "name": "Draft Creation",
+        "owner": "Writer",
+        "description": "Write full blog post and social media variants based on the content brief. Generate cover image.",
+        "output": "Blog post (markdown) + social posts (per platform) + cover image (PNG)"
+      },
+      {
+        "step": 3,
+        "name": "Editorial Review",
+        "owner": "Editor",
+        "description": "Review draft for quality, SEO compliance, accuracy, and brand voice. Approve or return with revision notes.",
+        "output": "Approved content or revision notes"
+      },
+      {
+        "step": 4,
+        "name": "Publish & Distribute",
+        "owner": "Writer",
+        "description": "Post approved content to target platforms. Share via Slack for team visibility.",
+        "output": "Published posts with links"
+      }
+    ]
+  }
+}

package/config/templates/demo-team.json

@@ -0,0 +1,22 @@
+{
+  "id": "demo-team",
+  "name": "Demo Team",
+  "description": "Developer + Product Manager + Ops Engineer for a quick Crewly demo. Shows multi-role collaboration: the PM defines tasks, the developer builds features, and the ops engineer handles deployment and infrastructure.",
+  "members": [
+    {
+      "name": "Developer",
+      "role": "developer",
+      "systemPrompt": "You are the developer on a demo team. Implement features, write tests, and fix bugs. Coordinate with the product manager on requirements and the ops engineer on deployment needs. Write clean, well-tested TypeScript code following project conventions."
+    },
+    {
+      "name": "Product Manager",
+      "role": "product-manager",
+      "systemPrompt": "You are the product manager on a demo team. Define requirements, create task breakdowns, and prioritize the backlog. Review the developer's work against acceptance criteria. Coordinate between the developer and ops engineer to keep the team aligned and shipping."
+    },
+    {
+      "name": "Ops Engineer",
+      "role": "ops",
+      "systemPrompt": "You are the ops engineer on a demo team. Manage deployments, CI/CD pipelines, and infrastructure. Monitor system health and respond to incidents. Coordinate with the developer on build and release processes. Keep environments stable and well-documented."
+    }
+  ]
+}

package/config/templates/social-media-ops-team/README.md

@@ -0,0 +1,145 @@
+# Social Media Ops — Quick Start
+
+## Overview
+
+An AI team that monitors trends, creates platform-native content, manages posting schedules, and analyzes engagement metrics. Runs a continuous weekly cycle: plan → create → publish → analyze → optimize.
+
+**Target Users**: E-commerce brands, DTC companies, social-first businesses
+**Team Size**: 3 agents (Social Manager + Content Creator + Analyst)
+
+## Prerequisites
+
+- Crewly installed and running (`npx crewly start`)
+- Gemini API key configured (required for `nano-banana-image` skill)
+- (Optional) Xiaohongshu access for `rednote-reader` skill
+
+## Quick Start
+
+```bash
+# 1. Create the team from template
+npx crewly create-team --template social-media-ops-team
+
+# 2. Start the team
+npx crewly start
+```
+
+## Required Skills
+
+| Skill | Purpose | Config Required |
+|-------|---------|----------------|
+| `social-media-post` | Generate platform-optimized social posts | None |
+| `nano-banana-image` | Create visual assets and graphics | `GEMINI_API_KEY` |
+| `feedback-analyzer` | Analyze audience comments and sentiment | None |
+| `daily-standup-report` | Compile daily activity summaries | None |
+
+## Optional Skills
+
+| Skill | Purpose |
+|-------|---------|
+| `rednote-reader` | Monitor Xiaohongshu trends (China market) |
+| `send-pdf-to-slack` | Share weekly reports via Slack |
+
+## Workflow
+
+```
+          Monday                    Tue-Thu                  Friday
+            │                         │                        │
+  Social Manager                Content Creator             Analyst
+      │                              │                        │
+      ├─ Monitor trends              │                        │
+      ├─ Review competitors          │                        │
+      ├─ Plan weekly calendar        │                        │
+      │         │                    │                        │
+      │         └────────────────────▶                        │
+      │                              ├─ Create posts          │
+      │                              ├─ Generate visuals      │
+      │                              ├─ Adapt per platform    │
+      │                              │         │              │
+      │◀─────────────────────────────┤         │              │
+      │                              │         │              │
+      ├─ Review & approve            │         │              │
+      ├─ Schedule posting            │         │              │
+      │                              │         │              │
+      │                              │         └──────────────▶
+      │                              │                        ├─ Collect metrics
+      │                              │                        ├─ Analyze performance
+      │                              │                        ├─ Weekly report
+      │                              │                        │
+      │◀──────────────────────────────────────────────────────┤
+      ├─ Adjust next week's          │                        │
+      │   strategy                   │                        │
+      └──────────────────────────────┘                        │
+                              Next cycle                      │
+```
+
+## Expected Output Examples
+
+### Weekly Content Calendar (from Social Manager)
+```markdown
+## Week of March 3, 2026
+
+| Day | Platform | Topic | Format | Status |
+|-----|----------|-------|--------|--------|
+| Mon | X | Product launch teaser | Thread (5 tweets) | Draft |
+| Mon | LinkedIn | Industry insight post | Long-form | Draft |
+| Tue | X | Customer testimonial | Quote card | Draft |
+| Wed | X | Behind-the-scenes | Photo + caption | Draft |
+| Wed | Reddit | r/ecommerce value post | Tutorial | Draft |
+| Thu | LinkedIn | Team spotlight | Story post | Draft |
+| Fri | X | Weekly roundup | Thread | Draft |
+
+**Theme**: Product launch week
+**Hashtags**: #AIteams #ecommerce #automation
+**Competitor watch**: [Brand X] launching similar feature — differentiate on pricing
+```
+
+### Platform-Native Post (from Content Creator)
+```
+[X/Twitter — Thread]
+1/ We just shipped something wild.
+
+An AI team that runs your entire social media — from trend research
+to posting to analytics.
+
+Not a scheduler. Not a chatbot. A full team. Here's how it works 👇
+
+2/ The Social Manager agent monitors trends 24/7.
+It watches X, LinkedIn, Reddit, and even Xiaohongshu.
+
+When it spots a trending topic in your niche, it creates a content brief
+and assigns it to the Content Creator.
+
+3/ The Content Creator produces platform-native posts.
+...
+```
+
+### Weekly Analytics Report (from Analyst)
+```markdown
+## Social Performance — Week of Feb 24, 2026
+
+### Summary
+- **Total posts**: 12 across 3 platforms
+- **Total impressions**: 45,200 (+18% vs last week)
+- **Engagement rate**: 4.2% (benchmark: 2.5%)
+- **Top post**: "AI Team ROI Calculator" thread — 12K impressions, 340 engagements
+
+### Platform Breakdown
+| Platform | Posts | Impressions | Engagement | Best Day |
+|----------|-------|-------------|------------|----------|
+| X | 7 | 28,400 | 4.8% | Tuesday |
+| LinkedIn | 3 | 12,100 | 3.1% | Monday |
+| Reddit | 2 | 4,700 | 5.2% | Wednesday |
+
+### Recommendations
+1. **Double down on X threads** — highest engagement format (5.1% avg)
+2. **Post LinkedIn content Mon-Tue** — 2x engagement vs Thu-Fri
+3. **Reddit tutorials outperform discussions** — 3x upvotes on how-to posts
+4. **Test video content next week** — competitor [Brand X] seeing 8% engagement on video
+```
+
+## Customization
+
+- **Add platforms**: Add Xiaohongshu by enabling `rednote-reader` in optional skills
+- **Change cadence**: Modify Social Manager's prompt for daily vs weekly planning
+- **Add team members**: Add a second Content Creator for higher volume
+- **Integrate Slack**: Add `send-pdf-to-slack` to auto-share weekly reports with stakeholders

package/config/templates/social-media-ops-team/team-config.json

@@ -0,0 +1,21 @@
+{
+  "name": "Social Media Ops",
+  "description": "AI team that monitors social trends, creates platform-native content, manages posting schedules, and analyzes engagement. Built for e-commerce brands, DTC companies, and social-first businesses.",
+  "members": [
+    {
+      "name": "Social Manager",
+      "role": "content-strategist",
+      "systemPrompt": "You are the social media manager on a social ops team. You own the content calendar, monitor trending topics and competitor activity, and set the strategy for each platform (X, LinkedIn, Reddit, Xiaohongshu). Use the rednote-reader skill to monitor Xiaohongshu trends and competitor posts. Define posting schedules, approve content before publishing, and review analytics to optimize strategy. Coordinate the Content Creator for production and the Analyst for performance insights."
+    },
+    {
+      "name": "Content Creator",
+      "role": "designer",
+      "systemPrompt": "You are the content creator on a social ops team. You produce platform-native social media posts, short-form copy, and visual assets. Use the social-media-post skill to generate platform-optimized posts for X, LinkedIn, and Reddit. Use the nano-banana-image skill to create eye-catching visuals and graphics. Adapt content tone and format to each platform's audience. Follow the Social Manager's content calendar and brand guidelines."
+    },
+    {
+      "name": "Analyst",
+      "role": "product-manager",
+      "systemPrompt": "You are the analytics lead on a social ops team. You track engagement metrics, identify high-performing content patterns, and produce weekly performance reports. Use the feedback-analyzer skill to analyze audience comments and sentiment. Use the daily-standup-report skill to compile daily activity summaries. Recommend content adjustments based on data: what topics resonate, best posting times, which platforms drive the most engagement. Feed insights back to the Social Manager for strategy iteration."
+    }
+  ]
+}