operations
Skill1 starsChanged 5 months agoMITView on GitHub
Guide founders through startup operations including hiring, OKRs, and board management. Use when a founder says "help me write a job description", "how do I set OKRs", "create a board deck", "structure investor updates", "build a hiring plan", "interview scorecard", "quarterly planning", "team goals", "board meeting", or needs operational templates for running their startup.
9 other projects use a version of this.
Adopted by
Most recently taken up by
- HKTITAN/isb-skillstheir own version, first seen Nov 1, 2026
- grace-method/grace-plugintheir own version, first seen Oct 25, 2026
- QuixiAI/Hexistheir own version, first seen Oct 8, 2026
- QuixiAI/agi-memorytheir own version, first seen Oct 8, 2026
- joaocarloscruz/skillstheir own version, first seen Sep 12, 2026
- poorvith-mp/skills-businesstheir own version, first seen Aug 19, 2026
Other versions9 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 9
- QuixiAI/agi-memory★ 623same name
- QuixiAI/Hexis★ 623same name
- travisjneuman/.claude★ 106same name
- HKTITAN/isb-skills★ 4same name
- ryonakae/hermes-self-improvement★ 4same name
- sykuang/rednote-mcp★ 4same name
- joaocarloscruz/skills★ 1same name
- poorvith-mp/skills-business★ 1same name
- grace-method/grace-plugin★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository14 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- business-modelSkill
- customer-successSkill
- finance-accountingSkill
- founder-playbookSkill
- fundraisingSkill
- go-to-marketSkill
- growth-analyticsSkill
- idea-validationSkill
- legal-complianceSkill
- marketing-brandSkill
- productSkill
- salesSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
23 rules. 0 are common, 13 are distinctive, and 10 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
13
Distinctive
This author's own choices. Worth a look.
10
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Ask: "What operational challenge are you facing?"
- Distinctive: line 61
Keep requirements list short (5-7 items max)—long lists reduce diversity
- Distinctive: line 62
Use standard titles (no "ninja" or "rockstar")
- Distinctive: line 68
Every interview should use a scorecard to reduce bias and enable comparison.
- Distinctive: line 174
If a KPI is underperforming, create an OKR to address it.
- Distinctive: line 242
Keep it short—bullet points, not paragraphs
- Distinctive: line 270
Use consistent structure meeting-to-meeting
- Distinctive: line 271
Don't read slides—they're discussion prompts
- Distinctive: line 291
No structured interview process (gut-feel hiring)
- Distinctive: line 300
No connection between company and team OKRs
- Distinctive: line 304
Only sending updates when fundraising
- Distinctive: line 306
No consistent format (makes comparison hard)
- Distinctive: line 307
Not asking for specific help
- Very specific: line 314
Create using docx skill:
- Very specific: line 337
Create as markdown or docx:
- Very specific: line 359
Use idea-validation skill before hiring for unvalidated products
- Very specific: line 360
Use business-model skill for compensation benchmarking
- Very specific: line 361
Use fundraising skill for investor relationships
- Very specific: line 362
Use product skill for roadmaps that inform OKRs
- Very specific: line 363
Use go-to-market skill for sales hiring plans
- Very specific: line 364
Use docx skill for job descriptions and updates
- Very specific: line 365
Use xlsx skill for OKR trackers and scorecards
- Very specific: line 366
Use pptx skill for board decks
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Startup Operations
Guide founders from chaotic early-stage operations to structured, scalable processes for hiring, goal-setting, and board management.
Workflow
1. Diagnose Need
Ask: "What operational challenge are you facing?"
| Need | Signals | Next Step |
| Hiring | "Write job description", "interview process", "hiring plan" | → Step 2: Hiring |
| OKRs/Goals | "Set OKRs", "quarterly goals", "team alignment" | → Step 3: OKRs |
| Board/Investors | "Board deck", "investor update", "board meeting" | → Step 4: Board Management |
| All of the above | New to operations, scaling team | → Start with Step 2 |
2. Hiring
Build a hiring system that attracts talent and makes consistent decisions.
Job Description Framework
Structure:
[Role Title]
[Company] | [Location] | [Remote Policy]
About Us
[2-3 sentences: What you do, for whom, why it matters]
[Stage, funding, notable investors/customers]
The Role
[What this person will own and accomplish—outcomes, not tasks]
[Why this role matters now]
What You'll Do
- [Outcome-focused responsibility 1]
- [Outcome-focused responsibility 2]
- [Outcome-focused responsibility 3]
What We're Looking For
- [Essential skill/experience 1]
- [Essential skill/experience 2]
- [Desirable: nice-to-have]
Compensation
[Salary range] + [Equity range]
[Key benefits]Job Description Rules:
- Lead with outcomes, not tasks ("Own the customer onboarding experience" vs "Build onboarding flows")
- Be specific about stage ("0-1 experience", "scaling from $1M to $10M ARR")
- Include salary range—saves everyone time
- Keep requirements list short (5-7 items max)—long lists reduce diversity
- Use standard titles (no "ninja" or "rockstar")
See references/job-descriptions.md for role-specific templates.
Interview Scorecard
Every interview should use a scorecard to reduce bias and enable comparison.
Scorecard Structure:
| Criteria | Weight | 1-5 Score | Evidence/Notes |
| Technical Skills | |||
| [Role-specific skill 1] | High | ||
| [Role-specific skill 2] | Medium | ||
| Working Style | |||
| Comfort with ambiguity | High | ||
| Communication clarity | Medium | ||
| Values Fit | |||
| [Company value 1] | Medium | ||
| Overall Recommendation | Hire / No Hire / Maybe |
Scoring Guide:
- 5 = Exceptional, exceeds requirements
- 4 = Strong, meets all requirements
- 3 = Acceptable, meets most requirements
- 2 = Weak, gaps in key areas
- 1 = Poor, significant concerns
Interview Best Practices (First Round):
- Same questions for all candidates (enables comparison)
- Score immediately after interview (memory fades)
- Hide feedback until all interviewers submit (prevents groupthink)
- Focus on evidence, not impressions ("They described X" vs "They seemed smart")
See references/interview-scorecards.md for role-specific scorecards.
Hiring Plan
For scaling teams, create a hiring plan that ties headcount to goals.
Hiring Plan Template:
| Role | Priority | Start Date | Why Now | Success Metric |
| Sr. Engineer | P0 | Q1 | Ship v2 by March | V2 launched |
| SDR | P1 | Q2 | Pipeline < $500K | Pipeline > $2M |
| Designer | P2 | Q2 | UX complaints | NPS +10 |
Prioritization Questions:
- What breaks if we don't hire this role?
- Can we outsource or defer this?
- What's the cost of a bad hire vs. waiting?
3. OKRs & Goal Setting
OKRs (Objectives and Key Results) create focus and alignment. Use them to ensure everyone works on what matters most.
OKR Framework
The Formula:
I will [OBJECTIVE] as measured by [KEY RESULTS]Objective: Qualitative, inspiring, time-bound (what you want to achieve)
- Formula: Verb + what you're going to do + so that/in order to
- Example: "Deliver a must-have product in order to delight customers and grow our user base"
Key Results: Quantitative, measurable (how you'll know you achieved it)
- Formula: Verb + what you're going to track + from X to Y
- Example: "Increase NPS score from 40 to 50"
Key Initiatives: Actions you'll take to achieve key results (optional)
- Measured as % completed
- Example: "Build a dashboard to track UX performance issues"
OKR Examples (Early-Stage Startup)
Company-wide OKRs:
Objective 1: Hit $10M ARR by EOQ
KR1: 110% net revenue retention
KR2: Grow weighted pipeline to $8M+ by EOQ
KR3: Close rate of 15% from initial meeting to close-won
Objective 2: Hire and retain the best team
KR1: Average time to fill < 45 days from JD posted
KR2: <10% quarterly regrettable attrition
Objective 3: Deliver a fast, reliable AI product experience
KR1: Achieve 99.9% uptime for the inference API
KR2: Reduce average response latency from 800ms to 300ms
KR3: Increase task success rate from 60% to 80%OKR Best Practices (Liz Wessel / Google)
Writing OKRs:
- ✅ 3 objectives max per company/team/individual per cycle
- ✅ 1-3 key results per objective
- ✅ Key results must be quantifiable—use numbers
- ✅ Revisit frequently—don't set and forget
- ❌ Don't make KRs a task list ("launch feature X")
- ❌ Avoid vague objectives ("Be the best")
- ❌ Don't conflate KPIs (what you track) with OKRs (what you're trying to change)
OKR vs KPI Distinction:
- KPIs = metrics you always track (revenue, churn, NPS)—health of business
- OKRs = outcomes you're trying to change this quarter—direction of change
If a KPI is underperforming, create an OKR to address it.
OKR Superpowers Checklist:
- Focus: What can be eliminated?
- Alignment: Who are the stakeholders?
- Tracking: Can we measure success?
- Transparency: Where are bottlenecks?
- Stretch: Is it propelling business forward?
Necessary & Sufficient Test:
- Are all Key Results necessary to achieve the Objective?
- Will accomplishing Key Results be sufficient to achieve the Objective?
OKR Cadence for Startups
| Stage | Cadence | Focus |
| Pre-PMF | Monthly or 6-week cycles | Learning velocity, user feedback |
| Post-PMF | Quarterly | Growth metrics, retention |
| Scaling | Quarterly with annual goals | Revenue, team, market expansion |
See references/okr-templates.md for tracking spreadsheet and more examples.
4. Board Management
Build trust with investors through consistent, transparent communication.
Investor Update Email
Send monthly (or at minimum quarterly) to keep investors informed and engaged.
Structure:
Subject: [Company] Update - [Month Year]
ASKS
- [Specific ask with context—intros, advice, resources]
GOING WELL ✅
- Hiring: [Team changes]
- Launched: [Product updates with links]
- [Key metric]: XX,XXX (+Y% m/m vs. +Z% target)
NOT GOING WELL ⚠️
- [Key metric]: XX,XXX (+Y% m/m vs. +Z% target)
- [Brief explanation]
- [Issue with context]
COMPANY HEALTH
- Cash: $X.XM
- Burn: -$XXXK/month
- Runway: X months
- Team: X people (Y FT, Z contractors)
PRIORITIES (Next 30 Days)
1. [Priority 1]: [Brief description, <500 chars]
2. [Priority 2]: [Brief description]
3. [Priority 3]: [Brief description]
SHOUT OUTS
- [Person/firm] for [specific help]Investor Update Rules:
- Lead with asks—make it easy to help
- Be honest about what's not working—builds trust
- Include runway—investors need to know
- Keep it short—bullet points, not paragraphs
- Send consistently—monthly builds muscle memory
See references/investor-updates.md for full templates.
Board Deck Structure
For formal board meetings (typically quarterly after seed).
Recommended Slides (12-15 total):
- Agenda — Topics + time allocation + focus session
- Key Concerns & Asks — What's keeping you up at night, specific help needed
- Executive Summary — State of company, 90-day goals
- Highlights — 3-5 wins with owners credited
- Lowlights — 3-5 challenges, what you're doing about them
- KPIs Dashboard — Key metrics vs. targets, trends
- Financial Summary — Cash, burn, runway, budget vs. actual
- Product Update — Shipped, in progress, roadmap
- Team Update — Hires, departures, org chart, open roles
- Sales/Pipeline — Pipeline, conversion, customer wins
- Competitive/Market — Industry updates, competitive moves
- Focus Session — Deep dive on one strategic topic
- Priorities — Next 90 days
- Action Items — Board commitments, decisions needed
Board Meeting Best Practices:
- Send deck 3-4 days in advance
- Use consistent structure meeting-to-meeting
- Don't read slides—they're discussion prompts
- Reserve 30%+ of time for discussion
- Assign a note-taker immediately
- End with clear action items and owners
- Save all decks for due diligence later
See references/board-decks.md for slide templates.
Board Meeting Cadence
| Stage | Frequency | Duration | Focus |
| Pre-seed | Monthly informal | 30-60 min | Product, early users |
| Seed | Quarterly | 2 hours | PMF, hiring, fundraising |
| Series A+ | Quarterly | 2-3 hours | Growth, strategy, governance |
5. Operational Anti-Patterns
Hiring Mistakes:
- Writing job descriptions with 15+ requirements
- No structured interview process (gut-feel hiring)
- Not checking references
- Hiring too senior too early (they need structure you don't have)
- Outsourcing founder-led sales too early
OKR Mistakes:
- Too many OKRs (more than 3 objectives)
- Key results that are tasks, not outcomes
- Setting OKRs and never reviewing them
- No connection between company and team OKRs
- Treating OKRs as performance reviews
Board Mistakes:
- Only sending updates when fundraising
- Hiding bad news
- No consistent format (makes comparison hard)
- Not asking for specific help
- Running overtime with no discussion time
Deliverables
1. Job Description
Create using docx skill:
- Role-specific template from
references/job-descriptions.md - Customized for company stage and culture
- Clear outcomes and requirements
2. Interview Scorecard
Create using xlsx skill:
- Role-specific criteria
- Weighted scoring system
- Evidence capture fields
- Recommendation section
3. OKR Tracker
Create using xlsx skill:
- Company/team/individual OKRs
- Progress tracking (weekly/monthly)
- Owner assignments
- Status indicators (on track, at risk, off track)
4. Investor Update Email
Create as markdown or docx:
- Monthly update following template
- Metrics formatted consistently
- Clear asks at top
5. Board Deck
Create using pptx skill:
- 12-15 slide structure
- Consistent with previous decks
- Focus session identified
Reference Files
references/job-descriptions.md— Templates by role (engineer, PM, sales, ops)references/interview-scorecards.md— Scorecard templates and question banksreferences/okr-templates.md— OKR tracker spreadsheet, examples by functionreferences/investor-updates.md— Email templates and reporting cadencereferences/board-decks.md— Slide templates and meeting agendas
Integration with Other Skills
- Use
idea-validationskill before hiring for unvalidated products - Use
business-modelskill for compensation benchmarking - Use
fundraisingskill for investor relationships - Use
productskill for roadmaps that inform OKRs - Use
go-to-marketskill for sales hiring plans - Use
docxskill for job descriptions and updates - Use
xlsxskill for OKR trackers and scorecards - Use
pptxskill for board decks
Adapted from Linas Beliūnas's The One-Person Unicorn founder skill set.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

