agentleFS
systemind-teamsystemind-team/AICOO-Skills/skills/daily-brief/SKILL.md

daily-brief

Skill35 starsChanged 4 months agoMITView on GitHub

Use this skill when the user asks for a daily briefing, morning summary, executive brief, top priorities, COO strategies, or Eisenhower matrix. Triggers on: 'daily brief', 'morning brief', 'daily summary', 'executive summary', '今日简报', '优先级矩阵', '/v1/briefing', '/v1/briefings', '/v1/briefing/strategies', '/v1/briefing/matrix'.

  • Reads credentials
  • Sends data out

30 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use weekly-review, setup and 1 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • QuixiAISkill

    weekly-review

    Review the past week across goals, tasks, calendar, journal, and commitments, then propose the next week

    Also in 5 projects that use this

  • VercelSkill

    setup

    Set up Vercel CLI and project configuration. Use when the user says "set up Vercel", "configure Vercel", "link to Vercel", or "vercel init".

    Also in 3 projects that use this

  • SentrySkill

    skill-creator

    Create new agent skills following the Agent Skills specification. Use when asked to "create a skill", "add a new skill", "write a skill", "make a skill", "build a skill", or scaffold a new skill with SKILL.md. Guides through requirements, writing, registration, and verification.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 23 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use /loop or /routine directly.

    line 80
  2. Distinctive:

    Use the provided script:

    line 96
  3. Distinctive:

    When you report to user, include:

    line 111
  4. Distinctive:

    Keep concise and action-oriented.

    line 118

“Common” is measured: kept by at least 6 in 10 of the 23 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.

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

Daily Brief

Generate an executive daily brief from Aicoo context, then derive top strategies and a matrix view.

Prerequisites

  • AICOO_API_KEY must be set
  • Base URL: https://www.aicoo.io/api/v1

Endpoints

  • POST /api/v1/briefing
  • POST /api/v1/briefing/strategies
  • POST /api/v1/briefing/matrix
  • GET /api/v1/briefings

Core Workflow

Step 1: Generate briefing

curl -s -X POST "https://www.aicoo.io/api/v1/briefing" \
  -H "Authorization: Bearer $AICOO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"timeDuration":"last 24 hours"}' | jq .

This returns:

  • statusQuoSummary
  • todoSummary
  • calendarSummary
  • notesSummary
  • emailAttentionSummary
  • suggestions[]

Step 2: Get top 3 COO strategies

curl -s -X POST "https://www.aicoo.io/api/v1/briefing/strategies" \
  -H "Authorization: Bearer $AICOO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "statusQuoSummary":"...",
    "todoSummary":"...",
    "calendarSummary":"...",
    "notesSummary":"...",
    "emailAttentionSummary":"..."
  }' | jq .

Step 3: Build Eisenhower matrix

curl -s -X POST "https://www.aicoo.io/api/v1/briefing/matrix" \
  -H "Authorization: Bearer $AICOO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "statusQuoSummary":"...",
    "todoSummary":"...",
    "calendarSummary":"...",
    "notesSummary":"...",
    "emailAttentionSummary":"..."
  }' | jq .

Step 4: Retrieve history

curl -s "https://www.aicoo.io/api/v1/briefings?limit=10" \
  -H "Authorization: Bearer $AICOO_API_KEY" | jq .

Claude Code Automation

Use /loop or /routine directly.

/loop example

/loop 24h generate my daily brief from /v1/briefing, then generate /v1/briefing/strategies and /v1/briefing/matrix. Return a concise executive summary with top 3 actions.

/routine example

/routine daily-brief every weekday at 08:30: run /v1/briefing + /v1/briefing/strategies + /v1/briefing/matrix and post concise output.

OpenClaw Automation (CRON)

Use the provided script:

# Every weekday at 08:30
30 8 * * 1-5 /path/to/aicoo-skills/scripts/daily-brief-cron.sh >> /tmp/aicoo-daily-brief.log 2>&1

Optional envs:

  • PULSE_BRIEF_TIME_DURATION (default: last 24 hours)
  • PULSE_BRIEF_SAVE_NOTE=1 (save output to /os/notes)
  • PULSE_BRIEF_NOTE_TITLE_PREFIX (default: Daily Brief)

Output Contract

When you report to user, include:

  1. Today's focus (2-3 bullets)
  2. Top 3 strategic priorities
  3. Eisenhower Q1/Q2 highlights
  4. Suggested next actions

Keep concise and action-oriented.

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.