update-dashboard
Skill109 starsChanged 40 days agoMITView on GitHub
Update dashboard.yaml with current knowledge base metrics from analysis report
3 other projects use a version of this.
Adopted by
Most recently taken up by
- muhammad-anas35/AI-Employee-Gold-tiertheir own version, first seen Sep 25, 2026
- muhammad-anas35/Nexus-ai-employeetheir own version, first seen Sep 25, 2026
- syeda-hoorain-ali/personal-ai-employee-hackathontheir own version, first seen Feb 23, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- muhammad-anas35/AI-Employee-Gold-tier★ 1same name
- muhammad-anas35/Nexus-ai-employee★ 1same name
- syeda-hoorain-ali/personal-ai-employee-hackathon★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository61 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- adviseSkill
- ai-crystallizeSkill
- analyze-kbSkill
- auto-discoverySkill
- benchmark-memorySkill
- brain-mergeSkill
- changelog-protocolSkill
- coherence-sweepSkill
- compute-lifecycleSkill
- create-articleSkill
- create-explanatory-imageSkill
- decideSkill
- deep-researchSkill
- detect-tensionsSkill
- dialecticSkill
- domain-watchSkill
- elicitation-techniquesSkill
- epistemic-classificationSkill
- epub-chapter-extractorSkill
- extract-document-insightsSkill
- extract-insightsSkill
- find-connectionsSkill
- first-runSkill
- get-perspective-onSkill
- get-youtube-transcriptSkill
- git-commit-pushSkill
- graduate-insightsSkill
- incubation-loopSkill
- ingest-sourceSkill
- insight-capture-formatSkill
- insight-interviewSkill
- integrate-recent-notesSkill
- learn-new-thingsSkill
- manage-reference-dataSkill
- manage-thinking-topicsSkill
- manage-watching-domainsSkill
- multi-format-book-extractorSkill
- nano-banana-image-generatorSkill
- propagate-changeSkill
- quick-searchSkill
- reasoning-checksSkill
- recallSkill
- ref-auditSkill
- ref-bridgeSkill
- ref-ingestSkill
- ref-querySkill
- ref-reconcileSkill
- ref-refreshSkill
- refresh-indexSkill
- ref-supersedeSkill
- scheduled-runSkill
- scope-mountSkill
- search-vaultSkill
- self-diagnosticSkill
- start-hereSkill
- synthesize-insightsSkill
- talkSkill
- test-memory-systemSkill
- think-about-itSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 201
Use the following extraction logic:
- Distinctive: line 230
All numeric values are integers (no commas in YAML)
“Common” is measured: kept by at least 6 in 10 of the 3 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.
Files
Update Dashboard
Refresh the Trinity dashboard with current knowledge base metrics extracted from the analysis report.
Output Location
Write to: /home/developer/dashboard.yaml
STEP 1: Read Analysis Report
Read knowledge-base-analysis.md from the project rootExtract the following metrics using regex or line parsing:
Core Metrics (from header section, lines 4-5)
- Analysis Date: Pattern
**Analysis Date:** YYYY-MM-DD - Total Notes: Pattern
**Total Notes:** X,XXX - Blocks: Pattern
**Blocks:** XX,XXX - Permanent Notes: Pattern
**Permanent Notes:** XXX - AI Insights: Pattern
**AI Insights:** XXX - Document Insights: Pattern
**Document Insights:** XXX
From Summary Table (lines 14-25)
- Document Sessions: From table row
- MOCs: From table row
- Changelogs: From table row
- Source notes: From table row
- Output pieces: From table row
- Change values: The "+XX" column for trends
From Domain Distribution (lines 389-398)
- AI/Agents: XX%
- Neuroscience/Dopamine: XX%
- Buddhism/Consciousness: XX%
- Decision-Making/Biases: XX%
- Identity/Belief Systems: XX%
- Business/Content Marketing: XX%
- Flow/Performance: XX%
From Statistics (lines 383-385)
- Original frameworks: Count
STEP 2: Build Dashboard YAML
Construct the dashboard with gathered values:
title: "Cornelius Knowledge Base"
refresh: 300
sections:
- title: "Knowledge Base Overview"
layout: grid
columns: 3
widgets:
- type: metric
label: "Total Notes"
value: {total_notes}
trend: up
trend_value: "{notes_change}"
description: "All notes in vault"
- type: metric
label: "Total Blocks"
value: {total_blocks}
trend: up
trend_value: "{blocks_change}"
description: "Content blocks indexed"
- type: text
content: "Last Analysis: {analysis_date}"
size: small
color: gray
- title: "Note Categories"
layout: grid
columns: 3
widgets:
- type: metric
label: "Permanent Notes"
value: {permanent_notes}
trend: up
trend_value: "{permanent_change}"
description: "Atomic insights"
- type: metric
label: "AI Insights"
value: {ai_insights}
trend: up
trend_value: "{ai_change}"
description: "AI-extracted notes"
- type: metric
label: "Document Insights"
value: {document_insights}
trend: up
trend_value: "{doc_change}"
description: "Research extracts"
- type: metric
label: "MOCs"
value: {mocs}
trend: up
trend_value: "{mocs_change}"
description: "Navigation hubs"
- type: metric
label: "Source Notes"
value: {source_notes}
description: "Books & articles"
- type: metric
label: "Output Pieces"
value: {output_pieces}
trend: up
trend_value: "{output_change}"
description: "Published content"
- title: "Domain Distribution"
layout: grid
columns: 2
widgets:
- type: progress
label: "AI/Agents"
value: {ai_percent}
color: blue
- type: progress
label: "Neuroscience/Dopamine"
value: {neuro_percent}
color: purple
- type: progress
label: "Buddhism/Consciousness"
value: {buddhism_percent}
color: green
- type: progress
label: "Decision-Making"
value: {decision_percent}
color: orange
- type: progress
label: "Identity/Belief"
value: {identity_percent}
color: yellow
- type: progress
label: "Business/Marketing"
value: {business_percent}
color: gray
- title: "Growth & Activity"
layout: grid
columns: 4
widgets:
- type: metric
label: "Document Sessions"
value: {doc_sessions}
description: "Research sessions"
- type: metric
label: "Original Frameworks"
value: {frameworks}
description: "Custom models"
- type: metric
label: "Changelogs"
value: {changelogs}
description: "Activity records"
- type: text
content: "Phase: Technical Implementation"
size: small
color: blue
- title: "Seven Thematic Hubs"
layout: list
widgets:
- type: list
title: "Primary Knowledge Domains"
items:
- "Consciousness & Self (Buddhism-Neuroscience Bridge)"
- "Dopamine & Motivation (Master Hub)"
- "Decision-Making & Cognitive Biases"
- "Identity & Belief Systems"
- "AI Agents & Digital Intelligence (Largest - 546 notes)"
- "Flow States & Peak Performance"
- "Business & Content Marketing Psychology"
style: bullet
max_items: 7STEP 3: Parse Metrics from Report
Use the following extraction logic:
For header metrics (line 5):
Pattern: **Total Notes:** (\d+,?\d*) | **Blocks:** (\d+,?\d*) | **Permanent Notes:** (\d+) | **AI Insights:** (\d+) | **Document Insights:** (\d+)For table metrics (lines 14-25):
Look for lines with | Total notes | X,XXX | +XXX |
Extract value and change columnsFor domain percentages (lines 389-398):
Pattern: AI/Agents.*:\s+(\d+)%
Pattern: Neuroscience.*:\s+(\d+)%
etc.STEP 4: Write Dashboard
Write the constructed YAML to /home/developer/dashboard.yamlEnsure:
- All numeric values are integers (no commas in YAML)
- Percentages are integers without % symbol
- Trends use "up" or "down" based on change values
- Date is in YYYY-MM-DD format
STEP 5: Confirm Update
Report what was updated:
Dashboard updated at {current_timestamp}
Metrics refreshed:
- Total Notes: {value} ({change})
- Permanent Notes: {value} ({change})
- AI Insights: {value} ({change})
- Document Insights: {value} ({change})
- Domain distribution: AI {X}%, Neuro {X}%, Buddhism {X}%...
Dashboard written to: /home/developer/dashboard.yamlScheduling
This skill can be scheduled via /trinity-schedules:
# Daily update (recommended)
/trinity-schedules add update-dashboard --cron "0 9 * * *"
# After each /analyze-kb run
Run manually: /update-dashboardNote: Dashboard data is only as fresh as the last /analyze-kb run. Consider running analyze-kb before update-dashboard for accurate metrics.
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
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.

