SKILLEMALL.ai
GitHub ↗ RU Sign in

AC mission-control

Build a personal dashboard for OpenClaw with task management, memory browser, calendar, team tracking, and GitHub trends. Use when the user wants to create a web-based mission control dashboard for their OpenClaw instance, track tasks, view memories, manage calendar events, or build a custom dashboard interface.

modbender/skill-library-mcp Agent Skills author: modbender MIT 1 file body ≈ 3 212 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Build a personal dashboard for OpenClaw with task management, memory browser, calendar, team tracking, and GitHub trends.

As a process C 62/100 · Has gaps — weak spots: result and completion, consistency, running it twice

GeneratorGitHubData and analyticsPersonal productivitytype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
A
93/100
safety, quality, tests
Safety 60%
100
Quality 40%
82
Run on models
none yet
Process rating
C
62/100
Has gaps
Result and completion w 14
0
Progress reporting w 2
0
Running it twice w 4
30
the three weakest of ten parameters · all ten

How to improve

    For the model run — optional
    • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
    • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

    Guard findings · 0

    ✓ No critical or high findings

    Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 62/100

    • 0Result and completion. Does not say what the result is
    • 0Progress reporting. Says nothing while it works
    • 30Running it twice. 11 mutating operations with no state check
    • 40Consistency. Frontmatter name (mission-control) differs from the folder (mission-control-builder)
    • 50Failures and branches. 0 branches, has a failure section
    • 70When it triggers. States when to use, but not when not to
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 85Steps. 19 steps, 1 vague phrases
    • 100Tools and files. No external tools needed
    • 100Execution cost. Instruction body is 3212 tokens
    • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
    • low 10 top-level sections: this looks like several domains in one skill

    Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

    Quality signals

    • +5Description has no quoted example phrases that should trigger the skill
    • +4Description does not say when NOT to use the skill (false activations)
    • +3Output format is not stated: the model decides each time
    • -2localhost URLs: will not work for another user
    • +1No license
    • +2Single-language instructions
    • +3Description length 313: enough signal without eating the budget
    • +4Structure: 24 headings
    • +3Step-by-step instructions: 19 items
    • +4Has examples (14 code blocks)

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 82.