agentleFS
Sign inStart free
alectivismalectivism/maven-template/skills/maven/SKILL.md

maven

Skill1 starsChanged 6 months agoMITView on GitHub

Start a MAVEN session with context loading and daily briefing. Use when the user says "/maven", "/start", "start session", "good morning", "let's get started", or begins a new work session.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read these files (skip any that don't exist):

    line 21
  2. Very specific:

    If no session log for today, read the most recent one in sessions/

    line 25
  3. Very specific:

    If state/current.md hasn't been updated in 3+ days, flag it

    line 28
  4. Distinctive:

    Keep the briefing concise — under 30 seconds to read

    line 58
  5. Distinctive:

    Don't read back the entire state file — synthesize

    line 60
  6. Distinctive:

    If this is the first session ever, trigger onboarding flow instead

    line 61

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Start MAVEN Session

Startup Sequence

1. Check Date

Determine today's date.

2. Load Context

Read these files (skip any that don't exist):

  • state/current.md — active priorities and open threads
  • state/goals.md — current goals
  • Today's session log: sessions/YYYY-MM-DD.md
  • If no session log for today, read the most recent one in sessions/

3. Check Context Freshness

  • If state/current.md hasn't been updated in 3+ days, flag it
  • Note any overdue items or deadlines

4. Deliver Briefing

Format:

## MAVEN Briefing — [Day of Week], [Date]

### Top Priorities
1. [Priority from current.md]
2. [Priority]
3. [Priority]

### Today's Calendar
[Check Outlook calendar for today's events if ms365 is available]

### Alerts
- [Overdue items]
- [Upcoming deadlines within 3 days]
- [Stale context warnings]

### Open Threads
- [Active threads needing attention]

5. Offer Direction

End with: "What would you like to focus on?"

Guidelines

  • Keep the briefing concise — under 30 seconds to read
  • Highlight blockers or urgent items first
  • Don't read back the entire state file — synthesize
  • If this is the first session ever, trigger onboarding flow instead

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free