agentleFS
Sign inStart free
AbdulSamad94AbdulSamad94/Personal-AI-Employee/.agents/skills/dashboard-update/SKILL.md

dashboard-update

Skill8 starsChanged 4 months agoMITView on GitHub

Update the AI Employee Dashboard with current status, recent activity, and business metrics. Use after processing any tasks, at the end of every reasoning loop, when the user says "update dashboard", "show status", "what's happening", or on every scheduled run.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 5 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

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

    Keep vault/Dashboard.md accurate and up to date so the business owner can see exactly what is happening at a glance at any time.

    line 12
  2. Very specific:

    Read vault/Business_Goals.md for revenue targets.

    line 25
  3. Very specific:

    Read most recent log file in vault/Logs/ for recent actions.

    line 26
  4. Distinctive:

    After processing any task from Needs_Action/

    line 128
  5. Distinctive:

    After creating any approval request

    line 129
  6. Distinctive:

    After any approval is executed

    line 130
  7. Distinctive:

    When explicitly asked by the human

    line 132
  8. Distinctive:

    Every 30 minutes during active sessions

    line 133

≈ “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

Skill: Dashboard Update

Purpose

Keep vault/Dashboard.md accurate and up to date so the business owner can see exactly what is happening at a glance at any time.

Step 1 — Gather Current State

Count files in each folder:

  • vault/Needs_Action/ — count .md files
  • vault/Pending_Approval/ — count .md files
  • vault/Approved/ — count .md files
  • vault/Plans/ — count in_progress plans
  • vault/Done/ — count files created today

Read vault/Business_Goals.md for revenue targets. Read most recent log file in vault/Logs/ for recent actions.

Step 2 — Write Dashboard

Overwrite vault/Dashboard.md with this exact format:

🤖 AI Employee Dashboard

Last Updated: [ISO timestamp] Status: 🟢 Active

📊 Current Status

MetricCount
🔴 Active Tasks (Needs Action)[count]
⏳ Pending Approval[count]
✅ Completed Today[count]
📋 Plans In Progress[count]

🚨 Urgent Items

[List any URGENT tasks from Needs_Action/ here] [Write "None" if no urgent items]

⚠️ Payments Pending

[List any payment approval requests here] [Write "None" if no payments pending]

📬 Recent Activity

[List last 10 actions from today's log file, newest first] Format each line as:

  • [HH:MM] [action type] — [brief description]

Example:

  • 14:30 Email Draft — Reply to Client A re: Invoice #123
  • 14:15 LinkedIn Post — Drafted achievement post for approval
  • 14:00 Task Processed — FILE_report.pdf moved to Done/

💰 Business Metrics

Monthly Revenue Target: $[target from Business_Goals.md] Current MTD: $[amount if known, otherwise "Not tracked yet"] Active Projects: [list project names from Business_Goals.md]

📅 Upcoming Deadlines

[List any deadlines found in Business_Goals.md or recent tasks] [Write "None identified" if none found]

🔄 System Health

ComponentStatus
Gmail Watcher🟢 Running
WhatsApp Watcher🔴 Not built yet
LinkedIn Watcher🟢 Running
File System Watcher🔴 Not built yet
Email MCP Server🔴 Not built yet
Approval Watcher🔴 Not built yet

📝 Notes for Human

[Any important notes, escalations, or things needing attention] [Write "Nothing to flag" if all is normal]

Generated by AI Employee v0.1

Step 3 — Log the Update

Append to vault/Logs/[YYYY-MM-DD].md:

[timestamp] | dashboard_update | vault/Dashboard.md | success

When to Auto-Update Dashboard

Update Dashboard.md automatically:

  • After processing any task from Needs_Action/
  • After creating any approval request
  • After any approval is executed
  • At the start of every reasoning loop run
  • When explicitly asked by the human
  • Every 30 minutes during active sessions

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