opencode-skills-collection 4.0.53 → 4.0.55

package/bundled-skills/interactive-portfolio/references/detailed-guide.md

@@ -0,0 +1,500 @@
+# Interactive Portfolio - Detailed Guide
+
+> This file contains the detailed procedure and reference material extracted from `SKILL.md` for focused loading. The root skill defines activation, examples, safety constraints, and limitations.
+
+## Capabilities
+
+- Portfolio architecture
+- Project showcase design
+- Interactive case studies
+- Personal branding for devs/designers
+- Contact conversion
+- Portfolio performance
+- Work presentation
+- Testimonial integration
+
+
+## Patterns
+
+### Portfolio Architecture
+
+Structure that works for portfolios
+
+**When to use**: When planning portfolio structure
+
+
+## Portfolio Architecture
+
+### The 30-Second Test
+In 30 seconds, visitors should know:
+1. Who you are
+2. What you do
+3. Your best work
+4. How to contact you
+
+### Essential Sections
+| Section | Purpose | Priority |
+|---------|---------|----------|
+| Hero | Hook + identity | Critical |
+| Work/Projects | Prove skills | Critical |
+| About | Personality + story | Important |
+| Contact | Convert interest | Critical |
+| Testimonials | Social proof | Nice to have |
+| Blog/Writing | Thought leadership | Optional |
+
+### Navigation Patterns
+```
+Option 1: Single page scroll
+- Best for: Designers, creatives
+- Works well with animations
+- Mobile friendly
+
+Option 2: Multi-page
+- Best for: Lots of projects
+- Individual case study pages
+- Better for SEO
+
+Option 3: Hybrid
+- Main sections on one page
+- Detailed case studies separate
+- Best of both worlds
+```
+
+### Hero Section Formula
+```
+[Your name]
+[What you do in one line]
+[One line that differentiates you]
+[CTA: View Work / Contact]
+```
+
+### Project Showcase
+
+How to present work effectively
+
+**When to use**: When building project sections
+
+
+## Project Showcase
+
+### Project Card Elements
+| Element | Purpose |
+|---------|---------|
+| Thumbnail | Visual hook |
+| Title | What it is |
+| One-liner | What you did |
+| Tech/tags | Quick scan |
+| Results | Proof of impact |
+
+### Case Study Structure
+```
+1. Hero image/video
+2. Project overview (2-3 sentences)
+3. The challenge
+4. Your role
+5. Process highlights
+6. Key decisions
+7. Results/impact
+8. Learnings (optional)
+9. Links (live, GitHub, etc.)
+```
+
+### Showing Impact
+| Instead of | Write |
+|------------|-------|
+| "Built a website" | "Increased conversions 40%" |
+| "Designed UI" | "Reduced user drop-off 25%" |
+| "Developed features" | "Shipped to 50K users" |
+
+### Visual Presentation
+- Device mockups for web/mobile
+- Before/after comparisons
+- Process artifacts (wireframes, etc.)
+- Video walkthroughs for complex work
+- Hover effects for engagement
+
+### Developer Portfolio Specifics
+
+What works for dev portfolios
+
+**When to use**: When building developer portfolio
+
+
+## Developer Portfolio
+
+### What Hiring Managers Look For
+1. Code quality (GitHub link)
+2. Real projects (not just tutorials)
+3. Problem-solving ability
+4. Communication skills
+5. Technical depth
+
+### Must-Haves
+- GitHub profile link (cleaned up)
+- Live project links
+- Tech stack for each project
+- Your specific contribution (for team projects)
+
+### Project Selection
+| Include | Avoid |
+|---------|-------|
+| Real problems solved | Tutorial clones |
+| Side projects with users | Incomplete projects |
+| Open source contributions | "Coming soon" |
+| Technical challenges | Basic CRUD apps |
+
+### Technical Showcase
+```javascript
+// Show code snippets that demonstrate:
+- Clean architecture decisions
+- Performance optimizations
+- Clever solutions
+- Testing approach
+```
+
+### Blog/Writing
+- Technical deep dives
+- Problem-solving stories
+- Learning journeys
+- Shows communication skills
+
+### Portfolio Interactivity
+
+Adding memorable interactive elements
+
+**When to use**: When wanting to stand out
+
+
+## Portfolio Interactivity
+
+### Levels of Interactivity
+| Level | Example | Risk |
+|-------|---------|------|
+| Subtle | Hover effects, smooth scroll | Low |
+| Medium | Scroll animations, transitions | Medium |
+| High | 3D, games, custom cursors | High |
+
+### High-Impact, Low-Risk
+- Custom cursor on desktop
+- Smooth page transitions
+- Project card hover effects
+- Scroll-triggered reveals
+- Dark/light mode toggle
+
+### Creative Ideas
+```
+- Terminal-style interface (for devs)
+- OS desktop metaphor
+- Game-like navigation
+- Interactive timeline
+- 3D workspace scene
+- Generative art background
+```
+
+### The Balance
+- Creativity shows skill
+- But usability wins jobs
+- Mobile must work perfectly
+- Don't hide content behind interactions
+- Have a "skip" option for complex intros
+
+
+## Sharp Edges
+
+### Portfolio more complex than your actual work
+
+Severity: MEDIUM
+
+Situation: Spent 6 months on portfolio, have 2 projects to show
+
+Symptoms:
+- Been "working on portfolio" for months
+- More excited about portfolio than projects
+- Portfolio tech more impressive than work
+- Afraid to launch
+
+Why this breaks:
+Procrastination disguised as work.
+Portfolio IS a project, but not THE project.
+Diminishing returns on polish.
+Ship it and iterate.
+
+Recommended fix:
+
+
+## Right-Sizing Your Portfolio
+
+### The MVP Portfolio
+| Element | MVP Version |
+|---------|-------------|
+| Hero | Name + title + one line |
+| Projects | 3-4 best pieces |
+| About | 2-3 paragraphs |
+| Contact | Email + LinkedIn |
+
+### Time Budget
+```
+Week 1: Design and structure
+Week 2: Build core pages
+Week 3: Add 3-4 projects
+Week 4: Polish and launch
+```
+
+### The Truth
+- Your portfolio is not your best project
+- Shipping beats perfecting
+- You can always iterate
+- Better projects > better portfolio
+
+### When to Stop
+- Core pages work on mobile
+- 3-4 solid projects showcased
+- Contact form works
+- Loads in < 3 seconds
+- Ship it.
+
+### Portfolio looks great on desktop, broken on mobile
+
+Severity: HIGH
+
+Situation: Recruiters check on phone, everything breaks
+
+Symptoms:
+- Looks great in browser DevTools
+- Broken on actual phone
+- Text too small
+- Buttons hard to tap
+- Navigation hidden
+
+Why this breaks:
+Built desktop-first.
+Didn't test on real devices.
+Complex interactions don't translate.
+Forgot about thumb zones.
+
+Recommended fix:
+
+
+## Mobile-First Portfolio
+
+### Mobile Reality
+- 60%+ traffic is mobile
+- Recruiters browse on phones
+- First impression = mobile impression
+
+### Mobile Must-Haves
+- Readable without zooming
+- Tappable links (min 44px)
+- Navigation works
+- Projects load fast
+- Contact easy to find
+
+### Testing Checklist
+```
+[ ] iPhone Safari
+[ ] Android Chrome
+[ ] Tablet sizes
+[ ] Slow 3G simulation
+[ ] Real device (not just DevTools)
+```
+
+### Graceful Degradation
+```css
+/* Complex hover → simple tap */
+@media (hover: none) {
+  .hover-effect {
+    /* Show content directly */
+  }
+}
+```
+
+### Visitors don't know what to do next
+
+Severity: MEDIUM
+
+Situation: Great portfolio, zero contacts
+
+Symptoms:
+- Lots of views, no contacts
+- People don't know you're available
+- Contact page is afterthought
+- No clear ask
+
+Why this breaks:
+No clear CTA.
+Contact buried at bottom.
+Multiple competing actions.
+Assuming visitors will figure it out.
+
+Recommended fix:
+
+
+## Portfolio CTAs
+
+### Primary CTAs
+| Goal | CTA |
+|------|-----|
+| Get hired | "Let's work together" |
+| Freelance | "Start a project" |
+| Network | "Say hello" |
+| Specific role | "Hire me for [X]" |
+
+### CTA Placement
+```
+Hero section: Main CTA
+After projects: Secondary CTA
+Footer: Final CTA
+Floating: Optional persistent CTA
+```
+
+### Making Contact Easy
+- Email link (mailto:)
+- LinkedIn (opens new tab)
+- Calendar link (Calendly)
+- Simple contact form
+- Copy email button
+
+### What to Avoid
+- Contact form only (people hate forms)
+- Hidden contact info
+- Too many options
+- Vague CTAs ("Learn more")
+
+### Portfolio shows old or irrelevant work
+
+Severity: MEDIUM
+
+Situation: Best work is 3 years old, newer work not shown
+
+Symptoms:
+- jQuery projects in 2024
+- I did this in college
+- Tech stack doesn't match target jobs
+- Haven't touched portfolio in 2+ years
+
+Why this breaks:
+Haven't updated in years.
+Newer work is "not ready."
+Scared to remove old favorites.
+Portfolio drift.
+
+Recommended fix:
+
+
+## Portfolio Freshness
+
+### Update Cadence
+| Action | Frequency |
+|--------|-----------|
+| Add new project | When completed |
+| Remove old project | Yearly review |
+| Update copy | Every 6 months |
+| Tech refresh | Every 1-2 years |
+
+### Project Pruning
+Keep if:
+- Still proud of it
+- Relevant to target jobs
+- Shows important skills
+- Has good results/story
+
+Remove if:
+- Embarrassed by code/design
+- Tech is obsolete
+- Not relevant to goals
+- Better work exists
+
+### Showing Growth
+- Latest work first
+- Date projects (or don't)
+- Show evolution if relevant
+- Archive instead of delete
+
+
+## Validation Checks
+
+### No Clear Contact CTA
+
+Severity: HIGH
+
+Message: No clear way for visitors to contact you.
+
+Fix action: Add prominent contact CTA in hero and after projects section
+
+### Missing Mobile Viewport
+
+Severity: HIGH
+
+Message: Portfolio may not be mobile-responsive.
+
+Fix action: Add <meta name='viewport' content='width=device-width, initial-scale=1'>
+
+### Unoptimized Portfolio Images
+
+Severity: MEDIUM
+
+Message: Portfolio images may be slowing down load time.
+
+Fix action: Use WebP, implement lazy loading, add srcset for responsive images
+
+### Projects Missing Live Links
+
+Severity: MEDIUM
+
+Message: Projects should have live links or source code.
+
+Fix action: Add live demo URLs and GitHub links where possible
+
+### Projects Missing Impact/Results
+
+Severity: LOW
+
+Message: Projects don't show impact or results.
+
+Fix action: Add metrics, outcomes, or testimonials to project descriptions
+
+
+## Collaboration
+
+### Delegation Triggers
+
+- scroll animation|parallax|GSAP -> scroll-experience (Scroll experience for portfolio)
+- 3D|WebGL|three.js|spline -> 3d-web-experience (3D portfolio elements)
+- brand|logo|colors|identity -> branding (Personal branding)
+- copy|writing|about me|bio -> copywriting (Portfolio copy)
+- SEO|search|google -> seo (Portfolio SEO)
+
+### Developer Portfolio
+
+Skills: interactive-portfolio, frontend, scroll-experience
+
+Workflow:
+
+```
+1. Plan portfolio structure
+2. Select 3-5 best projects
+3. Design hero and project sections
+4. Add subtle scroll animations
+5. Implement and optimize
+6. Launch and share
+```
+
+### Creative Portfolio
+
+Skills: interactive-portfolio, 3d-web-experience, scroll-experience, branding
+
+Workflow:
+
+```
+1. Define personal brand
+2. Design unique experience
+3. Build interactive elements
+4. Showcase work creatively
+5. Ensure mobile works
+6. Launch
+```
+
+
+## Related Skills
+
+Works well with: `scroll-experience`, `3d-web-experience`, `landing-page-design`, `personal-branding`

package/bundled-skills/internal-comms/SKILL.md

@@ -7,6 +7,13 @@ date_added: "2026-03-21"
 license: Complete terms in LICENSE.txt
 ---
 
+## Compatibility and maintenance
+
+Primary editorial path for this compatibility group. The full instructions and support files remain local so existing installations
+continue to work offline. This is one shared procedure, not an additional capability.
+Preserve the callable ID when an existing manifest or client configuration uses it.
+Modified in AAS on 2026-09-05; original metadata and license notices are retained.
+
 ## When to use this skill
 To write internal communications, use this skill for:
 - 3P updates (Progress, Plans, Problems)
@@ -29,7 +36,19 @@ To write any internal communication:
     - `examples/general-comms.md` - For anything else that doesn't explicitly match one of the above
 3. **Follow the specific instructions** in that file for formatting, tone, and content gathering
 
-If the communication type doesn't match any existing guideline, ask for clarification or more context about the desired format.
+For other formats, use the provided audience/purpose and the general guide. Ask only for missing information that materially changes the draft.
+
+## Scope and example
+
+Use the supplied audience, date range and approved sources. Read only relevant
+accessible material; reactions, executive seniority and document views are not proof
+of accuracy. A private source does not automatically belong in a company-wide update.
+Drafting does not authorize sending, scheduling or publishing the communication.
+
+For a weekly 3P update, turn two confirmed shipped items, one next-week task and one
+open dependency into Progress/Plans/Problems. Preserve dates and uncertainty, link the
+source where appropriate and leave unknown metrics out. Expected handoff is a draft
+for the intended audience, not a claim that a message was sent.
 
 ## Keywords
 3P updates, company newsletter, company comms, weekly update, faqs, common questions, updates, internal comms

package/bundled-skills/internal-comms/examples/3p-updates.md

@@ -1,10 +1,11 @@
+<!-- Modified in AAS on 2026-09-05. Audience, permissions and approved sources take precedence over template suggestions; draft only unless sending is authorized. -->
 ## Instructions
 You are being asked to write a 3P update. 3P updates stand for "Progress, Plans, Problems." The main audience is for executives, leadership, other teammates, etc. They're meant to be very succinct and to-the-point: think something you can read in 30-60sec or less. They're also for people with some, but not a lot of context on what the team does.
 
-3Ps can cover a team of any size, ranging all the way up to the entire company. The bigger the team, the less granular the tasks should be. For example, "mobile team" might have "shipped feature" or "fixed bugs," whereas the company might have really meaty 3Ps, like "hired 20 new people" or "closed 10 new deals." 
+3Ps can cover a team of any size, ranging all the way up to the entire company. The bigger the team, the less granular the tasks should be. For example, "mobile team" might have "shipped feature" or "fixed bugs," whereas the company might have really meaty 3Ps, like "hired 20 new people" or "closed 10 new deals."
 
 They represent the work of the team across a time period, almost always one week. They include three sections:
-1) Progress: what the team has accomplished over the next time period. Focus mainly on things shipped, milestones achieved, tasks created, etc.
+1) Progress: what the team accomplished during the past reporting period. Focus mainly on things shipped, milestones achieved, tasks created, etc.
 2) Plans: what the team plans to do over the next time period. Focus on what things are top-of-mind, really high priority, etc. for the team.
 3) Problems: anything that is slowing the team down. This could be things like too few people, bugs or blockers that are preventing the team from moving forward, some deal that fell through, etc.
 
@@ -37,11 +38,11 @@ week for Plans)
 
 ## Formatting
 
-The format is always the same, very strict formatting. Never use any formatting other than this. Pick an emoji that is fun and captures the vibe of the team and update.
+Use this default format unless the user or company supplies another. Pick an emoji that is fun and captures the vibe of the team and update.
 
 [pick an emoji] [Team Name] (Dates Covered, usually a week)
 Progress: [1-3 sentences of content]
 Plans: [1-3 sentences of content]
 Problems: [1-3 sentences of content]
 
-Each section should be no more than 1-3 sentences: clear, to the point. It should be data-driven, and generally include metrics where possible. The tone should be very matter-of-fact, not super prose-heavy.
+Each section should be no more than 1-3 sentences: clear, to the point. It should be data-driven, and generally include metrics where possible. The tone should be very matter-of-fact, not super prose-heavy.

package/bundled-skills/internal-comms/examples/company-newsletter.md

@@ -1,8 +1,9 @@
+<!-- Modified in AAS on 2026-09-05. Audience, permissions and approved sources take precedence over template suggestions; draft only unless sending is authorized. -->
 ## Instructions
 You are being asked to write a company-wide newsletter update. You are meant to summarize the past week/month of a company in the form of a newsletter that the entire company will read. It should be maybe ~20-25 bullet points long. It will be sent via Slack and email, so make it consumable for that.
 
 Ideally it includes the following attributes:
-- Lots of links: pulling documents from Google Drive that are very relevant, linking to prominent Slack messages in announce channels and from executives, perhgaps referencing emails that went company-wide, highlighting significant things that have happened in the company.
+- Lots of links: pulling documents from Google Drive that are very relevant, linking to prominent Slack messages in announce channels and from executives, perhaps referencing emails that went company-wide, highlighting significant things that have happened in the company.
 - Short and to-the-point: each bullet should probably be no longer than ~1-2 sentences
 - Use the "we" tense, as you are part of the company. Many of the bullets should say "we did this" or "we did that"
 
@@ -18,7 +19,7 @@ If you have access to the following tools, please try to use them. If not, you c
 If you don't have access to any of these things, you can ask the user for things they want to cover. In this case, you'll mostly just be polishing up and fitting to this format more directly.
 
 ## Sections
-The company is pretty big: 1000+ people. There are a variety of different teams and initiatives going on across the company. To make sure the update works well, try breaking it into sections of similar things. You might break into clusters like {product development, go to market, finance} or {recruiting, execution, vision}, or {external news, internal news} etc. Try to make sure the different areas of the company are highlighted well.
+Adapt the scope and length to the actual company size; do not assume an employee count. There are a variety of different teams and initiatives going on across the company. To make sure the update works well, try breaking it into sections of similar things. You might break into clusters like {product development, go to market, finance} or {recruiting, execution, vision}, or {external news, internal news} etc. Try to make sure the different areas of the company are highlighted well.
 
 ## Prioritization
 Focus on:

package/bundled-skills/internal-comms/examples/faq-answers.md

@@ -1,3 +1,4 @@
+<!-- Modified in AAS on 2026-09-05. Audience, permissions and approved sources take precedence over template suggestions; draft only unless sending is authorized. -->
 ## Instructions
 You are an assistant for answering questions that are being asked across the company. Every week, there are lots of questions that get asked across the company, and your goal is to try to summarize what those questions are. We want our company to be well-informed and on the same page, so your job is to produce a set of frequently asked questions that our employees are asking and attempt to answer them. Your singular job is to do two things:
 

package/bundled-skills/internal-comms/examples/general-comms.md

@@ -1,3 +1,4 @@
+<!-- Modified in AAS on 2026-09-05. Audience, permissions and approved sources take precedence over template suggestions; draft only unless sending is authorized. -->
   ## Instructions
   You are being asked to write internal company communication that doesn't fit into the standard formats (3P
   updates, newsletters, or FAQs).

package/bundled-skills/internal-comms-anthropic/SKILL.md

@@ -1,11 +1,18 @@
 ---
 name: internal-comms-anthropic
-description: "To write internal communications, use this skill for:"
+description: "Compatibility alias for internal-comms: draft status updates, newsletters and FAQs from approved sources."
 risk: safe
 source: community
 date_added: "2026-02-27"
 ---
 
+## Compatibility and maintenance
+
+Compatibility alias of `internal-comms`; use that ID for new references when no existing contract requires this one. The full instructions and support files remain local so existing installations
+continue to work offline. This is one shared procedure, not an additional capability.
+Preserve the callable ID when an existing manifest or client configuration uses it.
+Modified in AAS on 2026-09-05; original metadata and license notices are retained.
+
 ## When to use this skill
 To write internal communications, use this skill for:
 - 3P updates (Progress, Plans, Problems)
@@ -28,7 +35,19 @@ To write any internal communication:
     - `examples/general-comms.md` - For anything else that doesn't explicitly match one of the above
 3. **Follow the specific instructions** in that file for formatting, tone, and content gathering
 
-If the communication type doesn't match any existing guideline, ask for clarification or more context about the desired format.
+For other formats, use the provided audience/purpose and the general guide. Ask only for missing information that materially changes the draft.
+
+## Scope and example
+
+Use the supplied audience, date range and approved sources. Read only relevant
+accessible material; reactions, executive seniority and document views are not proof
+of accuracy. A private source does not automatically belong in a company-wide update.
+Drafting does not authorize sending, scheduling or publishing the communication.
+
+For a weekly 3P update, turn two confirmed shipped items, one next-week task and one
+open dependency into Progress/Plans/Problems. Preserve dates and uncertainty, link the
+source where appropriate and leave unknown metrics out. Expected handoff is a draft
+for the intended audience, not a claim that a message was sent.
 
 ## Keywords
 3P updates, company newsletter, company comms, weekly update, faqs, common questions, updates, internal comms

package/bundled-skills/internal-comms-anthropic/examples/3p-updates.md

@@ -1,10 +1,11 @@
+<!-- Modified in AAS on 2026-09-05. Audience, permissions and approved sources take precedence over template suggestions; draft only unless sending is authorized. -->
 ## Instructions
 You are being asked to write a 3P update. 3P updates stand for "Progress, Plans, Problems." The main audience is for executives, leadership, other teammates, etc. They're meant to be very succinct and to-the-point: think something you can read in 30-60sec or less. They're also for people with some, but not a lot of context on what the team does.
 
-3Ps can cover a team of any size, ranging all the way up to the entire company. The bigger the team, the less granular the tasks should be. For example, "mobile team" might have "shipped feature" or "fixed bugs," whereas the company might have really meaty 3Ps, like "hired 20 new people" or "closed 10 new deals." 
+3Ps can cover a team of any size, ranging all the way up to the entire company. The bigger the team, the less granular the tasks should be. For example, "mobile team" might have "shipped feature" or "fixed bugs," whereas the company might have really meaty 3Ps, like "hired 20 new people" or "closed 10 new deals."
 
 They represent the work of the team across a time period, almost always one week. They include three sections:
-1) Progress: what the team has accomplished over the next time period. Focus mainly on things shipped, milestones achieved, tasks created, etc.
+1) Progress: what the team accomplished during the past reporting period. Focus mainly on things shipped, milestones achieved, tasks created, etc.
 2) Plans: what the team plans to do over the next time period. Focus on what things are top-of-mind, really high priority, etc. for the team.
 3) Problems: anything that is slowing the team down. This could be things like too few people, bugs or blockers that are preventing the team from moving forward, some deal that fell through, etc.
 
@@ -37,11 +38,11 @@ week for Plans)
 
 ## Formatting
 
-The format is always the same, very strict formatting. Never use any formatting other than this. Pick an emoji that is fun and captures the vibe of the team and update.
+Use this default format unless the user or company supplies another. Pick an emoji that is fun and captures the vibe of the team and update.
 
 [pick an emoji] [Team Name] (Dates Covered, usually a week)
 Progress: [1-3 sentences of content]
 Plans: [1-3 sentences of content]
 Problems: [1-3 sentences of content]
 
-Each section should be no more than 1-3 sentences: clear, to the point. It should be data-driven, and generally include metrics where possible. The tone should be very matter-of-fact, not super prose-heavy.
+Each section should be no more than 1-3 sentences: clear, to the point. It should be data-driven, and generally include metrics where possible. The tone should be very matter-of-fact, not super prose-heavy.

package/bundled-skills/internal-comms-anthropic/examples/company-newsletter.md

@@ -1,8 +1,9 @@
+<!-- Modified in AAS on 2026-09-05. Audience, permissions and approved sources take precedence over template suggestions; draft only unless sending is authorized. -->
 ## Instructions
 You are being asked to write a company-wide newsletter update. You are meant to summarize the past week/month of a company in the form of a newsletter that the entire company will read. It should be maybe ~20-25 bullet points long. It will be sent via Slack and email, so make it consumable for that.
 
 Ideally it includes the following attributes:
-- Lots of links: pulling documents from Google Drive that are very relevant, linking to prominent Slack messages in announce channels and from executives, perhgaps referencing emails that went company-wide, highlighting significant things that have happened in the company.
+- Lots of links: pulling documents from Google Drive that are very relevant, linking to prominent Slack messages in announce channels and from executives, perhaps referencing emails that went company-wide, highlighting significant things that have happened in the company.
 - Short and to-the-point: each bullet should probably be no longer than ~1-2 sentences
 - Use the "we" tense, as you are part of the company. Many of the bullets should say "we did this" or "we did that"
 
@@ -18,7 +19,7 @@ If you have access to the following tools, please try to use them. If not, you c
 If you don't have access to any of these things, you can ask the user for things they want to cover. In this case, you'll mostly just be polishing up and fitting to this format more directly.
 
 ## Sections
-The company is pretty big: 1000+ people. There are a variety of different teams and initiatives going on across the company. To make sure the update works well, try breaking it into sections of similar things. You might break into clusters like {product development, go to market, finance} or {recruiting, execution, vision}, or {external news, internal news} etc. Try to make sure the different areas of the company are highlighted well.
+Adapt the scope and length to the actual company size; do not assume an employee count. There are a variety of different teams and initiatives going on across the company. To make sure the update works well, try breaking it into sections of similar things. You might break into clusters like {product development, go to market, finance} or {recruiting, execution, vision}, or {external news, internal news} etc. Try to make sure the different areas of the company are highlighted well.
 
 ## Prioritization
 Focus on: