crewly 1.5.18 → 1.5.19

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

@@ -1,128 +0,0 @@
-# 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/norms/publish-checklist.md

@@ -1,64 +0,0 @@
-# Publish Checklist
-
-**Trigger**: before_publish
-**Applies to**: *
-**Version**: 1.0.0
-
-## Overview
-
-This is the final gate before any content goes live. Run through every item
-after content review is complete and all revisions are applied.
-
-## Steps
-
-1. **SEO Final Check**
-   - Title tag set and within 50-60 chars
-   - Meta description set and within 150-160 chars
-   - URL slug is clean, lowercase, hyphenated (no dates or IDs)
-   - Canonical URL set correctly (avoid duplicate content)
-   - Schema markup added if applicable (article, FAQ, how-to)
-
-2. **Image Verification**
-   - All images load correctly (no broken references)
-   - Images compressed (< 200KB for web, < 500KB for hero)
-   - Alt text on every image (descriptive, includes keyword where natural)
-   - Image dimensions match platform requirements
-   - Nano Banana credits included where applicable
-
-3. **Link Audit**
-   - All internal links resolve (no 404s)
-   - All external links open in new tab (`target="_blank"`)
-   - External links point to authoritative, current pages
-   - No affiliate links without disclosure
-   - CTA links tested and working
-
-4. **Cross-Platform Formatting**
-   - Blog post renders correctly in web preview
-   - Social posts fit platform character limits (X: 280, LinkedIn: 3000)
-   - Email version displays properly in major clients
-   - Mobile layout verified (responsive, no horizontal scroll)
-
-5. **Compliance & Legal**
-   - No copyrighted images without license
-   - Proper attribution for quotes and data
-   - Disclosure added for sponsored content
-   - GDPR/privacy considerations for any personal data references
-
-## Checklist
-
-- [ ] SEO metadata complete (title, meta, slug, canonical)
-- [ ] All images load, compressed, and have alt text
-- [ ] All internal links resolve (no 404s)
-- [ ] All external links work and open in new tab
-- [ ] CTA links tested
-- [ ] Renders correctly on desktop and mobile
-- [ ] Social posts within platform character limits
-- [ ] No copyright violations
-- [ ] Proper attributions included
-- [ ] Final proofread complete
-
-## Exceptions
-
-- **Urgent time-sensitive posts** (e.g., breaking news response): May publish with
-  a placeholder hero image and add the final image within 2 hours.
-- **Internal team content**: Skip compliance/legal section.

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

@@ -1,28 +0,0 @@
-{
-  "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.",
-  "norms": {
-    "enabled": true,
-    "files": [
-      { "file": "content-review.md", "trigger": "before_publish", "roles": ["*"] },
-      { "file": "brand-guidelines.md", "trigger": "always", "roles": ["*"] }
-    ]
-  },
-  "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

@@ -1,67 +0,0 @@
-{
-  "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/dev-fullstack/norms/docker-deploy-cleanup.md

@@ -1,28 +0,0 @@
-# Docker Deploy Cleanup SOP
-
-**Trigger**: after_deploy
-**Applies to**: developer, team-leader
-**Version**: 1.0.0
-
-## Overview
-
-Standard operating procedure for cleaning up Docker resources after every deployment. Prevents disk space exhaustion on development machines from accumulated build cache and old images.
-
-## Steps
-
-1. **Prune dangling resources** — Run `docker system prune -f` to remove dangling images, stopped containers, and unused networks.
-2. **Remove old images** — If multiple versions of the deployed image exist locally, remove all but the latest: `docker rmi <old-image:old-tag>`.
-3. **Verify disk recovery** — Check that `docker system df` shows reasonable usage. Flag if total usage exceeds 20 GB.
-4. **Never build simultaneously** — Only build one Docker image at a time. Concurrent builds compete for disk and CPU, causing flaky builds.
-
-## Checklist
-
-- [ ] `docker system prune -f` executed after deploy
-- [ ] Only the current version image remains locally for each service
-- [ ] No dangling `<none>` images present (`docker images --filter dangling=true`)
-- [ ] Build cache reclaimed (check `docker system prune` output)
-
-## Exceptions
-
-- Skip cleanup if deploying multiple services in sequence — run cleanup once at the end.
-- Do not prune named volumes (`docker volume prune`) without explicit approval, as they may contain persistent data.

package/config/templates/dev-fullstack/template.json

@@ -1,178 +0,0 @@
-{
-  "id": "dev-fullstack",
-  "name": "Fullstack Development Team",
-  "description": "Team Leader + developers + QA for building web applications",
-  "category": "development",
-  "version": "2.0.0",
-  "tags": ["development", "web", "fullstack", "testing"],
-  "icon": "laptop",
-  "hierarchical": true,
-  "compatibleRuntimes": ["claude-code", "crewly-agent"],
-  "defaultRuntime": "crewly-agent",
-  "norms": {
-    "enabled": true,
-    "files": [
-      { "file": "code-commit-sop.md", "trigger": "before_commit", "roles": ["developer", "team-leader"] },
-      { "file": "quality-gates.md", "trigger": "before_deploy", "roles": ["*"] }
-    ]
-  },
-  "roles": [
-    {
-      "role": "team-leader",
-      "label": "Tech Lead",
-      "defaultName": "Tech Lead",
-      "count": 1,
-      "hierarchyLevel": 1,
-      "canDelegate": true,
-      "defaultTools": [
-        "delegate_task",
-        "send_message",
-        "get_team_status",
-        "get_agent_status",
-        "report_status",
-        "complete_task",
-        "handle_agent_failure",
-        "schedule_check",
-        "subscribe_event",
-        "recall_memory",
-        "remember",
-        "bash_exec",
-        "read_file",
-        "write_file",
-        "edit_file",
-        "glob",
-        "grep",
-        "git_status",
-        "git_diff",
-        "git_commit"
-      ],
-      "modelConfig": {
-        "provider": "anthropic",
-        "model": "claude-sonnet-4-20250514",
-        "temperature": 0.3
-      },
-      "enableBrowser": true
-    },
-    {
-      "role": "developer",
-      "label": "Developer",
-      "defaultName": "Developer",
-      "count": 2,
-      "hierarchyLevel": 2,
-      "canDelegate": false,
-      "reportsTo": "team-leader",
-      "defaultTools": [
-        "report_status",
-        "complete_task",
-        "send_message",
-        "recall_memory",
-        "remember",
-        "bash_exec",
-        "read_file",
-        "write_file",
-        "edit_file",
-        "glob",
-        "grep",
-        "git_status",
-        "git_diff",
-        "git_commit"
-      ],
-      "modelConfig": {
-        "provider": "anthropic",
-        "model": "claude-sonnet-4-20250514",
-        "temperature": 0.2
-      },
-      "enableBrowser": false
-    },
-    {
-      "role": "qa-engineer",
-      "label": "QA Engineer",
-      "defaultName": "QA",
-      "count": 1,
-      "hierarchyLevel": 2,
-      "canDelegate": false,
-      "reportsTo": "team-leader",
-      "defaultTools": [
-        "report_status",
-        "complete_task",
-        "send_message",
-        "recall_memory",
-        "remember",
-        "bash_exec",
-        "read_file",
-        "glob",
-        "grep"
-      ],
-      "modelConfig": {
-        "provider": "anthropic",
-        "model": "claude-sonnet-4-20250514",
-        "temperature": 0.2
-      },
-      "enableBrowser": true
-    }
-  ],
-  "verificationPipeline": {
-    "name": "Development Quality Pipeline",
-    "steps": [
-      {
-        "id": "quality-gates",
-        "name": "Quality Gates",
-        "description": "Run typecheck, unit tests, lint, and build",
-        "method": "quality_gates",
-        "critical": true,
-        "config": {
-          "gates": ["typecheck", "tests", "build"]
-        }
-      },
-      {
-        "id": "code-review",
-        "name": "Code Review",
-        "description": "TL reviews code diff for patterns and quality",
-        "method": "code_review",
-        "critical": true,
-        "config": {
-          "maxDiffLines": 500,
-          "checkPatterns": true
-        }
-      },
-      {
-        "id": "browser-test",
-        "name": "Browser Verification",
-        "description": "Open in browser, screenshot, verify UI matches spec",
-        "method": "browser_test",
-        "critical": false,
-        "config": {
-          "screenshotTool": "computer-use",
-          "viewports": ["desktop"]
-        }
-      },
-      {
-        "id": "e2e",
-        "name": "E2E Tests",
-        "description": "Run Playwright end-to-end test suite",
-        "method": "e2e_test",
-        "critical": false,
-        "config": {
-          "framework": "playwright",
-          "testDir": "tests/e2e"
-        }
-      }
-    ],
-    "passPolicy": "critical_only",
-    "maxRetries": 2
-  },
-  "monitoringDefaults": {
-    "idleEvent": true,
-    "fallbackCheckMinutes": 5
-  },
-  "maxWorkersPerLeader": 4,
-  "mission": "Build and maintain fullstack web applications with high code quality and test coverage",
-  "budget": {
-    "maxTokensPerDay": 5000000,
-    "alertThreshold": 80
-  },
-  "qualityGate": {
-    "autoApprove": false,
-    "minQualityScore": 80
-  }
-}

package/config/templates/education-smb/README.md

@@ -1,27 +0,0 @@
-# Education SMB Team Template
-
-This template provides a complete AI team setup for small and medium-sized education businesses. It covers the entire lifecycle of educational service delivery, from curriculum design to student engagement and performance analytics.
-
-## 🏗️ Team Composition
-- **Curriculum Designer (Alex)**: Focuses on structure and pedagogy.
-- **Content Creator (Casey)**: Produces engaging lesson materials.
-- **Student Engagement Manager (Sam)**: Manages community and feedback.
-- **Analytics Specialist (Skyler)**: Provides data-driven insights.
-
-## 🔄 Included Workflows
-1. **Course Content Generation**: End-to-end flow from curriculum design to finalized content.
-2. **Student Communication**: Automates feedback loops and announcements.
-3. **Weekly/Monthly Reporting**: Generates operational and performance insights.
-
-## 📚 Bundled Knowledge
-- **Education Industry Context**: Industry-standard SOPs and terminology.
-- **Content Quality Standards**: Guidelines for pedagogical alignment and accessibility.
-
-## 🚀 Quick Start
-To instantiate this team, use the Crewly CLI:
-```bash
-npx crewly create team --template education-smb
-```
-
-## 🎯 Default Goals
-See `goals.md` for the pre-set OKRs designed to drive growth and efficiency in an educational SMB context.

package/config/templates/education-smb/goals.md

@@ -1,16 +0,0 @@
-# Education SMB Team OKRs
-
-## Objective 1: Deliver High-Quality, Scalable Educational Content
-- **KR1**: Complete the curriculum design and content production for [Course Name] within 30 days.
-- **KR2**: Achieve a 100% compliance rate with FERPA/COPPA standards across all content.
-- **KR3**: Maintain a minimum quality score of 4.5/5 across all peer reviews.
-
-## Objective 2: Maximize Student Engagement and Satisfaction
-- **KR1**: Increase average student completion rates for new courses by 20%.
-- **KR2**: Reduce response time to student queries to under 4 hours on average.
-- **KR3**: Maintain a Net Promoter Score (NPS) of 75 or higher.
-
-## Objective 3: Optimize Operational Efficiency through AI
-- **KR1**: Reduce the time-to-market for a new 10-lesson module from 3 weeks to 1 week.
-- **KR2**: Automate 80% of routine student notifications and progress reports.
-- **KR3**: Maintain an AI team token ROI of at least 5x compared to manual labor costs.

package/config/templates/education-smb/knowledge/docs/content-standards.md

@@ -1,24 +0,0 @@
-# Education Content Quality Standards
-
-## 1. Pedagogical Alignment
-- Content must align with the stated learning objectives of the curriculum.
-- Materials should follow an "Instructional Scaffolding" approach (moving from simple to complex).
-
-## 2. Reading Level and Accessibility
-- **Parent Content**: Target Grade 8 reading level.
-- **Student Content**: Target the specific grade level of the target audience.
-- **Teacher Content**: Can use professional terminology but must remain clear and actionable.
-
-## 3. Engagement and Interactivity
-- Use active voice and direct address.
-- Include knowledge checks or reflection prompts every 10-15 minutes of content.
-- Use diverse examples that represent various backgrounds and cultures.
-
-## 4. Compliance and Safety
-- No student PII (Personally Identifiable Information) in public-facing or AI-generated content.
-- All links must be verified for safety and relevance.
-- Content must be free of bias and stereotypes.
-
-## 5. Visual Consistency
-- Use consistent branding and formatting for all course materials.
-- All images must have alt-text for accessibility.

package/config/templates/education-smb/knowledge/docs/education-industry-context.md

@@ -1,13 +0,0 @@
-# Education Industry Context
-
-## Common SOPs
-1. **Curriculum Review Cycle**: Curricula should be reviewed every 6 months to ensure relevance and alignment with current standards.
-2. **Student Privacy Protection**: All student data must be handled according to FERPA (Family Educational Rights and Privacy Act) and COPPA (Children's Online Privacy Protection Act) guidelines.
-3. **Inclusive Design**: Educational materials must be accessible to students with diverse learning needs, following ADA (Americans with Disabilities Act) standards.
-
-## Key Terminology
-- **LMS (Learning Management System)**: Software for the administration, documentation, tracking, and delivery of educational courses.
-- **SIS (Student Information System)**: Management information system for education establishments to manage student data.
-- **IEP (Individualized Education Program)**: A document that is developed for each public school child who needs special education.
-- **Pedagogy**: The method and practice of teaching, especially as an academic subject or theoretical concept.
-- **Blended Learning**: A style of education in which students learn via electronic and online media as well as traditional face-to-face teaching.

package/config/templates/education-smb/knowledge/index.json

@@ -1,24 +0,0 @@
-{
-  "version": "1.0.0",
-  "lastUpdated": "2026-03-04T00:00:00.000Z",
-  "documents": [
-    {
-      "id": "edu-industry-context",
-      "title": "Education Industry Context",
-      "path": "docs/education-industry-context.md",
-      "category": "terminology",
-      "tags": ["education", "sop", "terminology"],
-      "summary": "Common education industry SOPs and terms.",
-      "createdAt": "2026-03-04T00:00:00.000Z"
-    },
-    {
-      "id": "edu-content-standards",
-      "title": "Education Content Quality Standards",
-      "path": "docs/content-standards.md",
-      "category": "best-practice",
-      "tags": ["content", "quality", "standards"],
-      "summary": "Guidelines for educational content quality.",
-      "createdAt": "2026-03-04T00:00:00.000Z"
-    }
-  ]
-}

package/config/templates/education-smb/learned-patterns.json

@@ -1,16 +0,0 @@
-{
-  "version": "1.0.0",
-  "lastUpdated": "2026-03-04T00:00:00.000Z",
-  "patterns": [
-    {
-      "id": "lp-edu-001",
-      "title": "Use conversational tone for parent communication",
-      "category": "best-practice",
-      "context": "Parent newsletters often feel overly formal or academic, leading to low engagement.",
-      "recommendation": "Use a friendly, conversational tone and focus on student achievements. Avoid heavy administrative jargon.",
-      "impact": "medium",
-      "discoveredAt": "2026-03-04T00:00:00.000Z",
-      "tags": ["communication", "parents"]
-    }
-  ]
-}