foryourhealth111-pixel/Vibe-Skills / bundled/skills/digital-brain
digital-brain
VerifiedThis skill should be used when the user asks to "write a post", "check my voice", "look up contact", "prepare for meeting", "weekly review", "track goals", or mentions personal brand, content creation, network management, or voice consistency.
operations/OPERATIONS.md
View on GitHub---
name: operations-module
description: Personal productivity - todos, goals, meetings, and metrics. Use for task management, goal tracking, meeting prep, and productivity reviews.
---
# Operations Module
Your personal productivity operating system.
## Files in This Module
| File | Format | Purpose |
|------|--------|---------|
| `todos.md` | Markdown | Active task list |
| `goals.yaml` | YAML | OKRs and goal tracking |
| `meetings.jsonl` | JSONL | Meeting log and notes |
| `metrics.jsonl` | JSONL | Key metrics tracking |
| `reviews/` | Folder | Weekly/monthly reviews |
## Workflows
### Daily Flow
```
1. Morning: Review todos.md, prioritize
2. Throughout: Check off completed, add new
3. Evening: Log any meetings, update metrics
```
### Weekly Review (Run every Sunday)
1. Run `agents/scripts/weekly_review.py`
2. Review completed vs. planned
3. Check metrics in metrics.jsonl
4. Plan next week's priorities
5. Update goals.yaml progress
### Goal Setting (Quarterly)
1. Review previous quarter goals
2. Update goals.yaml with new OKRs
3. Break down into monthly targets
4. Align content calendar with goals
## Agent Instructions
<instructions>
When managing operations:
1. **Todos**: Use priority levels (P0-P3), keep list current
2. **Goals**: Reference before major decisions or planning
3. **Meetings**: Log immediately after with key takeaways
4. **Metrics**: Update at least weekly
5. **Reviews**: Generate insights, not just summaries
Priority levels:
- P0: Do today, blocking other work
- P1: Do this week, important
- P2: Do this month, valuable
- P3: Backlog, nice to have
When asked to help plan or prioritize:
1. Check current goals.yaml for alignment
2. Review existing todos.md capacity
3. Consider time-sensitivity and dependencies
4. Suggest realistic timelines
</instructions>
## Productivity Principles
```yaml
principles:
- "Ruthless prioritization over busy work"
- "Completion > perfection for P1-P3"
- "Batch similar tasks together"
- "Protect deep work time"
- "Weekly reviews are non-negotiable"
```
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |