Initial mVP setup with Gitea Action workflow
- README with usage instructions - Gitea Action to handle issues via SSH to VPS - Supports skill hints in issue body (skill: role-pa, etc) - Labels: urgent, research, writing, code, waiting
This commit is contained in:
51
README.md
51
README.md
@@ -1,3 +1,50 @@
|
||||
# mVP
|
||||
# mVP - m Vice President
|
||||
|
||||
m Vice President - Personal AI Assistant
|
||||
Your personal AI assistant. Create issues, mAi handles them.
|
||||
|
||||
## How It Works
|
||||
|
||||
1. **Create an issue** describing what you need
|
||||
2. **mAi picks it up** (via webhook or scheduled run)
|
||||
3. **Work gets done** - research, writing, code, whatever
|
||||
4. **Results posted** as comments or linked PRs
|
||||
|
||||
## Issue Format
|
||||
|
||||
Just describe what you need. Optionally add labels or skill hints:
|
||||
|
||||
```markdown
|
||||
Title: Research best practices for X
|
||||
|
||||
skill: role-researcher
|
||||
|
||||
Find and summarize the top 3 approaches to X...
|
||||
```
|
||||
|
||||
## Skills
|
||||
|
||||
Specify in issue body with `skill: <name>` or use labels:
|
||||
|
||||
| Skill | Use For |
|
||||
|-------|---------|
|
||||
| `role-pa` | Emails, scheduling, organization |
|
||||
| `role-researcher` | Deep research and analysis |
|
||||
| `role-coder` | Code and technical tasks |
|
||||
| `web` | Web research and fetching |
|
||||
| `analyze` | Data analysis |
|
||||
|
||||
## Labels
|
||||
|
||||
- `urgent` - Process first
|
||||
- `research` - Research task
|
||||
- `writing` - Writing/drafting
|
||||
- `code` - Programming
|
||||
- `waiting` - Skip for now (needs input)
|
||||
|
||||
## Examples
|
||||
|
||||
**Research:** "Compare cloud providers for small startup"
|
||||
|
||||
**Writing:** "Draft weekly update email for project X"
|
||||
|
||||
**Code:** "Create Python script to parse sales.csv"
|
||||
|
||||
Reference in New Issue
Block a user