← Back to Skills Marketplace
philippeh5

Dashboard Manager2

by Philippeh5 · GitHub ↗ · v1.0.0
cross-platform ⚠ suspicious
730
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install dashboard-manager2
Description
Gère en temps réel la lecture, mise à jour et synchronisation du fichier data.json du dashboard Jarvis, incluant notes, tâches, logs et statistiques.
README (SKILL.md)

Dashboard Manager Skill

Description

Gère les interactions avec le dashboard Jarvis. Ce skill permet de lire, mettre à jour et synchroniser le fichier data.json en temps réel.

Fonctionnalités

  • Lecture/Sauvegarde : Accès au fichier data.json
  • Gestion des notes : Récupération des notes pending et marquage comme processed
  • Logging : Ajout d'entrées dans l'historique
  • Mise à jour du système : Statut, heartbeat, modèle actif
  • Statistiques : Compteurs de tokens et coûts
  • Gestion des tâches : Ajout et mise à jour
  • Sub-agents : Gestion des agents actifs

Configuration

Chemin du fichier

const DATA_FILE_PATH = 'D:\\Projets\\ClaudBot\\Jarvis_Dashboard\\data.json';

Permissions

  • Lecture/Écriture : Accès au fichier data.json
  • Système : Mise à jour du statut et heartbeat
  • Logging : Ajout d'entrées dans l'historique

API

Fonctions principales

// Chargement de la base de données
await loadDatabase();

// Sauvegarde de la base de données
await saveDatabase(db);

// Récupération des notes en attente
const pendingNotes = await getPendingNotes();

// Marquage d'une note comme traitée
await processNote(noteId);

// Ajout d'un log
await addLog('Action effectuée');

// Mise à jour du statut du système
await updateSystemStatus('idle', 'Claude-3-Opus');

// Mise à jour des statistiques
await updateStats(1500, 2800, 0.52);

// Ajout/mise à jour d'une tâche
await updateTask(1, { status: 'done' });

// Gestion des sub-agents
await addSubAgent('dashboard_agent', 'Monitoring dashboard');
await removeSubAgent('dashboard_agent');

Initialisation

const dashboardSkill = require('./skills/dashboard-manager');
const success = await dashboardSkill.init();
if (success) {
    console.log('🚀 Dashboard Manager initialisé');
}

Permissions requises

  • Accès fichier : D:\Projets\ClaudBot\Jarvis_Dashboard\data.json
  • Écriture système : Mise à jour du statut et heartbeat
  • Logging : Ajout d'entrées dans l'historique

Utilisation

Ce skill est conçu pour fonctionner en arrière-plan et maintenir la synchronisation entre Jarvis et le dashboard en temps réel.

Boucle de fonctionnement (The Loop)

  1. INPUT : Consulte quick_notes et traite les notes pending
  2. OUTPUT : Met à jour data.json avec les changements
  3. Auto-sync : Heartbeat toutes les 2 secondes
  4. Silent mode : Fonctionne sans intervention conversationnelle

Exemple d'utilisation

// Dans une réponse conversationnelle
await updateStats(estimatedInputTokens, estimatedOutputTokens, estimatedCost);
await addLog('Réponse à la question sur les agents');
await updateSystemStatus('idle');

Installation

  1. Copier le dossier dashboard-manager dans le répertoire des skills
  2. Vérifier le chemin du fichier data.json
  3. Activer le skill dans la configuration
  4. Le skill s'initialisera automatiquement

Dépannage

Problèmes courants

  • Fichier introuvable : Vérifier le chemin DATA_FILE_PATH
  • Permissions refusées : Vérifier les droits d'accès au fichier
  • JSON invalide : Vérifier la syntaxe du fichier data.json

Logs

Les logs sont ajoutés automatiquement dans la section logs du fichier data.json pour le suivi des actions.

Sécurité

  • Accès limité : Seul le fichier data.json est accessible
  • Écriture contrôlée : Les mises à jour sont validées
  • Logs d'audit : Toutes les actions sont enregistrées

Compatibilité

Ce skill est compatible avec OpenClaw et fonctionne avec n'importe quelle instance de Jarvis utilisant le dashboard V2 Ultimate.

Usage Guidance
Do not install immediately — ask the author to explain the mismatches before granting permissions. Specifically: - Confirm whether the skill is supposed to access data.json directly or proxy everything through a local HTTP service. The code suggests the latter; SKILL.md and skill.json suggest the former. - If the skill truly needs file access, require a clear justification and consider limiting the allowed path (or providing a copy of the file) rather than granting write access to your real dashboard file. - Verify the local HTTP server the skill talks to (http://localhost:8009): inspect its code, endpoints, and whether it could exfiltrate data or perform unexpected actions. - Ask the developer to remove unnecessary file permissions and unused dependencies, or update the code and documentation so they match (either implement file I/O as documented or remove file-related claims). - If you lack the ability to audit the local server, run the skill in an isolated environment (VM/container) and monitor network and file activity before enabling it in production. These inconsistencies look like sloppy packaging or version drift rather than obviously malicious behavior, but they create risk because you might grant privileges that the code doesn't need or that could be abused by a separate local service the skill depends on.
Capability Analysis
Type: OpenClaw Skill Name: dashboard-manager2 Version: 1.0.0 The skill is suspicious due to a critical vulnerability in `index.js` where user-controlled inputs (e.g., `noteId`, `docId`, `ruleId`) are directly interpolated into URL paths for the local `http://localhost:8009` API without apparent sanitization. This creates a high risk of injection attacks (e.g., path traversal, SQL injection) against the local backend server if an attacker can control these inputs. Additionally, there's a significant discrepancy between the `skill.json` and `SKILL.md` which declare direct file access permissions for `D:\Projets\ClaudBot\Jarvis_Dashboard\data.json` and list `fs`/`path` dependencies, while the `index.js` code exclusively communicates with a local HTTP API and performs no direct file operations, raising concerns about the true scope and intent of the skill's capabilities.
Capability Assessment
Purpose & Capability
SKILL.md and skill.json state the skill reads/writes D:\Projets\ClaudBot\Jarvis_Dashboard\data.json and requires file permissions, but index.js does not read or write that file—instead it issues HTTP calls to a local server at http://localhost:8009. Declared node dependencies ('fs' and 'path' with odd versions) are unnecessary for the provided code. The requested permissions and capabilities (file access, system writes) are disproportionate to what the code actually does.
Instruction Scope
The runtime instructions describe a background loop, auto-sync heartbeat every 2s, and direct file manipulation of data.json; the implementation exports only a set of API wrapper functions and contains no loop, no file I/O, and no heartbeat logic. SKILL.md therefore instructs operators to grant file permissions and to verify a specific local path that the code itself never touches—this mismatch expands the skill's effective scope if users follow the doc.
Install Mechanism
No install spec is provided (instruction-only with a code file). That minimizes disk-write risk from an installer; the only files are the skill bundle itself. No external downloads or extract steps are present.
Credentials
The skill requests file read/write permission to a specific Windows path in skill.json and SKILL.md but the code performs network calls to localhost instead and doesn't use environment variables or credentials. This asks for elevated local file access without code justification. The declared dependencies ('fs','path') and their placeholder versions are odd but not directly harmful—still they appear unnecessary.
Persistence & Privilege
The skill is not always-enabled and does not request system-wide or other-skills configuration changes. It exports functions for on-demand use; nothing in the bundle shows it self-enabling or persisting beyond normal skill files.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install dashboard-manager2
  3. After installation, invoke the skill by name or use /dashboard-manager2
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
- Added initial configuration file: `skill.yaml` - Removed test file: `test.js` - No changes to main documentation or features - First public version of the Dashboard Manager skill
Metadata
Slug dashboard-manager2
Version 1.0.0
License
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is Dashboard Manager2?

Gère en temps réel la lecture, mise à jour et synchronisation du fichier data.json du dashboard Jarvis, incluant notes, tâches, logs et statistiques. It is an AI Agent Skill for Claude Code / OpenClaw, with 730 downloads so far.

How do I install Dashboard Manager2?

Run "/install dashboard-manager2" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Dashboard Manager2 free?

Yes, Dashboard Manager2 is completely free (open-source). You can download, install and use it at no cost.

Which platforms does Dashboard Manager2 support?

Dashboard Manager2 is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Dashboard Manager2?

It is built and maintained by Philippeh5 (@philippeh5); the current version is v1.0.0.

💬 Comments