OpenClaw · Skill
Lofy Projects
Keeps projects, coursework, and research organized. Tracks status, deadlines, blockers, and helps prioritize work time.
Install
Start with the primary install command. Alternate entrypoints are included below for ClawHub and OpenClaw CLI users.
Primary command
clawhub install harrey401/lofy-projectsClawHub installer
npx clawhub@latest install harrey401/lofy-projectsOpenClaw CLI
openclaw skills install harrey401/lofy-projectsDirect OpenClaw install
openclaw install harrey401/lofy-projectsWhat this skill does
Keeps projects, coursework, and research organized. Tracks status, deadlines, blockers, and helps prioritize work time.
Why it matters
The scoring formula weights urgency and job relevance differently rather than sorting purely by deadline, so the recommendation adapts to context instead of always surfacing the most overdue item.
Typical use cases
- Deciding which project to tackle with 45 minutes free
- Getting a prep brief before a client or advisor meeting
- Logging hours worked on a project through plain-language chat
- Spotting which active projects haven't been touched in weeks
- Tracking milestones and blockers across job and academic work simultaneously
Source instructions
Project Pilot — Project & Academic Manager
Keeps projects, coursework, and research organized. Tracks status, deadlines, blockers, and helps prioritize work time.
Data File: data/projects.json
{
"projects": {
"example_project": {
"name": "Example Project",
"status": "active",
"phase": "Phase 1",
"description": "",
"stack": [],
"milestones": [
{ "name": "Milestone 1", "status": "in_progress", "target_date": null }
],
"blockers": [],
"next_actions": [],
"time_log": [],
"last_updated": null,
"job_relevance": "high"
}
},
"academic": { "graduation": null, "deadlines": [], "meetings": [] }
}
Priority Engine
When user asks "what should I work on?":
Priority = (Urgency × 3) + (Job_Relevance × 2) + (Momentum × 1) + (Energy_Match × 1)
Urgency (0-5): 5=due today, 4=48h, 3=this week, 2=this month, 1=no deadline, 0=backlog
Job_Relevance (0-5): 5=critical, 4=high, 3=medium, 2=portfolio, 1=low, 0=none
Momentum (0-3): 3=active progress, 2=touched last 3 days, 1=stale 1-2 weeks, 0=cold 2+ weeks
Energy_Match (0-2): 2=matches current energy, 1=neutral, 0=mismatch
Time-Based Recommendations
- < 30 min: Quick tasks — email, review, read, update docs
- 30-60 min: Medium — write one function, prep notes, apply to 1 job
- 1-2 hours: Focused — implement a feature, write paper section, debug
- 2+ hours: Deep work — major development sessions
Meeting Prep
When a meeting is detected:
- Identify related project
- Pull recent time_log entries since last meeting
- List current blockers
- Generate 2-3 questions to ask
- Suggest what to demo/present
- Send prep 2 hours before
Status Updates via Natural Language
- "Worked on [project] for 2 hours" → update time_log, last_updated
- "[Feature] is working now" → update milestone status
- "Stuck on [issue]" → add to blockers
- "Meeting moved to Thursday" → update meetings
Instructions
- Always read
data/projects.jsonbefore responding about projects - Update JSON after any project conversation
- For "what should I work on?" — ONE clear recommendation + one alternative
- Flag stale projects: "[Project] hasn't been touched in X days"
- Before meetings, proactively send prep
- Prioritize job-critical projects unless there's a deadline override