ccboard

Comprehensive TUI/Web dashboard for Claude Code monitoring

Install with Tessl CLI

npx tessl i github:FlorianBruniaux/claude-code-ultimate-guide --skill ccboard

What are skills?

2.61x

Quality

49%

Does it follow best practices?

Impact

94%

2.61x

Average score across 3 eval scenarios

Optimize this skill with Tessl

npx tessl skill review --optimize ./examples/skills/ccboard/SKILL.md

SKILL.md

Review

Evals

Quality

Discovery

22%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This description is too brief and vague to effectively guide skill selection. It lacks concrete actions, explicit trigger conditions, and natural user language. The description reads more like a product tagline than functional guidance for when Claude should select this skill.

Suggestions

Add a 'Use when...' clause specifying trigger scenarios like 'Use when the user wants to track Claude Code sessions, view usage statistics, or monitor real-time activity'

Replace 'comprehensive monitoring' with specific actions like 'Track session history, view token usage, display real-time activity logs, analyze conversation metrics'

Include natural user terms such as 'usage', 'stats', 'activity', 'sessions', 'track', 'view' that users would actually say when needing this functionality

Dimension	Reasoning	Score
Specificity	The description uses vague language like 'comprehensive' and 'monitoring' without specifying concrete actions. It doesn't explain what monitoring entails or what specific capabilities the dashboard provides.	1 / 3
Completeness	Only partially addresses 'what' (a dashboard for monitoring) and completely lacks any 'when' guidance. No 'Use when...' clause or explicit trigger conditions are provided.	1 / 3
Trigger Term Quality	Contains some relevant keywords ('TUI', 'Web dashboard', 'Claude Code', 'monitoring') but these are somewhat technical. Missing natural user terms like 'track sessions', 'view activity', 'usage stats', or 'real-time'.	2 / 3
Distinctiveness Conflict Risk	'Claude Code monitoring' provides some specificity, but 'dashboard' and 'monitoring' are generic enough to potentially conflict with other observability or analytics skills.	2 / 3
	Total	6 / 12 Passed

Implementation

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill provides excellent actionable guidance with clear commands, keyboard shortcuts, and troubleshooting steps. However, it's overly verbose for a skill file - including architecture details, credits, license info, and future roadmap that don't help Claude use the tool. The content would benefit from splitting reference material into separate files.

Suggestions

Remove or relocate non-actionable sections (Credits, License, Contributing, Architecture, Limitations/Roadmap) to a separate REFERENCE.md file

Condense the 8 Interactive Tabs section to a brief overview with a link to detailed documentation

Move the detailed command-line options and environment variables to an ADVANCED.md file, keeping only the most common usage in the main skill

Dimension	Reasoning	Score
Conciseness	The skill is comprehensive but includes significant verbosity - detailed feature lists, architecture explanations, and roadmap information that Claude doesn't need. The credits, license, and contributing sections add little actionable value.	2 / 3
Actionability	Provides concrete, executable commands throughout - installation via cargo, specific keyboard shortcuts, CLI options with examples, and troubleshooting commands. All guidance is copy-paste ready.	3 / 3
Workflow Clarity	Clear workflows for common tasks like daily monitoring, MCP troubleshooting, and session analysis. Each workflow has numbered steps with specific commands and expected outcomes.	3 / 3
Progressive Disclosure	Content is well-organized with clear sections, but everything is in one monolithic file. The detailed feature descriptions, architecture, and advanced usage could be split into separate reference files to keep the main skill leaner.	2 / 3
	Total	10 / 12 Passed

Validation

90%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Reviewed: about 7 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.