メニュー
Create and configure custom dashboards with widgets. Add task summaries, burndown charts, project progress, upcoming deadlines, and metric cards. Group tasks by status, project, or priority. Set default dashboards.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Optimal Engine is a self-hosted second brain and operating engine for human and AI workspaces. It preserves messy sources, organizes them into workspaces and Nodes, classifies Signals, turns extracted assertions into reviewable Claims, promotes accepted Claims into source-backed Facts and Memory Objects, assembles governed Context Packages, and projects the same state into markdown, wiki/API views, CLIs, MCP tools, and app surfaces. Use this skill when building or using persistent organizational memory, workspace topology, source-backed retrieval, agent work loops, multimodal intake, packages/exports, or governed tool/model execution. Architectural commitments: source-first evidence, workspace/Node scope, Signal = Mode + Genre + Type + Format + Structure, Claim -> Fact gate, Memory Core lineage, Context Packages, Active Memory Pools, Skill Packages, and projection surfaces over canonical runtime state. Self-hosted, MIT, runs locally first.
Analyze productivity trends, explain metrics, and identify bottlenecks. Answer questions like "why are tasks overdue" or "how am I doing this week". Provide actionable insights based on workspace data.
Configure notification preferences, set quiet hours, and manage alerts. Control how and when you receive notifications for tasks, mentions, deadlines, and team activity.
Create and manage projects. Add team members, set deadlines, track status, and organize work. Configure project settings, templates, and workflows.
Create, update, complete, and delete tasks. Filter by status, project, priority, or due date. Bulk operations for efficiency. Assign tasks to team members and manage task dependencies.
| name | dashboard-management |
| description | Create and configure custom dashboards with widgets. Add task summaries, burndown charts, project progress, upcoming deadlines, and metric cards. Group tasks by status, project, or priority. Set default dashboards. |
| metadata | {"version":"1.0.0","author":"businessos","tools_used":["configure_dashboard"],"depends_on":[],"context_hints":["User's current dashboard layout","User's workspace membership","Available projects for filtering"],"telemetry":{"track_events":["widget_added","widget_removed","dashboard_created","error_recovered"]}} |
Activate when user wants to:
Keywords: dashboard, widget, add, show, display, view, chart, summary, home, burndown, metrics, deadlines
Do NOT use when:
task-managementanalytics-insightsnotification-managementName: configure_dashboard
Actions:
| Action | Purpose | Required Params |
|---|---|---|
list_dashboards | Get user's dashboards | none |
list_widgets | Get available widget types | none |
get_dashboard | Get specific dashboard layout | dashboard_id or dashboard_name (optional, uses default) |
create_dashboard | Create new dashboard | name |
add_widget | Add single widget | widget_type |
add_widgets | Add multiple widgets | widgets[] |
remove_widget | Remove a widget | widget_id (or infer from context) |
update_widget | Modify widget config | widget_id, config |
set_default | Set default dashboard | dashboard_id or dashboard_name |
| User Says | Action | Key Params |
|---|---|---|
| "Show me my tasks" | add_widget | widget_type: task_summary |
| "Tasks grouped by project" | add_widget | widget_type: task_summary, config: {group_by: "project"} |
| "Tasks grouped by priority" | add_widget | widget_type: task_summary, config: {group_by: "priority"} |
| "What's due this week" | add_widget | widget_type: upcoming_deadlines, config: {days_ahead: 7} |
| "Show deadlines for next 2 weeks" | add_widget | widget_type: upcoming_deadlines, config: {days_ahead: 14} |
| "Add a burndown chart" | add_widget | widget_type: task_burndown |
| "Show project progress" | add_widget | widget_type: project_progress |
| "Create a new dashboard" | create_dashboard | name: (ask user or infer) |
| "Create a sales dashboard" | create_dashboard | name: "Sales Dashboard" |
| "Add tasks and deadlines" | add_widgets | widgets: [{type: task_summary}, {type: upcoming_deadlines}] |
| "Remove the burndown chart" | remove_widget | identify by type |
| "What dashboards do I have" | list_dashboards | none |
| "What widgets can I add" | list_widgets | none |
| "Make this my default" | set_default | current dashboard context |
| Type | Best For | Common Config |
|---|---|---|
task_summary | Workload overview | group_by: status/project/priority |
task_list | Detailed task view | limit, filter, show_completed |
upcoming_deadlines | Planning ahead | days_ahead: 7, 14, 30 |
task_burndown | Sprint tracking | days: 30, 90; project_id |
project_progress | Project health | project_id (optional) |
metric_card | Single KPI | metric: tasks_due_today, etc. |
recent_activity | Activity feed | limit: 10, 20, 50 |
workload_heatmap | Capacity planning | date_range: month, quarter |
client_overview | Sales pipeline | pipeline_stage |
notes_pinned | Quick reference | limit |
quick_actions | Shortcuts | actions[] |
agent_shortcuts | AI commands | shortcuts[] |
User: "I want to see my tasks on the dashboard"
Tool Call:
{
"action": "add_widget",
"widget_type": "task_summary"
}
Response: "Added a task summary widget to your dashboard. It shows your tasks grouped by status."
User: "Show me tasks grouped by project"
Tool Call:
{
"action": "add_widget",
"widget_type": "task_summary",
"config": {
"group_by": "project"
}
}
Response: "Added a task summary grouped by project to your dashboard."
User: "Set up my dashboard with tasks, deadlines, and a burndown chart"
Tool Call:
{
"action": "add_widgets",
"widgets": [
{"type": "task_summary", "config": {"group_by": "status"}},
{"type": "upcoming_deadlines", "config": {"days_ahead": 14}},
{"type": "task_burndown", "config": {"days": 30}}
]
}
Response: "Added 3 widgets to your dashboard: task summary, 2-week deadlines, and 30-day burndown chart."
User: "Create a project dashboard for Alpha with progress and tasks"
Tool Call:
{
"action": "create_dashboard",
"name": "Alpha Project",
"widgets": [
{"type": "project_progress", "config": {"project_id": "alpha-uuid"}},
{"type": "task_list", "config": {"project_id": "alpha-uuid", "limit": 20}}
]
}
Response: "Created 'Alpha Project' dashboard with progress tracking and task list."
User: "Remove the deadlines widget"
Approach:
upcoming_deadlines widget exists → remove itTool Call (if unambiguous):
{
"action": "remove_widget",
"widget_id": "widget-uuid-here"
}
Response: "Removed the upcoming deadlines widget from your dashboard."
Tool Returns:
{
"success": false,
"error": "widget_type_not_found",
"requested": "team_capacity",
"available_alternatives": ["workload_heatmap", "task_summary"]
}
Say: "Team capacity widget isn't available yet. I can add a workload heatmap that shows task density over time, or a task summary. Which would you prefer?"
Tool Returns:
{
"success": false,
"error": "dashboard_full",
"current_count": 12,
"max_count": 12
}
Say: "Your dashboard already has 12 widgets (the maximum). I can remove one to make room, or create a new dashboard. What would you prefer?"
When user says "remove the task widget" but multiple task widgets exist:
Say: "I found several task widgets on your dashboard:
Which one would you like to remove?"
If you need more details, these references are available:
WIDGETS.md - Full widget catalog with visuals and all config optionsCONFIGS.md - Detailed configuration parameter documentationERRORS.md - Complete error codes and recovery strategiesEXAMPLES.md - 20+ example conversationsRequest a reference when: